Thread Subject: Re: Web and Software subcommittee meetingwillstart at 9:45 AM Eastern time
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: Hoffman, Allen
Date: Thu, Feb 08 2007 10:17 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: Andi Snow-Weaver: "Web and Software subcommittee meeting willstart at 9:45 AM Eastern time"
- Messages sorted by: Author | Thread | Date
All:
Below are some items that might be considered as part of a set that
defines a minimum list of attributes or capacities for a document
encoding scheme to include to be considered "accessible", in and of
itself. I'd like to throw this out for discussion as we begin moving to
the content questions.
Proposed CFR1194.27
(a) An encoding mechanism shall be provided to associate non-text
elements with textual descriptions displayable by a user-agent.
(b) An encoding mechanism shall be provided to include synchronized
text of verbal content, and audio descriptions of critical nonverbal
activity displayable by a user-agent.
(c) An encoding mechanism shall be provided to identify all colors
selected for text, both foreground and background displayable by a
user-agent.
(d) An encoding mechanism shall be provided to identify the logical
reading order of the content displayable by a user-agent.
(e) An encoding mechanism shall be provided to identify row and
column headers for tabular information displayable by a user-agent.
(f) An encoding mechanism shall be provided to associated row and
column headers with other table cells, displayable by a user-agent.
(g) An encoding mechanism shall be provided to identify identity,
operation, and state, of any interactive elements displayable by a
user-agent.
(h) An encoding mechanism shall be provided to identify link text or
graphics displayable by a user-agent.
(i) An encoding mechanism shall be provided to identify embedded
comments and associate those comment locations within the document.
(j) Encoding mechanism which allow programmatic input and execution
of end-user scripting, shall provide access to the embedded scripts.
(k) An encoding mechanism shall be provided to identify text of
scanned images of text, displayable by a user-agent. Note, this means
allowing for inclusion of the text of a scanned image of text.
(l) An encoding mechanism shall be provided to include data used for
any dynamic presentations, graphs, or other extracted information
displayable by a user-agent.
Allen Hoffman
DHS Office on Accessible Systems & Technology
- Next message in Thread: None
- Previous message in Thread: Andi Snow-Weaver: "Web and Software subcommittee meeting willstart at 9:45 AM Eastern time"
WebAIM is an initiative of:
