E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 14 (In chronological order)

From: sucharu
Date: Thu, Nov 19 2015 1:17AM
Subject: keyboard accessibility while screen reader on
No previous message | Next message →

Hello list,

Good afternoon!

Thanks for your valuable suggestions.

There is a situation:

There are few focusable elements on the page that get activated using
keyboard but when screen-reader is turned on, they don't get activated when
entered upon.

Looking for guidance.

Thanks,

Sucharu

From: Steve Faulkner
Date: Thu, Nov 19 2015 2:16AM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

On 19 November 2015 at 08:17, sucharu < = EMAIL ADDRESS REMOVED = > wrote:

> There is a situation:
>
> There are few focusable elements on the page that get activated using
> keyboard but when screen-reader is turned on, they don't get activated when
> entered upon.
>
> Looking for guidance.
>

Hi, if you want guidance suggest providing the following info:

browser/OS/AT types and versions
steps to reproduce issue and test page.

--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;

From: sucharu
Date: Thu, Nov 19 2015 3:02AM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

Hi Steve,
Thanks for quick response.
Will soon provide you with the information you asked for as I need some permissions for that.
Meanwhile, can you please guide me about "how a screen readerworks and interacts with machine "

From: Patrick H. Lauke
Date: Thu, Nov 19 2015 3:09AM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

On 19/11/2015 10:02, sucharu wrote:
> Meanwhile, can you please guide me about "how a screen readerworks and interacts with machine

Some starting points:
https://www.google.co.uk/search?q=how%20do%20screen%20readers%20work

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

From: sucharu
Date: Thu, Nov 19 2015 3:24AM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

Hello sir,
Thanks a lot.
I went through the material you referred to, valuable indeed.
But still the question to which I look for is unanswered i.e.
"do functionality meant to achieved through keyboard can get altered while screen reader is turned on"

From: Steve Faulkner
Date: Thu, Nov 19 2015 3:39AM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

On 19 November 2015 at 10:24, sucharu < = EMAIL ADDRESS REMOVED = > wrote:

> "do functionality meant to achieved through keyboard can get altered while
> screen reader is turned on"


depends on interactive element type and SR mode and how you are attempting
to interact.

--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;

From: sucharu
Date: Thu, Nov 19 2015 4:05AM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

There is a situation where an error message appears which is focusable and
Which is dismissed when ENTER
Is pressed.
But when screen reader is turned on that error message is non-dismissable.

From: Steve Faulkner
Date: Thu, Nov 19 2015 4:15AM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

On 19 November 2015 at 11:05, sucharu < = EMAIL ADDRESS REMOVED = > wrote:

> There is a situation where an error message appears which is focusable and
> Which is dismissed when ENTER
> Is pressed.
> But when screen reader is turned on that error message is non-dismissable.
>

Hi Sucharu,

I would really like to help you, but you must provide the following
information to make that possible:


- browser
- OS
- Assistive Tech (where applicable)
- Steps to reproduce
- Test page


--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;

From: Jonathan Avila
Date: Thu, Nov 19 2015 3:09PM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

> "do functionality meant to achieved through keyboard can get altered while screen reader is turned on"

Generally this occurs when a control is watching for keyboard events like onKeyUp etc for enter and space and perhaps works with onMouseDown but the control does not support the click event. When the screen reader is in browse mode and the user presses enter it sends the click event to an element -- not a key press and not a mouseDown. There is a setting in some screen readers like JAWS to change this behavior but this needs to be corrected in the web page.

Jonathan

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
= EMAIL ADDRESS REMOVED =

703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter

From: Jennison Mark Asuncion
Date: Thu, Nov 19 2015 3:10PM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

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

From: Steve Faulkner
Date: Thu, Nov 26 2015 3:47AM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

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 ADDRESS 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
> > > > >

From: Jonathan C. Cohn
Date: Tue, Dec 01 2015 5:21PM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

Why would anybody do that in the first place?


Jonathan Cohn

> On Nov 26, 2015, at 5:47 AM, Steve Faulkner < = EMAIL ADDRESS 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 ADDRESS 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
>> >> >> >> > > > >

From: _mallory
Date: Wed, Dec 02 2015 5:51AM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | Next message →

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 ADDRESS 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 ADDRESS 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
> >> > >> > >> > >> > > > > > > > > > > > >

From: Steve Faulkner
Date: Wed, Dec 02 2015 5:59AM
Subject: Re: keyboard accessibility while screen reader on
← Previous message | No next message

By error I think

On Wednesday, 2 December 2015, Jonathan C. Cohn < = EMAIL ADDRESS REMOVED = >
wrote:

> Why would anybody do that in the first place?
>
>
> Jonathan Cohn
>
> > On Nov 26, 2015, at 5:47 AM, Steve Faulkner < = EMAIL ADDRESS REMOVED =
> <javascript:;>> 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 ADDRESS REMOVED = <javascript:;>> 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
> >> > >> > >> > >> > > > > > > > > > > > > >


--
--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;