Re: Should techniques move to HTML5?

Andrew,

I think it is important to create HTML5 specific techniques - especially
where these kinds ofdifferences exist, and keep and identify HTML4
techniques. A note can be added to that HTML4 technique that identifies
that it is not applicable in HTML5.

Katie Haritos-Shea
703-371-5545
On Dec 18, 2015 7:48 AM, "Andrew Kirkpatrick" <akirkpat@adobe.com> wrote:

> 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
> http://twitter.com/awkawk
> http://blogs.adobe.com/accessibility
>