Skip to content
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.

Test for WCAG success criterion 1.4.3: Contrast #186

Open
1 of 5 tasks
hannolans opened this issue Mar 16, 2014 · 2 comments
Open
1 of 5 tasks

Test for WCAG success criterion 1.4.3: Contrast #186

hannolans opened this issue Mar 16, 2014 · 2 comments

Comments

@hannolans
Copy link
Contributor

http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html
The visual presentation of text and images of text has a contrast ratio of at least 4.5:1

Applicability

Always

Selector

Text parts:

  • Text is less than 18 point if not bold and less than 14 point if bold (Situation A)
  • Text is at least 18 point if not bold and at least 14 point if bold (Situation B)

No minimum contrast requirement for text or images of text:

  • that are part of an inactive user interface component
  • that are pure decoration
  • that are not visible to anyone,
  • that are part of a picture that contains significant other visual content
  • that is part of a logo or brand name

Failures

Techniques

Relationship between techniques and Failures

  • G18 and G145 are exactly the same, only the ratio differs
  • G18 is also used on AAA level, but then for situation B.
  • F24 is counterpart for G148
  • F83 is part of the check in G18+G145, but as images can't change their contrast with a control or backgorund css it's a real failure and G174 or G148 can't help that.
  • G18 + G145 is the most common technology, but if they fail, we can't fail this success criterion if we don't check for G148 (easy) or G174 (difficult as we should detect a control)
@attiks
Copy link
Contributor

attiks commented Apr 18, 2014

PR created for checking font size and weight to determine ratio: #216

@jessebeach
Copy link
Member

Working in branch issue-129

@jessebeach jessebeach self-assigned this May 27, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants