Thread Subject: Re: Accessible document encodingscheme requirements
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: Peter Korn
Date: Fri, Feb 23 2007 6:50 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Sean Hayes: "Re: Accessible document encodingscheme requirements"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
Hi Andi, Allen,
This is a great list. I have just a few comments on some of the items,
which I am placing in-line for context.
> Proposed CFR1194.27
>
> (a) An encoding mechanism shall be provided to associate non-text elements
> with textual descriptions displayable by a user-agent.
>
We need to be clear on whether this applies to all non-text elements, or
only certain elements (or perhaps define "element"). For example, is it
necessary to be able to encode a text description for each and every
line that makes up spokes of a wheel graphic that is embedded within a
text document advertisement for bicycle wheels? Or only the group of
non-text elements that make up the graphic?
> ...
>
> (f) An encoding mechanism shall be provided to associated row and column
> headers with other table cells, displayable by a user-agent.
>
I think you mean "associate" here, vs. "associated".
Separate from those two points, should there be any statement about
keyboard navigation to content? Imagine for example the objects that
make up a slide presentation - the header, the body text, multiple
images in the body of the slide, etc.
Regards,
Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.
- Next message in Thread: Sean Hayes: "Re: Accessible document encodingscheme requirements"
- Previous message in Thread: None
WebAIM is an initiative of:
