Hi James, so it is a bug fix working its way into the safari release
version, great thanks.
--
Regards
SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>
On 11 August 2015 at 08:18, James Craig <jcraig@apple.com> wrote:
> I believe the core problem was an ambiguity in ARIA 1.0. Both the
> ambiguity and the resulting WebKit modification were resolved earlier this
> year.
>
> https://bugs.webkit.org/show_bug.cgi?id=139142
>
>
> On Aug 10, 2015, at 7:31 AM, Steve Faulkner <faulkner.steve@gmail.com>
> wrote:
>
> The ARIA Core Accessibility API Mappings 1.1 spec states that
> aria-hidden=false is 'not mapped' on any platform
> http://www.w3.org/TR/core-aam-1.1/#ariaHiddenFalse
>
> So having aria-hidden=false on an element is the same as not having the
> attribute at all in respect to the representation of the element and any
> subtree content.
> <div> = <div aria-hidden=false>
>
> This does not appear to be the case in iOS
> For example this test page: http://s.codepen.io/stevef/debug/BNMqea?
> the div with aria-hidden contains a div with style="display: none" the
> content of which is announced by VoiceOver (in iOS only)
>
> code:
> <h1>hidden content</h1>
> <div aria-hidden="false">
> <div id="userOpinionSecret" style="display: none">WE know this user,
> he is not popular</div>
> </div>
> <h2>end of hidden content</h2>
>
> This seems like a bug to me.
>
> thanks to Birkir for pointing this issue out.
> --
>
> Regards
>
> SteveF
> Current Standards Work @W3C
> <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>
>
>