Jim's email.

Current

2.3.5 Allow Override of Accesskeys (former 2.1.11) : 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. (Level AA)

Intent: Content authors may utilize the Accesskey attribute to define short cut keys which allow quick access to specific elements, actions, or parts of their Web content. The author-selected short cuts may utilize keystrokes that are unique to their site, differing from conventions used, and or familiar, to users of other similar sites, or sites offering similar functionality. Users of assistive technologies who rely upon keyboard input may wish to have a consistent mapping of shortcut keys to similar, or common actions or functions across the sites they visit.

Proposed

2.3.5 Allow Override of Accesskeys (former 2.1.11) : The user can override any recognized author supplied content keybinding (i.e. accesskey attribute in HTML). The user must have an option to save the override of user interface keyboard shortcuts so that the rebinding persists beyond the current session. (Level AA)

Intent: Depending on the markup language, content authors may be able to define short cut keys which allow quick access to specific elements, actions, or parts of their Web content. For example, in HTML, the author may use the Accesskey attribute to define these short cut keys. The author-selected short cuts may utilize keystrokes that are unique to their site, differing from conventions used, and or familiar, to users of other similar sites, or sites offering similar functionality. Users of assistive technologies who rely upon keyboard input may wish to have a consistent mapping of shortcut keys to similar, or common actions or functions across the sites they visit.

Summary

(1 response didn't contain an answer to this question)

Details

From the Kim and Jeanne meeting of 24 June to do an editorial pass of the document

Current

Key methods for achieving that goal include:
optional self-pacing configurability device independence interoperability direct support for both graphical and auditory output adherence to published conventions.

Proposed

To achieve this goal, user agents must:
be configurable
be discoverable
be predictable
provide direct support for both graphical and auditory output
enable optional self-pacing
be device independent
be interoperable
adhere to published conventions

Summary

Details

From the Kelly email

Current

1.2.3 Repair Missing Associations: The user can specify whether or not the user agent should attempt to predict associations from author-specified presentation attributes (i.e. position and appearance). (Level AAA)

Proposed

Delete this SC. I don't know of an UA that does this and it seems really hard to do.

Summary

Details

From the Kim and Jeanne meeting of 24 June to do an editorial pass of the document

Background

1.11.1 was Basic Link Information. It had an IER written. It was deleted and 1.11.3 (Extended Link Information) was renumbered to become the new 1.11.2 with no IER. Should the IER for the old 1.11.1 be used?

Proposed

1.11.2 Extended Link Information: The following information is provided for each link (Level AAA) :
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)

Intent of Success Criterion 1.11.2:
Users who use screen readers need to be able to easily discover information about a link, including the title of the link, whether or not that link is a webpage, PDF etc. and whether the link goes to a new page or a different location in the current page, in order to navigate Web content more quickly and easily.

Examples of Success Criterion 1.11.2:

Robert, who uses a screen reader, needs to know whether a given link will automatically open in a new page or a new window. The browser indicates this information so he can discover it before he makes a decision to click on a link.

Maria has an attention disorder, new windows opening are a large distraction. She needs to know whether a given link will automatically open in a new page or a new window. The browser indicates this information so she can decide not to follow a link that opens a new window.

Summary

Details

From the Kim and Jeanne meeting of 24 June to do an editorial pass of the document

Background

This sentence was found in the printed version of 4.1.5 but was a separate SC that looked like it had been truncated into 4.1.5.

Proposed

4.1.x Programmatic Write Access: Ifk the user can modify the state or value of a pice of content through the *user interface* (e.g. by checking a box or editing a text area), the same degree of write access is available programmatically. (Level A) :

Is this sufficiently covered by 4.1.5?
4.1.5 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). (Level A)

Summary

Details