- From: Greg Lowney <gcl-0039@access-research.org>
- Date: Wed, 28 Apr 2010 13:09:19 -0800
- To: WAI-UA list <w3c-wai-ua@w3.org>
- Message-ID: <4BD8A3FF.2040400@access-research.org>
Below are proposed Intent and Examples for 5.3.2 per my survey response
ad our discussion on last weeks' conference call.
My apologies for being late this, but I ended up out of town longer than
expected.
*5.3.2 Document Accessibility Features: *All user agent features that
benefit accessibility @@DEFINE - as specified in the conformance claim@@
are documented. (Level A)
· *Intent of Success Criterion 5.3.2:*
When a product's accessibility features are explained in its
documentation, users can find and learn how to use the features they
need. This is especially critical for users who rely on accessibility
features, as they may need to find and configure those features before
they can effectively explore the product's user interface. If a feature
is undocumented or if its description is difficult find, that features
may as well not exist for many users, particularly if they would have to
hunt for the feature a large set of menus, dialog boxes, and
configuration files.
· *Examples of Success Criterion 5.3.2:*
o Peter uses an alternative keyboard and cannot use a mouse. When he
needs to select and copy text from a Web page, he searches the online
help for "keyboard selection" and gets a page which tells him how to
turn on "caret browsing" and use arrow and shift keys to select the text
he wants. Since he had never heard that phrase before, he's grateful
that it was indexed under terms that came naturally to him.
o Francia relies on a screen reader, and the browser's installation
instructions tell her that she has to start the browser with a specific
command-line option to enable its screen reader compatibility features.
In case she installed the product without reading those instructions,
she can find the same information repeated in the product's primary
documentation.
o Rashid wants to know whether a new mobile phone's media player
supports closed captioning before he purchases it. He consults the
documentation on the manufacturer's Web site, which not only tells him
that the feature is supported but provides instructions for turning them
on and controlling their presentation options.
I have a few more thoughts on 5.3 in general that I'll send in separate
email.
Thanks,
Greg
Received on Wednesday, 28 April 2010 20:09:58 UTC