RE: Should techniques move to HTML5?

2. Change the entire technique to HTML5 and removing the TD scope line in the procedure.  Also note that @scope on TD is a legacy solution for HTML4/XHTML and is discouraged (forbidden?) by HTML5. 

 

JF

 

From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com] 
Sent: Friday, December 18, 2015 9:47 AM
To: WCAG <w3c-wai-gl@w3.org>
Subject: Should techniques move to HTML5?

 

Hey, we received a new issue from Mark Rogers (https://github.com/w3c/wcag/issues/127) which notes an issue in F91.  F91 includes an allowance for a table header to be identified with <td scope=“col”> but HTML5 explicitly disallows the use of scope on TD elements.

 

We could:

1. Add in "(HTML4 and XHTML only)” for the line in the procedure that allows for this
2. Change the entire technique to HTML5 and removing the TD scope line in the procedure.
3. Make a new, very similar failure for HTML5 that removes the TD scope line.

I’m sure that we aren’t interested in encouraging TD with scope, but as a failure we need to be careful.

 

What do people think?  Is there a downside to adapting this and other techniques to HTML5, even if it means losing some HTML4 content?

 

Thanks,

AWK

 

Andrew Kirkpatrick

Group Product Manager, Accessibility

Adobe 

 

akirkpat@adobe.com <mailto:akirkpat@adobe.com> 

http://twitter.com/awkawk

http://blogs.adobe.com/accessibility