Thread Subject: Content - proposed wording to address cognitive impairment challenges
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Whitney Quesenbery
Date: Mon, Jun 25 2007 10:05 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Peter Wallack: "Re: Content - proposed wording to address cognitive impairment challenges"
- Previous message in thread: David Poehlman: "Re: Content - proposed wording to address cognitive impairment challenges"
- Messages sorted by: Author | Thread | Date
<html>
<body>
And here's the suggestion for a content requirement:<br><br>
<br>
Authors should follow best practices for creating content that is
accessible for people with disabilities. These guidelines
include:<br><br>
1. Organize the content to serve the
reader?s needs, considering their tasks and goals.<br><br>
2. Use everyday words that convey meaning
clearly and directly.<br><br>
3. Uses the present tense and the active
voice.<br><br>
4. Uses short, simple sentences.<br><br>
5. Includes useful headings.<br><br>
6. Uses lists and tables to simplify
complex material.<br>
Discussion: Clearly written content improves accessibility for people
with several disabilities, including people with cognitive and reading
disabilities, those whose primary language is American Sign Language and
those reading in Braille. <br><br>
<br>
We were thinking about where these provisions could fit:<br><br>
The one for interaction could go in:<br>
3 Software & General Behavior Provisions <br>
[3.1] All products<br><br>
The best fit for the one on content is in the section on 6. Electronic
Content Provisions <br><br>
It could go in [6.1] If Web Content and Applications, but it's not
restricted to web content - and could include documentation,
instructions, error messages and other content in any E&IT.<br><br>
<br><br>
<br>
At 10:07 AM 6/25/2007, Walser, Kate wrote:<br><br>
<blockquote type=cite class=cite cite=""><font face="verdana" size=2>
All,<br>
</font><br>
<font face="verdana" size=2> <br>
</font><br>
<font face="verdana" size=2>Whitney and I drafted wording to address
issues that impact all people with disabilities, especially those with
cognitive impairment. Here?s one related to interaction. Not sure where
it should go ? maybe Web / Software or General. Please take a look and
pose comments. Whitney will send an additional one shortly.<br>
</font><br>
<font face="verdana" size=2> <br>
</font><br>
<font face="verdana" size=2> <br>
</font><br>
<font face="verdana" size=2>X.X - Interaction<br>
</font><br>
<font face="verdana" size=2> <br>
</font><br>
<font face="verdana" size=2>Applications should follow best practices for
designing interaction paradigms that are accessible for people with
disabilities including:<br>
</font><br>
<font face="verdana" size=2>1. Provide a means to undo actions, such as
by resetting the form to the original information <br>
</font><br>
<font face="verdana" size=2>2. Provide a way to move backwards one step
in a process to fix mistakes or check answers <br>
</font><br>
<font face="verdana" size=2>3. Provide a way to cancel actions before
submitting<br>
</font><br>
<font face="verdana" size=2> <br>
</font><br>
<font face="verdana" size=2>Discussion:<br>
</font><br>
<font face="verdana" size=2>Well-designed interaction enables people to
reverse and reset actions in case they have made a mistake or are unable
to complete a transaction at the time. It also provides a way for people
to explore an interaction without the threat of modifying their data
unintentionally. This is particularly helpful for all users, especially
in cases where they have triggered an action unintentionally or realize
they've made a mistake after they've taken the action.<br>
</font><br>
<font face="verdana" size=2> <br>
</font><br>
<font face="verdana" size=2> <br>
</font><br>
<font face="verdana" size=2>Thanks, and best regards,<br>
</font><br>
<font face="verdana" size=2>Kate<br>
</font><br>
<font face="verdana" size=2> <br>
</font><br>
<font face="verdana" size=2> <br>
</font><br>
<font face="verdana" size=1>Kate Walser<br>
</font><br>
<font face="verdana" size=1>Director, Usability Center of Excellence<br>
</font><br>
<font face="verdana" size=1>SRA International, Inc.<br>
</font><br>
<font face="verdana" size=1>4300 Fair Lakes Court<br>
</font><br>
<font face="verdana" size=1>Fairfax</font>, VA 22033<br>
<br>
<font face="verdana" size=1>(703) 502-1170<br>
</font><br>
<font face="verdana" size=2> </blockquote>
<x-sigsep><p></x-sigsep>
<br>
Whitney Quesenbery<br>
Whitney Interactive Design<br>
= EMAIL ADDRESS REMOVED = <br>
phone: 908-638-5467<br>
mobile: 908-328-5959 <br>
<a href="http://www.wqusability.com/" eudora="autourl">
www.WQusability.com<br>
</a><a href="http://www.usabilityprofessionals.org/" eudora="autourl">
www.usabilityprofessionals.org</a> <br><br>
"Warning: Objects in the calendar are closer than they
appear."</font></body>
</html>
- Next message in Thread: Peter Wallack: "Re: Content - proposed wording to address cognitive impairment challenges"
- Previous message in Thread: David Poehlman: "Re: Content - proposed wording to address cognitive impairment challenges"