Current:

4.1.9 Override of UI Keyboard Commands: The user can override any keyboard shortcut binding for the user agent user interface except for conventional bindings for the operating environment (e.g., for access to help). The rebinding options must include single-key and key-plus-modifier keys if available in the operating environment. (Level A)

Proposed:

4.1.9 Override of UI Keyboard Commands: The user can override any keyboard shortcut binding for the user agent user interface except for conventional bindings for the operating environment (e.g., for access to an open command). The rebinding options must include single-key and key-plus-modifier keys if available in the operating environment. This does not prohibit a user agent from supporting user override of conventional bindings for the operating platform to extend accessibility of the user agent. (Level A)

Summary

Details

Current:

Guideline 4.5 Store preference settings.

4.5.1 Save Settings: User agent preference settings are stored between sessions. (Level A)

4.5.2 User Profiles: The user can save and retrieve multiple sets of user agent preference settings. (Level AA)

4.5.3 Portable Profiles: Sets of preferences are stored as separate files (allowing them to be transmitted electronically). (Level AAA)

4.5.4 Preferences Wizard: A "wizard" helps the user to configure (at least) the accessibility-related user agent preferences. (Level AAA)

Proposed:

Guideline 4.5 Configure and Store accessibility preference settings.

4.5.1 Reconfigure Accessibility Defaults: The user agent will allow default settings that impact accessibility to be reconfigured by the user. (Level A)

4.5.2 Save Accessibility Settings: User agent accessibility preference settings are stored between sessions. (Level A)

4.5.3 Accessibility User Profiles: The user can save and retrieve multiple sets of user agent preference settings. (Level AA)

4.5.4 Accessibility Portable Profiles: Sets of preferences are stored as separate files (allowing them to be transmitted electronically). (Level AAA)

4.5.5 Accessibility Preferences Wizard: A "wizard" helps the user to configure (at least) the accessibility-related user agent preferences. (Level AAA)

Summary

Details

A potentially harmful flash occurs when there is a pair of opposing changes in luminance (i.e., an increase in luminance followed by a decrease, or a decrease followed by an increase) of 20 candelas per square metre (cd.m-2) or more (see notes 1 and 2). This applies only when the screen luminance of the darker image is below 160 cd.m-2. Irrespective of luminance, a transition to or from a saturated red is also potentially harmful.

Isolated single, double, or triple flashes are acceptable, but a sequence of flashes is not permitted when both the following occur:
i. the combined area of flashes occurring concurrently occupies more than one quarter of the displayed (see note 3) screen area; and
ii. there are more than three flashes within any one-second period. For clarification, successive flashes for which the leading edges are separated by 9 frames or more are acceptable, irrespective of their brightness or screen area.

Notes:
1. A luminance voltage of 234 mV results in light output of 20.1 cd.m-2. If the brighter image of a flash or pattern is above this level, then it is potentially harmful if the light output between the darker and brighter images differs by 20 cd.m-2 or more.
2. A luminance voltage of 631 mV results in light output of 160 cd.m-2. If the darker image of a flash or pattern is below this level, then it is potentially harmful if the light output between the darker and brighter images differs by 20 cd.m-2 or more.

Summary

Details

ISSUE-4 Move 4.5.3 to Level AA. Seems to me this should stay at AAA, while it would be useful for transferring profiles between the same browser, I think it maybe goes beyond the our remit for UAAG as this seems to more about additional functionality which is not pre-provided for all, and it seems that if we wanted to facilitate transfer between different UA we would need to define a language. A good idea in and of itself but beyond our remit I think.

Summary

Details

#108. (Re 4.9.7) Split multimedia stop/start from pause/resume: I'm concerned that none of the major Web browsers comply with the Level A success criteria that they allow the user to stop, pause, and resume multimedia. Neither Firefox, Internet Explorer, nor Safari allow the user to pause and resume animated gifs regardless of their duration. Consider splitting this SC into two: the ability to stop and start multimedia as Level A, and the ability to pause and resume multimedia as Level AA. (Priority: 1 High) (Type: Narrow)

Summary

Details

#109. (Re 4.9.7 **) Remove restrictions based on multimedia duration: 4.9.7 and 4.9.8 both restrict their applicability to multimedia that lasts three seconds or longer at default playback rate. Because a user agent would often not know the duration of multimedia content, it would have to provide these controls for all multimedia, so I would remove the 3-second restriction from both success criteria (and my proposed split off 4.9.7). (Someone could argue that the Note for this guideline, which says it only applies to multimedia "that the user agent can recognize" means that 4.9.7 and 4.9.8 would only apply to multimedia for which the user agent can recognize the length. If that is the working group's intention then the Note should be significantly reworded to make this clear, and the working group needs to accept that these criteria would have extremely limited applicability.) (Priority: 1 High) (Type: Expand)

Summary

Details

#110. (Re 4.9.8 **) Remove restrictions based on multimedia duration: Please see my comment with this title for 4.9.7 (Stop/Pause/Resume Multimedia). (Priority: 1 High) (Type: Expand

Summary

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

Details