WebAIM - Web Accessibility In Mind

E-mail List Archives

for

From: Sailesh Panchang
Date: Aug 4, 2025 10:49AM

Steve,
The entire content of the anchor element or button should be ignored as
per my understanding and JAWS does that for the link but is apparently
failing to do that for a button as you reported.
So the role of the content within the element is immaterial if it is meant
to be ignored.
And in such situations the deprecated SC 4.1.1 would probably play a
role: flag improper nesting of elements.
Thanks,
Sailesh

Sailesh Panchang

Email: <EMAIL REMOVED>
Deque Systems Inc | - Accessibility for Good | www.deque.com














On Mon, Aug 4, 2025 at 10:52 AM Steve Green via WebAIM-Forum <
<EMAIL REMOVED> > wrote:

> Here's another test that clearly shows something is wrong somewhere. I
> replaced the link element with a button, and JAWS now does announce the
> heading, but it ignores the "aria-label" attribute. You would expect it to
> behave the same as before, but it doesn't. It announces the following code
> as "heading level three button bar".
>
> <button aria-label="foo">
> <h3>bar</h3>
> </button>
>
> NVDA reads this as "button foo", so it is acknowledging the "aria-label"
> attribute and ignoring the heading, as it did with the link.
>
> As before, Chrome's accessibility tree shows the button's name as "foo".
> The heading has a role of "h3" and contents of "bar".
>
> Steve
>