Thread Subject: Re: Group A: 21(c) Keyboard focus
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: Jim Tobias
Date: Mon, Oct 30 2006 8:15 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Andrew Kirkpatrick: "Re: Group A: 21(c) Keyboard focus"
- Previous message in thread: Hoffman, Allen: "Re: Group A: 21(c) Keyboard focus"
- Messages sorted by: Author | Thread | Date
> -----Original Message-----
> From: Hoffman, Allen [mailto: = EMAIL ADDRESS REMOVED = ]
> Sent: Monday, October 30, 2006 9:43 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Group A: 21(c) Keyboard focus
>
<snip>
> These kinds of testing
> tasks need to be part of normal tool sets to become widely
> used in my opinion. Begs the question if development tools
> have a special place, and possible a special requirement to
> match in Section 508 technical standards? I don't see any
> specific location within existing software or web standards
> that this fits into, so this area might have to be addressed
> some other way if it is at all.
Allen, this is a fascinating idea. It would be possible to add such a
requirement to 508: a provision to purchase development tools that support
both accessible content and testing for accessible content. Furthermore,
all web, software, and content developed for federal purposes could be
required to use such tools.
- Next message in Thread: Andrew Kirkpatrick: "Re: Group A: 21(c) Keyboard focus"
- Previous message in Thread: Hoffman, Allen: "Re: Group A: 21(c) Keyboard focus"
WebAIM is an initiative of:
