W3C WBS Home

Results of Questionnaire UAWG Survey for 19 January 2012

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 2012-01-13 to 2012-01-27.

6 answers have been received.

Jump to results for question:

  1. Intent for 2.3.x
  2. Example for 2.7.2
  3. Example for 2.7.3
  4. Example for 2.7.4
  5. Summary for 2.10
  6. Summary for 2.11
  7. Examples for 2.11.7
  8. Example for 2.11.8
  9. Examples for 2.11.9
  10. Examples for 2.11.11
  11. Examples for 2.11.12
  12. Example for 3.3.3
  13. Example for 3.3.4
  14. 5.1.1 to be removed
  15. Intent for 5.3.2
  16. Intent & Examples for 5.3.1

1. Intent for 2.3.x

2.3.x Discover navigation and activation keystrokes (former 2.5.1): The user can discover direct navigation and activation keystrokes both programmatically and via perceivable labels. (Level A)

[SC is for reference only - no change]

proposed Intent

This success criterion reduces the cognitive load for keyboard interface users. Navigation by keyboard interface may vary by platform, user agent and assistive technology. Taken as a whole, this creates hardship for keyboard interface users. The user of the keyboard interface needs perceivable labels to learn and be able to operate navigation effectively.

Summary

ChoiceAll responders
Results
Agree with the proposal 3
Disagree with the proposal
Neutral, will accept consensus of the group 1
Suggest the following changes to the proposal 2

Details

Responder Intent for 2.3.xComments on 2.3.x
Jeanne F Spellman Suggest the following changes to the proposal I think the disability angle needs to be more clear.

This success criterion reduces the cognitive load for keyboard interface users *, some of whom may also have cognitive disabilities*. Navigation by keyboard interface may vary by platform, user agent and assistive technology, *requiring memorization of a very large number of keyboard shortcut commands*. Taken as a whole, this creates hardship for keyboard interface users. The *some users* of the keyboard interface needs perceivable labels to learn and be able to operate navigation effectively, *while those using assistive technologies require communication of the keystrokes by programmatic means.*

NOTE: 2.3.x still needs examples.
Jan Richards Agree with the proposal
Greg Lowney Neutral, will accept consensus of the group It's acceptable but...

I'd add something clarifying that these do not have to always be presented, but can instead be a user option or on request (e.g. tapping Alt in Windows).

Also, if we're going to leave the part about "programmatically" in the SC, we should mention it in the Intent paragraph.
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Suggest the following changes to the proposal add "application":
Navigation by keyboard interface may vary by application, platform, user agent and assistive technology.

I think the following needs expansion or revision:

Taken as a whole, this creates hardship for keyboard interface users.

2. Example for 2.7.2

2.7.2 Persistent Accessibility Settings: User agent accessibility preference settings persist between sessions. (Level A)

[SC is for reference only - no change]

proposed

Lynn has moderately low vision, and sets the default zoom level, font size, and colors to make pages easier for her to read. Because those settings are persistent, she doesn't have to manually restore her settings every time she starts the browser.

Brian has to adjust some settings in his browser to make it fully compatible with his speech input system. It's difficult for him to get it set up, since he can't fully operate the browser until it's done, so once it's configured this way he relies on it staying in that configuration even if he upgrades the browser, restarts his system and so forth.

Summary

ChoiceAll responders
Results
Agree with the proposal 6
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal

Details

Responder Example for 2.7.2Comments on 2.7.2
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Agree with the proposal
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Agree with the proposal

3. Example for 2.7.3

2.7.3 Restore all to default: The user can restore all preference settings to default values. (Level A)

[SC is for reference only - no change]

proposed

Ron accidentally changes a browser setting that makes his browser incompatible with his screen reader, preventing him from changing it back. He instead restarts his browser using a command line option that starts it in the default configuration, which he's able to use, and from there he can change the setting that caused him problems.

Summary

ChoiceAll responders
Results
Agree with the proposal 6
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal

Details

Responder Example for 2.7.3Comments on 2.7.3
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Agree with the proposal
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Agree with the proposal

4. Example for 2.7.4

2.7.4 Multiple Sets of Preference Settings: The user can save and retrieve multiple sets of user agent preference settings. (Level AA)

[SC is for reference only - no change]

proposed

When Hiroki is carrying his tablet computer he operates it with the built-in touchscreen, but when at his desk he links it to a Bluetooth keyboard and mouse, and redirects the display to a full-size computer monitor. The browser allows him to quickly switch between two completely different configurations for these different environments.

Davy has moderately low vision and prefers to adjust the contrast of media differently during the day than at night. Because this requires a number of different steps, for different types of media and aspects of the browser's display, he has two user profiles, one for each environment.

Aaron usually uses a keyboard and mouse, but when his repetitive strain injury is bothering him he prefers to use the mouse and avoid using the keyboard as much as possible. At those times he users his browser's user preference profiles to load a different configuration that’s optimized for the mouse, including custom toolbars that make most of the commands he uses available as toolbar buttons.

Summary

ChoiceAll responders
Results
Agree with the proposal 6
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal

Details

Responder Example for 2.7.4Comments on 2.7.4
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Agree with the proposal
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Agree with the proposal

5. Summary for 2.10

proposed

The user can avoid potential seizures with a default browser configuration that does not flash more than three times a second above a luminescence or color threshold (2.10.1), or does not flash at all (2.10.2).

Summary

ChoiceAll responders
Results
Agree with the proposal 5
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal 1

Details

Responder Summary for 2.10Comments on 2.10
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Agree with the proposal
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Suggest the following changes to the proposal The user can avoid potential seizures with a default browser configuration that prevents the browser user interface and rendered content from flashing more than three times a second above a luminescence or color threshold (2.10.1), or does not flash at all (2.10.2).

6. Summary for 2.11

proposed

The user can control background images (2.11.1); render and control placeholders for time-based media and executable content (2.11.2, 2.11.3, 2.11.4); adjust playback (2.11.5), stop/pause/resume (2.11.6), navigate, (2.11.7) and specify tracks for prerecorded time-based media (2.11.9); scale and position alternative media tracks (2.11.11); and adjust contrast and brightness of visual time-based media (2.11.12).

Summary

ChoiceAll responders
Results
Agree with the proposal 5
Disagree with the proposal
Neutral, will accept consensus of the group 1
Suggest the following changes to the proposal

Details

Responder Summary for 2.11Comments on 2.11
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Neutral, will accept consensus of the group It's OK, but...

I prefer not lumping SC together, so would split the second clause into something like "; present placeholders for time-based media (2.11.2) and executable regions (2.11.3), or block all executable content (2.11.4);"
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Agree with the proposal

7. Examples for 2.11.7

2.11.7 Navigate Time-Based Media: The user can navigate along the timebase using a continuous scale, and by relative time units within rendered audio and animations (including video and animated images) that last three or more seconds at their default playback rate. (Level A)

[SC is for reference only - no change]

proposed

Jared has a print disability which makes it laborious to read text. He is watching a technical training video which will display section objectives or summary questions as text. When the text flashes by too quickly for him to read, he presses a key command to skip back an increment so he can read the text, or pause the video if more time is required.

Debbie has difficulty with bright or flashing video. When she encounters a flashing transition in a video, she quickly presses a key command to forward the video past the flashing, then carefully uses the slider to adjust the video back to the start of the next section avoiding the flashing material.

Summary

ChoiceAll responders
Results
Agree with the proposal 6
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal

Details

Responder Examples for 2.11.7Comments on 2.11.7
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Agree with the proposal
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Agree with the proposal

8. Example for 2.11.8

2.11.8 Semantic Navigation of Time-Based Media: The user can navigate by semantic structure within the time-based media, such as by chapters or scenes present in the media (Level AA).

[SC is for reference only - no change]

proposed

Marka is blind and is listening to a video of an hour-long lecture. The section she is in has some complex material that builds on material from an earlier section. While a sighted user could pause the video and move the slider back until she recognized visually distinct content from the section she wanted, Marka uses a control to skip back section by section until she hears the section title name she wants to review. When she is finished, Marka uses the control to move forward section by section until she hears the title of topic she was originally in.

Wes has repetitive stress injury where repetition reduces the amount of screen time he has per day. Wes stops playback of a training video when he is tired and after resting, he can navigate to the scene where he left off.

Summary

ChoiceAll responders
Results
Agree with the proposal 5
Disagree with the proposal
Neutral, will accept consensus of the group 1
Suggest the following changes to the proposal

Details

Responder Example for 2.11.8Comments on 2.11.8
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Neutral, will accept consensus of the group It's fine, but could change "screen time", since RSI doesn't affect the amount of time one can watch content on the screen, as long as they don't have to interact with it. Also, since if he merely pauses the video he wouldn't have to navigate, so might say "Wes has repetitive stress injury that limits the length of his computer sessions. He stops playback of a training video when he is tired and after resting, he can restart it and navigate to the scene where he left off."
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Agree with the proposal

9. Examples for 2.11.9

2.11.9 Track Enable/Disable of Time-Based Media: During time-based media playback, the user can determine which tracks are available and select or deselect tracks. These selections may override global default settings for captions, audio descriptions, etc. (Level AA)

[SC is for reference only - no change]

proposed

Marka is listening to a video of a lecture. The professor is demonstrating a chemistry experiment and is not speaking during a key part. Since she cannot see what the professor is demonstrating, Marka brings up a menu of the available tracks and discovers that there is a audio description track available. Marka selects the description track, rewinds a few minutes, and listens to the description of the experiment.

Gorges is deaf, and enjoys current run movies. He subscribes to a web service that streams major popular movies. While he speaks English, a certain movie uses a slang that he doesn't understand. He pauses the movie, selects a menu of caption tracks and finds a Spanish caption track. He then watches the rest of the movie with Spanish captioning.

Summary

ChoiceAll responders
Results
Agree with the proposal 5
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal 1

Details

Responder Examples for 2.11.9Comments on 2.11.9
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal I notice Marka and Marka are most likely the same persona. I wonder if it is worth settling on names for the whole document instead of constantely picking new ones.
Greg Lowney Suggest the following changes to the proposal 1. In the SC itself, the word "may" is problematic, implying that the user agent may choose whether or not the choice overrides global settings. It should be changed to "During time-based media playback, the user can determine which tracks are available and select or deselect tracks, overriding global default settings for captions, audio descriptions, etc."

2. Style only, but the second example could be shortened to start "Gorges is deaf, and subscribes to a web service that streams major popular movies."
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Agree with the proposal

10. Examples for 2.11.11

2.11.11 Scale and position visual alternative media tracks: The user can scale and position alternative media tracks independent of base video. (Level AAA)

[SC is for reference only - no change]

proposed

Justin has low vision and works in a noisy environment that makes it difficult to listen to instructional videos. When he enlarges the text of the captions to a viewable size, they block most of the video image. Justin selects an option that displays the caption track in a separate window, which he positions below the video image so they captions do not block the video image.

Summary

ChoiceAll responders
Results
Agree with the proposal 6
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal

Details

Responder Examples for 2.11.11Comments on 2.11.11
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Agree with the proposal
Kelly Ford Agree with the proposal they captions needs to be the captions.
Jim Allan Agree with the proposal
Markku Hakkinen Agree with the proposal

11. Examples for 2.11.12

2.11.12 Video Contrast and Brightness: Users can adjust the contrast and brightness of visual time-based media. (Level AAA)

[SC is for reference only - no change]

proposed

Frank has low vision that requires a higher contrast to discern a video image. When Frank is watching an instructional video, he selects a menu that allows him to increase the contrast of the video, to make it easier for him to see the important content.

Kelly has photo-epilepsy and is watching an amateur video taken on a sunny day near the water. Concerned that the video may contain flashing that could trigger a seizure, Kelly selects a menu of video controls that allow her to reduce the brightness and contrast of the video. While some of the detail is lost, Kelly can safely watch the video.

Summary

ChoiceAll responders
Results
Agree with the proposal 5
Disagree with the proposal
Neutral, will accept consensus of the group 1
Suggest the following changes to the proposal

Details

Responder Examples for 2.11.12Comments on 2.11.11
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Neutral, will accept consensus of the group Minor point, but technically Frank wouldn't select "a menu", but instead activate a "menu item" or a "menu command".
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Agree with the proposal

12. Example for 3.3.3

3.3.3 Changes Between Versions: Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. (Level AA)

[previous SC is for reference only - no change]

proposed

Martha goes to an app store on her computer and notices that an update for the web browser she uses is available. She installs it and finds a welcome page talking about the new features in this release when she launches the updated version of the browser. One of the links on that page says "What's new For Accessibility". following this link Martha reads about the accessibility improvements added and discovers this update had added a feature allowing her to have tooltips displayed for elements when she is using caret browsing. the text says, "In this version, we added the ability to display tooltips on elements with a title attribute when using the keyboard. With caret browsing turned on simply arrow onto an element with a title and the tooltip will remain visible while the caret is within the element." The text also informs Martha that this feature is off by default and that she should go to accessibility settings to turn it on.

Summary

ChoiceAll responders
Results
Agree with the proposal 4
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal 2

Details

Responder Example for 3.3.3Comments on 3.3.3
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Suggest the following changes to the proposal It's acceptable, but...

Minor grammar point, but second sentence would be clearer as "When she install it she finds..."

Could delete either the fourth or fifth sentences altogether, since they're redundant to each other.

Fix capitalization.
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Suggest the following changes to the proposal Small change (cap the):
...caret browsing. The text says, "In this version, we added the ability to display tooltips on elements with a title attribute when using the keyboard.

13. Example for 3.3.4

3.3.4 Centralized View: There is a dedicated section of the documentation that presents a view of all features of the user agent necessary to meet the requirements of User Agent Accessibility Guidelines 2.0. (Level AAA)

[previous SC is for reference only - no change]

proposed

Bob downloads a new web browser on his mobile phone. He's never used this software before and also uses a screen reader that is part of his phone's operating system. He opens a help option for the web browser and finds an accessibility section that gives details on the various accessibility features of the browser such as screen layout, interaction with his screen reader and a list of supported touch gestures.

Summary

ChoiceAll responders
Results
Agree with the proposal 5
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal 1

Details

Responder Example for 3.3.4Comments on 3.3.4
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Suggest the following changes to the proposal It's acceptable, but...

Could simplify the third sentence to "The browser's online help includes a section on accessiblity that point him to pages discussing non-visual access, such as..."

Of course, two of the three listed features would not be necessary to meet the requirements of UAAG20, so aren't actually required by the SC. Might that obfuscate what the SC actually does require?
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Agree with the proposal

14. 5.1.1 to be removed

proposed to REMOVE:

5.1.1 Follow Accessibility Guidelines: Non-web-based user agent user interfaces follow user interface accessibility guidelines for the platform. (Level A)

this SC is a duplicate of 5.3.2

Summary

ChoiceAll responders
Results
Agree with the proposal 6
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal

Details

Responder 5.1.1 to be removedComments on 5.1.1
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Agree with the proposal
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen Agree with the proposal

15. Intent for 5.3.2

5.3.2 Implement Accessibility Features of platform: Implement and cite in the conformance claim the accessibility features of content and platform technology specifications. Accessibility features are those that are either (Level A) :
* identified as such in the specification or
* allow authors to satisfy a requirement of WCAG.

[SC is for reference only - no change]

proposed

The operating system on which a user agent is running has expected conventions around accessibility for areas such as keyboard behavior, support of an accessibility API, user interface design, and other standards related to accessibility. The intent of this success criteria is to ensure that user agents comply with the basic accessibility requirements of the platform in use.

Summary

ChoiceAll responders
Results
Agree with the proposal 4
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal 1

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

Details

Responder Intent for 5.3.2Comments on 5.3.2
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Suggest the following changes to the proposal It's acceptable, but...

Could simplify the first sentence to read "Most operating systems have conventions and expectations that aid accessibility, such as ..." That would also be technically more correct, since some operating systems might not have any such conventions.
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen

16. Intent & Examples for 5.3.1

5.3.1 Implement accessibility features of content specs: Implement and cite in the conformance claim the accessibility features of content specifications. Accessibility features are those that are either (Level A)
• identified as such in the specification or
• allow authors to satisfy a requirement of WCAG.

[SC is for reference only - no change]

proposed Intent

Accessibility features are included in content specs to provide features required by users with various disabilities. If those features are not fully supported by the user agent, users can't easily take advantage of those features. The user should be able to easily discover detailed information about the user agent’s adherence to accessibility standards, including those related to content such as HTML and WAI-ARIA, and should be able to do so without installing and testing the accessibility features. This will allow them to make informed decisions about whether or not to they will be able to use, and therefore should install, a new product or version of that product.

proposed Example

Jordy uses a web site which uses WAI-ARIA to identify the functions of custom controls. If he were to use a web browser that didn't support this aspect of WAI-ARIA and expose that information to assistive technology, the web site would be unusable with his web browser. Therefore Jordy needs to choose a web browser that he knows fully supports WAI-ARIA, and he determines this by reading product documentation and UAAG conformance claims posted on the Web.

Summary

ChoiceAll responders
Results
Agree with the proposal 4
Disagree with the proposal
Neutral, will accept consensus of the group
Suggest the following changes to the proposal 1

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

Details

Responder Intent & Examples for 5.3.1Comments on 5.3.1
Jeanne F Spellman Agree with the proposal
Jan Richards Agree with the proposal
Greg Lowney Suggest the following changes to the proposal It's acceptable, but...

The Intent would be simpler and more accurate to replace the first portion with "Most content specs include features important to users with disabilities, and users may find it difficult or impossible to use a product that fails to support those features. Users should be able to..."

Also could simplify "If he were to use" to "If he used".
Kelly Ford Agree with the proposal
Jim Allan Agree with the proposal
Markku Hakkinen

More details on responses

Non-responders

The following persons have not answered the questionnaire:

  1. Judy Brewer <jbrewer@w3.org>
  2. Eric Hansen <ehansen@ets.org>
  3. Wayne Dick <wayneedick@gmail.com>
  4. Peter Parente <pparent@us.ibm.com>
  5. Simon Pieters <simonp@opera.com>
  6. Takeshi Kurosawa <kurosawa-takeshi@mitsue.co.jp>
  7. Alan Cantor <alan@cantoraccess.com>
  8. Simon Harper <simon.harper@manchester.ac.uk>
  9. Kimberly Patch <Kim@redstartsystems.com>
  10. he wen <rockywen@tencent.com>
  11. Henny Swan <hswan@paciellogroup.com>
  12. Shaohang Yang <shaohang.ysh@alibaba-inc.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


Maintained by Laurent Carcone, from a development by Dominique Hazaël-Massieux (dom@w3.org) on an original design by Michael Sperberg-McQueen $Id: showv.php3,v 1.127 2015-02-04 08:52:34 carcone Exp $. Please send bug reports and request for enhancements to lcarcone@w3.org with w3t-sys@w3.org copied (if your mail client supports it, send mail directly to the right persons)