1. Support input and output device-independence

1.1 Full keyboard access (P1)

(Original)

1. Ensure that the user can operate, through keyboard input alone, any user agent functionality available through the user interface.

Normative inclusions and exclusions

1. This checkpoint excludes the requirements of checkpoint 1.2.
2. Conformance detail: For both content and user agent

Notes

• For example, ensure that the user can interact with enabled elements, select content, navigate viewports, configure the user agent, access documentation, install the user agent, and operate user interface controls, all entirely through keyboard input.

UAAG2 ISSUES

• Nov.4.JA,JR: "any functionality available throught the user interface" - if content not coded right then ua can't get there
• Nov.4.JR: Maybe we want to work on a concept of "browser understood user interface rendered controls"- if something has tabindex-1 it has been hidden by author and UA no longer has responsbility?

1.2 Activate event handlers (P1)

(Original)

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.

Normative inclusions and exclusions

1. Provision one of this checkpoint applies to handlers of any input device event type, including event types for keyboard, pointing device, and voice input.
2. The user agent is not required to allow activation of event handlers associated with a given device (e.g., the pointing device) in any order other than what the device itself allows (e.g., a mouse down event followed by a mouse drag event followed by a mouse up event).
3. The requirements for this checkpoint refer to any explicitly associated input device event handlers associated with an element, independent of the input modalities for which the user agent conforms. For example, suppose that an element has an explicitly associated handler for pointing device events. Even when the user agent only conforms for keyboard input (and does not conform for the pointing device, for example), this checkpoint requires the user agent to allow the user to activate that handler with the keyboard.
4. This checkpoint is mutually exclusive of checkpoint 1.1 since the current checkpoint may be excluded from a conformance profile, unlike other keyboard operation requirements.
5. Conformance profile labels: Events

Notes

• Refer to the checkpoints of guideline 9 for more information about focus requirements.

UAAG2 ISSUES

• Nov.4.JA,JR: Need to clarify once again what's allowed to get focus.
• 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

ckl: Add some more techniques related to ARIA and accessibility APIs, such as:

12. ckl: In a Rich Internet Application (RIA), an element with an event handler often defines a widget and has a defined "role" attribute to describe the behavior of the widget. The user agent must expose the value of role attributes to assistive technologies through DOM interfaces but should also expose these attributes using platform accessibility APIs. IAccessible2 (IA2) for Windows and the Accessibility Toolkit (ATK) for Linux have roles defined which easily map to roles defined for Accessible Rich Internet Applications (ARIA).

• ckl:See http://www.w3.org/TR/aria-role/ for ARIA roles.

• ckl:See http://accessibility.freestandards.org/a11yspecs/ia2/docs/html/ for IA2 roles.

• ckl:See http://developer.gnome.org/doc/API/2.0/atk/AtkObject.html#AtkRole for ATK roles.

1.3 Provide text messages (P1) Techniques for checkpoint 1.3

(Original)

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. ckl: Allow configuration not to render non-essential or low priority text messages based on priority properties defined by the author.

Notes

• For example, if the user is alerted of an event by an audio cue, a visually-rendered text equivalent in the status bar could satisfy this checkpoint. Per checkpoint 6.5, a text equivalent for each such message must be available through an API. See also checkpoint 6.6 for requirements for programmatic notification of changes to the user interface.

• ckl: Examples of priority properties for a text message are off (not currently live), polite (low priority), assertive (medium priority), and rude (high priority) for AJAX live regions.

ckl: Under techniques for this guideline, reference Live Regions section of ARIA States spec: http://www.w3.org/TR/aria-state/#liveregions

UAAG2 ISSUES

• Nov.4.JA: "1.3.2 Allow configuration by user to override the priority level of text messages defined by the author."?

• 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

Guideline 2. Ensure user access to all content

2.1 Render content according to specification (P1)

(Original)

1. Render content according to format specification (e.g., for a markup language or style sheet language).

Normative inclusions and exclusions

1. Rendering requirements include format-defined interactions between author preferences and user preferences/capabilities (e.g., when to render the alt attribute in HTML, the rendering order of nested OBJECT elements in HTML, test attributes in SMIL, and the cascade in CSS2).
2. When a rendering requirement of another specification contradicts a requirement of UAAG 1.0, the user agent may disregard the rendering requirement of the other specification and still satisfy this checkpoint; see the section on the relation of this document to general software design guidelines and other specifications for more information.
3. The user agent is not required to satisfy this checkpoint for all implemented specifications; see the section on conformance profiles for more information.
4. This checkpoint excludes the requirements of checkpoint 2.6.

Notes

• If a conforming user agent does not render a content type, it should allow the user to choose a way to handle that content (e.g., by launching another application or by saving it to disk).

UAAG2 ISSUES

• Accessible notification of user about changes in content when specific content is refreshed without a total page refresh (Referece WAI-ARIA)

2.2 Provide text view (P1)

(Original)

1. For content authored in text formats, provide a view of the text source.

Normative inclusions and exclusions

1. For the purposes of this checkpoint, a text format is:
   • any media object given an Internet media type of "text" (e.g., "text/plain", "text/html", or "text/*") as defined in RFC 2046 [RFC2046], section 4.1, or
   • any media object identified by Internet media type to be an XML document (as defined in [XML], section 2) or SGML application. Refer, for example, to Internet media types defined in "XML Media Types" [RFC3023].
2. The user agent is only required to satisfy this checkpoint for text formats that are part of a conformance claim; see the section on conformance profiles for more information. However, user agents should provide a text view for all implemented text formats.

UAAG2 ISSUES

2.3 Render conditional content (P1)

(Original)

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:
     • render C in place of D;
     • render C in addition to D;
     • 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
     • 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:
     • render a placeholder for C, and allow the user to view the original author-supplied content associated with each placeholder;
     • 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
     • allow the user to follow a link in context to C.

Sufficient techniques

1. To satisfy provision one of this checkpoint, the configuration may be a switch that, for all content, turns on or off the access mechanisms described in provision two.
2. To satisfy provision two of this checkpoint, the user agent may provide access on a per-element basis (e.g., by allowing the user to query individual elements) or for all elements (e.g., by offering a configuration to render conditional content all the time).
3. To satisfy the requirement of provision two of this checkpoint to allow the user to view the content associated with each placeholder, the user agent may either render the associated content in a separate viewport or in place of the placeholder.

Normative inclusions and exclusions

1. For the placeholder requirement of provision two of this checkpoint, a request to view the original content associated with a placeholder is considered an explicit user request to render that content.
2. The user agent is not required to include placeholders in the document object. A placeholder that is part of the document object should conform to the Web Content Accessibility Guidelines 1.0 [WCAG10]. If a placeholder is not part of the document object, it is part of the user interface only (and subject, for example, to checkpoint 1.3).
3. Conformance detail: For all content

Notes

• For instance, an HTML user agent might allow users to query each element for access to conditional content supplied for the alt, title, and longdesc attributes. Or, the user agent might allow configuration so that the value of the alt attribute is rendered in place of all IMG elements (while other conditional content might be made available through another mechanism).

UAAG2 ISSUES

2.4 Allow time-independent interaction (P1)

(Original)

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.

Sufficient techniques

1. The user agent may satisfy this checkpoint by pausing processing automatically to allow for user input, and resuming processing on explicit user request. When using this technique, pause at the end of each time interval where user input is possible. In the paused state:
   • Alert the user that the rendered content has been paused (e.g., highlight the pause button in a multimedia player's control panel).
   • Highlight which enabled elements are time-sensitive.
   • Allow the user to interact with the enabled elements.
   • Allow the user to resume on explicit user request (e.g., by pressing the play button in a multimedia player's control panel; see also checkpoint 4.5).
2. The user agent may satisfy this checkpoint by generating a time-independent (or, "static") view, based on the original content, that offers the user the same opportunities for interaction. The static view should reflect the structure and flow of the original time-sensitive presentation; orientation cues will help users understand the context for various interaction opportunities.

Normative inclusions and exclusions

1. When satisfying this checkpoint for a real-time presentation, the user agent may discard packets that continue to arrive after the construction of the time-independent view (e.g., when paused or after the construction of a static view).
2. This checkpoint does not apply when the user agent cannot recognize the time interval in the presentation format, or when the user agent cannot control the timing (e.g., because it is controlled by the server).

Notes

• If the user agent satisfies this checkpoint by pausing automatically, it may be necessary to pause more than once when there are multiple opportunities for time-sensitive user interaction. When pausing, pause synchronized content as well (whether rendered in the same or different viewports) per checkpoint 2.6. In SMIL 1.0 [SMIL], for example, the begin, end, and dur attributes synchronize presentation components. See also checkpoint 3.5, which involves client-driven content retrieval.

UAAG2 ISSUES

• how to handle interactions that are out of ua control - security timeout from server, ajax refresh

2.5 Make captions, transcripts, audio descriptions available (P1)

(Original)

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.

Normative inclusions and exclusions

1. Conformance profile labels: Video, Audio
2. Conformance detail: For all content

UAAG2 ISSUES

2.6 Respect synchronization cues (P1)

(Original)

1. Respect synchronization cues (e.g., in markup) during rendering.

Normative inclusions and exclusions

1. This checkpoint is mutually exclusive of checkpoint 2.1 since it may be excluded from a conformance profile.
2. Conformance profile labels: Video, Audio

UAAG2 ISSUES

2.7 Repair missing content (P2)

(Original)

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.

Sufficient techniques

1. The user agent may satisfy this checkpoint by basing the repair text on any of the following available sources of information: URI reference (as defined in [RFC2396], section 4), content type, or element type. Note, however, that additional information that would enable more helpful repair might be available but not "near" the missing conditional content. For instance, instead of generating repair text on a simple URI reference, the user agent might look for helpful information near a different instance of the URI reference in the same document object, or might retrieve useful information (e.g., a title) from the resource designated by the URI reference

Normative inclusions and exclusions

1. Conformance detail: For all content

Notes

• Some markup languages (such as HTML 4 [HTML4] and SMIL 1.0 [SMIL] require the author to provide conditional content for some elements (e.g., the alt attribute on the IMG element).

UAAG2 ISSUES

2.8 No repair text (P3)

(Original)

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.

Normative inclusions and exclusions

1. Conformance detail: For all content

Notes

In some authoring scenarios, empty content (e.g., alt="" in HTML) may make an appropriate text equivalent, such as when non-text content has no other function than pure decoration, or when an image is part of a "mosaic" of several images and does not make sense out of the mosaic. Refer to the Web Content Accessibility Guidelines 1.0 [WCAG10] for more information about text equivalents.

UAAG2 ISSUES

2.9 Render conditional content automatically (P3)

(Original)

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.

Sufficient techniques

1. The user agent may satisfy provision one of this checkpoint through multiple configurations (e.g., a first configuration to render one type of conditional content automatically and a second to render another type).

Normative inclusions and exclusions

1. The user agent is not required to render all conditional content at the same time in a single viewport.
2. Conformance detail: For all content

Notes

• For instance, an HTML user agent might allow configuration so that the value of the alt attribute is rendered in place of all IMG elements (while other conditional content might be made available through another mechanism).

UAAG2 ISSUES

2.10 Don't render text in unsupported writing systems (P3)

(Original)

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.

Normative inclusions and exclusions

1. This checkpoint does not require the user agent to allow different configurations for different writing systems.

Notes

• The primary purpose of this checkpoint is to benefit users with serial access to content or who navigate sequentially, allowing them to skip portions of content that would be unusable if rendered graphically as "garbage."

UAAG2 ISSUES

Guideline 3. Allow configuration not to render some content that may reduce accessibility

3.1 Toggle base background images

(Original)

1. Allow configuration not to render images that are rendered on the base background (defn: The base background is the background of the content as a whole, such that no content may be layered behind it. In graphics applications, the base background is often referred to as the canvas.).

Sufficient techniques

1. Allowing users to turn off images that the user agent would render on the base background.

Normative inclusions and exclusions

1. This checkpoint must be satisfied for all implemented image specifications; see the section on conformance profiles.
2. When configured not to render background images, the user agent is not required to retrieve them until the user requests them explicitly. When background images are not rendered, user agents should render a solid background color instead; see checkpoint 4.3 for information about text colors.
3. This checkpoint only requires control of background images for "two-layered" renderings, where the background is considered the first layer and everything rendered above it is considered the second layer.
4. Conformance profile labels: Image

Notes

• When background images are not rendered, they are considered conditional content. See checkpoint 2.3 for information about providing access to conditional content.

UAAG2 EDIT HISTORY

• "Base background" formulation approved in July 26 meeting (http://www.w3.org/2007/07/26-ua-minutes.html)

• "Base bakground reformulation" (http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0014.html)

• Discussion on July 19 meeting - sent for edits (http://www.w3.org/2007/07/19-ua-minutes.html)

• "Viewport" formulation proposal (http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0006.html)

• Initial comments:
  • need clarification in 3.1 - are we talking about page level background images or all element background images. The toggle control could affect all backgrounds identifiable as such in the page, though. Or it could be scoped to a current object.

  • PP: We need to have a discussion about 1) what browser developers consider possible to implement for this checkpoint and 2) at what level control over background images becomes so fine grained that it is unusable. Is it possible for browser developers to disable background images on every element? Does this amount to ignoring the CSS background and background-image styles plus the background attribute on body? As for users, is it really necessary to have control over all elements on the page? Could a user even practically select the proper element to disable its background image, especially since they might be having a hard time seeing it in the first place (hence the need for this checkpoint).

  • JA: This is an historical issue, see http://lists.w3.org/Archives/Public/w3c-wai-ua/2001AprJun/0118.html. Can't find a working group response to the issues raised.

  • what happens if background images are used in ajax widgets and images are turned off?

  • PP: I have no good solution for this problem. The browser cannot determine whether background images are being used simply for style or to carry semantic meaning. I think encoding information into CSS background images should really be considered a violation of WCAG that the browser can do little to remedy. If the user turns off CSS, and lots of images with semantic meaning disappear, the content author needs to fix his/her content.

  • CL: The Dojo widget set detects when background images are turned off (as well as when in high contrast)and provides text equivalents for widgets which are rendered using background images. However, widget sets not considering accessibility will not be doing this.

  • 12 July 2007 redefine background image or deprecate guideline because of breaking AJAX widgets??

3.2 Toggle audio, video, animated images, and animated/blinking text

• Allow configuration not to render audio, video, or animated image content, except on explicit user request.

• Allow configuration to render animated or blinking text content as motionless, unblinking text.

Sufficient techniques

• The user agent may satisfy the first success criteria by making video and animated images invisible and audio silent, but this technique is not recommended.

• The user agent may satisfy the second success criteria by showing still images in place of video and image animations. @@Still issues with this@@

• The user must still have access to all animated/blinking text content, but the user agent may render it in a separate viewport (e.g., for large amounts of streaming text).
• The user agent may satisfy the second success criteria by always rendering animated or blinking text as motionless, unblinking text.

Normative inclusions and exclusions

• This checkpoint does not apply for content the user agent cannot deterministically recognize as audio, video, animated images, or animated/blinking text.

• This configuration is required for content rendered without any user interaction (including content rendered on load or as the result of a script), as well as content rendered as the result of user interaction that is not an explicit user request (e.g., when the user activates a link).
• This checkpoint must be satisfied for all implemented audio, video, and animated image specifications; see the section on conformance profiles.
• When configured not to render audio, video, or animated images except on explicit user request, the user agent is not required to retrieve them until the user requests them explicitly.

• Checkpoint 4.3 addresses user control of blinking effects caused by rapid color changes.

• Conformance profile labels: VisualText, Animation, Video, Audio === Note ===

See guideline 4 for additional requirements related to the control of rendered audio, video, and animated images. When these content types are not rendered, they are considered conditional content. See checkpoint 2.3 for information about providing access to conditional content. Animation (a rendering effect) differs from streaming (a delivery mechanism). Streaming content might be rendered as an animation (e.g., an animated stock ticker or vertically scrolling text) or as static text (e.g., movie subtitles, which are rendered for a limited time, but do not give the impression of movement).

UAAG2 EDIT HISTORY

• 3.2 and 3.3 combined

UAAG2 ISSUES from 3.2

• PP: Proposal to combine 3.2 and 3.3 (http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0048.html)

• Initial Comments
  • animations can be created in many way (gif, javascript, flash, svg, etc), UA can only control some (e.g. gif, svg[?]) - is is reasonable to require the UA to control items it may know noting about. This is related to Compound Documents.

  • PP

    • GIFs: Browser does the rendering. Can show a static frame.
    • Flash: Browser knows about the embedded plug-in. Might allow the user to disable Flash content altogether. This might kill more than heavily animated Flash on a page. But, in general, isn't most Flash animated anyways? Isn't that a point of using it?
    • Video/audio: Browser should know from MIME type that directly linked content is video or audio. Problem is harder when there's a level of indirection For instance, the browser might know to load a plug-in, but could be unaware that the plug-in decided to load some multimedia content.
    • SVG+JS: Hard to know what the JS is doing to the SVG. Animating it? Responding to a mouse click by updating some text? Going off and fetching some data asynchronously?

    • General JS: Even harder to determine. For instance, JS can draw into the <canvas> tag supported by Safari, Webkit, Firefox, IE (via plug-in) etc. The drawing is a bitmap.

  • What if we say if the browser can deterministically ascertain that content is animating, video, or audio, then it must provide an option to conditionally render or not render that content.

  • animated icons in title bar- (http://lists.w3.org/Archives/Public/w3c-wai-ua/2006JulSep/0016.html) may need to redefine the content area (viewport) to include the parts of the user interface/chrome (title bar, address bar, and tabs, etc) that render author created content

  • PP: Where is it stated that this checkpoint applies to the viewport, but not to the chrome? I don't see anything immediately in the checkpoint. If it is in some general definition, then, yes, that definition needs to be revised so that this checkpoint (and probably others) apply to rendered documents, chrome of the browser, and any extensions that plug-into the chrome by way of a public API which the browser can control.

UAAG2 ISSUES from 3.3

• Initial comments:
  • animation can be created in many way (gif, javascript, flash, svg, etc), UA can only control some (e.g. gif, svg[?]) (see issue in 3.2)

  • animated icons in title bar- (http://lists.w3.org/Archives/Public/w3c-wai-ua/2006JulSep/0016.html)

may need to redefine the content area (viewport) to include the title bar, address bar, and tabs, etc.(see issue in 3.2)

• PP: See comments in 3.2. I think whatever decide there, applies here. On that note, is there a reason for having these as two separate checkpoints? To me, animated text falls into the same category as any other animated content.

• 12 July 2007 combine Guidelines 3.3 and 3.2. these are very closely related.

3.4 Toggle executable content (P1)

(Original)

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

Sufficient techniques

1. Provide the user with the ability to toggle whether the base user agent executes content that it is able to . - if cond. content exists reveal it (2.3)
2. Provide the user with the ability to toggle the loading of plugins that execute content the base browser is unable to execute - if cond. content exists reveal it (2.3)

Notes

• Executable content may provide very useful functionality, not all of which causes accessibility problems. If content is not executed it is important to instead render any conditional content that the author may provide.@@take another look at this@@.

UAAG2 ISSUES

• JA proposal: http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0071.html

  • remove the normative exclusion
  • New wording: 3.4 Toggle executable content (P1)
    1. Allow configuration not to execute any executable content (e.g., scripts, plugs-ins and applets).

• JR proposal re: new checkpoint for no stripped down user agent windows (http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0007.html)

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

  • PP: But the browser does have control over whether those separate applications can load or not. Maybe this checkpoint should be titled with something to the effect of "Toggle executable content," and the definition, inclusions/exclusions, and notes can be fleshed out to include applets, embeds, objects, etc.?

  • 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

  • PP: These issues seem to call for a whole new checkpoint for me. They are not simply talking about an on/off switch like 3.4. They are saying the user should have some control over how executable content runs.

3.5 Toggle automatic content retrieval (P1)

(Original)

1. Allow configuration so that the user agent only retrieves content on explicit user request.

Normative inclusions and exclusions

1. When the user chooses not to retrieve (fresh) content, the user agent may ignore that content; buffering is not required.
2. This checkpoint only applies when the user agent (not the server) automatically initiates the request for fresh content. However, the user agent is not required to satisfy this checkpoint for "client-side redirects," i.e., author-specified instructions that a piece of content is temporary and intermediate, and is replaced by content that results from a second request.

Notes

• For example, if the user agent supports automatic content retrieval, to ensure that the user does not become disoriented by sudden automatic changes, allow configurations such as "Never retrieve content automatically" and "Require confirmation before content retrieval."

UAAG2 ISSUES

• PP: Ideas and discussion of issue: http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0016.html

• Initial Comments

  • AJAX - content retieval and update without page refresh (http://www.w3.org/2006/07/20-ua-minutes.html)

  • PP: Disabling automatic content fetches using XMLHttpRequest is difficult unless the browser tracks what event initiated the fetch. For instance, did the user recently give some input that cause the fetch or not? I think determining the original event source for all fetches is untenable though, so I'm not sure what the user agent can do to meet this checkpoint considering AJAX.

  • Perhaps tying into live region markup would help here? The markup is intended to assist a browser plus AT in determining what automatic changes are relevant. But perhaps the browser could also provide a setting that, when enabled, prevents any regions marked live from automatically updating without an explicit user request. I know the live region markup was not designed directly for this purpose, but it seems a valid use.
  • the information written by the author in a manner, such that the UA can provide configuration parameters
  • how is the updated info displayed and the user alerted. not a sole UA responsibility, author should provide

• PP: Is there anything in WCAG 2.0 about providing configuration parameters or disabling auto-refresh to meet this need? I'm not sure what we can / should do in UAAG to address it.

3.6 Toggle images (P2)

(Original)

1. Allow configuration not to render image content.

Sufficient techniques

1. The user agent may satisfy this checkpoint by making images invisible, but this technique is not recommended.

Normative inclusions and exclusions

1. This checkpoint must be satisfied for all implemented image specifications; see the section on conformance profiles.
2. When configured not to render images, the user agent is not required to retrieve them until the user requests them explicitly.
3. Conformance profile labels: Image

Notes

• When images are not rendered, they are considered conditional content. See checkpoint 2.3 for information about providing access to conditional content.

UAAG2 ISSUES

• Initial COmments:

  • PP: I want to raise a clarification issue here. I assume this checkpoint was originally talking specifically about <img> tags alone. If so, that criterion should be made explicit now that there is at least one (i.e. CSS background images) to get image content onto a page covered by another checkpoint.

  • 12 July 2007 should toggle all images <img>, <object>, css, etc. there may be additional accessibility issues with element borders adding visual clutter for folks with some types of cognitive disabilities.

Guideline 4. Ensure user control of rendering

4.1 Configure text scale (P1)

(Original)

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.

Sufficient techniques

1. The user agent may satisfy provision one of this checkpoint through a number of mechanisms, including zoom, magnification, and allowing the user to configure a reference size for rendered text (e.g., render text at 36 points unless otherwise specified). For example, for CSS2 [CSS2] user agents, the medium value of the font-size property corresponds to a reference size.

Normative inclusions and exclusions

1. The word "scale" is used in this checkpoint to mean the general size of text.
2. The user agent is not required to satisfy this requirement through proportional scaling. What must hold is that if rendered text A is smaller than rendered text B at one value of the configuration setting of provision one, then text A will still be smaller than text B at another value of this configuration setting.

3. Conformance profile labels: VisualText

UAAG2 ISSUES

4.2 Configure font family (P1)

(Original)

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.

Sufficient techniques

1. For text that cannot be rendered properly using the user's preferred font family, the user agent should substitute an alternative font family.

Normative inclusions and exclusions

1. Conformance profile labels: VisualText

Notes

• For example, allow the user to specify that all text is to be rendered in a particular sans-serif font family.

UAAG2 ISSUES

4.3 Configure text colors (P1)

(Original)

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.

Normative inclusions and exclusions

1. Color includes black, white, and grays.

2. Conformance profile labels: VisualText

Notes

• User configuration of foreground and background colors may inadvertently lead to the inability to distinguish ordinary text from selected text or focused text. See checkpoint 10.2 for more information about highlight styles.

UAAG2 ISSUES

4.4 Slow multimedia (P1)

(Original)

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.

Normative inclusions and exclusions

1. Conformance profile labels: Animation, Audio

Notes

• The style exception of this checkpoint is based on the assumption that authors have satisfied the requirements of the "Web Content Accessibility Guidelines 1.0" [WCAG10] not to convey information through style alone (e.g., through color alone or style sheets alone).

UAAG2 EDIT HISTORY

• Simplifying proposal: http://lists.w3.org/Archives/Public/w3c-wai-ua/2007JulSep/0020.html

• 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.
• removed exclusion 1 (was "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. ")

4.5 Start, stop, pause, and navigate multimedia (P1)

(Original)

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.

Sufficient techniques

1. The user agent may satisfy the navigation requirement of provision two of this checkpoint through forward and backward serial access techniques (e.g., advance five seconds), or direct access techniques (e.g., start playing at the 10-minute mark), or some combination.

Normative inclusions and exclusions

1. When using serial access techniques to satisfy provision two of this checkpoint, the user agent is not required to play back content during advance or rewind (though doing so may help orient the user).
2. When the user pauses a real-time audio or animation, the user agent may discard packets that continue to arrive during the pause.
3. This checkpoint applies to content that is either rendered automatically (e.g., on load) or on explicit request from the user.
4. The user agent is not required to satisfy this checkpoint for audio and animations whose recognized role is to create a purely stylistic effect; see checkpoint 4.4 for more information about what constitutes a stylistic effect.
5. Conformance profile labels: Animation, Audio

Notes

• The lower bound of three seconds is part of this checkpoint since control is not required for brief audio and animation content, such as short clips or beeps. Respect synchronization cues per checkpoint 2.6.

UAAG2 ISSUES

• JR: 4.5.2 What's the use case for this being here?

4.6 Do not obscure captions (P1)

(Original)

1. For graphical viewports, allow configuration so that captions synchronized with a visual track in content are not obscured by it.

Sufficient techniques

1. Render captions "on top" of the visual track and, as part of satisfying checkpoint 4.3, allow the user to configure the foreground and background color of the rendered captions text.
2. Render captions and video in separate viewports.

Normative inclusions and exclusions

UAAG2 ISSUES

• Only if "caption" semantics are known

4.7 Global volume control (P1)

(Original)

1. Allow global configuration of the volume of all rendered audio.

2. As part of satisfying provision one of this checkpoint, allow the user to choose zero volume (i.e., silent).

Normative inclusions and exclusions

1. This checkpoint must be satisfied for all implemented specifications that produce sound; see the section on conformance profiles.
2. Conformance profile labels: Audio
3. Conformance detail: For both content and user agent

Notes

• User agents should allow configuration of volume through available operating environment mechanisms.

UAAG2 ISSUES

• 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. Process may or may not be native to OS. The UA may not know about audio control seperate from the OS.

• JR: This issue is actually covered in the techniques where it is clear that the UA can rely on the OS.

• JR: Why say “Rendered Audio” are there other kinds?

4.8 Independent volume control (P1)

(Original)

1. Allow independent control of the volumes of rendered audio content synchronized to play simultaneously.

Normative inclusions and exclusions

1. The user control required by this checkpoint includes the ability to override author-specified volumes for the relevant sources of audio.
2. The user agent is not required to satisfy this checkpoint for audio whose recognized role is to create a purely stylistic effect; see checkpoint 4.4 for more information about what constitutes a stylistic effect.
3. Conformance profile labels: Audio

Notes

• The user agent should satisfy this checkpoint by allowing the user to control independently the volumes of all audio sources (e.g., by implementing a general audio mixer type of functionality). See checkpoint 4.10 for information about controlling the volume of synthesized speech.

UAAG2 ISSUES

• UA that have roles to control audio are usually "plug-ins" or screen readers. not 'standard' user agents
• definition of "recongnized" in normative inclusions #2 is not the same as UAAG definition of "recongnize", definition of "recognize" is too focused on HTML

change normative inclusion #2 UA should be required to adjust volume for all audio content - stylistic or semantic

• in the note: need to clarify by adding "including foreground and background audio" (semantic vs. sytlistic - regardless of the stated 'role' of the content)

4.9 Configure synthesized speech rate (P1)

(Original)

1. Allow configuration of the synthesized speech rate, according to the full range offered by the speech synthesizer.

Normative inclusions and exclusions

1. Conformance profile labels: Speech

Notes

• The range of synthesized speech rates offered by the speech synthesizer may depend on natural language.

UAAG2 ISSUES

• this is very screen reader specific.most UA that are self-voiceing are using extensions or plug-ins

(where do plug-in and extensions fit in UAAG?) [editor note: this may be irrelevant, as the checkpoint only pertains to UA attempting compliance in the Speech area]

• JR: I think all the speech items need a group discussion

4.10 Configure synthesized speech volume (P1)

(Original)

1. Allow control of the synthesized speech volume, independent of other sources of audio.

Normative inclusions and exclusions

1. The user control required by this checkpoint includes the ability to override author-specified synthesized speech volume.
2. Conformance profile labels: Speech

Notes

• See checkpoint 4.8 for information about independent volume control of different sources of audio.

UAAG2 ISSUES

• JR: I think all the speech items need a group discussion

4.11 Configure synthesized speech characteristics (P1)

(Original)

1. Allow configuration of synthesized speech characteristics according to the full range of values offered by the speech synthesizer.

Normative inclusions and exclusions

1. Conformance profile labels: Speech

Notes

• Some speech synthesizers allow users to choose values for synthesized speech characteristics at a higher abstraction layer, i.e., by choosing from present options that group several characteristics. Some typical options one might encounter include: voice (e.g., adult male voice, female child voice, robot voice), pitch, and stress. Ranges for values may vary among speech synthesizers.

UAAG2 ISSUES

• JR: I think all the speech items need a group discussion

4.12 Specific synthesized speech characteristics (P2)

(Original)

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.

Normative inclusions and exclusions

1. Conformance profile labels: Speech

Notes

• This checkpoint is more specific than checkpoint 4.11. It requires support for the voice characteristics listed in the provisions of this checkpoint. Definitions for these characteristics are based on descriptions in section 19 of the Cascading Style Sheets Level 2 Recommendation [CSS2]; refer to that specification for additional informative descriptions. Some speech synthesizers allow users to choose values for synthesized speech characteristics at a higher abstraction layer, for example, by choosing from present options distinguished by gender, age, or accent. Ranges of values may vary among speech synthesizers.

UAAG2 ISSUES

• All (1-4) This is very dependent on the speech synthesizer and beyond the control of the UA [editor note: delete this. CP is only for Speech conformance]

• JR: I think all the speech items need a group discussion

4.13 Configure synthesized speech features (P2)

(Original)

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.

Normative inclusions and exclusions

1. Conformance profile labels: Speech

Notes

• Definitions for the functionalities listed in the provisions of this checkpoint are based on descriptions in section 19 of the Cascading Style Sheets Level 2 Recommendation [CSS2]; refer to that specification for additional informative descriptions.

UAAG2 ISSUES

• may not be completely controllable by the UA. there is negotiation between html, UA rendering, and text to speech engine.
• allow user to control components (speech characteristics) seperately, but there may be a synergistic effect with in the TTS, and additional synergies with other markup (Voice XML, etc.)
• settings feed off of each other with unexpected consequences. User is unsure which componnent is at fault...UA, or TTS, or markup
• symbols and dictionary definitions, are unique to each TTS, it is a speech setting of sorts
• TTS is trying to determine context of string of information to determine inflection, etc
• difficult to control, sythesizer has specific settings different from html settings. e.g. HP (Hewelt Packard), configure UA to not expand abbr, then send HP to synthsizer, and sythesizer says 'horsepower' as its own generated expansion.

• JR: Not sure what to do here – but checkpoint seems badly named – maybe "Configure the Format of Synthesized Speech"

• JR: I think all the speech items need a group discussion

4.14 Choose style sheets (P1)

(Original)

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.

Normative inclusions and exclusions

1. This checkpoint only applies to user agents that support style sheets.

Notes

• By definition, the user agent's default style sheet is always present, but may be overridden by author or user styles. Developers should not consider that the user's ability to turn off author and user style sheets is an effective way to improve content accessibility; turning off style sheet support means losing the many benefits they offer. Instead, developers should provide users with finer control over user agent or content behavior known to raise accessibility barriers. The user should only have to turn off author and user style sheets as a last resort.

UAAG2 ISSUES

• user selectable javascript changing DOM on page load (where does this fit in guidelines) http://www.opera.com/support/tutorials/userjs/

• JR: Hard to imagine a P1 requirement for user defined Javascript

Guideline 5. Ensure user control of user interface behavior

5.1 No automatic content focus change (P2)

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.

Sufficient techniques

1. To satisfy provision one of this checkpoint, configuration is preferred, but is not required if the content focus can only ever be moved on explicit user request.

Normative inclusions and exclusions

UAAG2 ISSUES

5.2 Keep viewport on top (P2)

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.

Normative inclusions and exclusions

UAAG2 ISSUES

5.3 Manual viewport open only (P2)

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.

Sufficient techniques

1. To satisfy provision one of this checkpoint, configuration is preferred, but is not required if viewports can only ever open on explicit user request.

Normative inclusions and exclusions

1. If a viewport (e.g., a frame set) contains other viewports, the provisions of this checkpoint only apply to the outermost container viewport.
2. User creation of a new viewport (e.g., empty or with a new resource loaded) through the user agent's user interface constitutes an explicit user request.

Note

• Generally, viewports open automatically as the result of instructions in content. See also checkpoint 5.1 (for control over changes of focus when a viewport opens) and checkpoint 6.6 (for programmatic notification of changes to the user interface).

UAAG2 ISSUES

5.4 Selection and focus in viewport (P2)

1. Ensure that when a viewport's selection or content focus changes, it is at least partially in the viewport after the change.

Normative inclusions and exclusions

1. Conformance profile labels: Selection

Note

• For example, if users navigating links move to a portion of the document outside a graphical viewport, the viewport should scroll to include the new location of the focus. Or, for users of audio viewports, allow configuration to render the selection or focus immediately after the change.

UAAG2 ISSUES

5.5 Confirm form submission (P2)

1. Allow configuration to prompt the user to confirm (or cancel) any form submission.

Sufficient techniques

1. Configuration is preferred, but is not required if forms can only ever be submitted on explicit user request.

Normative inclusions and exclusions

Note

• Examples of automatic form submission include: script-driven submission when the user changes the state of a particular form control (e.g., via the pointing device), submission when the user has interacted with all form controls, and submission when an onmouseover or onchange event occurs.

UAAG2 ISSUES

Proposal 5.x Allow configuration to allow users to open viewports with full user interface or author specified user interface. ja: Nov 4 2007

ja: fixes javascript opening windows with no scroll bars, etc.

Guideline 6. Implement interoperable application programming interfaces

6.1 Programmatic access to HTML/XML infoset (P1)

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.

Normative inclusions and exclusions

UAAG2 ISSUES

• A major concern with these 2 guidelines (6.1 & 6.2) is that out-of-process DOM APIs (such as accessibility APIs and ISimpleDOMNode) are often readonly and not read/write, which can be a problem for users of these APIs, such as ATs.

• But in-process APIs, such as JavaScript and XUL, which are used by plugins, extensions, and DHTML/AJAX Web applications, are read-write so there isn't a problem for them.

*CL: The requirement to provide read/write access should exist at least in-process - unless we want to ensure read/write access by both in-process and out-of-process APIs, especially since a screen reader is usually out-of-process. But then there are security issues to address for out-of-process.

*CL: Add a definition of "programmatic access" and "programmatic read access" based on the WCAG definition of "programmatically determined", such as "exposed to an assistive technology through an accessibility API that is supported by commonly available assistive technology."

*CL: The ARIA specs state a requirement about mapping roles, states, and properties to an adaptive interface or accessibility API for an operating system. This requirement could be more explicit in these guidelines for both ARIA markup as well as HTML 4.01 elements and attributes. Ask PF to define "adaptive interface." Define "accessibility API" as a programming interface for an application to provide, and an assistive technology to obtain, information about documents, applications, objects (aka elements) and attributes, characters, and events.

6.2 DOM access to HTML/XML content (P1)

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.

Normative inclusions and exclusions

1. Refer to the "Document Object Model (DOM) Level 2 Core Specification" [DOM2CORE] for information about which versions of HTML, XML, Java, and ECMAScript are covered. Appendix D contains the Java bindings and Appendix E contains the ECMAScript bindings.
2. The user agent is not required to export the bindings outside of the user agent process (though doing so may be useful to assistive technology developers).

Notes

• This checkpoint stands apart from checkpoint 6.1 to emphasize the distinction between what information is required and how to provide access to that information. Furthermore, the DOM Level 2 Core Specification does not provide access to current states and values referred to in provision three of checkpoint 6.1. For HTML content, the interfaces defined in [DOM2HTML] do provide access to current states and values.

UAAG2 ISSUES

• A major concern with these 2 guidelines (6.1 & 6.2) is that out-of-process DOM APIs (such as accessibility APIs and ISimpleDOMNode) are often readonly and not read/write, which can be a problem for users of these APIs, such as ATs.

But in-process APIs, such as JavaScript and XUL, which are used by plugins, extensions, and DHTML/AJAX Web applications, are read-write so there isn't a problem for them.

6.3 Programmatic access to non-HTML/XML content (P1)

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.

Normative inclusions and exclusions

1. "Structured programmatic access" means access through an API to recognized information items of the content (such as the information items of the XML Infoset [INFOSET]). Plain text has little structure, so an API that provides access to it will be correspondingly less complex than an API for XML content. For content more structured than plain text, an API that only provides access to a stream of characters does not satisfy the requirement of providing structured programmatic access. This document does not otherwise define what is sufficiently structured access.
2. An API is considered "available" if the specification of the API is published (e.g., as a W3C Recommendation) in time for integration into a user agent's development cycle.

Notes

• This checkpoint addresses content not covered by checkpoints 6.1 and 6.2.

UAAG2 ISSUES

6.4 Programmatic access to information about rendered content (P1)

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.

*CL: Should be provision three of checkpoint 6.3.

*CL: We should consider combining 6.1 - 6.4. The techniques sections describe why there are separate guidelines - separating what info from how to provide, and HTML vs DOM vs non-HTML vs graphical content. But there is a lot of duplication. Need to decide if UAAG should require both DOM and accessibility APIs, especially in light of the fact that ATs don't want to get ARIA info out of the DOM.

Normative inclusions and exclusions

Notes

• User agents should provide programmatic access to additional useful information about rendered content that is not available through the APIs required by checkpoints 6.2 and 6.3, including the correspondence (in both directions) between graphical objects and their source in the document object, and information about the role of each graphical object.

UAAG2 ISSUES

6.5 Programmatic operation of user agent user interface (P1)

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.

*CL: Should be provision three of checkpoint 6.3.

Normative inclusions and exclusions

1. For security reasons, user agents are not required to allow instructions in content to modify user agent user interface controls. See more information on security considerations.
2. Conformance detail: For user agent features

Notes

• APIs used to satisfy the requirements of this checkpoint may vary. For instance, they may be independent of a particular operating environment (e.g., the W3C DOM), or the conventional APIs for a particular operating environment, or the conventional APIs for programming languages, plug-ins, or virtual machine environments. User agent developers are encouraged to implement APIs that allow assistive technologies to interoperate with multiple types of software in a given operating environment (e.g., user agents, word processors, and spreadsheet programs), as this reuse will benefit users and assistive technology developers. User agents should always follow operating environment conventions for the use of input and output APIs.

UAAG2 ISSUES

6.6 Programmatic notification of changes (P1)

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.

*CL: Should be provision three of checkpoint 6.3.

Normative inclusions and exclusions

1. The user agent is not required to provide notification of changes in the rendering of content (e.g., due to an animation effect or an effect caused by a style sheet) unless the document object is modified as part of those changes.
2. Conformance profile labels: Selection
3. Conformance detail: For both content and user agent

Notes

• For instance, provide programmatic notification when user interaction in one frame causes automatic changes to content in another.

UAAG2 ISSUES

• not all events are referenced in the DOM

not just limit notifications to AT through the DOM should include notification through the accessibility API

• no caret indicator in the DOM, AT must rely on accessibility api for caret informaton/location
• AJAX = html + css+ javascript, accessibility tools can access dom for js events and html, but css changes are difficult
• issue: this may be out of date. in past calls we have talked about UAs increasingly relying on API rather than the DOM. How do we update this exclusion?

6.7 Conventional keyboard APIs (P1)

1. Implement APIs for the keyboard as follows:
   • Follow operating environment conventions.
   • If no conventions exist, implement publicly documented APIs.

*ckl: 2. Establish and document how the user agent resolves key binding conflicts between the user agent user interface, user agent extensions (e.g plug-ins), HTML elements (i.e. accesskeys), and JavaScript functions (i.e. keypress events). If a keystroke is not defined by the user agent user interface,the user agent should pass it on to the user agent extensions, HTML elements, then JavaScript functions, in that order. Not sure we should be this prescriptive - just throwing it out there for discussion.

Normative inclusions and exclusions

Notes

• An operating environment may define more than one conventional API for the keyboard. For instance, for Japanese and Chinese, input may be processed in two stages, with an API for each stage.

UAAG2 ISSUES

• plug-in keybindings, more conflicts with UA, AT
• if plug-in does not need a key, it should pass it on to the UA, not swallow it.
• Plug-ins should have some pass through to the UA function
• chaining, if something higher up the api chain gets a key lower level api may not see the event

6.8 API character encodings (P1)

1. For an API implemented to satisfy requirements of this document, support the character encodings required for that API.

Normative inclusions and exclusions

1. Conformance detail: For both content and user agent

Notes

• Support for character encodings is an important part of ensuring that text is correctly communicated to assistive technologies. For example, the DOM Level 2 Core Specification [DOM2CORE], section 1.1.5 requires that the DOMString type be encoded using UTF-16.

UAAG2 ISSUES

6.9 DOM access to CSS style sheets (P2)

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:
3. 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
4. In other operating environments, the exported bindings (e.g., C++) must be publicly documented.

Normative inclusions and exclusions

1. For the purposes of satisfying this checkpoint, Cascading Style Sheets (CSS) are defined by either CSS Level 1 [CSS1] or CSS Level 2 [CSS2].
2. Refer to the "Document Object Model (DOM) Level 2 Style Specification" [DOM2STYLE] for information about which versions of Java and ECMAScript are covered. Appendix B contains the Java bindings and Appendix C contains the ECMAScript bindings.
3. The user agent is not required to export the bindings outside of the user agent process.

UAAG2 ISSUES

6.10 Timely exchanges through APIs (P2)

1. For APIs implemented to satisfy the requirements of this document, ensure that programmatic exchanges proceed in a timely manner.

Normative inclusions and exclusions

1. Conformance detail: For both content and user agent

Notes

• For example, the programmatic exchange of information required by other checkpoints in this document should be efficient enough to prevent information loss, a risk when changes to content or user interface occur more quickly than the communication of those changes. Timely exchange is also important for the proper synchronization of alternative renderings. The techniques for this checkpoint explain how developers can reduce communication delays. This will help ensure that assistive technologies have timely access to the document object model and other information that is important for providing access.

UAAG2 ISSUES

• define 'timely'
• chaining, if something higher up the api chain gets a key lower level api may not see the event
• UA extensions keybinding conflicts, big conflicts. keybinding negotiation (extension, content access key, plugins)

perhaps assign keys to roles, or similar to fonts have a list of proposed keys with fallback options

• Situations in which an API exchange is too slow include, but are not limited to, the following:
  • The user agent updates the content in the active view but does not indicate the change through the API in a timely manner such that an AT can update its cached content before the next user query or command. As a result, the user ends up working with stale content.
  • The user agent processes user input but does not indicate confirmation through the API in a timely manner such that the user knows the input was received. As a result, the user is apt to think the input was lost and repeat the action.

Guideline 7. Observe operating environment conventions

7.1 Respect focus and selection conventions (P1)

1. Follow operating environment conventions that benefit accessibility when implementing the selection, content focus, and user interface focus.

Normative inclusions and exclusions

1. This checkpoint is mutually exclusive of checkpoint 7.3 since it has a higher priority.

Conformance profile labels: Selection

Notes

• See checkpoints 9.1 and 9.2 for more information about content focus and user interface focus.

UAAG2 ISSUES

• Selection in browser content is problematic - some browsers don't allow content selection from the keyboard

7.2 Respect input configuration conventions (P1)

1. Ensure that default input configurations of the user agent do not interfere with operating environment accessibility conventions (e.g., for keyboard accessibility).

Normative inclusions and exclusions

1. Conformance detail: For user agent features

Notes

• Information about operating environment accessibility conventions is available in the Techniques document [UAAG10-TECHS]. See checkpoint 11.5 for information about the user agent's default input configuration.

UAAG2 ISSUES

7.3 Respect operating environment conventions (P2)

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.

Normative inclusions and exclusions

1. For the purposes of this checkpoint, an operating environment convention that benefits accessibility is either

one identified as such in operating environment design or accessibility guidelines, or one that allows the author to satisfy any requirement of the "Web Content Accessibility Guidelines 1.0" [WCAG10] or of the current document.

1. This checkpoint excludes the requirements of checkpoints 7.1 and 7.4.
2. Conformance detail: For user agent features

Notes

• Some of these conventions (e.g., sticky keys, mouse keys, and show sounds) are discussed in the Techniques document [UAAG10-TECHS].

UAAG2 ISSUES

• There are some issues between AJAX widgets/controls and High contrast mode and alternate keyboard interfaces (sticky keys)

7.4 Provide input configuration indications (P2)

1. Follow operating environment conventions to indicate the input configuration.

Normative inclusions and exclusions

1. This checkpoint is mutually exclusive of checkpoint 7.3 to emphasize the importance of consistency in input configurations.
2. Conformance detail: For user agent features

Notes

• For example, in some operating environments, when a functionality may be triggered through a menu and through the keyboard, the developer may design the menu entry so that the character of the activating key is also shown. See checkpoint 11.5 for information about the user agent's default input configuration.

UAAG2 ISSUES

Guideline 8. Implement specifications that benefit accessibility

8.1 Implement accessibility features (P1)

1. Implement the accessibility features of specifications (e.g., markup languages, style sheet languages, metadata languages, and graphics formats).

Normative inclusions and exclusions

1. This checkpoint applies to both W3C-developed and non-W3C specifications.
2. For the purposes of this checkpoint, an accessibility feature of a specification is either:
   • one identified as such in the specification, or
   • one that allows the author to satisfy any requirement of the "Web Content Accessibility Guidelines 1.0" [WCAG10].
3. The user agent is not required to satisfy this checkpoint for all implemented specifications; see the section on conformance profiles for more information.
4. Conformance detail: For all content

Notes

• The Techniques document [UAAG10-TECHS] provides information about the accessibility features of some specifications, including W3C specifications.

UAAG2 ISSUES

• what kind of information are we trying to convey to the user about the relationsship of columnes in a colgroup. What is the UA supposed to communicate to the user.
• TABINDEX and ACCESSKEY as curently implementd are confusing to end users. Although TABINDEX=-1 and ACCESSKEY are used extensively in AJAX and new web applications. How to resolve?

8.2 Conform to specifications (P2)

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

Sufficient techniques

1. When a requirement of another specification contradicts a requirement of the current document, the user agent may disregard the requirement of the other specification and still satisfy this checkpoint.

Normative inclusions and exclusions

1. A specification is considered "available" if it is published (e.g., as a W3C Recommendation) in time for integration into a user agent's development cycle.
2. The user agent is not required to satisfy this checkpoint for all implemented specifications; see the section on conformance profiles for more information.
3. Conformance detail: For all content

Notes

• For instance, for markup, the user agent may conform to HTML 4 [HTML4], XHTML 1.0 [XHTML10], and/or XML 1.0 [XML]. For style sheets, the user agent may conform to CSS ([CSS1], [CSS2]). For mathematics, the user agent may conform to MathML 2.0 [MATHML20]. For synchronized multimedia, the user agent may conform to SMIL 1.0 [SMIL].

UAAG2 ISSUES

• Should this be removed due to vagueness. Can you pick an choose conformance to specifications. Or, must a UA conform to all specifications for all item in the UAAG conformance claim.

Guideline 9. Provide navigation mechanisms

9.1 Provide content focus (P1)

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.

Normative inclusions and exclusions

1. When a viewport includes no enabled elements (either because the format does not provide for this, or a given piece of content has no enabled elements), the content focus requirements of the following checkpoints do not apply: 1.2, 5.1, 5.4, 6.6, 7.1, 9.3, 9.4, 9.5, 9.6, 9.7, 10.2, and 11.5.

Notes

• For example, when two frames of a frameset contain enabled elements, allow the user to make the content focus of either frame the current focus. Note that viewports "owned" by plug-ins that are part of a conformance claim are also covered by this checkpoint. See checkpoint 7.1 for information about implementing content focus according to operating environment conventions.

UAAG2 ISSUES

• need to update the definitons of "enable elements" and "interactive elements" to provide for components used in DHTML/AJAX. Definition change may impact the scope of other checkpoints.
• Where is the line drawn between what the UA vs Author coding should do to provide for accessibility.

Proposals

• Definition of "interactive element" needs to no longer say that the interactive elements are defined by specification alone since any element can be made interactive with JS.
  • "An interactive element is piece of content that, by specification or by programmatic enablement, may have associated behaviors to be executed or carried out as a result of user or programmatic interaction." etc.
• UA should provide focus to chrome elements, all standard HTML form widgets, all elements set to receive focus according to author markup, and any HTML elements made interactive by their rendering (e.g. scrollable divs, scrollable iframes).

9.2 Provide user interface focus (P1)

1. Provide a user interface focus.

Normative inclusions and exclusions

Notes

• See checkpoint 7.1 for information about implementing user interface focus according to operating environment conventions.

UAAG2 ISSUES

• are extensions to the user interface (chrome) considered part of the 'base' UA? Should extensions conform to UAAG? We think, yes. Does UAAG need addtional checkpoints to cover this? Will adding techniqes to cover this, change the scope of the checkpoint?
• Definition of Content. Related to Compound Documents and DHTML/AJAX. Focus management between base UA and nested/child UA (Object, flash, mathml, svg). Also, applications within web content that create a new user interface. Is this new application with it's own user interface considered a new embedded UA that must conform to UAAG or just more content?

Proposals

• User agent is responsible for providing user interface focus to chrome extensions. (If it knows how to insert and render the extension in its chrome, then it should have good enough programmatic access and knowledge to properly give focus.)
• User agent is responsible for notifying any nested user agent that focus should move into it (but the outer UA can't control whether or not the inner one respects focus).
  • Outermost UA (browser?) should provide a way to skip over misbehaving embedded UAs that "eat" focus.

9.3 Move content focus (P1)

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.

Sufficient techniques

1. To satisfy provision two of this checkpoint, configuration is preferred, but is not required if the content focus only ever changes on explicit user request.

Normative inclusions and exclusions

1. The user agent may also include disabled elements in the navigation order.

Notes

• In addition to forward sequential navigation, the user agent should also allow reverse sequential navigation. See checkpoint 9.9 for information about structured navigation. See checkpoints 5.1 and 6.6 for more information about focus changes.

UAAG2 ISSUES

• consider combining 9.3 (move content focus forward) with 9.7 (move content focus reverse). Add 'moving backward' to requirement 1 of 9.3. Moving content focus forward and backward is standard functionality in UAs.

Proposal

• To combine with backward, remove note and make first requirement explicit:
  • Allow the user to move the content focus forward or backward to any enabled element in the viewport.

9.4 Restore viewport state history (P1)

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.

Normative inclusions and exclusions

1. The viewport history associates values for these three state variables (point of regard, content focus, and selection) with a particular document object. If the user returns to a state in the history and the user agent retrieves new content, the user agent is not required to restore the saved values of the three state variables.
2. Conformance profile labels: Selection

UAAG2 ISSUES

• browser has base functionality to save the 3 states- but content and user configuration can change this. Need to add to Note:. This may change scope of the check point.

Proposals

• Add Note saying "Both user agent settings and scripts in content may affect the ability of the UA to restore state history. The UA is not responsible for overcoming these factors."

9.5 No events on focus change (P2)

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.

Normative inclusions and exclusions

1. Conformance profile labels: Events

Notes

• For instance, in this configuration for an HTML document, do not activate any handlers for the onfocus, onblur, or onchange attributes. In this configuration, user agents should still apply any stylistic changes (e.g., highlighting) that may occur when there is a change in content focus.

UAAG2 ISSUES

• the UA does not know know the state of event handlers.
• events on DHTML controls, related to WAI_ARIA

Proposals

• When is not activating event handlers beneficial? Is this checkpoint even desired now that many Web pages included JS-driven interactive content?

9.6 Show event handlers (P2)

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.

Normative inclusions and exclusions

1. Conformance profile labels: Events

Notes

• For example, allow the user to query the element with content focus for the list of input device event types, or add them directly to the sequential navigation order described in checkpoint 9.3. See checkpoint 1.2 for information about activation of event handlers associated with the element with focus.

UAAG2 ISSUES

9.7 Move content focus in reverse (P2)

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.

Normative inclusions and exclusions

UAAG2 ISSUES

Proposals

• Combine with 9.3. See proposals in that section.

9.8 Provide text search (P2)

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.

Normative inclusions and exclusions

Conformance detail: For all rendered content

Notes

• If the user has not indicated a start position for the search, the search should start from the beginning of content. Per checkpoint 7.3, use operating environment conventions for indicating the result of a search.

UAAG2 ISSUES

• allow searching within conditional content. Also, what happens when condtional content - "alt" (images on) become rendered content - "alt" (images off)
• Remove requirement 2 of 9.8.. removing requirement for "forward" search implies that requiement 1 includes the current functionality of UAs providing forward/backward search functionality [3]

Proposals

• Whether conditional content is rendered or not, it should be searched if it's intended for human consumption, exists in the markup of the page, and is not hidden via a style attribute.
• Yes, remove 9.8 requirement 2.

9.9 Allow structured navigation (P2)

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.

Normative inclusions and exclusions

Notes

• This specification intentionally does not identify which "important elements" must be navigable as this will vary by specification. What constitutes "efficient navigation" may depend on a number of factors as well, including the "shape" of content (e.g., sequential navigation of long lists is not efficient) and desired granularity (e.g., among tables, then among the cells of a given table). Refer to the Techniques document [UAAG10-TECHS] for information about identifying and navigating important elements.

UAAG2 ISSUES

• Change "allow" to "provide", structured navigation should be provided natively, not added on by AT.
• Issue/Technique: add technique or requirement stating that UA must provide object attributes (element name and roles, etc.) to the accessibiltiy API to enable structured navigation function by AT

this is an issue if we change wording to "provide" this is a technique if wording remais as "allow"

Proposals

• If "provide":
  • "Provide efficient navigation over important structural elements in rendered content."
• Why is exposing role/state information to accessibility API an issue if providing but only a technique if allowing? Information needs to be exposed regardless so the AT can report role/state information whether the UA is doing the structured nav or the AT is driving it. But it is more important if the AT is in charge.

9.10 Configure important elements (P3)

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.

Normative inclusions and exclusions

Notes

• For example, allow the user to navigate only paragraphs, or only headings and paragraphs, or to suppress and restore navigation bars, or to navigate within and among tables and table cells.

UAAG2 ISSUES

• consider removing and adding as a "doing more "technique for 9.9 and 10.4, or adding configuration as a requirement for 9.9 and 10.4.

Proposals

• Depends on group consensus.

Guideline 10. Orient the user

10.1 Associate table cells and headers (P1)

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

Sufficient techniques

1. The user agent may satisfy this checkpoint by allowing the user to query each table cell for associated header information.
2. 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

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

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.

Normative inclusions and exclusions

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

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

Normative inclusions and exclusions

1. Conformance profile labels: Selection

UAAG2 ISSUES

10.4 Provide outline view (P2)

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

Normative inclusions and exclusions

1. 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.
2. 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.
3. 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)

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.

Normative inclusions and exclusions

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

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.

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)

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

Sufficient techniques

1. 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.
2. 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

1. For two-dimensional spatial renderings, relative position includes both vertical and horizontal positions.
2. 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.

UAAG2 ISSUES

Guideline 11. Allow configuration and customization

11.1 Current user input configuration (P1)

1. Provide information to the user about current user preferences for input configurations.

Sufficient techniques

1. To satisfy this checkpoint, the user agent may make available binding information in a centralized fashion (e.g., a list of bindings) or a distributed fashion (e.g., by listing keyboard shortcuts in user interface menus). See related documentation checkpoints 12.2, 12.3, and 12.5.

Normative inclusions and exclusions

1. Conformance detail: For user agent features

UAAG2 ISSUES

11.2 Current author input configuration (P2)

1. Provide a centralized view of the current author-specified input configuration.

Sufficient techniques

1. The user agent may satisfy this checkpoint by providing different views for different input modalities (keyboard, pointing device, and voice).

Normative inclusions and exclusions

1. Conformance detail: For all content

Notes

• For example, for HTML documents, provide a view of keyboard bindings specified by the author through the accesskey attribute. The intent of this checkpoint is to centralize information about author-specified bindings so that the user does not have to read an entire document to learn about available bindings.

UAAG2 ISSUES

• Should the user be able to override (change) these input configurations in the UA
• How should UA expose author specified keybindings that occur in javascript or other scripting which are not exposed in the DOM or to accessibility APIs. [should the be a WCAG requirement?]

11.3 Allow override of bindings (P2)

1. Allow the user to override any binding that is part of the user agent default input configuration.

Normative inclusions and exclusions

1. The user agent is not required to allow the user to override conventional bindings for the operating environment (e.g., for access to help).
2. The override requirement only applies to bindings for the same input modality (e.g., the user must be able to override a keyboard binding with another keyboard binding).
3. This checkpoint excludes the requirements of checkpoint 11.4.
4. Conformance detail: For user agent features

Notes

• See checkpoint 11.5 for default input configuration requirements and checkpoint 12.3 for information about their documentation.

UAAG2 ISSUES

• move 'doing more' 2. Allow users to easily restore the default input configuration.

to be a Normative Inclusion

• add Normative Inclusion: When user overrides a binding the UA must update the current iinput configuration (in order to meet 11.1 requiarements)

11.4 Single-key access (P2)

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.

Sufficient techniques

1. The user agent may satisfy the requirements of provision two of this checkpoint with a "single-key mode." In a single-key mode, the complete set of functionalities required by provision two must be available through single-key bindings. The user must be able to remain in single-key mode until explicitly requesting to leave it.

Normative inclusions and exclusions

1. In this checkpoint, "key" refers to a physical key of the keyboard (rather than, say, a character of the document character set).
2. The user agent is not required to allow the user to override conventional bindings for the operating environment (e.g., for access to help).
3. Provision two of this checkpoint does not require single physical key bindings for character input, only for the activation of user agent functionalities.
4. If the number of physical keys on the keyboard is less than the number of functionalities required by checkpoint 11.5, then provision two of this checkpoint does not require the user agent to allow single-key bindings for all of the functionalities. The user agent should give preference to those functionalities listed in provision one of checkpoint 11.5.
5. This checkpoint is mutually exclusive of checkpoint 11.3 since it is specific to the keyboard and to emphasize the importance of easy keyboard access.
6. Conformance detail: For user agent features

Notes

• Because single-key access is so important to some users with physical disabilities, user agents should ensure that: (1) most keys of the physical keyboard may be configured for single-key bindings, and (2) most functionalities of the user agent may be configured for single-key bindings. For information about access to user agent functionality through a keyboard API, see checkpoint 6.7.

UAAG2 ISSUES

11.5 Default input configuration (P2)

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.

Sufficient techniques

1. The user agent may satisfy the functionality of entering a URI for a new resource in a number of ways, including by prompting the user or by moving the user interface focus to a control for entering URIs.

Normative inclusions and exclusions

1. Conformance detail: For user agent features

Notes

• This checkpoint does not make any requirements about the ease of use of default input configurations, though clearly the default configuration should include single-key bindings and allow easy operation. Ease of use is addressed by the configuration requirements of checkpoint 11.3.

UAAG2 ISSUES

11.6 User profiles (P2)

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

Normative inclusions and exclusions

1. This checkpoint does not require the user agent to provide multiple default profiles.
2. This checkpoint does not require that user profiles be portable (i.e., removable from the user agent to be reread by a different instance of the user agent). Portable user profiles are very useful, however.
3. Conformance detail: For user agent features

UAAG2 ISSUES

11.7 Tool bar configuration (P3)

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.

Normative inclusions and exclusions

1. Conformance detail: For user agent features

UAAG2 ISSUES

Guideline 12. Provide accessible user agent documentation and help

12.1 Provide accessible documentation (P1)

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

Normative inclusions and exclusions

1. Conformance detail: For user agent features

UAAG2 ISSUES

12.2 Provide documentation of accessibility features (P1)

1. Provide documentation of all user agent features that benefit accessibility.

Sufficient Techniques

1. The user agent may satisfy this checkpoint either by
   • providing a centralized view of the accessibility features, or
   • integrating accessibility features into the rest of the documentation.

A centralized view is sufficient to satisfy this checkpoint and is required to satisfy checkpoint 12.5.

Normative inclusions and exclusions

1. For the purposes of this checkpoint, a user agent feature that benefits accessibility is one implemented to satisfy the requirements of this document (including the requirements of checkpoints 8.1 and 7.3, and the API requirements of guideline 6).
2. Conformance detail: For user agent features

Notes

• The help system should include discussion of user agent features that benefit accessibility. The user agent should satisfy this checkpoint by providing both centralized and integrated views of accessibility features in the documentation.

UAAG2 ISSUES

• see http://lists.w3.org/Archives/Public/w3c-wai-ua/2006OctDec/0049.html

• Update normative inclusion 1. to include "only if a feature is implemented" (the inclusion specifies the requirements of 8.1, 7.3, and guideline 6. some of the requirements may not be implemented, and the UA should not have to document them) (conformance for 12.2 is determined by dcoumentation, not implementation.)

12.3 Provide documentation of default bindings (P1)

1. Provide documentation of the default user agent input configuration (e.g., the default keyboard bindings).

ckl: 2. Establish and document how the user agent resolves key binding conflicts between the user agent user interface, user agent extensions (e.g plug-ins), HTML elements (i.e. accesskeys), and javascript functions (i.e. keypress events).

Sufficient Techniques

1. If the user agent does not allow the user to override the default user agent input configuration (see checkpoint 11.3), the documentation used to satisfy this checkpoint also satisfies checkpoint 11.1.

Normative inclusions and exclusions

1. Conformance detail: For user agent features

Notes

• Documentation should warn the user whenever the default input configuration is inconsistent with conventions of the operating environment.

UAAG2 ISSUES

• Remove sufficient technique from 12.3 (poorly worded and a statement of fact)

12.4 Provide documentation of changes between versions (P2)

1. Provide documentation of changes since the previous version of the user agent to features that benefit accessibility.

Normative inclusions and exclusions

1. The features that benefit accessibility are those defined in checkpoint 12.2.
2. Conformance detail: For user agent features

UAAG2 ISSUES

12.5 Provide dedicated accessibility section (P2)

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

Sufficient Techniques

1. A centralized view is required to satisfy this checkpoint and is sufficient to satisfy checkpoint 12.2.

Normative inclusions and exclusions

1. The features that benefit accessibility are those defined in checkpoint 12.2.
2. Conformance detail: For user agent features

UAAG2 ISSUES

• needs clarification in wording in normative inclusion 1, specifing user agent features rather than content.
• expand Normative inclustion to include content info from 8.1 and techniques of 12.2