Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing accessible name on progressbar references WCAG SC 1.1.1 instead of 4.1.2 #4282

Closed
1 task done
yatil opened this issue Dec 20, 2023 · 4 comments
Closed
1 task done
Labels
ungroomed Ticket needs a maintainer to prioritize and label

Comments

@yatil
Copy link

yatil commented Dec 20, 2023

Product

axe-core

Product Version

No response

Latest Version

  • I have tested the issue with the latest version of the product

Issue Description

Expectation

When a progressbar element (role="progressbar") has no accessible name, I expect this to be a SC 4.1.2 Name, Role, Value violation

Actual

The violation is categorized as a SC 1.1.1 Non-text Content violation.

How to Reproduce

Create a page with an aria-progress bar, do not label it. Run axe-core.

Additional context

See the Pull Request where the test was added:

@yatil yatil added the ungroomed Ticket needs a maintainer to prioritize and label label Dec 20, 2023
@WilcoFiers
Copy link
Contributor

Thank you for opening this issue. I don't think there's a definitive answer to this. The way I read 4.1.2, it applies to user interface components, which is defined as something perceived as a single control by users. When I think of a control I think of something I can interact with. Something that lets me do something. Progress bars provide information, but they aren't (usually) interactive. Since they pretty much by their nature have to provide information without text, I think it fits better under "non-text content" than "user interface component".

I get where you're coming from. 4.1.2 is the SC where most of the ARIA stuff goes. But this was an intentional decision.

@yatil
Copy link
Author

yatil commented Dec 20, 2023

The superclass role of a progressbar is a widget which is, quote:

An interactive component of a graphical user interface (GUI).

As the value can change, this IMHO qualifies as a user interface component. At least both, 4.1.2 and 1.1.1 should be cited, even if 1.1.1 is redundant.

@WilcoFiers
Copy link
Contributor

(Sorry vacation). In what way are progress bars interactive?

@yatil
Copy link
Author

yatil commented Jan 10, 2024

That’s the definition in WAI-ARIA. I linked to the relevant document. I cannot name the reasons for the ARIA WG’s decisions.

A progress bar often changes based on user input or a user action, even if not directly with that element. I think that’s interactive enough for me. That said, I don’t think I care enough.

@yatil yatil closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ungroomed Ticket needs a maintainer to prioritize and label
Projects
None yet
Development

No branches or pull requests

2 participants