Section WCAG Web Content Accessibility Guidelines
Criteria | Supporting Features | Remarks (e.g., definition, equivalent facilitation, scope of support provided) |
1.1.1 Non-text Content: All non-text content thatis presented to the user has a text alternative that serves theequivalent purpose, except for the situations listed below. (Level A) - Controls, Input: Ifnon-text content is a control or accepts user input, then it has a namethat describes its purpose. (Refer to Guideline 4.1 for additionalrequirements for controls and content that accepts user input.)
- Time-Based Media: Ifnon-text content is time-based media, then text alternatives at leastprovide descriptive identification of the non-text content. (Refer toGuideline 1.2 for additional requirements for media.)
- Test: Ifnon-text content is a test or exercise that would be invalid ifpresented in text, then text alternatives at least provide descriptiveidentification of the non-text content.
- Sensory: Ifnon-text content is primarily intended to create a specific sensoryexperience, then text alternatives at least provide descriptiveidentification of the non-text content.
- CAPTCHA: If the purpose of non-textcontent is to confirm that content is being accessed by a person ratherthan a computer, then text alternatives that identify and describe thepurpose of the non-text content are provided, and alternative forms ofCAPTCHA using output modes for different types of sensory perceptionare provided to accommodate different disabilities.
- Decoration, Formatting, Invisible: Ifnon-text content is pure decoration, is used only for visualformatting, or is not presented to users, then it is implemented in away that it can be ignored by assistive technology.
| Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
- Additional state information is programmatically exposed, such as whether a field is ‘required’.
- Images that convey information have meaningful alternative text.
- The product does not use image maps or CAPTCHAs.
Exceptions: Bug# 17905047: Admin Page – Approval Groups UI - issues found with color contrast, image and link. Bug# 17905083: Admin Page – Evidence Form UI: issues found with form, image and link. Bug# 17904884 & 17905009: Admin Page – Business Parameters UI: issues found with form, color contrast, image and link. Bug# 17905161: Administration Page – Task configuration UI – issues found color, form and table. |
1.2.1 Audio-only and Video-only (Prerecorded): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: (Level A)Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content. Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
| Product has been developed to conform to this standard subject to the remarks on the right. | There is no pre-recorded audio or video in the product |
1.2.2 Captions (Prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearlylabeled as such. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | There is no prerecorded audio in the product, and thus no captions. |
1.2.3 Audio Description or Media Alternative (Prerecorded): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | There is no prerecorded audio or video in the product. |
1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | There is no live audio content in the product |
1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | There is no prerecorded audio content in the product |
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Structure and hierarchy is marked up with Header elements.
- Meaningful labels programmatically associated with form elements.
- Style sheets are used only to change the layout and presentation of the screen
- User interface component labels are associated with the fields they are labeling
- Headings are encoded with HTML heading tags
- List markup is used for marking up lists
- Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
Exceptions: Bug 21294647 - In the Admin section, under Rules, two tables have a blank column. This empty column is missing column headings. BUG 21784789: Tables in product documentation are missing row headers |
1.3.2 Meaningful Sequence:When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - The sequence of elements in the DOM matches a logical reading sequence
|
1.3.3 Sensory Characteristics:Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A) Note:For requirements related to color, refer to Guideline 1.4. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for : - Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound
- Instructions which refer to graphics reference the text alternative of the graphic
|
1.4.1 Use of Color:Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A) Note:This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Information conveyed by color or font styles is available in alternative formats, such as shape and text.
- Information conveyed has a contrast ratio of at least 3:1
|
1.4.2 Audio Control:If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A) Note:Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Moving, blinking, or scrolling information that is designed to last for more than three seconds can be paused.
- Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden.
- Content that automatically updates, or has time limits, can be adjusted by the user.
|
1.4.3 Contrast (Minimum):The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA)
- Large Text:Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
- Incidental:Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
- Logotypes:Text that is part of a logo or brand name has no minimum contrast requirement.
| Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Text and images of text in non-disabled controls have a luminosity contrast ratio of at least 4.5:1.
- Large scale text has a minimum ratio of at least 3:1
Exceptions: Bug 21338128 High contrast :Text boxes are not visible in worklist app. Missing border around several text boxes, so the text boxes do not appear properly in high contrast. The label appears, but you cannot see where to position your mouse. Bug 21338494 High contrast: Issues with button and drop downs in BPM Worklist. Some buttons and dropdowns lose their background color when in high contrast mode. Bug 21309912 Color contrast. Instructional text on one form has 2:80:1 contrast, not the required 4.5:1. |
1.4.4 Resize text:Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Response to the operating system Large Fonts mode
- Text can be resized up to 200% without loss of content or functionality
Exceptions: Bug 21373561 Large font: Issues in worklist app - No scroll bar in several locations when browser font set to 200%
- Not all content visible on tabs when browser font set to 200%
|
1.4.5 Images of Text:If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA)- Customizable:The image of text can be visually customized to the user's requirements;
- Essential:A particular presentation of text is essential to the information being conveyed.
Note:Logotypes (text that is part of a logo or brand name) are considered essential. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential
|
2.1.1 Keyboard:All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A) Note 1:This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not. Note 2:This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
- StickyKeys, FilterKeys and Toggle Keys usage.
Exceptions: -
Bug 21375267 Keyboard: Issues in worklist app. Cannot access lists via keyboard (human task list, several buttons, value text). You can tab into fields, but the values in the list are not read via screen reader. -
Bug 21608954 Multi-key shortcuts do not work in some places, which poses problems for StickyKeys. |
2.1.2 No Keyboard Trap:If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A) Note:Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control
|
2.2.1 Timing Adjustable:For each time limit that is set by the content, at least one of the following is true: (Level A)
- Turn off:The user is allowed to turn off the time limit before encountering it; or
- Adjust:The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
- Extend:The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
- Real-time Exception:The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
- Essential Exception:The time limit is essential and extending it would invalidate the activity; or
- 20 Hour Exception:The time limit is longer than 20 hours.
Note:This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Content that has time limits can be adjusted by the user.
- Users are warned before time expires and can extend the time limit.
|
2.2.2 Pause, Stop, Hide:For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)
- Moving, blinking, scrolling:For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
- Auto-updating:For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Note 1:For requirements related to flickering or flashing content, refer to Guideline 2.3. Note 2:Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. Note 3:Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so. Note 4:An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Content that automatically updates, or time limits, can be adjusted by the user.
- Moving, blinking, or scrolling information that is designed to last for more than three seconds can be paused.
- Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden.
|
2.3.1 Three Flashes or Below Threshold:Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A) Note:Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. | Product has been developed to conform to this standard subject to the remarks on the right. | The product has been tested for: - No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.
- No portion of the screen flashes more than three times in any one second period.
|
2.4.1 Bypass Blocks:A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
|
2.4.2 Page Titled:Web pages have titles that describe topic or purpose. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Pages have a meaningful title specified in the TITLE element
|
2.4.3 Focus Order:If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
|
2.4.4 Link Purpose (In Context):The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - The text of links and their surrounding paragraph, list, table cell (with marked up table headers), or preceding heading is sufficient to describe their purpose
Exceptions: Bug 21293832 Link Errors in Business phrases tab. Link is missing text Bug 21293867 Link Errors in Decision properties tab. Drop-down arrow Link missing descriptive text. Bug 21293767 Link Errors in Rules tab - Drop down arrows are missing link text. |
2.4.5 Multiple Ways:More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for - Pages are fully inter-linked to each other
- Page contains controls that enable reaching all pages
|
2.4.6 Headings and Labels:Headings and labels describe topic or purpose. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Headers describe the topic or purpose of the content below them
- Labels describe the purpose of the associated field
Exceptions: - Bug 21302367 Label is missing in field to paste certificate contents, rules tab, dictionary settings and identity browser
- Bug 21269822 Missing alt text for drop-down arrow and a checkbox on rules tab and report icons on the reports tab.
|
2.4.7 Focus Visible:Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The component was tested for visual indication of cursor position |
3.1.1 Language of Page:The default human language of each Web page can be programmatically determined. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Properly set lang attribute for each page
|
3.1.2 Language of Parts:The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - There are no passages of text in a language other than the main language of the page.
|
3.2.1 On Focus:When any component receives focus, it does not initiate a change of context. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
|
3.2.2 On Input:Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
|
3.2.3 Consistent Navigation:Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Pages that are grouped together into sets with a common navigation mechanism use the navigation in the same way and the elements appear in the same order each time
|
3.2.4 Consistent Identification:Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Images and controls are used and identified consistently throughout the product
|
3.3.1 Error Identification:If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - When input errors are detected, they are described to the user in text, and the item where the error occurred is identified.
|
3.3.2 Labels or Instructions:Labels or instructions are provided when content requires user input. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Labels or instructions are provided when the product requires user input
|
3.3.3 Error Suggestion:If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Error messages offer suggestions to the user for fixing the error, when the system has simple suggestions.
|
3.3.4 Error Prevention (Legal, Financial, Data):For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA)
- Reversible:Submissions are reversible.
- Checked:Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
- Confirmed:A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
| Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for : - Data can be reviewed, corrected, and confirmed by the user before it is finalized
|
4.1.1 Parsing:In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A) Note:Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs
- Pages validate to the HTML specification
|
4.1.2 Name, Role, Value:For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A) Note:This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - FRAMES and iFRAMES are titled with meaningful text
- Controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
- Additional state information is programmatically exposed, such as whether a field is ‘required’.
|
Section 1194.21 Software Applications and Operating Systems
Criteria | Supporting Features | Remarks (e.g., definition, equivalent facilitation, scope of support provided) |
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
- StickyKeys, FilterKeys and Toggle Keys
Exceptions: -
Bug 21375267 Keyboard: Issues in worklist app. Cannot access lists via keyboard (human task list, several buttons, value text). You can tab into fields, but the values in the list are not read via screen reader. -
Bug 21608954 Multi-key shortcuts do not work in some places, which poses problems for StickyKeys |
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for response to the following accessibility features: - Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
- StickyKeys, FilterKeys and ToggleKeys
Exceptions: - Bug 21608954 Multi-key shortcuts do not work in some areas, which poses problems for StickyKeys
- Bug 21375267 Keyboard: Issues in worklist app. Cannot access lists via keyboard (human task list, several buttons, value text). You can tab into fields, but the values in the list are not read via screen reader.
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The component was tested for visual indication of cursor position. - Meaningful labels are programmatically associated with form elements, including synthesized controls.
- Controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
- Additional state information is programmatically exposed, such as whether a field is ‘required’.
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
- Additional state information is programmatically exposed, such as whether a field is ‘required’.
- FRAMES and iFRAMES are titled with meaningful text
- Images that convey information have meaningful alternative text.
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Images that convey information have meaningful alternative text using ALT and if necessary, LONGDESC
- Images that are decorative are marked so as to be ignored by assistive technology, either by using ALT=”” or CSS background images
- Images and controls are used consistently throughout the product.
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Text is supplied through HTML or injected into the browser DOM; the browser is responsible for exposing such content in a way that is usable by assistive technology on the platform.Text content, text input caret location, and text attributes are supported.
|
1194.21(g) Applications shall not override user selected contrast and color selections and other individual display attributes. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Text and images of text in non-disabled controls have a luminosity contrast ratio of at least 4.5:1.
- Large scale text has a minimum ratio of at least 3:1
- Large font setting up to 200% produces no visual errors.
Exceptions: Bug 21338128 High contrast :Text boxes are not visible in worklist app. Missing border around several text boxes, so the text boxes do not appear properly in high contrast. The label appears, but you cannot see where to position your mouse. Bug 21338494 High contrast: Issues with button and drop downs in BPM Worklist. Some buttons and dropdowns lose their background color when in high contrast mode. Bug 21309912 Color contrast . Instructional text on one form has 2:80:1 contrast, not the required 4.5:1. |
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Content that automatically updates, or time limits, can be adjusted by the user.
- Moving, blinking, or scrolling information that is designed to last for more than three seconds can be paused.
- Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden.
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Information conveyed by color or font styles is available in alternative formats, such as shape and text.
- Information conveyed has a contrast ratio of at least 3: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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Text and images of text in non-disabled controls have a luminosity contrast ratio of at least 4.5:1.
- Large scale text has a minimum ratio of at least 3:1
Exceptions: Bug 21338128 High contrast :Text boxes are not visible in worklist app. Missing border around several text boxes, so the text boxes do not appear properly in high contrast. The label appears, but you cannot see where to position your mouse. Bug 21338494 High contrast: Issues with button and drop downs in BPM Worklist. Some buttons and dropdowns lose their background color when in high contrast mode. Bug 21309912 Color contrast. Instructional text on one form has 2:80:1 contrast, not the required 4.5:1. |
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product has been tested for: - No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.
- No portion of the screen flashes more than three times in any one second period.
|
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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Labels or instructions are provided when the product requires user input
- FRAMES and iFRAMES are titled with meaningful text
- Controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
- Additional state information is programmatically exposed, such as whether a field is ‘required’.
|
Section 1194.22 Web-based Internet Information and Applications
Criteria | Supporting Features | Remarks (e.g., definition, equivalent facilitation, scope of support provided) |
1194.22(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
- Additional state information is programmatically exposed, such as whether a field is ‘required’.
- Images that convey information have meaningful alternative text.
- The product does not use image maps or CAPTCHAs
- Pages have a meaningful title specified in the TITLE element
Exceptions: Bug# 17905047: Admin Page – Approval Groups UI - issues found with color contrast, image and link. Bug# 17905083: Admin Page – Evidence Form UI: issues found with form, image and link. Bug# 17904884 & 17905009: Admin Page – Business Parameters UI: issues found with form, color contrast, image and link. Bug# 17905161: Administration Page – Task configuration UI – issues found color, form and table. |
1194.22(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Not Applicable | There is no prerecorded audio or video content in the product. |
1194.22(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Information conveyed by color or font styles is available in alternative formats, such as shape and text.
- Information conveyed has a contrast ratio of at least 3:1
|
1194.22(d) Documents shall be organized so they are readable without requiring an associated style sheet. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Style sheets are used only to change the layout and presentation of the screen
|
1194.22(e) Redundant text links shall be provided for each active region of a server-side image map. | Product has been developed to conform to this standard subject to the remarks on the right. | The product does not use image maps. |
1194.22(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. | Product has been developed to conform to this standard subject to the remarks on the right. | The product does not use image maps. |
1194.22(g) Row and column headers shall be identified for data tables. | Product has been developed to conform to this standard subject to the remarks on the right. | The product has been tested for - Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
Exceptions: - Bug 21294647 In the Admin section, under Rules, two tables have a blank column. This empty column is missing column headings.
- BUG 21784789: Tables in product documentation are missing row headers
|
1194.22(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Complex data tables with multiple levels of table headings or other organization of data, use the ID, HEADERS, and AXIS attributes.
- Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
Exceptions: BUG 21784789: Tables in product documentation are missing row headers |
1194.22(i) Frames shall be titled with text that facilitates frame identification and navigation. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - FRAMES and iFRAMES are titled with meaningful text
|
1194.22(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | Product has been developed to conform to this standard subject to the remarks on the right. | The product has been tested for: - No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.
- No portion of the screen flashes more than three times in any one second period.
|
1194.22(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. | Product has been developed to conform to this standard subject to the remarks on the right. | Text–only pages are not necessary because pages have been coded to meet other applicable standards, to the extent indicated. |
1194.22(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Content generated by JavaScript has been coded to meet other applicable standards, to the extent indicated.
|
1194.22(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with ยง1194.21(a) through (l). | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Content rendered by required plug-ins or applications has been coded to meet other applicable standards, to the extent indicated.
- Links are provided for downloading non-standard applets or plug-ins.
|
1194.22(n) When electronic forms are designed to be completed on-line, 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. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - FRAMES and iFRAMES are titled with meaningful text
- Controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
- Additional state information is programmatically exposed, such as whether a field is ‘required’.
|
1194.22(o) A method shall be provided that permits users to skip repetitive navigation links. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
|
1194.22(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Content that has time limits can be adjusted by the user.
- Users are warned before time expires and can extend the time limit.
|
Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) - 1.1, (b) - 1.4, (c) - 2.1, (d) - 6.1, (e) - 1.2, (f) - 9.1, (g) - 5.1, (h) - 5.2, (i) - 12.1, (j) - 7.1, (k) - 11.4.