#

level

wording

editor/Applicability Notes

action/issue

rework

comments

111

a

Configurable Default Rendering: The user can specify which types of alternative content to render by default.

no

needs work - handle wrong

112

a

Browse and Render: When a rendered element has alternative content, the user can render alternatives according to the following: * synchronized alternatives for time-based media (e.g. captions, audio descriptions, sign language) can be rendered at the same time as their associated audio tracks and visual tracks, * and non-synchronized alternatives (e.g. short text alternatives, long descriptions) can be rendered as replacements for the original rendered content.

no

address the ability to have the alternative content presented to you without replacing the default version, e.g. display title or alt text in pop-up or tooltip?

121

a

Repair Missing Alternatives: The user can specify whether or not the user agent should generate and render repair text (e.g. file name) when it recognizes that the author has not provided alternative content.

no

this sounds like what people curse about MSWord, predicting what you want to do. or what it thinks you mean

131

a

 Highlighted Items: The user can globally specify that the following be highlighted so that each class is uniquely distinguished. It is not the intention that all recognized enabled elements be uniquely distinguished, just that they be distinguished from disabled elements. a. selection, b. active keyboard focus (indicated by focus cursors and/or text cursors), c. recognized enabled elements, d. presence of alternative content, e. recently visited links

no

review, too many options, should say "these could include". should remove f. presence of alternative content

133

aa

Highlighted Input Controls: The user can have the following highlighted when they are recognized: (a) enabled controls that take input (e.g. push buttons, radio buttons, check boxes, and text input fields, but not groupings or static text and images) regardless of whether they are read-write or read-only, and (b) elements with scripted input handlers (e.g. images or text ranges that have onClick or onKeyPress events) regardless of whether the current state allows them to operate.

no

review, reword, add auditory

184

a

Viewport Scrollbars: Graphical viewports include scrollbars if the rendered content (including after user preferences have been applied) extends beyond the viewport dimensions, overriding any values specified by the author.

a-634

no

185

a

Viewport History: For user agents that implement a viewport history mechanism (e.g. "back" button), the user can return to any state in the viewport history, restoring the prior point of regard, input focus and selection.

no

jan rewrite

1102

aa

 Outline View: An outline view of rendered content is provided, composed of labels for important structural elements (e.g. heading text, table titles, form titles, and other labels that are part of the content).  Note: The outline constitutes the important structural elements for the user (See 1.10.3). 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.

a-639

no

jan reword. 2.5.7 ??

1112

aaa

Extended Link Information: The user agent provides for each link:  * link title, * technology type (of the linked Web resource), * internal/external: (whether the link is internal to the resource e.g. the link is to a target in the same Web page)

no

mail thread

211

a

Keyboard Operation: All functionality can be operated via the keyboard using sequential or direct keyboard commands that do not require specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g. free hand drawing). This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

no

working on bluedog term

222

a

Sequential Navigation Between Viewports: The user can move the keyboard focus backwards and forwards between viewports, without having to sequentially navigate all the elements in a viewport.

combine 213 here, remove 213

224

aa

Options for Wrapping in Navigation: When user interaction with web content causes focus wrapping at the@@, the user can prevent wrapping or the user can receive feedback when wrapping

no

232

a

Present Direct Commands in Rendered Content: The user can have any recognized direct commands in rendered content (e.g. accesskey, landmark) be presented with their associated elements.

a-656

no

234

aa

Present Direct Commands in User Interface: The user can have any direct commands (e.g. keyboard shortcuts) in the user agent user interface be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button).

a-656

no

235

aa

Allow Override of Accesskeys: The user can override any recognized author supplied content keybinding (i.e. access key). The user must have an option to save the override of user interface keyboard shortcuts so that the rebinding persists beyond the current session.

example - good place to add i18n example, accesskey - o umlaut, but not on local keyboard

no

duplication of 214

275

no

jeanne has action ?moved? Not in document

277

aaa

Portable Preference Settings: The user can transfer preference settings across locations onto a compatible system.

a-641

no

jeanne has action

412

a

Name, Role, State, Value, Description: For all user interface components including user interface, rendered content, generated content, and alternative content, the user agent makes available the name, role, state, value, and description via a platform accessibility architecture

examples -- This needs to be finished and be a legitimate example. Help!, resources -- more needed

a-651, a-649

no

415

a

Write Access: If the user agent keeps an internal representation of the user content in terms of element structure, relationships between elements, element meaning, or some combination thereof, it must expose this internal representation via an appropriate means (normally by using the platform accessibility architecture or a programmatically available DOM).

no

416

a

Properties: If any of the following properties are supported by the accessibility platform architecture, make the properties available to the accessibility platform architecture: a. the bounding dimensions and coordinates of onscreen elements, b. font family of text, c. font size of text, d. foreground color of text, e. background color of text. f. change state/value notifications, g. selection, h. highlighting, i. input device focus, j. direct keyboard commands

a-651

no

421

a

Hand-Off Focus: The user agent programmatically notifies any nested user agent(s) (e.g. plug-ins) when active input focus moves to a nested agent.

i-69, a-587, a-588

no

422

a

Retrieve Focus: At any time, the user is able to retrieve input focus from a nested viewport (including a nested viewport that is a user agent).

i-69, a-586, a-585

no

521

a

Web-Based Accessible (Level A) : User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "A".

no

522

aa

Web-Based Accessible (Level AA) : User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "AA".

no

523

aaa

Web-Based Accessible (Level AAA) : User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "AAA".

no

542

a

Handle Unrendered Technologies: If the user agent does not render a technology, the user can choose a way to handle content in that technology (e.g. by launching another application or by saving it to disk).

no

151

a

Global Volume: The user can independently adjust the volume of all audio tracks, relative to the global volume level set through operating environment mechanisms. If the global setting is mute, the user agent may override a global mute on explicit user request that cautions the user about the implication.

no - believe this is fixed wording matches the comment

no -- possible rewroding -- The user can independently adjust the volume of all audio tracks, relative to the global volume level set through operating environment mechanisms. If the global setting is mute, the user agent may override a global mute on explicit user request that cautions the user about the implication. (Level A)