Thread Subject: Timing Provision
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: Andi Snow-Weaver
Date: Fri, Jun 22 2007 3:15 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Gregg Vanderheiden: "Re: Timing Provision"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
The Self-contained Closed products subcommittee has recommended that there
not be a separate category. Rather they recommend that in closed products,
the hardware should meet the hardware provisions and the software should
meet the software provisions. One consequence of this is that the timing
provision previously in the self-contained category is now in the software
section of the current working draft. [1]
We discussed the web version of this provision at length. "Sufficient time
to respond" is a testability issue. We concluded that we should harmonize
this with WCAG 2.0. [2] The ISO Software Accessibility standard has taken a
similar approach as WCAG 2.0 and has an identical provision on timing.
Unless there are any objections, I propose that we recommend the same
provision for software.
Note that we are still discussing some of the latest wording changes in
WCAG 2.0 and some issues have been raised with regard to testing software.
But in general, I think we are agreed that this is the approach we want to
take and are just working out some of the details.
[1] http://teitac.org/wiki/EWG:Draft_May_30#D._Timing
[2] http://teitac.org/wiki/EWG:Draft_May_30#K._Timing_.28Web.29
Andi
- Next message in Thread: Gregg Vanderheiden: "Re: Timing Provision"
- Previous message in Thread: None
WebAIM is an initiative of:
