Re: Should techniques move to HTML5?

Hi Andrew, all--
It seems that deprecation in HTML5 is straightforward and means it shouldn't be used, even if it is supported by AT.
Maybe I don't understand the distinction between it being an HTML5 vs. a WCAG issue, though...

Mike
 

    On Friday, December 18, 2015 12:27 PM, Andrew Kirkpatrick <akirkpat@adobe.com> wrote:
 

 It’s a good point Jon. 
I tried an HTML5 file with td’s with scope (http://awkawk.github.io/table_td_scope_5.html) and found that at least on OSX that the scope attribute is honored.  I’m not sure how other combinations deal with this…
Thanks,AWK
Andrew KirkpatrickGroup Product Manager, AccessibilityAdobe 
akirkpat@adobe.comhttp://twitter.com/awkawkhttp://blogs.adobe.com/accessibility
From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Friday, December 18, 2015 at 11:03
To: Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
Subject: RE: Should techniques move to HTML5?

#yiv1643967315 #yiv1643967315 -- _filtered #yiv1643967315 {font-family:Wingdings;panose-1:5 0 0 0 0 0 0 0 0 0;} _filtered #yiv1643967315 {font-family:Wingdings;panose-1:5 0 0 0 0 0 0 0 0 0;} _filtered #yiv1643967315 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv1643967315 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv1643967315 #yiv1643967315 p.yiv1643967315MsoNormal, #yiv1643967315 li.yiv1643967315MsoNormal, #yiv1643967315 div.yiv1643967315MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv1643967315 a:link, #yiv1643967315 span.yiv1643967315MsoHyperlink {color:blue;text-decoration:underline;}#yiv1643967315 a:visited, #yiv1643967315 span.yiv1643967315MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv1643967315 p.yiv1643967315MsoListParagraph, #yiv1643967315 li.yiv1643967315MsoListParagraph, #yiv1643967315 div.yiv1643967315MsoListParagraph {margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv1643967315 span.yiv1643967315EmailStyle17 {color:#44546A;}#yiv1643967315 .yiv1643967315MsoChpDefault {font-size:10.0pt;} _filtered #yiv1643967315 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv1643967315 div.yiv1643967315WordSection1 {}#yiv1643967315 _filtered #yiv1643967315 {} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {font-family:Wingdings;} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {font-family:Wingdings;} _filtered #yiv1643967315 {font-family:Symbol;} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {font-family:Wingdings;} _filtered #yiv1643967315 {font-family:Symbol;} _filtered #yiv1643967315 {} _filtered #yiv1643967315 {font-family:Wingdings;}#yiv1643967315 ol {margin-bottom:0in;}#yiv1643967315 ul {margin-bottom:0in;}#yiv1643967315 Ø HTML5 explicitly disallows the use of scope on TD elements.    I think the first question we need to agree on is whether  td with a scope in HTML5 is or is not a WCAG 2 violation.  If we see it as a violation then I would propose adding in a comment that this would not be a failure under HTML 4/XHTML.    Jonathan    Jonathan Avila Chief Accessibility Officer
SSB BART Group 
jon.avila@ssbbartgroup.com 703.637.8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter    From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
Sent: Friday, December 18, 2015 10:47 AM
To: WCAG
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 Kirkpatrick Group Product Manager, Accessibility Adobe     akirkpat@adobe.com http://twitter.com/awkawk http://blogs.adobe.com/accessibility