Thread Subject: Re:
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: Mon, Jan 22 2007 1:30 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: Hoffman, Allen: "Re:"
- Messages sorted by: Author | Thread | Date
Allen,
Can you make a draft proposal?
Andi
Allen Hoffman wrote:
I can't concur more with Peter's summary of the components for
document
down
encoding
Hoffman
As far as tools go, I would think we would still need a well-defined
> API or standard format for content types (e.g., SGML, XHTML, XML, ODF,
RTF, PDF, etc.) along with the proper versioning before we could begin
recommending tools.
the first issue is whether all of
can be encoded in the format
(e.g. HTML defining the existence of ALT tags for images -> if there
such a definition, then you can't encode it even if you want to).
that is the question of whether document authors are encoding
information that they should. This will likely give rise to some
calls -> if a particular document element can have both a name
description, it may not always be necessary for obvious/simple
have a description in addition to the name. The third (and
issue is ensuring that the applications that
are accessible, support AT on the
this has less to do with any specific standard format, as it
any every document format in question must address the
document authors address the second, and document
the
third)."
mailing list
http://list.teitac.org/mailman/listinfo/teitac-websoftware
- Next message in Thread: None
- Previous message in Thread: Hoffman, Allen: "Re:"
WebAIM is an initiative of:
