- From: <jason@accessibleculture.org>
- Date: Wed, 3 Jun 2015 14:19:59 +1200
- To: Alexander Surkov <surkov.alexander@gmail.com>
- Cc: Steve Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html@w3.org>, Alice Boxhall <aboxhall@google.com>
FYI, I did some more testing and updated this section in the HTML-AAM: http://rawgit.com/w3c/aria/master/html-aam/html-aam.html#use-of-msaa-variant-by-some-user-agents FF returns the tag name in MSAA accRole for fewer elements than it used to, but it still does it for a good number of elements. Chrome does it too, but for far fewer elements. Jason Kiss jason@accessibleculture.org http://www.accessibleculture.org > On 28/05/2015, at 4:24 pm, Jason Kiss <jason@accessibleculture.org> wrote: > > Some history on that note: https://www.w3.org/Bugs/Public/show_bug.cgi?id=16769 > > Could be that Chrome has since dropped the BSTR hack. Would need to > test. A quick look shows that a blockquote element still gets exposed > by Chrome with MSAA accrole of "blockquote", although the q element > doesn't seem to get exposed similarly with "q". My quick look might > have been too quick, though. > > On Sat, May 2, 2015 at 4:23 AM, Alexander Surkov > <surkov.alexander@gmail.com> wrote: >> Afaik some of it is used by commercial screen readers, it's not webby but >> I'm not sure whether any of them wanted to share extra info on this. >> >> On Fri, May 1, 2015 at 11:47 AM, Steve Faulkner <faulkner.steve@gmail.com> >> wrote: >>> >>> Is this note an accurate refelction of implementaions? mentions chrome, >>> can't find examples where chrome does this, only firefox. >>> >>> http://rawgit.com/w3c/aria/master/html-aam/html-aam.html#use-of-msaa-variant-by-some-user-agents >>> >>> Also any info on which AT make use of this info? >>> -- >>> >>> Regards >>> >>> SteveF >>> HTML 5.1 >> >>
Received on Wednesday, 3 June 2015 02:20:35 UTC