Re: Should techniques move to HTML5?

Do whatever will be most clear for users AND require least amount of maintenance going forward (HTML5.1, anyone?). 

I suggest: 
5. headers marked up as td elements with the scope attribute (HTML4 only)

Mike
 

    On Friday, December 18, 2015 11:25 AM, John Foliot <john.foliot@deque.com> wrote:
 

 #yiv5602359274 #yiv5602359274 -- _filtered #yiv5602359274 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv5602359274 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv5602359274 #yiv5602359274 p.yiv5602359274MsoNormal, #yiv5602359274 li.yiv5602359274MsoNormal, #yiv5602359274 div.yiv5602359274MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv5602359274 a:link, #yiv5602359274 span.yiv5602359274MsoHyperlink {color:blue;text-decoration:underline;}#yiv5602359274 a:visited, #yiv5602359274 span.yiv5602359274MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv5602359274 span.yiv5602359274EmailStyle17 {color:#1F497D;}#yiv5602359274 .yiv5602359274MsoChpDefault {font-size:10.0pt;} _filtered #yiv5602359274 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv5602359274 div.yiv5602359274WordSection1 {}#yiv5602359274 _filtered #yiv5602359274 {} _filtered #yiv5602359274 {} _filtered #yiv5602359274 {} _filtered #yiv5602359274 {} _filtered #yiv5602359274 {} _filtered #yiv5602359274 {} _filtered #yiv5602359274 {} _filtered #yiv5602359274 {} _filtered #yiv5602359274 {} _filtered #yiv5602359274 {}#yiv5602359274 ol {margin-bottom:0in;}#yiv5602359274 ul {margin-bottom:0in;}#yiv5602359274 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:   
   - Add in "(HTML4 and XHTML only)” for the line in the procedure that allows for this
   - Change the entire technique to HTML5 and removing the TD scope line in the procedure.
   - 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 KirkpatrickGroup Product Manager, AccessibilityAdobe   akirkpat@adobe.comhttp://twitter.com/awkawkhttp://blogs.adobe.com/accessibility