Updated Summaries

Here are updated Summaries from Kim and Greg, along with some comments 
and suggestions marked with asterisks:


Summary: If synthesized speech is produced, the user can specify speech 
rate, volume, and voice (1.6.1, Level A), pitch and pitch range (1.6.2, 
Level AA), advanced synthesizer speech characteristics like emphasis 
(1.6.3, Level AAA) and features like spelling (1.6.4, Level AAA).

Summary: The user agent supports user stylesheets (1.7.1, Level A), the 
user can choose which if any user-supplied (1.7.2, Level A) and 
author-supplied (1.7.3, Level A) stylesheets to use, and the user can 
save stylesheets (1.7.4, Level AA).

* I suspect we can delete 1.7.1 as redundant to 1.7.2.

Summary: The user agent provides programmatic and visual cues to keep 
the user oriented. These include highlighting the viewport (1.8.1, Level 
A), keeping the focus within the viewport (1.8.2 & 1.8.7, Level A), 
resizing the viewport (1.8.3, Level A), providing scrollbars that 
identify when content is outside the visible region (1.8.4, Level A) and 
which portion is visible (1.8.5, Level A), changing the size of 
graphical content with zoom (1.8.6, Level A & 1.8.12, Level AA), and 
restoring the focus and point of regard when the user returns to a 
previously viewed page (1.8.8, Level AA). Users can set a preference 
whether new windows or tabs open automatically (1.8.9, Level AA) or get 
focus automatically (1.8.10, Level AA). The user can specify that all 
viewports have the same user interface elements (1.8.11, Level AA), if 
and how new viewports open (1.8.9, Level AA), and whether the new 
viewport automatically gets focus (1.8.10, Level AA). The user can mark 
items in a webpage and use shortcuts to navigate back to marked items. 
(1.8.13, Level AAA).

* 1.8.3 doesn't belong lumped in with keeping oriented.

Summary: The user can view the source of content (1.9.2, Level AAA), or 
an outline view of important elements. (1.9.1, Level AA).

Summary: The user can access information about content relationships 
(e.g. form labels, table headers) (1.10.1, Level AA), and extended link 
information (e.g. title, internal vs. external) (1.10.2, Level AAA)

* 1.10.1 use of "can access related elements" and "show", the latter 
reads like hiding/showing, the former more like either navigating to or 
visually drawing a linkage between.

Summary: Every viewport has a keyboard focus (2.1.2, Level A). Users can 
operate all functions using just the keyboard (2.1.1, Level A), activate 
important or common features with shortcut keys, (2.1.6, Level A), 
escape keyboard traps (2.1.3, Level A), specify that selecting an item 
in a dropdown list or menu not activate that item (2.1.4, Level A) and 
use standard keys for its platform (2.1.5, Level A).

Summary: Users can use the keyboard to navigate sequentially to all the 
operable elements in the viewport (2.2.1, Level A) as well as between 
viewports (2.2.2, Level A), and the default navigation order is document 
order (2.2.3, Level A). Users can optionally disable wrapping or request 
a signal when wrapping occurs (2.2.4, Level AA).

Summary: Users can navigate directly (e.g. using keyboard shortcuts) to 
important elements (2.3.1, Level AA) with the option of immediate 
activation of the operable elements (2.3.3, Level A). Display commands 
with the elements to make it easier for users to discover the commands 
(2.3.2 & 2.3.4, Level AA). The user can remap and save direct commands 
(2.3.5, Level AA).

* 2.3 needs to be reordered to reflect changed priority levels.

* Does 2.3.3 really deserve to be higher priority than 2.3.1?

Summary: Users can search rendered content (2.4.1, Level A) forward or 
backward (2.4.2, Level A) and can have the matched content highlighted 
in the viewport (2.4.3, Level A). The user is notified if there is no 
match (2.4.4, Level A). Users can also search by case and for text 
within alternative content (2.4.5, Level AA).

Summary: Users can view (2.5.1, Level A), navigate (2.5.2, Level A), and 
configure the elements used in navigating (2.5.3, Level AAA) content 
hierarchy.

Summary: Users can discover what event handlers (e.g. onmouseover) are 
available at each element and activate an element's events individually 
even if they do not have the corresponding input device (2.6.1, Level A).

Summary: Users can restore preference settings to default (2.7.2, Level 
A), and accessibility settings persist between sessions (2.7.1, Level 
A). Users can manage multiple sets of preference settings (2.7.3, Level 
AA), and adjust preference setting outside the user interface so the 
current user interface does not prevent access (2.7.4, Level AA), and 
transport settings to compatible systems (2.7.5, Level AA).

Summary: It's recommended that users can add, remove, reposition, and 
assign shortcuts to user agent controls, and restore them to their 
default settings (2.8.1, Level AA).

Summary: Users can extend the time limits for user input when such 
limits are controllable by the user agent (2.9.1, Level A).

Summary: To help users avoid seizures, the default configuration 
prevents the browser user interface and rendered content from flashing 
more than three times a second above luminescence or color thresholds 
(2.10.1, Level A), or even below the thresholds (2.10.2, Level AAA).

Summary: The user can present placeholders for time-based media (2.11.1, 
Level A) and executable regions (2.11.2, Level A), or block all 
executable content (2.11.3, Level A), adjust playback (2.11.4, Level A), 
stop/pause/resume (2.11.5, Level A), navigate by time (2.11.6, Level A) 
or semantic structures such as chapter (2.1.7, Level AA), enable or 
disable tracks (2.11.8, Level AA), and adjust contrast and brightness of 
visual time-based media (2.11.9, Level AAA).

* The Note about recognized should be replaced by a global note.

Summary: User agents support all of the platform's text input devices 
(2.12.1, Level A), and for all input devices the user can input text 
(2.12.3, Level AAA) and perform all other functions (2.12.2, Level AA).

Summary: Users can turn off non-essential messages from the author or 
user-agent (3.1.1, Level AA).

Summary: Users can have form submissions require confirmation (3.2.1, 
Level AA), go back after navigating (3.2.2, Level AA), have their text 
checked for spelling errors (3.2.3, Level AA), undo text entry (3.2.4, 
Level A), avoid or undo settings changes (3.2.5, Level A), and receive 
indications of progress activity (3.2.6, Level A).

* 3.2 needs to be reordered to reflect changed priority levels.

Summary: User documentation is available in an accessible format (3.3.1, 
Level A), it includes accessibility features (3.3.2, Level A), 
delineates differences between versions (3.3.3, Level AA), provides a 
centralized view of conformance UAAG2.0 (3.3.4, Level AAA).

Summary: Users can prevent non-requested focus changes (3.4.1, Level A).

Summary: The user agent supports platform accessibility services (4.1.1, 
Level A) that are quick and responsive (4.1.7, Level A), including 
providing information about all controls and operation (4.1.2, Level A & 
4.1.6, Level AA), access to DOMs (4.1.4, Level A). Controls can be 
adjusted programmatically (4.1.5, Level A). Where something can't be 
made accessible, provide an accessible alternative version, such as a 
standard window in place of a customized window (4.1.3, Level A).

* 4.1 needs to be reordered to reflect changed priority levels.

Summary: When the browser's controls are authored in HTML or similar 
standards, they need to meet W3C's Web Content Accessibility Guidelines 
(5.1.1, Levels A, AA, AAA). The user agent supports the accessibility 
features of content formats (5.1.2, Level A) and of the platform (5.1.3, 
Level A), allows handling of unrendered technologies (5.1.4, Level A) 
including by alternative viewers (5.1.5, Level AA), and allows users to 
report accessibility issues (5.1.6, Level AAA).

     Thanks,
     Greg and Kim