Showing content from https://www.w3.org/TR/2002/REC-UAAG10-20021217/uaag10-chktable below:
Table of Checkpoints for User Agent Accessibility Guidelines 1.0
This document is an appendix to "User Agent Accessibility Guidelines 1.0" [UAAG10]. It provides a list of all checkpoints from the User Agent Accessibility Guidelines 1.0, organized by concept, as a checklist for user agent developers. Please refer to the Guidelines document for introductory information, information about related documents, a glossary of terms, and more.
This list may be used to review a tool or set of tools for accessibility. For each checkpoint, indicate whether the checkpoint has been satisfied, has not been satisfied, or is not applicable.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.
This document is not an independent W3C Recommendation but rather an appendix to "User Agent Accessibility Guidelines 1.0" [UAAG10].
Note: To reduce the length of this document, some normative information about checkpoints does not appear in the checklist below. Please refer to the Guidelines document for additional information on normative inclusions and exclusions, and for information about sufficient techniques.
Each checkpoint in this document is assigned a priority that indicates its importance for users with disabilities.
Checkpoints Provisions Satisfied Comments 1.1 Full keyboard access (P1)
(Techniques for 1.1)
1. Ensure that the user can operate, through keyboard input alone, any user agent functionality available through the user interface. 1.2 Activate event handlers (P1)
(Techniques for 1.2)
1. Allow the user to activate, through keyboard input alone, all input device event handlers that are explicitly associated with the element designated by the content focus. 2. In order to satisfy provision one of this checkpoint, the user must be able to activate as a group all event handlers of the same input device event type. For example, if there are 10 handlers associated with the onmousedown event type, the user must be able to activate the entire group of 10 through keyboard input alone, and must not be required to activate each handler separately. 1.3 Provide text messages (P1)
(Techniques for 1.3)
1. Ensure that every message (e.g., prompt, alert, or notification) that is a non-text element and is part of the user agent user interface has a text equivalent. 2.1 Render content according to specification (P1)
(Techniques for 2.1)
1. Render content according to format specification (e.g., for a markup language or style sheet language). 2.2 Provide text view (P1)
(Techniques for 2.2)
1. For content authored in text formats, provide a view of the text source. 2.3 Render conditional content (P1)
(Techniques for 2.3)
1. Allow configuration to provide access to each piece of unrendered conditional content "C". 2. When a specification does not explain how to provide access to this content, do so as follows:
- If C is a summary, title, alternative, description, or expansion of another piece of content D, provide access through at least one of the following mechanisms:
- (1a) render C in place of D;
- (2a) render C in addition to D;
- (3a) provide access to C by allowing the user to query D. In this case, the user agent must also alert the user, on a per-element basis, to the existence of C (so that the user knows to query D); and
- (4a) allow the user to follow a link to C from the context of D.
- Otherwise, provide access to C through at least one of the following mechanisms:
- (1b) render a placeholder for C, and allow the user to view the original author-supplied content associated with each placeholder;
- (2b) provide access to C by query (e.g., allow the user to query an element for its attributes). In this case, the user agent must also alert the user, on a per-element basis, to the existence of C; and
- (3b) allow the user to follow a link in context to C.
2.4 Allow time-independent interaction (P1)
(Techniques for 2.4)
1. For rendered content where user input is only possible within a finite time interval controlled by the user agent, allow configuration to provide a view where user interaction is time-independent. 2.5 Make captions, transcripts, audio descriptions available (P1)
(Techniques for 2.5)
1. Allow configuration or control to render text transcripts, collated text transcripts, captions, and audio descriptions in content at the same time as the associated audio tracks and visual tracks. 2.6 Respect synchronization cues (P1)
(Techniques for 2.6)
1. Respect synchronization cues (e.g., in markup) during rendering. 3.1 Toggle background images (P1)
(Techniques for 3.1)
1. Allow configuration not to render background image content. 3.2 Toggle audio, video, animated images (P1)
(Techniques for 3.2)
1. Allow configuration not to render audio, video, or animated image content, except on explicit user request. 3.3 Toggle animated or blinking text (P1)
(Techniques for 3.3)
1. Allow configuration to render animated or blinking text content as motionless, unblinking text. Blinking text is text whose visual rendering alternates between visible and invisible, at any rate of change. 3.4 Toggle scripts (P1)
(Techniques for 3.4)
1. Allow configuration not to execute any executable content (e.g., scripts and applets). 3.5 Toggle automatic content retrieval (P1)
(Techniques for 3.5)
1. Allow configuration so that the user agent only retrieves content on explicit user request. 4.1 Configure text scale (P1)
(Techniques for 4.1)
1. Allow global configuration of the scale of visually rendered text content. Preserve distinctions in the size of rendered text as the user increases or decreases the scale. 2. As part of satisfying provision one of this checkpoint, provide a configuration option to override rendered text sizes specified by the author or user agent defaults. 3. As part of satisfying provision one of this checkpoint, offer a range of text sizes to the user that includes at least:
- the range offered by the conventional utility available in the operating environment that allows users to choose the text size (e.g., the font size), or
- if no such utility is available, the range of text sizes supported by the conventional APIs of the operating environment for drawing text.
4.2 Configure font family (P1)
(Techniques for 4.2)
1. Allow global configuration of the font family of all visually rendered text content. 2. As part of satisfying provision one of this checkpoint, provide a configuration option to override font families specified by the author or by user agent defaults. 3. As part of satisfying provision one of this checkpoint, offer a range of font families to the user that includes at least:
- the range offered by the conventional utility available in the operating environment that allows users to choose the font family, or
- if no such utility is available, the range of font families supported by the conventional APIs of the operating environment for drawing text.
4.3 Configure text colors (P1)
(Techniques for 4.3)
1. Allow global configuration of the foreground and background color of all visually rendered text content. 2. As part of satisfying provision one of this checkpoint, provide a configuration option to override foreground and background colors specified by the author or user agent defaults. 3. As part of satisfying provision one of this checkpoint, offer a range of colors to the user that includes at least:
- the range offered by the conventional utility available in the operating environment that allows users to choose colors, or
- if no such utility is available, the range of colors supported by the conventional APIs of the operating environment for specifying colors.
4.4 Slow multimedia (P1)
(Techniques for 4.4)
1. Allow the user to slow the presentation rate of rendered audio and animation content (including video and animated images). 2. As part of satisfying provision one of this checkpoint, for a visual track, provide at least one setting between 40% and 60% of the original speed. 3. As part of satisfying provision one of this checkpoint, for a prerecorded audio track including audio-only presentations, provide at least one setting between 75% and 80% of the original speed. 4. When the user agent allows the user to slow the visual track of a synchronized multimedia presentation to between 100% and 80% of its original speed, synchronize the visual and audio tracks (per checkpoint 2.6). Below 80%, the user agent is not required to render the audio track. 4.5 Start, stop, pause, and navigate multimedia (P1)
(Techniques for 4.5)
1. Allow the user to stop, pause, and resume rendered audio and animation content (including video and animated images) that last three or more seconds at their default playback rate. 2. Allow the user to navigate efficiently within rendered audio and animations (including video and animated images) that last three or more seconds at their default playback rate. 4.6 Do not obscure captions (P1)
(Techniques for 4.6)
1. For graphical viewports, allow configuration so that captions synchronized with a visual track in content are not obscured by it. 4.7 Global volume control (P1)
(Techniques for 4.7)
1. Allow global configuration of the volume of all rendered audio, with an option to override audio volumes specified by the author or user agent defaults. 2. As part of satisfying provision one of this checkpoint, allow the user to choose zero volume (i.e., silent). 4.8 Independent volume control (P1)
(Techniques for 4.8)
1. Allow independent control of the volumes of rendered audio content synchronized to play simultaneously. 4.9 Configure synthesized speech rate (P1)
(Techniques for 4.9)
1. Allow configuration of the synthesized speech rate, according to the full range offered by the speech synthesizer. 4.10 Configure synthesized speech volume (P1)
(Techniques for 4.10)
1. Allow control of the synthesized speech volume, independent of other sources of audio. 4.11 Configure synthesized speech characteristics (P1)
(Techniques for 4.11)
1. Allow configuration of synthesized speech characteristics according to the full range of values offered by the speech synthesizer. 4.14 Choose style sheets (P1)
(Techniques for 4.14)
1. Allow the user to choose from and apply alternative author style sheets (such as linked style sheets). 2. Allow the user to choose from and apply at least one user style sheet. 3. Allow the user to turn off (i.e., ignore) author and user style sheets. 6.1 Programmatic access to HTML/XML infoset (P1)
(Techniques for 6.1)
1. Provide programmatic read access to XML content by making available all of the information items defined by the W3C XML Infoset [INFOSET]. 2. Provide programmatic read access to HTML content by making available all of the following information items defined by the W3C XML Infoset [INFOSET]:
- Document Information item: children, document element, base URI, charset
- Element Information items: element-type name, children, attributes, parent
- Attribute Information items: attribute-type name, normalized value, specified, attribute type, references, owner element
- Character Information items: character code, parent element
- Comment Information items: content, parent
3. If the user can modify the state or value of a piece of HTML or XML content through the user interface (e.g., by checking a box or editing a text area), allow programmatic read access to the current state or value, and allow the same degree of write access programmatically as is available through the user interface. 6.2 DOM access to HTML/XML content (P1)
(Techniques for 6.2)
1. Provide access to the content required in checkpoint 6.1 by conforming to the following modules of the W3C Document Object Model (DOM) Level 2 Core Specification [DOM2CORE] and exporting bindings for the interfaces they define:
- for HTML: the Core module
- for XML: the Core and XML modules
2. As part of satisfying provision one of this checkpoint:
- In the Java and ECMAScript operating environments, export the normative bindings specified in the DOM Level 2 Core Specification [DOM2CORE], or
- In other operating environments, the exported bindings (e.g., C++) must be publicly documented.
6.3 Programmatic access to non-HTML/XML content (P1)
(Techniques for 6.3)
1. For content other than HTML and XML, provide structured programmatic read access to content. 2. If the user can modify the state or value of a piece of non-HTML/XML content through the user interface (e.g., by checking a box or editing a text area), allow programmatic read access to the current state or value, and allow the same degree of write access programmatically as is available through the user interface. 3. As part of satisfying provision one of this checkpoint, implement at least one API according to this API cascade:
- The API is defined by a W3C Recommendation, or the API is publicly documented and designed to enable interoperability with assistive technologies.
- If no such API is available, or if available APIs do not enable the user agent to satisfy the requirements,
- implement at least one publicly documented API to satisfy the requirements, and
- follow operating environment conventions for the use of input and output APIs.
6.4 Programmatic access to information about rendered content (P1)
(Techniques for 6.4)
1. For graphical user agents, make available bounding dimensions and coordinates of rendered graphical objects. Coordinates must be relative to the point of origin in the graphical environment (e.g., with respect to the desktop), not the viewport. 2. For graphical user agents, provide access to the following information about each piece of rendered text: font family, font size, and foreground and background colors. 3. As part of satisfying provisions one and two of this checkpoint, implement at least one API according to the API cascade described in provision two of checkpoint 6.3. 6.5 Programmatic operation of user agent user interface (P1)
(Techniques for 6.5)
1. Provide programmatic read access to user agent user interface controls, selection, content focus, and user interface focus. 2. If the user can modify the state or value of a user agent user interface control (e.g., by checking a box or editing a text area), allow programmatic read access to the current state or value, and allow the same degree of write access programmatically as is available through the user interface. 3. As part of satisfying provisions one and two of this checkpoint, implement at least one API according to the API cascade described in provision two of checkpoint 6.3. 6.6 Programmatic notification of changes (P1)
(Techniques for 6.6)
1. Provide programmatic notification of changes to content, states and values of content, user agent user interface controls, selection, content focus, and user interface focus. 2. As part of satisfying provision one of this checkpoint, implement at least one API according to the API cascade of provision two of checkpoint 6.3. 6.7 Conventional keyboard APIs (P1)
(Techniques for 6.7)
1. Implement APIs for the keyboard as follows:
- Follow operating environment conventions.
- If no conventions exist, implement publicly documented APIs.
6.8 API character encodings (P1)
(Techniques for 6.8)
1. For an API implemented to satisfy requirements of this document, support the character encodings required for that API. 7.1 Respect focus and selection conventions (P1)
(Techniques for 7.1)
1. Follow operating environment conventions that benefit accessibility when implementing the selection, content focus, and user interface focus. 7.2 Respect input configuration conventions (P1)
(Techniques for 7.2)
1. Ensure that default input configurations of the user agent do not interfere with operating environment accessibility conventions (e.g., for keyboard accessibility). 8.1 Implement accessibility features (P1)
(Techniques for 8.1)
1. Implement the accessibility features of specifications (e.g., markup languages, style sheet languages, metadata languages, and graphics formats). 9.1 Provide content focus (P1)
(Techniques for 9.1)
1. Provide at least one content focus for each viewport (including frames) where enabled elements are part of the rendered content. 2. Allow the user to make the content focus of each viewport the current focus. 9.2 Provide user interface focus (P1)
(Techniques for 9.2)
1. Provide a user interface focus. 9.3 Move content focus (P1)
(Techniques for 9.3)
1. Allow the user to move the content focus to any enabled element in the viewport. 2. Allow configuration so that the content focus of a viewport only changes on explicit user request. 3. If the author has not specified a navigation order, allow at least forward sequential navigation, in document order, to each element in the set established by provision one of this checkpoint. 9.4 Restore viewport state history (P1)
(Techniques for 9.4)
1. For user agents that implement a viewport history mechanism, for each state in a viewport's browsing history, maintain information about the point of regard, content focus, and selection. 2. When the user returns to any state in the viewport history (e.g., via the "back button"), restore the saved values for the point of regard, content focus, and selection. 10.1 Associate table cells and headers (P1)
(Techniques for 10.1)
1. For graphical user agents that render tables, for each table cell, allow the user to view associated header information. 10.2 Highlight selection, content focus, enabled elements, visited links (P1)
(Techniques for 10.2)
1. Allow global configuration to highlight the following four classes of information in each viewport: the selection, content focus, enabled elements, and recently visited links. 2. For graphical user interfaces, as part of satisfying provision one of this checkpoint, allow at least one configuration where the highlight mechanisms for the four classes of information:
- differ from each other, and
- do not rely on rendered text foreground and background colors alone.
3. For graphical user interfaces, as part of satisfying provision one of this checkpoint, if a highlight mechanism involves text size, font family, rendered text foreground and background colors, or text decorations, offer at least the following range of values:
- for text size, the range required by provision three of checkpoint 4.1.
- for font family, the range required by provision three of checkpoint 4.2.
- for text foreground and background colors and decorations, the range offered by the conventional utility available in the operating environment for users to choose rendered text colors or decorations (e.g., the standard font and color dialog box resources supported by the operating system). If no such utility is available, the range supported by the conventional APIs of the operating environment for specifying text colors or drawing text.
4. Highlight enabled elements according to the granularity specified in the format. For example, an HTML user agent rendering a PNG image as part of a client-side image map is only required to highlight the image as a whole, not each enabled region. An SVG user agent rendering an SVG image with embedded graphical links is required to highlight each (enabled) link that may be rendered independently according to the SVG specification. 10.6 Highlight current viewport (P1)
(Techniques for 10.6)
1. Highlight the viewport with the current focus (including any frame that takes current focus). 2. For graphical viewports, as part of satisfying provision one of this checkpoint, provide at least one highlight mechanism that does not rely on rendered text foreground and background colors alone (e.g., use a thick outline). 3. If the techniques used to satisfy provision one of this checkpoint involve rendered text size, font family, rendered text foreground and background colors, or text decorations, allow global configuration and offer same ranges of values required by provision three of checkpoint 10.2. 11.1 Current user input configuration (P1)
(Techniques for 11.1)
1. Provide information to the user about current user preferences for input configurations. 12.1 Provide accessible documentation (P1)
(Techniques for 12.1)
1. Ensure that at least one version of the user agent documentation conforms to at least level Double-A of the Web Content Accessibility Guidelines 1.0 [WCAG10]. 12.2 Provide documentation of accessibility features (P1)
(Techniques for 12.2)
1. Provide documentation of all user agent features that benefit accessibility. 12.3 Provide documentation of default bindings (P1)
(Techniques for 12.3)
1. Provide documentation of the default user agent input configuration (e.g., the default keyboard bindings).
For the latest version of any W3C specification please consult the list of W3C Technical Reports at http://www.w3.org/TR.
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4