from Jan' proposal:

Documentation: Any information that supports the use of a user agent. This information may be provided electronically or otherwise and includes help, manuals, installation instructions, tutorials, etc. Note: The level of technical detail in documentation for users should match the technical level of the feature. For example, user documentation for a browser's zoom function should not refer users to the source code repository for that browser.

EXISTING:
Documentation: Any information that supports the use of a user agent. This information may be found, for example, in manuals, installation instructions, the help system, and tutorials. Documentation may be distributed (e.g. as files installed as part of the installation; some parts may be delivered on CD-ROM, others on the web). (http://www.w3.org/WAI/UA/2013/ED-UAAG20-20130925/#def-documentation)

Summary

Details

from Jan' proposal:

PROPOSAL (adapted from ATAG2):
Intent: Some users with disabilities will need help in determining how to use the accessibility features that user agents provide. There are four possibilities:
(a) This information can be provided in the documentation of the user agent (e.g. help system, context sensitive help, etc.);
(b) The user interface element is self-explanatory (e.g. a zoom % drop-down menu); (c) The accessibility feature is actually a service of the platform (e.g. high contrast mode), which therefore has the responsibility to document the feature; or
(d) The feature is not used directly by users (e.g., passing information to a platform accessibility service). In this case, user documentation does not make sense, although developer documentation (e.g. how accessibility APIs are used, the user agent's own plug-in API) would still be recommended.

Existing: http://www.w3.org/WAI/UA/UAAG20/#sc_332

Summary

Details

From Jim's proposal:

Proposal: using ATAG as a model, rewrote for UAAG. The ATAG definition as based on feedback from vendors. It is more comprehensive. I believe the IER is ok even with the rewording.

3.3.2 Describe Accessibility Features: For each user agent feature that is used to meet UAAG 2.0, at least one of the following is true: (Level A)
(a) Described in the Documentation: Use of the feature is explained in the user agents's documentation; or
(b) Described in the Interface: Use of the feature is explained in the user agent user interface; or
(c) Platform Service: The feature is a service provided by an underlying platform; or
(d) Not Used by Users: The feature is not used directly by users (e.g., passing information to a platform accessibility service).

Summary

Details

see Implementing UAAG 2.0 Guideline 1.4 to see how the Intent and Examples look at the guideline level.

Jeanne proposed that this examples and intent be moved to the appropriate success criteria to make it consistent with the rest of Implementing UAAG 2.0.

PROPOSED - move the 1.4 Text Customization Intent and examples to the appropriate success criteria keeping the consistency with other guidelines in Implementing UAAG 2.0.

Summary

Details

See 1.4.1 changes in 25 September 2013 UAAG 2.0 Editors Draft.

PROPOSED:
1.4.1 Configure text globally: The user can globally set all of the following characteristics of visually rendered text content: (Level A)
* Text scale (the general size of text)
* Text color and background color, choosing from all platform color options
* Font family, choosing from all platform fonts

Summary

Details

See new 1.4.2 in 25 September 2013 UAAG 2.0 Editors Draft.

PROPOSED:
1.4.2 Configure text elements: The user can set all of the following characteristics of visually rendered text content for headings, main text, and other elements:(Level AA)
* Text scale (the general size of text)
* Text color and background color, choosing from all platform color options
* Font family, choosing from all platform fonts

Summary

Details

See new 1.4.3 in 25 September 2013 UAAG 2.0 Editors Draft.

PROPOSED:
1.4.3 Configure text globally: The user can globally set all of the following characteristics of visually rendered blocks of text:(Level AA)
Line spacing of at least 1.0, 1.3, 1.5, and 2.0
Character spacing of at least 0.01, 0.03, 0.06, 0.09
Word spacing of at least 0.01, 0.03, 0.06, 0.09
Text style (underline, italic, bold)
Justification - undo full justification

Summary

Details

See new 1.4.4 in 25 September 2013 UAAG 2.0 Editors Draft.

PROPOSED:
1.4.4 Printing configured and reflowed text: The user can print blocks of text that is configured according to the success criteria of guideline 1.4 and/or reflowed according to success criteria 1.8.x, including text that is zoomed. (Level AA)

Summary

Details

See new 1.4.5 in 25 September 2013 UAAG 2.0 Editors Draft.

PROPOSED:
1.4.5 Configure text elements: The user can set all of the following characteristics of visually rendered text content for headings, main text, and other elements: (Level AAA)
Text style (underline, italic, bold)
Margins (for example, space above headings, indentation of lists)
Borders

Summary

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

Details

See new 1.4.6 in 25 September 2013 UAAG 2.0 Editors Draft.

PROPOSED:
1.4.6 Configure text globally: The user can globally set all of the following characteristics of visually rendered blocks of text:(Level AAA)
Line spacing between 0.7 and 3.0, at increments of 0.10.
Justification (setting left, right, or full)
Capitalization (undoing all caps)
Hyphenation
Margins (to clear clutter away from blocks of text)
Borders

Summary

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

Details

See changes 1.8.7 in 25 September 2013 UAAG 2.0 Editors Draft.

PROPOSED:
1.8.7. Reflow Text:The user can specify that text content in a graphical viewport reflows so that blocks of text fit within the width of the viewport in a single column.(Level A)

Note 1: [N<] Reflow applies to rescaled or zoomed text. [>N]

Summary

Details

See changes to IER for 1.8.7 and 1.8.9 in 25 September 2013 Implementing UAAG 2.0 Editors Draft.

Summary

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

Details

See Greg's email.

PROPOSED:
2.10.x Allow avoiding animation: The user can disable any animations that are part of the user agent user interface. All information is available through means that do not require the use of animation. (Level A)

Intent of Success Criterion 2.10.x:

Users with sensory, attentional, cognitive, or vestibular impairments can find that animations cause distraction, disorientation, nausea, dizziness or vertigo. If the user agent presents any such movies or animated effects, it should provide a global setting that allows the user to disable them, and doing so should not cause the loss of functionality or information.

Examples of Success Criteria 2.10.x:

* Allesandro finds it impossible to ignore visual changes. Unnecessary animations make it very difficult for him to read or interact with other content on the screen. When he's reading an article on a newspaper website and finds an animated icon in the browser's notification area distracting, he goes to the browser's settings dialog and chooses the option to disable browser animations.
* Rachel has a vestibular disorder that causes her to experience dizziness when she sees certain types of videos or animations. Her web browser smoothly scrolls the window every time she presses the pages up or down, and this simulated motion can make her dizzy or nauseous, so she adjusts the browser's user preference options to turn off smooth scrolling, so that the browser effectively redraws the contents of the window each time.

References: * Guideline 2.11 - Provide control of content that may reduce accessibility
* "Why iOS 7 is making some users sick", http://www.theguardian.com/technology/2013/sep/27/ios-7-motion-sickness-nausea.
* Vestibular Disorders Association, https://vestibular.org.

Add to Examples of Success Criteria 2.11.3 (Execution Toggle):

* Rachel has a vestibular disorder that causes her to experience dizziness when she sees certain types of videos or animations. She wants to order theatre tickets, but unfortunately the web site displays an animated background that every few seconds slides out the background image and slides another into its place, and this animation makes Rachel severely uncomfortable. Therefore she clicks a button on the browser's toolbar to temporarily disable scripts on this page, which causes the animation to stop.

Summary

Details