W3C

Site Navigation

Nearby

Results of Questionnaire UAWG Survey for 1 December 2011

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 2011-11-30 to 2011-12-30.

5 answers have been received.

Jump to results for question:

  1. 2.6.3 Activate all event handlers
  2. 2.7.8 Preferences Wizard
  3. 2.8.1 Configure Position
  4. 2.8.2 Restore Default Toolbars
  5. 2.9.1 Timing Adjustable
  6. 2.9.2 Retrieval Progress
  7. 2.10.1 Three Flashes or Below Threshold
  8. 2.11.1 Background Image Toggle
  9. 2.11.2 Time-Based Media Load-Only
  10. 2.11.5 Playback Rate Adjustment for Prerecorded Content
  11. 2.11.10 Sizing Playback Viewport
  12. 2.6.3 Activate all event handlers
  13. 2.11.12 Adjust Playback Contrast and Brightness

1. 2.6.3 Activate all event handlers

2.6.3 Activate all event handlers

The user can, through keyboard input alone, simultaneously activate all input device event handlers explicitly associated with the content focus element. (Level A)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 2
No, more discussion needed. See comments 3

Details

Responder 2.6.3 Activate all event handlersComments 2.6.3
Greg Lowney No, more discussion needed. See comments As I pointed out on the 9/22 call, simultaneously activating ALL event handlers would be pointless: why would you want to simulate simultaneous click, double click, drag, keydown, keyup, and keypress events?

Maybe the intention is more akin to "The user can, through keyboard input alone, activate *any combination of* input device event handlers explicitly associated with the content focus element."

That's clearer and would be useful, but I don't think it's practical, as it would require that every user agent needs to have built-in macro capability. That doesn't sound like Level A to me.

(FYI a web search shows http://www.w3.org/WAI/UA/2010/ED-UAAG20-20100224/Overview.html to be the earliest occurrence of "simultaneously activate all input device event handlers", but it's been taken up by PF at http://www.w3.org/WAI/PF/HTML/wiki/Access/event_handler_requirements.)
Simon Harper Yes, it is ok as is
Jeanne F Spellman No, more discussion needed. See comments This is dated. Widgets are far more complex these days, and you could create havoc activating all input device handlers. I think we should delete this one.
Jim Allan Yes, it is ok as is
Kimberly Patch No, more discussion needed. See comments The user can, through a modalality independent interface...

2. 2.7.8 Preferences Wizard

2.7.8 Preferences Wizard

A wizard helps the user to configure the accessibility-related user agent preferences (at least). (Level AAA)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 5
No, more discussion needed. See comments

Details

Responder 2.7.8 Preferences WizardComments 2.7.8
Greg Lowney Yes, it is ok as is OK but could be better.

1. Overall I don't consider this one important; "wizards" in their common implementation are only one way of addressing the high-level goal, but since it's only AAA it can stay.

2. I'd take out "(out least)"; you could clarify in the Intent paragraph that it's fine if the wizard include other options as well.

3. Do we need to define wizard? OS X and Gnome both use other terms.

4. By saying "A wizard" are we limiting it to a single wizard? If a product has separate wizards for visual settings, audio settings, etc., would we really want it to fail?
Simon Harper Yes, it is ok as is
Jeanne F Spellman Yes, it is ok as is although we probably need a testable definition of "wizard"
Jim Allan Yes, it is ok as is
Kimberly Patch Yes, it is ok as is

3. 2.8.1 Configure Position

2.8.1 Configure Position

When graphical *user agent user interfaces* have toolbars, panels, inspectors, or similar, the user can add, remove and configure the position of user agent *user interface controls* from a pre-defined set. (Level AAA)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 4
No, more discussion needed. See comments 1

Details

Responder 2.8.1 Configure PositionComments 2.8.1
Greg Lowney No, more discussion needed. See comments 1. Acceptable at Level AAA, but it's pretty vague. Is a menu bar "similar" enough to a toolbar? How about a status bar that includes controls? It's also hard for me to see why you would want this power over controls in a window's "panel" but not controls in the window itself. If a panel appears only during a certain task, is it a panel and covered by this SC, or just an alternative presentation of a modeless dialog box, and therefore not covered?

2. Technically the grammar is incorrect, since it actually states that IF a browser has toolbars, ALL UI controls need to be configurable, not just those in the toolbars. This could be corrected by changing to something like "The user can add, remove, or reposition predefined controls in toolbars, side panels, and the like that are part of the user agent user interface."
Simon Harper Yes, it is ok as is Sounds Like a tongue twister!

Sentiment is good - language seems complicated.
Jeanne F Spellman Yes, it is ok as is
Jim Allan Yes, it is ok as is
Kimberly Patch Yes, it is ok as is

4. 2.8.2 Restore Default Toolbars

2.8.2 Restore Default Toolbars

The user can restore the default toolbar, panel, or inspector configuration. (Level AAA)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 5
No, more discussion needed. See comments

Details

Responder 2.8.2 Restore Default ToolbarsComments 2.8.2
Greg Lowney Yes, it is ok as is
Simon Harper Yes, it is ok as is
Jeanne F Spellman Yes, it is ok as is Probably could be AA
Jim Allan Yes, it is ok as is
Kimberly Patch Yes, it is ok as is

5. 2.9.1 Timing Adjustable

2.9.1 Timing Adjustable

Where time limits for user input are recognized and controllable by the user agent, the user can extend the time limit. (Level A)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 5
No, more discussion needed. See comments

Details

Responder 2.9.1 Timing AdjustableComments 2.9.1
Greg Lowney Yes, it is ok as is OK, but there is a minor disagreement of plural (time limits for user input) vs. singular (the time limit) that could be fixed by making the last word to "limits".
Simon Harper Yes, it is ok as is
Jeanne F Spellman Yes, it is ok as is
Jim Allan Yes, it is ok as is
Kimberly Patch Yes, it is ok as is

6. 2.9.2 Retrieval Progress

2.9.2 Retrieval Progress

By default, the user agent shows the progress of content retrieval. (Level A)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 4
No, more discussion needed. See comments 1

Details

Responder 2.9.2 Retrieval ProgressComments 2.9.2
Greg Lowney Yes, it is ok as is
Simon Harper Yes, it is ok as is
Jeanne F Spellman No, more discussion needed. See comments ..."in a programmatically accessible manner." "Shows" is too vague.
Jim Allan Yes, it is ok as is
Kimberly Patch Yes, it is ok as is

7. 2.10.1 Three Flashes or Below Threshold

2.10.1 Three Flashes or Below Threshold

In its default configuration, the user agent does not display any user interface components or recognized content that flashes more than three times in any one-second period, unless the flash is below the general flash and red flash thresholds. (Level A)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 5
No, more discussion needed. See comments

Details

Responder 2.10.1 Three Flashes or Below ThresholdComments 2.10.1
Greg Lowney Yes, it is ok as is
Simon Harper Yes, it is ok as is
Jeanne F Spellman Yes, it is ok as is
Jim Allan Yes, it is ok as is
Kimberly Patch Yes, it is ok as is

8. 2.11.1 Background Image Toggle

2.11.1 Background Image Toggle

The user has the global option to hide/show background images. (Level A)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 5
No, more discussion needed. See comments

Details

Responder 2.11.1 Background Image ToggleComments 2.11.1
Greg Lowney Yes, it is ok as is OK, although could also say "options to hide or show" rather than using the slash construction.
Simon Harper Yes, it is ok as is
Jeanne F Spellman Yes, it is ok as is
Jim Allan Yes, it is ok as is
Kimberly Patch Yes, it is ok as is

9. 2.11.2 Time-Based Media Load-Only

2.11.2 Time-Based Media Load-Only

The user can load time-based media content @@ Editors' Note: DEFINE@@ such that a placeholder is displayed, but the content is not played until explicit user request. (Level A)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 4
No, more discussion needed. See comments 1

Details

Responder 2.11.2 Time-Based Media Load-OnlyComments 2.11.2
Greg Lowney Yes, it is ok as is It's OK, but could be better: since the user is actually choosing NOT to "load" the time-based media, at least in those cases where the placeholder can be rendered without having to load the media content, I think it would be better as something like "The user have placeholders rendered for time-based media content, such that the content is not played until explicit user request."
Simon Harper Yes, it is ok as is until **an** explicit user request
Jeanne F Spellman Yes, it is ok as is
Jim Allan Yes, it is ok as is
Kimberly Patch No, more discussion needed. See comments definition needed

10. 2.11.5 Playback Rate Adjustment for Prerecorded Content

2.11.5 Playback Rate Adjustment for Prerecorded Content

The user can adjust the playback rate of prerecorded time-based media content, such that all of the following are true: (Level A)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 4
No, more discussion needed. See comments 1

Details

Responder 2.11.5 Playback Rate Adjustment for Prerecorded ContentComments 2.11.5
Greg Lowney No, more discussion needed. See comments 1. Re (a), didn't I see proposed or related wording earlier that talked about a minimum number of settings available between and including the minimum and maximum values? The wording here would allow passing with two values, 100% and 110%, as they are both between 50% and 250%. Yet we do not want to require infinitely fine gradation either.

2. This and other SC in this section use the term "content", implying that they apply to media that's author-specified but not media that's included as part of the user agent user interface. If, for example, the user agent's help is in the form of a video, does or should anything require its playback speed to be adjustable?

3. We may not want to get that detailed, but currently a product could pass if the user could only change the playback options for the entire duration of the recording. For example, if you could choose options for playing at speeds from 50% to 250%, but changing the speed would always restart the media at the beginning, a lot of both the mainstream and accessibility benefits would be lost.

4. It seems unclear what the fourth item is requiring. Does it just mean that the speed settings available to satisfy the first item must include 100%? Or is it trying to say there must be a shortcut of some type making it easier to reset to 100% than to other speeds?

5. Editorial, but the wording of the fourth item doesn’t match the style of the first three; it would if reworded as "The user can reset the playback rate to normal (100%)." (Although, as I already mentioned, that seems redundant.)
Simon Harper Yes, it is ok as is
Jeanne F Spellman Yes, it is ok as is
Jim Allan Yes, it is ok as is
Kimberly Patch Yes, it is ok as is

11. 2.11.10 Sizing Playback Viewport

2.11.10 Sizing Playback Viewport

The user can adjust the size of the time-based media up to the full height or width of the containing viewport. In doing so, the user can preserve aspect ratio and adjust the size of the playback viewport to avoid cropping, within the scaling limitations imposed by the media itself. (Level AA)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 4
No, more discussion needed. See comments 1

Details

Responder 2.11.10 Sizing Playback ViewportComments 2.11.10
Greg Lowney No, more discussion needed. See comments There are quite a few things about this SC that don't make sense to me. Do you mean something like "The user can adjust the size of time-based media to the largest size that fits within the containing viewport without cropping or changing aspect ratio, within any limitations imposed by the media or platform"? (This doesn't address #4 or 5, below.)

1. I don't understand the part about "adjust the size of the playback viewport ". Did you use two different phrases, "the time-based media" in the first sentence and "the playback viewport" in the second, to mean the same thing? If so, I think that just creates confusion. If not, then I don't understand the second sentence at all, but if you did, then it seems that most of the second sentence is redundant to the first.

2. I don't understand the phrase "and adjust the size of the playback video to avoid cropping".

3. It's ambiguous as to which sentence(s) or clause(s) "within the scaling limitations imposed by the media itself" applies to. Are the limitations you're referring to something like video that can never be resized for technical or licensing reasons? What about cases where the media is in theory scalable, but the user agent cannot do it because of limitations of bandwidth, memory, or computing power?

4. What about cases where maximizing the size of the video leaves no room for captions or playback controls that are normally shown along with the video in the same viewport? Is what we really intend is to maximize the size of the media and its accompanying controls, or are you intending that accompanying captions or controls be made "floatable" over the playing media? Note that the SC currently does not require any sizes other than the full height or width of the viewport.

5. Is it worth addressing the benefits of full-screen playback?
Simon Harper Yes, it is ok as is
Jeanne F Spellman Yes, it is ok as is
Jim Allan Yes, it is ok as is
Kimberly Patch Yes, it is ok as is

12. 2.6.3 Activate all event handlers

2.6.3 Activate all event handlers

The user can, through keyboard input alone, simultaneously activate all input device event handlers explicitly associated with the content focus element. (Level A)

Summary

ChoiceAll responders
Results
Yes, it is ok as is 2
No, more discussion needed. See comments 1

Details

Responder 2.6.3 Activate all event handlersComments 2.6.3
Greg Lowney No, more discussion needed. See comments This is a repeat of question #1; see comments above.
Simon Harper Yes, it is ok as is
Jeanne F Spellman
Jim Allan Yes, it is ok as is
Kimberly Patch

13. 2.11.12 Adjust Playback Contrast and Brightness

2.11.12 Adjust Playback Contrast and Brightness

User can control the contrast and brightness of the content within the playback viewport.

Applicability Notes:

The guideline only applies to images, animations, video, audio, etc. that the user agent can recognize.

Summary

ChoiceAll responders
Results
Yes, it is ok as is 3
No, more discussion needed. See comments 2

Details

Responder 2.11.12 Adjust Playback Contrast and BrightnessComments 2.11.12
Greg Lowney No, more discussion needed. See comments Needs a Priority Level.

As noted above, I don't really like introducing the term "playback viewport" for what we refer to in other places as "the time-based media". In this case, do you really mean just the playing media, or also to accompanying playback controls, captions and the like that appear in the same viewport?

The use of the phrase "playback" implies that this applies specifically to time-based media, but the wording of the SC applies to anything and everything in the viewport where some media is played, including text. Is that intended, or accidental?

Editorial: "The user" would be better than "User".

We could remove the Applicability Note by changing "the content" to "recognized content", as in "The user can control the contrast and brightness of recognized content within the playback viewport."

It's not clear what is meant by adjusting "contrast and brightness" or audio content, which the Applicability Note requires.
Simon Harper No, more discussion needed. See comments I think this one is really onerous - does anything do this?
Jeanne F Spellman Yes, it is ok as is
Jim Allan Yes, it is ok as is
Kimberly Patch Yes, it is ok as is

More details on responses

  • Greg Lowney: last responded on 1, December 2011 at 06:59 (UTC)
  • Simon Harper: last responded on 1, December 2011 at 07:05 (UTC)
  • Jeanne F Spellman: last responded on 1, December 2011 at 16:20 (UTC)
  • Jim Allan: last responded on 1, December 2011 at 17:40 (UTC)
  • Kimberly Patch: last responded on 1, December 2011 at 18:44 (UTC)

Everybody has responded to this questionnaire.

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

WBS home / Questionnaires / WG questionnaires / Answer this questionnaire

Report issues on GitHub project w3c/wbs-design or by mail to sysreq.