Thread Subject: Accessible document encoding schemerequirements

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, Feb 23 2007 1:30 PM


Allen Hoffman posted a proposal to the list a few weeks ago but I think it
got missed by most of you because the subject line didn't reflect the
content of the post. The proposal was a list of requirements for a document
encoding scheme to meet in order to be considered accessible. I've copied
it here in a new thread so we can discuss it. Please review this and
comment on it. We will discuss it at next week's meeting.

<beginning of Allen's proposal>

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.

<end of Allen's proposal>

Andi


  • Next message in Thread: None
  • Previous message in Thread: None

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University