Thread Subject: Re: 1194.22(b) in Group A: Re: Jim Tobias'comment about requiring AT
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: Andi Snow-Weaver
Date: Thu, Oct 19 2006 12:50 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Jim Tobias: "Re: 1194.22(b) in Group A: Re: Jim Tobias'commentabout requiring AT"
- Previous message in thread: Peter Korn: "1194.22(b) in Group A: Re: Jim Tobias' commentabout requiring AT"
- Messages sorted by: Author | Thread | Date
<beginning of Peter's comment>
"I believe we should have outcomes-based requirements (e.g. "a user must
be able to operate all keyboard functions with a single keypress"), and
then recommend specific guidance as to how to accomplish thing (e.g.
"cf. StickyKeys capabilities for latching keyboard modifiers"), and the
finally ensure that we don't foreclose innovation (by maintaining 1194.5
Equivalent facilitation "Nothing in this part is intended to prevent the
use of designs or technologies as alternatives to those prescribed in
this part provided they result in substantially equivalent or greater
access to and use of a product for people with disabilities.")."
<end of Peter's comment>
Peter, I understand the desire for not making 508 too prescriptive about
where the function must be provided but this approach complicates
compliance reporting for multi-platform products. If your software depends
on StickyKeys in the OS to support this requirement, then the same software
product will be 508 compliant on platforms that include StickyKeys but
non-compliant on platforms that don't.
- Next message in Thread: Jim Tobias: "Re: 1194.22(b) in Group A: Re: Jim Tobias'commentabout requiring AT"
- Previous message in Thread: Peter Korn: "1194.22(b) in Group A: Re: Jim Tobias' commentabout requiring AT"