search

w3c / wcag21

Repository used during WCAG 2.1 development. New issues, Technique ideas, and comments should be filed at the WCAG repository at https://github.com/w3c/wcag.
https://w3c.github.io/wcag/21/guidelines/
Other
142 stars 55 forks source link

Understanding Non-Text contrast needs update to reflect consensus. #946

Closed DavidMacDonald closed 6 years ago

DavidMacDonald commented 6 years ago

Currently there are a number of things in the Understanding of Non-Text contrast that need updating: There are 2 paragraphs talking about the need to identify hit area, and our current consensus is that we need to identify the control, not the hit area. Here's the current text:

For active controls on the page, such as buttons and form fields, any visual boundary that indicates the component's hit area (the region where a pointer can activate the control) must have sufficient contrast with the adjacent background ... This success criteria does not require that controls have a visual boundary indicating the hit area, but that if there is an indicator then it has sufficient contrast. If only the text (or icon) is visible and there is no visual indication of the hit area, then there is no contrast requirement beyond the text contrast (1.4.3 Contrast (Minimum)) or icon contrast covered by the Graphical Objects portion of this Success Criteria. Note that for people with cognitive disabilities it is recommended to delineate the boundary of controls to aid in the recognition of controls and therefore the completion of activities.

Also there is an example on an input with just an underline, but the graphic has all 4 sides with borders.

michael-n-cooper commented 6 years ago

This issue was moved to w3c/wcag#406