WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: accessible tables: colgroup vs headers and ids

for

From: Trafford, Logan
Date: Apr 18, 2016 6:03AM

My guess is that AChecker's algorithms have a condition built in that checks for any colspans (or rowspans) and once it encounters one, the result is that it wants headers and ids defined.

In theory, colgroup and scope SHOULD be sufficient.
https://www.w3.org/WAI/tutorials/tables/irregular/


Logan

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Angela French
Sent: Friday, April 15, 2016 3:32 PM
To: WebAim Forum ( <EMAIL REMOVED> )
Subject: [WebAIM] accessible tables: colgroup vs headers and ids

Hello,
I would appreciate a little accessibility-related feedback on the two tables on this page<http://www.sbctc.edu/colleges-staff/policies-rules/policy-manual/ch6-append-h.aspx>;. We have used the scope attribute, in an attempt to make complex tables accessible, because that is all that the text editor in our CMS provides. However, the accessibility validator in our CMS, which uses http://achecker.ca throws errors for not using headers and ids. Does properly used colgroup suffice, or is it necessary to hand code such tables with headers and ids to make them accessible?

Thanks,



Angela French
Internet/Intranet Specialist
Washington State Board for Community and Technical Colleges
360-704-4316
<EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
www.sbctc.edu<;http://www.sbctc.edu/>;

This e-mail originates from the City of Ottawa e-mail system. Any distribution, use or copying of this e-mail or the information it contains by other than the intended recipient(s) is unauthorized. Thank you.

Le présent courriel a été expédié par le système de courriels de la Ville d'Ottawa. Toute distribution, utilisation ou reproduction du courriel ou des renseignements qui s'y trouvent par une personne autre que son destinataire prévu est interdite. Je vous remercie de votre collaboration.