Thread Subject: Re: Content
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: Roberto Scano - IWA/HWG
Date: Fri, Jan 12 2007 2:20 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Hoffman, Allen: "Re: Content"
- Previous message in thread: Andi Snow-Weaver: "Content"
- Messages sorted by: Author | Thread | Date
----- Original Message -----
From: "Andi Snow-Weaver" < = EMAIL ADDRESS REMOVED = >
To: < = EMAIL ADDRESS REMOVED = >
Sent: Friday, January 12, 2007 10:04 PM
Subject: [teitac-websoftware] Content
It's time to start discussing the issues around content. We have collected
a number of issues , specifically:
- forms embedded in e-mail
- e-mail attachments (Word, PDF, JPG, GIF formats)
- TIFF and PDF documents on the Web
- row and column headers in content
Are there other issues?
Another accessibility problem in e-mail is quoting of content. There are
some suggestion about how to quote in accessible mode
Thoughts on how we might solve the issues?
For e-mail attachment, what we can suggest is to follow the accessibility
guidelines developed/offered by the company that develop the document (eg:
Microsoft Word, Excel, PDF, etc.). For raw images, like JPG, TIFF, GIF,
there is no possibility to define an "alt" attribute: user should add
textual description for raw image attachments inside body of message.
Another problem is the e-mail rendering by User Agents: if i send, for
example, an e-mail formatted in XHTML, my e-mail client convert in MSHTML...
So how can we guarantee that the sent content will be rendered "as is" in
the receiver user agent?