WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Buttons not operable with 'Space/Enter' When Screen Reader is ON

for

From: Birkir R. Gunnarsson
Date: Jan 3, 2019 8:24PM

Good points. Yes, my experience is that the synthetic onclick event
sent by screen readers works in most situations, but there are
situations where it doesn't.
These are situations where there is a keyboard handler and mouse
handlers, the author thinks he/she has got everything covered, but
does not consider the synthetic onclick event sent by screen readers.
The lesson, always support the onclick event.
This is also a problem if the event is captured by another element,
e.g. an overlay (if screen reader users can navigate outside of a
modal pop up window in browse mode and try to activate some of the
background elements on the page while the modal is still visible).
The synthetic onclick event is intercepted by the modal dialog div and
either does nothing or closes the modal, but does not activate the
control.


On 1/3/19, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> On 03/01/2019 05:45, Jeevan Reddy wrote:
>> Hi Friends,
>> Happy new year 2019 for all of You!.
>> some of the buttons in our application are not operable with
>> 'Space/Enter'
>> when Screen Reader is On, but operable as expected when Screen Reader is
>> turned OFF.
>> we are using polymer JS, and tested with NVDA 2018.4 on Chrome.
>> can you pls share some insights how to resolve this?
>>
>> Your help is greatly appreciated!
>
> As ever, with questions of this kind, it's difficult to help (beyond
> lots of stabs in the dark and off-tangent hypothetical discussions)
> without seeing the actual code (even just a the markup for the buttons
> in question)...
>
> 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
> > > > >


--
Work hard. Have fun. Make history.