WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Query regarding equal access accessibility checker reported bug

for

From: glen walker
Date: Aug 9, 2023 12:28AM

IBM's accessibility checker marks it as an "info" warning, not a failure,
so it's not a WCAG failure. But I agree it's a false positive in the way
it's reporting it since the <input> does indeed have an accessible name
that comes from the value attribute.

The HTML spec for <input type="submit"> says:

"If the element has a value attribute, the button's label must be the value
of that attribute"

https://html.spec.whatwg.org/multipage/input.html#submit-button-state-(type=submit)

The button's label will be the accessible name.

Both WAVE and ARCToolkit report the accesskey as a warning and suggest you
not use it, but again, it's a warning and not a failure.
Axe doesn't say anything about it.

As a keyboard user myself, I love having an accesskey, but it's not very
discoverable (if at all). I generally have to inspect the code to see if
there's a field that I'm hoping has an access key, such as the search field
on wikipedia.org