W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2007

User Needs Summary: Guidlines 13-15

From: Peter Parente <pparent@us.ibm.com>
Date: Wed, 16 May 2007 16:11:51 -0400
To: w3c-wai-ua@w3.org
Message-Id: <1179346311.4387.18.camel@localhost.localdomain>
Hi all,

I won't be available for the call tomorrow, but here are my notes for
guidelines 13-15. Feel free to email me questions for clarifications or
ask me the next time we meet.



13.0 Understand how to use product (including discovery and activation
of any access features needed)

Sounds like it maps most closely to Guideline 12 of UAAG (Provide
accessible user agent documentation and help).

13.1 Ability to get overview and orient themselves to product and
functions/parts without relying on visual presentation or markings on

Current mapping: CP 9.9, CP 10.4

I think the ISO checkpoint is talking about orienting the user to the
function of the product, not within the content rendered by the product.
I believe the ISO checkpoint is more closely related to UAAG 12.1-12.5.

13.2 Wording, symbols, and indicators used on products that are as easy
to understand as possible given the device and task.
Note: Information and feedback to be "salient," and "specific" rather
than subtle or abstract in order to understand it.

Current mapping: CP 8.1, CP 8.2

8.1 and 8.2 seem like UAAG catch-all guidelines. Perhaps UAAG should
explicitly talk about the wording, symbols, and indicators used in the
user agent chrome though?

13.3 Products to use standard conventions, words and symbols for their
culture (cross-cultural if possible).

Current mapping: CP 8.1, CP 8.2

Again, I guess it makes sense to defer to other specifications here.

13.4 Clear and easy activation mechanisms for any access features

Current mapping: CP 8.1, CP 8.2, CP 11.7, CP 12.1, CP 12.2, CP 12.3, CP
12.4, CP 12.5

If we accept 11.7, then I'd also add 11.3, 11.4, 11.6, 4.9-4.11, 6.7,
and 9.1. 

13.5 Navigation that supports different thinking styles.

Current mapping: CP 9.9, CP 10.4

The above allow for thinking in terms of document-structure and
outline-structure. I don't see any other guidelines about other
structured views of the content.

13.6 Ability to understand product if they have trouble thinking

Current mapping: CP 9.9, CP 10.4

Isn't 10.4 saying render the page as a hierarchy? Isn't that the
antithesis of this guideline?

13.7 Any text read aloud to them. 

Current mapping: CP 2.2, CP 2.5, CP 6.1, CP 6.2, CP 6.3, CP 6.4, CP 6.5,
CP 6.6, CP 8.1

Add 2.3, 3.4, 4.14 (CSS can add text content), 6.6, and 6.8.

13.8 Steps for operation that are minimized and clearly described.

Current mapping: CP 8.1, CP 8.2, CP 9.9, CP 10.4   

Again, I think this one is more about help than about how the content is
presented. I'd map all of 12.x instead of the above, plus maybe 7.4 and

13.9 Interfaces that limit the memorization required of the user to
operate them successfully.

Current mapping: CP 8.1, CP 8.2

More mappings to the catch-all category. Nothing in UAAG talks
specifically about memorization as far as I can tell. This mapping
refers people to other specs which may or may not cover the topic.

13.10 Cues to assist them in multi-step operations.

Current mapping: None.

Agreed. Nothing in UAAG talks about cueing as far as I can tell. With a
stretch, maybe 5.5.

13.11 Simple interfaces that only require them to deal with the controls
they need (advanced or optional controls removed in some fashion). 

Current mapping: CP 8.1, CP 8.2, CP 9.9, CP 10.4

I would change the mapping to 10.3, 11.6, 9.10, 11.7. Maybe add in all
toggles too with 3.1-3.5 depending on what you want to call the

13.12 Each function on its own key rather than having keys change their
functions but look/feel the same.

Current mapping: CP 1.1, CP 1.2, CP 1.3, CP 6.1, CP 6.2, CP 6.3, CP 6.4,
CP 6.5, CP 6.6, CP 6.7, CP 6.8, CP 7.3, CP 7.4, CP 8.2, CP 9.5, CP 9.6,
CP 9.8, CP 9.9, CP 10.1, CP 10.4, CP 10.5

All of these are related to keyboard access, but I don't think any of
them say "one and only one function per key" (i.e., no modes). I think
modeless operation is what the guideline is suggestion. I do not believe
UAAG has checkpoints on this topic.

13.13 Know that a product is usable by them and how to set it up to work
for them. 

Current mapping: CP 12.1, CP 12.2, CP 12.3, CP 12.4, CP 12.5

Agreed. This is about documentation.

14.0 Understand the output or displayed material (even after they
perceive it accurately) see also “perceive”

14.1 Textual material to be worded as clearly and simply as possible. 

Current mapping: CP 8.1, CP 8.2

Catch-all again.

14.2 Text, illustrations and diagrams in spoken form

Current mapping: CP 1.3, CP 2.2, CP 2.3, CP 2.5, CP 2.6, CP 8.2

Part of this guideline overlaps with 13.7 (Any text read aloud to them.)
I don't think 1.3 applies. 8.2 definitely applies since this is more
about WCAG. What about the chrome of the user agent? Does that fall
under external specs or should something in UAAG address it directly? I
don't see anything.

14.3 To not have device noise or regular audio output interfere with
ability to understand accessibility audio. 

Current mapping: CP 3.2, CP 4.5, CP 4.10, CP 7.3, CP 8.1, CP 8.2

Add 4.8, 4.9 4.11, 4.12, and 4.13.

14.4 Visual information generated by access features (such as captions)
not occur simultaneously with other visual information they must view
(e.g. captions not displayed at same time as critical information on

Current mapping: CP 2.6, CP 3.3, CP 3.4, CP 3.5, CP 4.6, CP 7.3, CP 8.1


14.5 Image resolution and speed be sufficient to understand any sign
language presented

Current mapping: CP 8.1, CP 8.2

Not directly addressed by UAAG.

14.6 Ability to slow audio, video, or animated information down slightly

Current mapping: CP 4.4, CP 4.9


14.7 Ability to replay, pause, change speed in order to understand

Current mapping: CP 4.5, CP 4.9


14.8 Ability to replay auditory information.

Current mapping: CP 4.5, CP 4.9


14.9 Enlargable text wordwrap so that it stays on screen and is

Current mapping: CP 2.1, CP 4.1, CP 6.1, CP 6.2, CP 6.3, CP 6.4, CP 6.5,
CP 8.1, CP 8.2

I'm not sure if all the 6.x directly apply. Yes, programmatic access
allows an AT to provide magnification. But you could say the same thing
about all the other guidelines: that programmatic access could allow an
external agent to do all the work.

14.10 Feedback using pictures or symbols.

Current mapping: CP 7.3, CP 8.1, CP 8.2

I don't think UAAG addresses this topic. 7.3 doesn't seem to apply here,
except to say use pictures/symbol according to your operating

14.11 Ability to silence audio output

Current mapping: CP 3.2, CP 3.5, CP 4.5, CP 4.7, CP 4.8, CP 4.10, CP 7.3

I'd remove 3.5 and 7.3.

15.0 Ability to use their assistive technology (AT) to control the

15.1 Product not interfere with AT.  (e.g. No electrical noise
interference with hearing devices.)

Current mapping: None

Perhaps a UA that does not meet all the 6.x requirements (programmatic
access), is interfering with an AT?

15.2 Ability to use their AT with the device (e.g. Alternate display,
amplifiers, or alternate controls)

Current mapping: None

Add all the 6.x requirements.

15.3 Full and efficient functional control of a product using their AT,
including pass-through of user feedback and notifications such as error

Current mapping: CP 1.1, CP 1.3, CP 6.1, CP 6.2, CP 6.3, CP 6.4, CP 6.5,
CP 6.6, CP 6.7, CP 6.8, CP 6.9

All of 6.x seems most relevant. I'd remove 1.1 and 1.3.

15.4 AT to be available that will work with new technologies, at the
time of release of the new technology

Current mapping: CP 1.1, CP 1.3, CP 6.1, CP 6.2, CP 6.3, CP 6.4, CP 6.5,
CP 6.6, CP 6.7, CP 6.8, CP 6.9, CP 8.1, CP 8.2

Same here. I'd only list the 6.x checkpoints.

Received on Wednesday, 16 May 2007 20:12:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:35 UTC