WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessible Modal

for

From: Chris Pearce
Date: May 21, 2015 3:08PM

Thanks everyone for your input, it has been really valuable and good to
know that the solution I've been using is the solution I should be using.

Chris

On 22 May 2015 at 04:46, Jonathan Avila < <EMAIL REMOVED> > wrote:

> > But aria-hiddenúlse on the same element will expose content to AT:
> <div hidden (or display:none) aria-hiddenúlse">This content is exposed
> to AT</div>
>
> This seems incorrect to me. From my read of the HTML spec user agents are
> only supposed to expose hidden content to an accessibility API if it is
> referenced by an id such as in the case of aria-labelledby and
> aria-describedby.
>
> Jonathan
>
> --
> Jonathan Avila
> Chief Accessibility Officer
> SSB BART Group
> <EMAIL REMOVED>
> Phone 703.637.8957
> Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter
>
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Sailesh Panchang
> Sent: Thursday, May 21, 2015 2:37 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Accessible Modal
>
> Jonathan,
> From the link for bug #945194 sent by Steve F, I see others also agree
> that the parent's aria-hidden=true will apply to a child with
> aria-hiddenúlse. I reproduce some text and code below:
> <start>
> <div aria-hidden="true"><div aria-hidden="false">the text is not visible
> for AT</div></div> That is correct. A descendant node set to
> aria-hidden="false" will not override a ancestor node's visibility. This
> shoulld be clarified in ARIA 1.1.
> but the same time HTML5 spec now requires <div hidden><div
> aria-hidden="false">HTML5 spec thinks this text should be visible for
> AT</div></div> That's an error in the spec then. Could probably be solved
> with some explanatory text.
>
> </end>
>
> But aria-hiddenúlse on the same element will expose content to AT:
> <div hidden (or display:none) aria-hiddenúlse">This content is exposed
> to AT</div>
>
> Thanks,
>
> Sailesh
>
>
> On 5/20/15, Steve Faulkner < <EMAIL REMOVED> > wrote:
> > On 20 May 2015 at 14:05, Jonathan Avila < <EMAIL REMOVED> >
> wrote:
> >
> >> this is just not practical.
> >
> >
> > Unfortunately unless we can get implementers to agree to implement
> > this behaviour, then that's what we have to work with.
> > As a side note: the native HTML mechanism for blocking interaction
> > with content outside of a modal <dialog> does not provide subtree
> > state to be changed from inert.
> > http://www.w3.org/TR/html51/editing.html#inert-subtrees
> >
> > --
> >
> > Regards
> >
> > SteveF
> > HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;
> > > > > > archives at http://webaim.org/discussion/archives
> > > >
> > > at http://webaim.org/discussion/archives
> > > > > >