Thread Subject: Re: General Issues: AT responsibility
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: Wed, Jan 10 2007 10:05 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Andi Snow-Weaver: "Re: General Issues: AT responsibility"
- Previous message in thread: Sean Hayes: "Re: General Issues: AT responsibility"
- Messages sorted by: Author | Thread | Date
> I believe row and header elements are a specific example of the more general case of labelling elements. If there is some reason why they should be handled differently can someone explain why they need to be special cased.
I think reasonable people can put this into different "slots" of 508 -
and certainly of an accessibility API. We've sorted row & column header
information into our AccessibleTable sub-interface. However, I can see
putting it instead into a labeling style of relationship just as easily.
I think the key is that row & column headers need to be exposed
programmatically to AT, and done so in a way that is natural for the API
in use on the platform in question.
Sun Microsystems, Inc.
> Sean Hayes
> Standards and Policy Team
> Accessible Technology Group
> mob +44 7977 455002
> office +44 117 9719730
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi Snow-Weaver
> Sent: 09 January 2007 21:57
> To: = EMAIL ADDRESS REMOVED =
> Subject: [teitac-websoftware] General Issues: AT responsibility
> In the course of our discussions on the exisiting 508 provisions, some
> other, more general issues popped up.
> One of these is the issue of AT responsibility to support what IT provides.
> Mike Fratkin brought up the issue during the discussion on row and column
> headers.  It is often the case that the IT software or website is
> providing accessibility information correctly through a standard
> accessibility API, however, the AT is not extracting the information and
> providing it to the user.
> Someone else mentioned that screen row and column header information would
> be useful to screen magnifier users but that, even though the information
> is available to the AT, screen magnifiers don't provide the information to
> 508 currently does not enforce any requirements on AT to support what IT
> provides. Thoughts on this topic?
>  http://teitac.org/mailarchives/mail_message.php?id=1439&listid=3
- Next message in Thread: Andi Snow-Weaver: "Re: General Issues: AT responsibility"
- Previous message in Thread: Sean Hayes: "Re: General Issues: AT responsibility"