WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Button and textual equivalent


From: Patrick H. Lauke
Date: Dec 6, 2014 8:52AM

On 05/12/2014 21:43, Jukka K. Korpela wrote:
> 2014-12-05, 23:21, Lucy Greco wrote:
>> I have tested with NVDA and JAWS and both have no
>> problem with this button
> Exactly how do they inform the user about this? There must be something
> odd going on if this button works.

From quick test with JAWS/IE "search button...button..." and in JAWS/FF
"search button, button, to activate press SPACE bar"
NVDA, strangely, did not announce anything for me in Firefox, and in IE
"button, search". Note that it seems IE does not correctly use/expose
aria-label as the accName (tested using aViewer [1]), so this last
result is likely due to NVDA doing some kind of remediation work and
announcing the role and value of the control. Firefox, however, does
correctly expose "search button" as accName, so the behavior of NVDA
here may just be a plain old bug in NVDA.

>> <button type="submit" class="btn btn-default" aria-label="search
>> button" value="Search"><span class="entypo search"></span></button>
> I think the element falls into the category "non-text content", since
> there are no characters in its content. I guess Guideline 1.1.1 could be
> interpreted so that it suffices to add a name=... attribute to the
> <button> element.

Name? I don't recall the name attribute being exposed at all in anything
other than form submission data - and pretty sure it doesn't act as a
fallback text content.

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