Thread Subject: Re: Allen's proposal for a newsection oncontent
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: Mon, Apr 02 2007 8:30 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Lybarger, Barbara (MOD): "Re: Allen's proposal for a newsection oncontent"
- Previous message in thread: Gregg Vanderheiden: "Re: Allen's proposal for a newsection oncontent"
- Messages sorted by: Author | Thread | Date
On your second point below. That is fine. If people will read
'encoding' in the general sense then we are ok.
On the first point, (i.e. color values of the foreground text and
background) I still am not sure I understand the benefit. If the
content is rendered
to the screen the AT can always get the color values. But from
discussions in our other group it was my understanding that there are
no AT that can deal
with presenting the millions of colors to people in a way that they can
Could you provide some examples of how this information would be used by
Also, why you think that it wouldn't always be available anyway?"
Let me take a stab at this by retracing my original thinking which of
course could be faulty:
The idea is to define a minimum set of accessibility capacities that
*m7st* be included in a method to store information for presentation.
For example, if tabular formats are supported in the format, then we
need to be able to associate headers and cells specifically.
When thinking about color we have "color shall not be used as the only
means to convey information..."
We also have requirements now about text attributes such as font, etc.
So if color is supported in the format, we need to ensure that the color
values, which could be from a wide range, are accessible by AT. This
may be mute as we have discussed, as the color has to be represented in
some way, and the user-agent would then present it. I guess I'm
thinking that we just should say that color values should be accessible
which may not need saying at all.
Color values are used by AT to tell what color items are, and in HTML is
definitely derived from the HTML generally.
I may be talking myself out of this requirement for encoding schemes,
but that's fine as long as we at least explored it before tossing it
Allen hoffman -- 202-447-0303
- Next message in Thread: Lybarger, Barbara (MOD): "Re: Allen's proposal for a newsection oncontent"
- Previous message in Thread: Gregg Vanderheiden: "Re: Allen's proposal for a newsection oncontent"