Thread Subject: Re: Group A: 21(c) Keyboard focus
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: Andrew Kirkpatrick
Date: Mon, Oct 30 2006 8:40 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Jim Tobias: "Re: Group A: 21(c) Keyboard focus"
- Previous message in thread: Jim Tobias: "Re: Group A: 21(c) Keyboard focus"
- Messages sorted by: Author | Thread | Date
> 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.
There is a whole industry that develops testing tools for various
technologies, I don't think that it is wise to remove competition and
innovation from that space by requiring that accessibility testing tools
be built into development tools.
I'm also concerned that the definition of "development tool" is
increasingly hard to pin down - does every CMS need to include this
functionality? Microsoft Word can create web pages from Word docs -
should Word inclue this also?
Testing tools are not the panacea that we'd all like them to be, I'm
worried that too much focus on integrated testing for accessibility
reinforces that misconception.