Thread Subject: Re: Group D: 22(g) Row and Column Headers
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: Fratkin, Mike
Date: Thu, Nov 30 2006 5:55 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Travis Roth: "Re: Group D: 22(g) Row and Column Headers"
- Previous message in thread: email@example.com: "Re: Group D: 22(g) Row and Column Headers"
- Messages sorted by: Author | Thread | Date
The WCAG language for tables addressed in the techniques for 1.3.1 may
be understandable for developers but may not be easily understood by
people assessing VPAT's or people testing for compliance. The Section
508 language seems to be more to the pint and clearer.
Additionally, the requirements for row and column header identification
greatly benefit users of screen readers but there is no capability for
low vision, screen magnification users to know row and column headers
when focused on data cells. Should this capability be the
responsibility of AT vendors or HTML enhancements?
Current wording: Row and column headers shall be identified for data
- in WCAG 2.0, tables are addressed in the techniques for 1.3.1 "
Information and relationships conveyed through presentation can be
programmatically determined, and notification of changes to these is
available to user agents, including assistive technologies."
- This is only in the Web requirements. Is this required for software?
- Are all data tables user interface elements or only those that contain
interactive user interface elements?
- Next message in Thread: Travis Roth: "Re: Group D: 22(g) Row and Column Headers"
- Previous message in Thread: firstname.lastname@example.org: "Re: Group D: 22(g) Row and Column Headers"