Proposed accessible name and description calculations for TABLE markup

One of the main questions is the mapping of table related markup to accessibility APIs to ensure the consistent browser and assistive technology behavior that everyone wants and to give developers predictable design practices.  

The markup under discussion includes:

CAPTION element
SUMMARY attribute
ARIA-LABELLEDBY attribute
ARIA-LABEL attribute
ARIA-DESCRIBEDBY attribute

The primary accessibility API mappings of concern are:

1. Accessible Name
2. Accessible Description

Suggested order of Accessible NAME calculation:

CAPTION element content 
ARIA-LABEL attribute value
ARIA-LABELLEDBY attribute calculated value (from list of ID references in ID order)

Suggested order of Accessible DESCRIPTION calculation:

Summary attribute value
ARIA-DESCRIBEDBY attribute calculated value (from list of ID references in ID oreder)


This algorithm provides both inline and reference means to provide accessible names and descriptions for tables, is compatible with previous accessibility techniques and the new aria techniques.


Jon Gunderson, Ph.D.
Coordinator Information Technology Accessibility
Disability Resources and Educational Services

Rehabilitation Education Center
Room 86
1207 S. Oak Street
Champaign, Illinois 61820

Voice: (217) 244-5870

WWW: http://www.cita.illinois.edu/
WWW: https://netfiles.uiuc.edu/jongund/www/

---------------------------------------------------------------
Privacy Information
---------------------------------------------------------------
This email (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. It is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this email is not the intended recipient, or agent responsible for delivering or copying of this communication, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the sender that you have received the message in error, then delete it. Thank you.

Received on Thursday, 7 January 2010 15:10:36 UTC