WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Scope-Attribute necessary for TH-Element?

for

From: Sailesh Panchang
Date: Jul 17, 2017 12:05PM

Actually, TH with scope=row for row headers was needed a few JAWS
versions-ago because JAWS seemed to have introduced a bug in
interpreting row headers back then. This has since been resolved.

The scope attribute is valid on TD too in HTML 4.01 (if one has legacy
content) and also works in HTML5 mostly but will generate a
validation issue.
See H63 technique at
https://www.w3.org/TR/WCAG20-TECHS/H63.html
For example of td with scope=row see Contact Info table:
http://www.eramp.com/david/tablesample2.htm
Best wishes,


On 7/17/17, Jonathan Avila < <EMAIL REMOVED> > wrote:
>> I'm Austrian and try to learn a11y-Slang and therefore misunderstand and
>> missformulate sometimes. You wrote: 'Assistive technology support should
>> generally be good but may need to be checked for the technology stack you
>> are trying to support.- Isn't AT support essential in any technology
>> stack? What did I understand wrong in Your formulation?
>
> All I was trying to say is that in order to make a claim of WCAG conformance
> you need to define and evaluate whether the techniques used to meet the
> success criteria are supported by the user agent and assistive technology
> that you are using to make the claim. That is -- your implementation
> doesn't have to work with all user agents or assistive technologies --
> strictly speak it only has to work with one -- but most experts agree that
> two is needed -- which assistive technology and user agents are not defined
> but the access to content should be taken into account during this
> determination. For example, for an internal site where an organization can
> control the technology used a smaller set of technology is likely
> sufficient. However for public access a broader set of technology support
> is likely needed -- but broad doesn't mean all although the goal is more
> support by more user agents and assistive technology.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> Level Access, inc. (formerly SSB BART Group, inc.)
> <EMAIL REMOVED>
> 703.637.8957 (Office)
> Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
> Looking to boost your accessibility knowledge? Check out our free webinars!
>
> The information contained in this transmission may be attorney privileged
> and/or confidential information intended for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any use, dissemination, distribution
> or copying of this communication is strictly prohibited.
>
>
>