W3C WBS Home

Results of Questionnaire UAWG Survey for 1 October

The results of this questionnaire are available to anybody. In addition, answers are sent to the following email addresses: w3c-archive@w3.org, jeanne@w3.org

This questionnaire was open from 2009-09-30 to 2009-10-16.

4 answers have been received.

Jump to results for question:

  1. proposal for adding test conditions to the Definition of User Agent
  2. 4.9.6 Slow Multimedia
  3. 4.9.X Increase Multimedia:
  4. 4.9.X Maintain Audio Characteristics
  5. HTML5 "hidden attribute"
  6. 3.5.x Container overflow options.

1. proposal for adding test conditions to the Definition of User Agent

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

ChoiceAll responders
Results
Accept the proposal 1
Recommend changes (see comments field)
The proposal needs more discussion (see comments field) 2
Disagree with the proposal
Neutral - will accept the consensus of the group 1

Details

Responder proposal for adding test conditions to the Definition of User AgentComments
Kimberly Patch Accept the proposal
Kelly Ford Neutral - will accept the consensus of the group
Jan Richards The proposal needs more discussion (see comments field) There is probably better wording than "hides its interaction"
Greg Lowney The proposal needs more discussion (see comments field) • If XML is stored as a text file, read by a text editor and rendered as text for the user, would that trigger part 1 because it is "using…a w3c specified technology" (XML)?

• I don't understand "If the generated interface, intentionally or unintentionally, hides its interaction from the technology used to generate it."

• What is "technology used to generate it"? If PHP code running on Unix get data from MySQL, wraps it in XML, uses HTTP to send it to a Windows PC where a custom, in-house application written in Visual Basic calls the Internet Explorer ActiveX Control to render and displayed the content in a region of the application's window, which is "generating" it? Does "the technology used to generate it" mean any layer, or the layer that does the rendering, or the layer that produced the XML?

2. 4.9.6 Slow Multimedia

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

ChoiceAll responders
Results
Accept the proposal 3
Recommend changes (see comments field) 1
The proposal needs more discussion (see comments field)
Disagree with the proposal
Neutral - will accept the consensus of the group

Details

Responder 4.9.6 Slow MultimediaComments
Kimberly Patch Accept the proposal
Kelly Ford Accept the proposal I don't think this one was a proposal, this is existing.
Jan Richards Accept the proposal Wording tweak:
as long as they are played at 75% of the original speed or higher.
=> down to 75% of the original speed.
WCAG,ATAG-style would put "; and" on each item for clarity
Greg Lowney Recommend changes (see comments field) • It should not be if a __ track "is present" but if a ____ track "is being presented", as these restrictions should not apply if a track is present but disabled by a user option (e.g. audio muted, or the user chooses to turn off one or more tracks).

• Just out of curiosity, what behavior is expected when audio and video are not synchronized?

3. 4.9.X Increase Multimedia:

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

ChoiceAll responders
Results
Accept the proposal 2
Recommend changes (see comments field) 1
The proposal needs more discussion (see comments field) 1
Disagree with the proposal
Neutral - will accept the consensus of the group

Details

Responder 4.9.X Increase Multimedia: Comments
Kimberly Patch Accept the proposal
Kelly Ford Accept the proposal
Jan Richards The proposal needs more discussion (see comments field) 110% and 140% seems too wide.

as long as they are played at 120% of the original speed or lower.
=>up to at least 120% of the original speed.

WCAG,ATAG-style would put "; and" on each item for clarity
Greg Lowney Recommend changes (see comments field) • It should not be if a __ track "is present" but if a ____ track "is being presented", as these restrictions should not apply if a track is present but disabled by a user option (e.g. audio muted, or the user chooses to turn off one or more tracks).

• Just out of curiosity, what behavior is expected when audio and video are not synchronized?

4. 4.9.X Maintain Audio Characteristics

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

ChoiceAll responders
Results
Accept the proposal 2
Recommend changes (see comments field)
The proposal needs more discussion (see comments field) 2
Disagree with the proposal
Neutral - will accept the consensus of the group

Details

Responder 4.9.X Maintain Audio CharacteristicsComments
Kimberly Patch Accept the proposal
Kelly Ford The proposal needs more discussion (see comments field) As I say the exact terms need discussion but I think the concept is worth having.
Jan Richards Accept the proposal Needs wording but I like the idea.
Greg Lowney The proposal needs more discussion (see comments field) • What is meant by limiting it to "prerecorded" audio? Does that mean synthesizes speech sped up does not count?

• It seems that this would normally be handled outside the level of the UA, wouldn't it? Would UA normally know when audio or sounds contain speech?

5. HTML5 "hidden attribute"

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

ChoiceAll responders
Results

Details

Responder HTML5 "hidden attribute"
Kimberly Patch I think it needs to do both. It's important that by default accessibility APIs should follow what the author intended. In addition, for situations like times when authoring tools are used incorrectly, the user should be able to override. Today's Web is proof that authoring tools are not always used correctly. I think of overrides like this is life preservers. No one intends to use them, but they are critical when needed.
Kelly Ford
Jan Richards I don't think so...since this info is hidden from all users.
Greg Lowney

6. 3.5.x Container overflow options.

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

ChoiceAll responders
Results
Accept the proposal 1
Recommend changes (see comments field)
The proposal needs more discussion (see comments field) 2
Disagree with the proposal
Neutral - will accept the consensus of the group 1

Details

Responder 3.5.x Container overflow options.Comments
Kimberly Patch Accept the proposal
Kelly Ford Neutral - will accept the consensus of the group
Jan Richards The proposal needs more discussion (see comments field)
Greg Lowney The proposal needs more discussion (see comments field) I suggest explicitly including the obvious third user option: (c) to truncate the rendered content to fit the containing element. That is sometimes the only way to make a page usable.

Of course, the option to scale the contained content to fit the container is also extremely useful in some situations, especially when the content is graphics rather than text.

More details on responses

Non-responders

The following persons have not answered the questionnaire:

  1. Judy Brewer <jbrewer@w3.org>
  2. Jim Allan <jimallan@tsbvi.edu>
  3. Eric Hansen <ehansen@ets.org>
  4. Markku Hakkinen <mhakkinen@ets.org>
  5. Wayne Dick <wayneedick@gmail.com>
  6. Peter Parente <pparent@us.ibm.com>
  7. Simon Pieters <simonp@opera.com>
  8. Takeshi Kurosawa <kurosawa-takeshi@mitsue.co.jp>
  9. Alan Cantor <alan@cantoraccess.com>
  10. Jeanne F Spellman <jeanne@w3.org>
  11. Simon Harper <simon.harper@manchester.ac.uk>
  12. he wen <rockywen@tencent.com>

Send an email to all the non-responders.


Compact view of the results / list of email addresses of the responders

WBS home / Questionnaires / WG questionnaires / Answer this questionnaire


Completed and maintained by Dominique Hazaël-Massieux (dom@w3.org) on an original design by Michael Sperberg-McQueen $Id: showv.php3,v 1.124 2014-10-06 13:46:23 dom Exp $. Please send bug reports and request for enhancements to dom@w3.org with w3t-sys@w3.org copied (if your mail client supports it, send mail directly to the right persons)