New Techniques/Issues Tracking Table for User Agent Accessibility Guidelines 1.0

comments please: structure, format, additional columns.

Priority 1 checkpoints

Checkpoints Provisions New Techniques Issues/Gaps
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.   need to reference DOM 3
  1. Should we reference other APIs, such as accessibility APIs?? http://lists.w3.org/Archives/Public/w3c-wai-ua/2006AprJun/0073.html also http://developer.apple.com/documentation/Accessibility/Conceptual/
    AccessibilityMacOSX/OSXAXModel/chapter_4_section_1.html
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.  Provide text messages, we need to add a technique about allowing non-essential alerts and text messages to be optional (turned off by the user if desired)  

http://www.w3.org/2006/06/15-ua-minutes.html

+ allowing non-essential (IF IDENTIFIED) alerts and text messages to be
optional (turned off by the user if desired).

+ AJAX implications as things change on-screen without a refresh

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).  Render content according to the spec, we need to expand the Example 2 technique about dynamic content changes. Users need to have an option to know when content has changed and where the changes are in additional to having access to the changes when they happen to navigate to the content that has changed.  Flesh out for AJAX and Roadmap functionality
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.
  1.  Use onscreen text (linked to the long description) indicating presence of a long description.
  2. user agent to send/expose information to the platform accessibility API for use by assistive technology that would make the information available to the user. note: this technique is for user agent with assistive technology.
  some recognition that some typres of situations are out of ua control - need specifics
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.    The techniques for this checkpoint seem to be narrowly focused on multimedia. I think is should be broadened to address meta refresh, AJAX refresh, security timeouts, etc.
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.  

Allow configuration for embedded media player objects to be opened in standalone non-embedded players to allow full access to the complete range of functionality allowed in a particular player.

note: user agent does not know what is in an object element, user only has control that the embedded play allows limited functionality. opening in a full player allows greater user control and functionality

 

  
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.    
  • add techniques to each checkpoint (3.x) clarifying that the toggle should be one setting that controls ALL of the various mechanism covered by each checkpoint.
  • http://dojotoolkit.org/pipermail/dojo-contributors/2006-June/002439.html
  • need clarification in 3.1 - are we talking about page level background images...CL: Right but unfortunately we already refer to CSS properties that could be done on element by element.
  • I would take the position that it applies to backgrounds of page parts as well as to whole pages. The toggle control could affect all backgrounds identifiable as such in the page, though. Or it could be scoped to a current object.
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.    

there is browser side and there is plugin side then there is part where they need to talk ... Seems to be tied in to compound doc stuff...with all its different layers

animated icons in title bar- (http://lists.w3.org/Archives/Public/w3c-wai-ua/2006JulSep/0016.html)
define the content area (viewport) to include the title bar, address bar, and tabs, etc.

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.    

add explicit technique about having setting to toggle annimation. current example uses ESC key, then page refresh to re-annimate (this is not a toggle)

annimation can be created in many way (gif, javascript, flash, svg, etc), UA can only control some (e.g. gif, svg[?])

animated icons in title bar- (http://lists.w3.org/Archives/Public/w3c-wai-ua/2006JulSep/0016.html)
define the content area (viewport) to include the title bar, address bar, and tabs, etc.

 

 
3.4 Toggle scripts (P1)

(Techniques for 3.4)		 1. Allow configuration not to execute any executable content (e.g., scripts and applets).    

Definition concerns. UA executes (has control over) javascript. UA does not execute (has no control over) applets, objects, etc. (plugins) - these require seperate applications

UA/user needs control over positioning and chrome attributes of generated content (javascript pop-ups with no address bar or scroll bar)

need abillity to control or over-ride the content rendered by html or script or other method

 

 
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.  allow user to change/override the author supplied meta refresh rate
  1.  AJAX - content retieval and update without page refresh (http://www.w3.org/2006/07/20-ua-minutes.html)
  2. the information written by the author in a manner, such that the UA can provide configuration parameters
  3. how is the updated info displayed and the user alerted. not a sole UA responsibility, author should provide
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.    may need to expand to include all foreground and background color. Author can change chrome scroll colors with CSS, including mouse arrows, and other chrome. . the scroll bar functionality is chrome, the change of color etc. (overriding user settings) is a viewport control
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).    

normative exclusion:
1. The user agent is not required to satisfy this checkpoint for audio and animations whose recognized role is to create a purely stylistic effect. Purely stylistic effects include background sounds, decorative animated images, and effects caused by style sheets.

the purpose of the audio, animation, etc. should not matter. The user should be able to stop it (CP3.2) or slow it down (CP4.4). How is the UA to know what is stylistic and what is real content? it doesn't matter what the role is, the user still needs control.

remove exclusion 1.

add technique - the user needs control over the rate of all audio and animation
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.    it would be better if the sufficient techniques here were clear that
only captions that are identified to the UA are covered.
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.    

techniques address css, but css does not allow for global (os level) control of volume.

UA's do not currently render sound natively, they require an external process. only that process can control the volume of the audio rendered by that process.

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).    

Priority 2 checkpoints

Checkpoints Provisions Satisfied Comments
2.7 Repair missing content (P2)

(Techniques for 2.7) 		1. Allow configuration to generate repair text when the user agent recognizes that the author has not provided conditional content required by the format specification.    
3.6 Toggle images (P2)

(Techniques for 3.6) 		1. Allow configuration not to render image content.
  1.  make the image replacement content a scolling pane
  2. additoinal technique: css wrap=scroll
  3. from image context menu, provide descriptions in full as part of image properties
 What about associated alt text and descriptions when images are turned off? are they rendered? what happens if the space for the image is too small to contain the text
4.12 Specific synthesized speech characteristics (P2)

(Techniques for 4.12) 		1. Allow configuration of synthesized speech pitch. Pitch refers to the average frequency of the speaking voice.    
2. Allow configuration of synthesized speech pitch range. Pitch range specifies a variation in average frequency.    
3. Allow configuration of synthesized speech stress. Stress refers to the height of "local peaks" in the intonation contour of the voice.    
4. Allow configuration of synthesized speech richness. Richness refers to the richness or brightness of the voice.    
4.13 Configure synthesized speech features (P2)

(Techniques for 4.13) 		1. Provide support for user-defined extensions to the synthesized speech dictionary.    
2. Provide support for spell-out: where text is spelled one character at a time, or according to language-dependent pronunciation rules.    
3. Allow at least two configurations for speaking numerals: one where numerals are spoken as individual digits, and one where full numbers are spoken.    
4. Allow at least two configurations for speaking punctuation: one where punctuation is spoken literally, and one where punctuation is rendered as natural pauses.    
5.1 No automatic content focus change (P2)

(Techniques for 5.1)		 1. Allow configuration so that if a viewport opens without explicit user request, neither its content focus nor its user interface focus automatically becomes the current focus.    
5.2 Keep viewport on top (P2)

(Techniques for 5.2)		 1. For graphical user interfaces, allow configuration so that the viewport with the current focus remains "on top" of all other viewports with which it overlaps.    
5.3 Manual viewport open only (P2)

(Techniques for 5.3)		 1. Allow configuration so that viewports only open on explicit user request.    
2. When configured per provision one of this checkpoint, instead of opening a viewport automatically, alert the user and allow the user to open it with an explicit request (e.g., by confirming a prompt or following a link generated by the user agent).    
3. Allow the user to close viewports.    
5.4 Selection and focus in viewport (P2)

(Techniques for 5.4) 		1. Ensure that when a viewport's selection or content focus changes, it is at least partially in the viewport after the change.    
5.5 Confirm form submission (P2)

(Techniques for 5.5)		 1. Allow configuration to prompt the user to confirm (or cancel) any form submission.    
6.9 DOM access to CSS style sheets (P2)

(Techniques for 6.9)		 1. For user agents that implement Cascading Style Sheets (CSS), provide programmatic access to style sheets by conforming to the CSS module of the W3C Document Object Model (DOM) Level 2 Style Specification [DOM2STYLE] and exporting bindings for the interfaces it defines.    
2. As part of satisfying provision one of this checkpoint:
  • In the Java and ECMAScript operating environments, export the normative bindings specified in the CSS module of the DOM Level 2 Style Specification [DOM2STYLE], or
  • In other operating environments, the exported bindings (e.g., C++) must be publicly documented.
    
6.10 Timely exchanges through APIs (P2)

(Techniques for 6.10) 		1. For APIs implemented to satisfy the requirements of this document, ensure that programmatic exchanges proceed in a timely manner.    
7.3 Respect operating environment conventions (P2)

(Techniques for 7.3) 		1. Follow operating environment conventions that benefit accessibility. In particular, follow conventions that benefit accessibility for user interface design, keyboard configuration, product installation, and documentation.    
7.4 Provide input configuration indications (P2)

(Techniques for 7.4) 		1. Follow operating environment conventions to indicate the input configuration.    
8.2 Conform to specifications (P2)

(Techniques for 8.2) 		1. Use and conform to either
  • W3C Recommendations when they are available and appropriate for a task, or
  • non-W3C specifications that enable the creation of content that conforms at level A or better to the Web Content Accessibility Guidelines 1.0 [WCAG10].
    
9.5 No events on focus change (P2)

(Techniques for 9.5) 		1. Allow configuration so that moving the content focus to or from an enabled element does not automatically activate any explicitly associated event handlers of any event type.    
9.6 Show event handlers (P2)

(Techniques for 9.6) 		1. For the element with content focus, make available the list of input device event types for which there are event handlers explicitly associated with the element.    
9.7 Move content focus in reverse (P2)

(Techniques for 9.7)		 1. Extend the functionality required in provision three of checkpoint 9.3 by allowing the same sequential navigation in reverse document order.    
2. As part of satisfying provision one of this checkpoint, the user agent must not include disabled elements in the navigation order.    
9.8 Provide text search (P2)

(Techniques for 9.8) 		1. Allow the user to search within rendered text content for a sequence of characters from the document character set.    
2. Allow the user to start a forward search (in document order) from any selected or focused location in content.    
3. When there is a match, do both of the following:
  • move the viewport so that the matched text content is at least partially within it, and
  • allow the user to search for the next instance of the text from the location of the match.
    
4. Alert the user when there is no match or after the last match in content (i.e., prior to starting the search over from the beginning of content).    
5. Provide a case-insensitive search option for text in scripts (i.e., writing systems) where case is significant.    
9.9 Allow structured navigation (P2)

(Techniques for 9.9)		 1. Allow the user to navigate efficiently to and among important structural elements in rendered content.    
2. As part of satisfying provision one of this checkpoint, allow forward and backward sequential navigation.    
10.3 Single highlight configuration (P2)

(Techniques for 10.3) 		1. Extend the functionality required by provision two of checkpoint 10.2 by allowing configuration through a single setting.    
10.4 Provide outline view (P2)

(Techniques for 10.4)		 1. Make available to the user an "outline" view of rendered content, composed of labels for important structural elements (e.g., heading text, table titles, form titles, and other labels that are part of the content).    
11.2 Current author input configuration (P2)

(Techniques for 11.2) 		1. Provide a centralized view of the current author-specified input configuration.    
11.3 Allow override of bindings (P2)

(Techniques for 11.3) 		1. Allow the user to override any binding that is part of the user agent default input configuration.    
11.4 Single-key access (P2)

(Techniques for 11.4) 		1. Allow the user to override any binding in the user agent default keyboard configuration with a binding to either a key plus modifier keys or to a single key.    
2. For each functionality in the set required by checkpoint 11.5, allow the user to configure a single-key binding. A single-key binding is one where a single key press performs the task, with zero modifier keys.    
11.5 Default input configuration (P2)

(Techniques for 11.5) 		1. Ensure that the user agent default input configuration includes bindings for the following functionalities required by other checkpoints in this document:
  • move content focus to the next enabled element in document order, and move content focus to the previous enabled element in document order (checkpoints 9.3 and 9.7);
  • activate the link designated by the content focus (checkpoints 1.1 and 9.1);
  • search for text, search again for same text (checkpoint 9.8);
  • increase the scale of rendered text, and decrease the scale of rendered text (checkpoint 4.1);
  • increase global volume, and decrease global volume (checkpoint 4.7); and
  • stop, pause, resume, and navigate efficiently selected audio and animations, including video and animated images (checkpoint 4.5).
    
2. If the user agent supports the following functionalities, the default input configuration must also include bindings for them:
  • next history state (forward), and previous history state (back);
  • enter a URI for a new resource;
  • add a URI to favorites (i.e., bookmarked resources);
  • view favorites;
  • reload a resource;
  • interrupt a request to load or reload a resource;
  • for graphical viewports: navigate forward and backward through rendered content by approximately the height of the viewport; and
  • for user agents that render content in lines of (at least) text: move the point of regard to the next and previous line.
    
11.6 User profiles (P2)

(Techniques for 11.6) 		1. For the configuration requirements of this document, allow the user to save user preferences in at least one user profile.    
2. Allow the user to choose from among available user agent default profiles, profiles created by the same user, and no profile (i.e., the user agent default settings).    
12.4 Provide documentation of changes between versions (P2)

(Techniques for 12.4) 		1. Provide documentation of changes since the previous version of the user agent to features that benefit accessibility.    
12.5 Provide dedicated accessibility section (P2)

(Techniques for 12.5) 		1. Provide a centralized view of all features of the user agent that benefit accessibility, in a dedicated section of the documentation.    

Priority 3 checkpoints

Checkpoints Provisions Satisfied Comments
2.8 No repair text (P3)

(Techniques for 2.8) 		1. Allow at least two configurations for when the user agent recognizes that conditional content required by the format specification is present but empty content:
  • generate no repair text.
  • generate repair as described in checkpoint 2.7.
    
2.9 Render conditional content automatically (P3)

(Techniques for 2.9) 		1. Allow configuration to render all conditional content automatically.    
2. As part of satisfying provision one of this checkpoint, provide access according to specification, or where unspecified, by applying one of the techniques 1a, 2a, or 1b defined in provision two of checkpoint 2.3.    
2.10 Don't render text in unsupported writing systems (P3)

(Techniques for 2.10)		 1. For graphical user agents, allow configuration not to render text in unsupported scripts (i.e., writing systems) when that text would otherwise be rendered.    
2. When configured per provision one of this checkpoint, indicate to the user in context that author-supplied content has not been rendered due to lack of support for a writing system.    
9.10 Configure important elements (P3)

(Techniques for 9.10)		 1. Allow configuration of the set of important elements and attributes identified for checkpoints 9.9 and 10.4.    
2. As part of satisfying provision one of this checkpoint, allow the user to include and exclude element types in the set.    
10.5 Provide link information (P3)

(Techniques for 10.5)		 1. To help the user decide whether to traverse a link in content, make available the following information about it:
  • link element content,
  • link title,
  • whether the link is internal to the resource (e.g., the link is to a target in the same Web page),
  • whether the user has traversed the link recently, and
  • information about the type, size, and natural language of linked Web resources.
    
10.7 Indicate viewport position (P3)

(Techniques for 10.7)		 1. Indicate the viewport's position relative to rendered content (e.g., the proportion of an audio or video clip that has been played, or the proportion of a Web page that has been viewed).    
11.7 Tool bar configuration (P3)

(Techniques for 11.7) 		1. For graphical user agent user interfaces with tool bars, allow the user to configure the position of user agent user interface controls on those tool bars.    
2. Offer a predefined set of controls that may be added to or removed from tool bars.    
3. Allow the user to restore the default tool bar configuration.    

Updated: August 1, 2006

Author: Jim Allan