| Provision(s) from §508 1194 | WCAG 2.0 LC Success Criteria |
|---|---|
| 1194.21(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. | 2.1.1 All functionality of the content is operable in a non-time-dependent manner through a keyboard interface, except where the task requires analog, time-dependent input. (Level 1) |
| 1194.21(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. | Not applicable. Web content does not have access to these features of the the operating system. |
| 1194.21(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes. | Indication of input focus is (should be) the responsibility of the browser. |
1194.21(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology. When an image represents a program element, the information conveyed by the image must also be available in text. |
4.1.2 For all user interface components, the name and role can be programmatically determined, states, properties, and values that can be set by the user can be programmatically determined and programmatically set, and notification of changes to these items is available to user agents, including assistive technologies." (Level 1) |
| 1194.21(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. | 3.2.4 Components that have the same functionality within a set of Web units are identified consistently. (Level 2) |
| 1194.21(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. | This is a requirement that text displayed by an application will be available to a screen reader. Sometimes applications wrote their text to the screen with homegrown routines and then that text would be unknown by screen readers which only watched (hooked into) the standard routines. |
| 1194.21(g) Applications shall not override user selected contrast and color selections and other individual display attributes. | Not applicable? Web content does not have access to these features of the the operating system. |
| 1194.21(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | 2.2.3 Content can be paused by the user unless the timing or movement is part of an activity where timing or movement is essential. (Level 2) |
| 1194.21(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | 1.3.2 Any information that is conveyed by color is also visually evident without color. (Level 1) |
| 1194.21(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided. | Not required for conformance to WCAG 2.0. |
| 1194.21(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. | 2.2.2 Content does not blink for more than three seconds, or a method is available to stop all blinking content in the Web unit or authored component. (Level 2) Note: For requirements related to flickering or flashing content, refer to Guideline 2.3 Allow users to avoid content that could cause seizures due to photosensitivity . 2.3.1 Content does not violate the general flash threshold or the red flash threshold. (Level 1) 2.3.2 Web units do not contain any components that flash more than three times in any one second period. (Level 3) |
1194.21(l) When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. |
1.3.1 Information and relationships conveyed through presentation can be programmatically determined, and notification of changes to these is available to user agents, including assistive technologies. (Level 1) 4.1.2 For all user interface components, the name and role can be programmatically determined, states, properties, and values that can be set by the user can be programmatically determined and programmatically set, and notification of changes to these items is available to user agents, including assistive technologies. (Level 1) 1.3.6 Information required to understand and operate content does not rely on shape, size, visual location, or orientation of components. (Level 2) 2.5.1 If an input error is detected, the error is identified and described to the user in text. (Level 1) 3.2.1 When any component receives focus, it does not cause a change of context. (Level 1) 3.2.2 Changing the setting of any form control or field does not automatically cause a change of context (beyond moving to the next field in tab order), unless the authored unit contains instructions before the control that describe the behavior. (Level 1) |