Thread Subject: Re: Group A distinguishing
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: Hoffman, Allen
Date: Tue, Oct 24 2006 12:25 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Andrew Kirkpatrick: "Re: Group A distinguishing"
- Previous message in thread: Hoffman, Allen: "Re: Group A distinguishing"
- Messages sorted by: Author | Thread | Date
When tabular or coordinate-based software or web interface elements are
used, information for identity, operation, state, focus, and content
must be programmatically exposed to assistive technology to allow the
end-user to access the information and relationships presented.
This sums up where my thoughts are going with the concept of combining
web and software provisions, at least for tables.
I suppose one might expand it to far, and cover other interface
elements, but that might be a bit hard to understand.
When software or web user interface elements are used to convey
information, prompt for and action, or perform interaction between the
user and the EIT, , including tabular or coordinate-based elements,
information for identity, operation, state, focus, and content must be
programmatically exposed to assistive technology to allow the end-user
to access the information and relationships presented.
This reads to me as a set, a condition (even if it is a long string of
or conditions), and an outcome, or requirement.
I'm certainly not attached to any of this writing, just providing some
example for us to chew on.
Department of Homeland Security