From a proposal from Simon Harper. Email comments

I'm trying to sort out the user agent wording.

We'd agreed on parts 1 and 2 (Jim was finishing wordsmithing on 2.2 with regard to the wording for presentation within the bounds of the primary UA). I'd like to make another proposal for part 3, thus:

If the following two conditions are met then it is a Web-based User Agent and Must Conform to UAAG:

1) If the user interface is generated as part of, or using, any w3c specified technology; and
2) If the generated interface, intentionally or unintentionally, hides its interaction from the technology used to generate it.

Notes:
1) this means if the interface is created from web content (even if code used for generating the interface only has hooks into html, such as JavaScript etc); and
2) if input is consumed or output hidden from the DOM Updating procedures of the Primary UA or Extension / Plug in.

Summary

Details

From a proposal from Kelly Ford. Email comments

Proposed

4.9.6 Slow Multimedia: The user can slow the presentation rate of recognized prerecorded audio and animation content, such that all of the following are true (Level A):
* if only an audio track is present, provide at least one setting between 75% and 80% of the original speed.
* if a visual track is present, provide at least one setting between 40% and 60% of the original speed.
* when audio and video tracks are expected to be synchronized, synchronization is maintained as long as they are played at 75% of the original speed or higher.

Summary

Details

From a proposal from Kelly Ford. Email comments

Proposed

4.9.X Increase Multimedia: The user can increase the presentation rate of recognized prerecorded audio and animation content, such that all of the following are true (Level AA):
* if only an audio track is present, provide at least one setting between 110% and 140% of the original speed.
* if a visual track is present, provide at least one setting between 110% and 120% of the original speed.
* when audio and video tracks are expected to be synchronized, synchronization is maintained as long as they are played at 120% of the original speed or lower.

Summary

Details

From a proposal from Kelly Ford. Email comments

Note:
We might want a level AAA guideline around preserving audio characteristics. I don't immediately recall the official term but it avoids the "chipmunk" effect when increasing audio playback rates and the deepening of the voice and such when slowing playback and is more common today when such features are offered. I'm also looking for some official numbers on acceptable rates for playback and the ability to maintain comprehension.

Proposed

4.9.X Maintain Audio Characteristics: When playing recognized prerecorded audio and animation sound at rates other than the default, speech characters are not distorted beyond X range (Level AAA).

Summary

Details

In consolidating the HTML5 comments, I realized that two comments came down on opposite sides on the "hidden attribute".

Issue#: UAWG05
Section: 7.1 The hidden attribute*
Comment: It's important to give users the ability to discover and navigate content when authoring tools are used incorrectly. The hidden attribute is a good example.

*Excerpt: "The **hidden **attribute must not be used to hide content that could legitimately be shown in another presentation, for example..." *

On occasion it will be, however, and full accessibility means the user needs some way to override this in order to deal with incorrectly rendered pages.

Issue#: UAWG12
Section: 7.1, the hidden attribute
Version: http://dev.w3.org/html5/spec/Overview.html Comment: Accessibility APIs must honor this. User agents will need to ensure to reflect the state of this attribute in their accessibility APIs. This may be stating the obvious but is worth calling out since there are various situations today where AT products do or do not show the same text that is visually displayed and this is another potential variable to keep in mind.

Should a user be able to override the hidden attribute and display "hidden" text?

Summary

Details

From a proposal from Jeanne Spellman. Email comments

Note:
Issue#: UAWG29
Section: HTML section: 11.2.3 Margins and padding
Comment: If the user wishes to increase the size of text in an iframe or other container element, the text may overflow the container. When text overflows the size of a box and the attribute value is set so that the overflow value is "hidden", the overflow text may not be passed to the Assistive Technology and the user may not be able to see the text that does not fit in the container. Proposal: Add after chart (Attribute value/'overflow' value) When the user has increased the text size of the document, the 'overflow' value should always be set to 'scroll'.

I propose adding a new SC in 3.6 Provide text configuration. Proposal:

Proposed

3.5.x Container overflow options. When text resized by the user overflows the containing element the user has the option to either: (a) expand the size of the containing element to display the text or (b) to override any author setting preventing scrollbars in order to display all of the text

Summary

Details