Re: Other problems, @hidden (ISSUE-204 aria-hidden)

hi leif,

My perception of the A11Y
> implementation guide is that it tries to document reality rather than
> specify it.
>

it is being developed to do both, where features are implemented and there
are differences the guide notes these.  Differences that effect
interoperability will have implementation recommendations associated and
serve as a guide for working with implementers to remove such issues. Where
implementations for new features have not occured they have/will be
specified.

The ARIA spec(s) do not talk about @hidden.
>

thats right

And my assumption was - and is - that this is because they are hard to
> document - perhaps because there is nothing to document. It seems to me
> that, at least for now, @hidden simply maps to style="display:none",
> and nothing more. Do you have data for any other conclusion?
>

your assumption is incorrect, stuff has not yet been documented in the most
part because we have not got to it yet.


We have heard that Firefox has started to implement what ISSUE-204 is
> about. So what does Firefox do if the @aria-describedby points to a
> hidden section which *also* has aria-hidden="true" set? I have not
> tested that exact example, but based on the tests I have don, I don't
> think it works. If so, then HTML5 is wrong - or at least not exact
> enough.
>

works fine with aria-hidden+display:none or aria-hidden or
aria-hidden+hidden
test page: https://dl.dropbox.com/u/377471/tests/firefox-describedby.html

the default action (showLongdesc) on the image is exposed regardless.

regards
SteveF



On 15 August 2012 12:37, Leif Halvard Silli <
xn--mlform-iua@xn--mlform-iua.no> wrote:

> Steve Faulkner, Wed, 15 Aug 2012 11:30:08 +0100:
>
> >> The 'HTML to Platform Accessibility APIs Implementation Guide' has not
> >> documented *any* correspondence between the hidden attribute and
> >> WAI-ARIA *or* with any accessibility APIs.[1]
> >
> > it is not the place of the 'HTML to Platform Accessibility APIs
> > Implementation Guide' to document ARIA mappings to HTML,
>
> AFAICT, I have misunderstood nothing. To document is not to spec but to
> show data about how the reality looks like. My perception of the A11Y
> implementation guide is that it tries to document reality rather than
> specify it.
>
> > that should
> > be in the aria implementation guide, which it is for aria-hidden [1]
>
> The ARIA spec(s) do not talk about @hidden.
>
> > Any reference to ARIA in the HTML guide is there for informative
> > purposes only.
>
> I see no differences between me and the A11Y implementation guide here.
>
> > as to @hidden, the 'HTML to Platform Accessibility APIs
> > Implementation Guide' has not *yet* documented the mappings
>
> And my assumption was - and is - that this is because they are hard to
> document - perhaps because there is nothing to document. It seems to me
> that, at least for now, @hidden simply maps to style="display:none",
> and nothing more. Do you have data for any other conclusion?
>
> We have heard that Firefox has started to implement what ISSUE-204 is
> about. So what does Firefox do if the @aria-describedby points to a
> hidden section which *also* has aria-hidden="true" set? I have not
> tested that exact example, but based on the tests I have don, I don't
> think it works. If so, then HTML5 is wrong - or at least not exact
> enough.
>
> > [1] http://www.w3.org/WAI/PF/aria-implementation/#mapping_state-property
> --
> leif halvard silli
>



-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html