Guideline 10. Orient the user

10.1 Associate table cells and headers (P1)

For graphical user agents that render tables, for each table cell, allow the user to view associated header information.

Sufficient techniques

The user agent may satisfy this checkpoint by allowing the user to query each table cell for associated header information.
The user agent may satisfy this checkpoint by rendering the table cell and associated header information so they are both visible in the same viewport.

Normative inclusions and exclusions

This checkpoint refers only to cell/header relationships that the user agent can recognize.

UAAG2 ISSUES

10.2 Highlight selection, content focus, enabled elements, visited links (P1)

Allow global configuration to highlight the following four classes of information in each viewport: the selection, content focus, enabled elements, and recently visited links.
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.
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.
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.

Normative inclusions and exclusions

Conformance profile labels: Selection

Notes

Examples of highlight mechanisms for selection and content focus include foreground and background color variations, underlining, border styling, and distinctive synthesized speech prosody. Because the selection and focus change frequently, user agents should not highlight them using mechanisms (e.g., font size variations) that cause content to reflow, as this may disorient the user. Graphical highlight mechanisms that generally do not rely on rendered text foreground and background color alone include underlines or border styling. Per checkpoint 7.1, follow operating environment conventions that benefit accessibility when implementing the selection and content focus. For instance, if specified at the level of the operating environment, inherit the user's preferences for selection styles.

UAAG2 ISSUES

10.3 Single highlight configuration (P2)

Extend the functionality required by provision two of checkpoint 10.2 by allowing configuration through a single setting.

Normative inclusions and exclusions

Conformance profile labels: Selection

UAAG2 ISSUES

10.4 Provide outline view (P2)

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

Normative inclusions and exclusions

What constitutes a label is defined by each markup language specification. For example, in HTML, a heading (H1-H6) is a label for the section that follows it, a CAPTION is a label for a table, and the title attribute is a label for its element.
The user agent is not required to generate a label for an important element when no label is present in content. The user agent may generate a label when one is not present.
A label is not required to be text only.

Notes

This outline view will provide the user with a simplified view of content (e.g, a table of contents). For information about what constitutes the set of important structural elements, see the Note following checkpoint 9.9. By making the outline view navigable, it is possible to satisfy this checkpoint and checkpoint 9.9 together: allow users to navigate among the important elements of the outline view, and to navigate from a position in the outline view to the corresponding position in a full view of content. See checkpoint 9.10 for additional configuration options.

UAAG2 ISSUES

10.5 Provide link information (P3)

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.

Normative inclusions and exclusions

User agents are expected to compute information about recently traversed links. For the other link information of this checkpoint, the user agent is only required to make available what is present in content.
The user agent is not required to compute or make available information that requires retrieval of linked Web resources.

UAAG2 ISSUES

10.6 Highlight current viewport (P1)

Highlight the viewport with the current focus (including any frame that takes current focus).
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).
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.

Normative inclusions and exclusions

Notes

See checkpoint 7.1 for information about implementing highlight mechanisms according to operating environment conventions.

UAAG2 ISSUES

10.7 Indicate viewport position (P3)

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

Sufficient techniques

The user agent may calculate the relative position according to content focus position, selection position, or viewport position, depending on how the user has been browsing.
The user agent may indicate the proportion of content viewed in a number of ways, including as a percentage or as a relative size in bytes. See checkpoint 1.3 for more information about text versions of messages to the user, including messages about position information.

Normative inclusions and exclusions

For two-dimensional spatial renderings, relative position includes both vertical and horizontal positions.
This checkpoint does not require the user agent to present information about retrieval progress. However, for streaming content, viewport position may be closely tied to retrieval progress.