WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: keyboard accessibility while screen reader on

for

From: _mallory
Date: Dec 2, 2015 5:51AM

it's probably a mis-read of an example where the aria-hidden is on some
child in a button holding the "x", since you'd want "close" (or whatever)
read out and not "x" or "times".

It might also be on a website somewhere as, when working on a site that
was using bootstrap and font-awesome and glyphicons (yeah they didn't know
what they wanted) I ran into a few of those buttons with aria-hidden right
on them as well. And since the writer of that content wasn't a web-dev and
would have no way of ever hearing about aria-anything himself, I can only
assume he found it on a bit of code somewhere.

So it's probably a copy-paste and there's something nasty out there on teh
interwebz.

_mallory

On Tue, Dec 01, 2015 at 07:21:06PM -0500, Jonathan C. Cohn wrote:
> Why would anybody do that in the first place?
>
>
> Jonathan Cohn
>
> > On Nov 26, 2015, at 5:47 AM, Steve Faulkner < <EMAIL REMOVED> > wrote:
> >
> > the person contacted me offlist and provided access to the problem UI.
> >
> > The issue was caused by a focusable button element with aria-hidden=true on
> > it
> >
> > <button aria-hidden="true">x</button>
> >
> > Once that it was removed JAWS worked as expected.
> >
> > Refer to 4th Rule of ARIA
> > http://w3c.github.io/aria-in-html/#fourth
> >
> >
> > --
> >
> > Regards
> >
> > SteveF
> > Current Standards Work @W3C
> > <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;
> >
> > On 19 November 2015 at 22:10, Jennison Mark Asuncion <
> > <EMAIL REMOVED> > wrote:
> >
> >> Like Steve, I would also like more details. However, my gut is saying
> >> that the screen reading software is not passing the Enter key to the
> >> application, possibly because the screen reader is in a mode where the
> >> Enter key is not meant to function at all.
> >>
> >> Jennison
> >> > >> > >> > >> > > > > > > > > > > > >