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

Element with role button contains an element that is not allowed #181

Open
blackfalcon opened this issue Jan 6, 2024 · 0 comments
Open
Assignees

Comments

@blackfalcon
Copy link
Member

blackfalcon commented Jan 6, 2024

Please verify the version of auro-datepicker you have installed

@latest

Rule description

One or more elements that has a role='button' attribute, not intentionally hidden in the DOM, contained one or more input elements (without an assigned ARIA role and not type=hidden), select elements (without an assigned ARIA role), textarea elements (without an assigned ARIA role) or A elements (without an assigned ARIA role).

Severity

Critical

WCAG Success criteria

4.1.2 Name, Role, Value - Level A

Why it matters

When elements with <code>role="button"</code> contain interactive elements, additional items may be appear in the focus order and the accessible name for an element may not be calculated correctly. This will cause users of screen reader who are blind or low vision to experience keyboard related access or may prevent the accessible name from being correctly communicated to these users preventing them from understanding the purpose of the control.

What to do

Avoid interactive elements within elements with <code>role="button"</code>. If two interactive elements are needed place them as siblings or in another structure that does not create an invalid structure.

Reproducing the error

This issue cannot be reproduced on the Auro docsite

Expected behavior

No accessibility error with role="button" use.

What browsers are you seeing the problem on?

No response

Additional context

LevelAccess issue https://alaskaair.hub.essentia11y.com/projects/6578ac73f0e9336405bfe140/tasks/6598ce4cf8acb247de0998dc?linkedPropertyData=652813da6eec28e13de119c4%7C652813da6eec28ef1ee119bd

Exit criteria

This issue can be closed once the error has been addressed and a LevelAccess scan indicates that the issue has been resolved.

Please be sure to include a screen shot of the scan with the pull request.

@blackfalcon blackfalcon added auro-datepicker not-reviewed Issue has not been reviewed by Auro team members Type: Bug Bug or Bug fixes accessibility labels Jan 6, 2024
@settings settings bot removed the accessibility label Feb 7, 2024
@blackfalcon blackfalcon added Type: a11y and removed not-reviewed Issue has not been reviewed by Auro team members labels May 8, 2024
@settings settings bot removed the Type: a11y label Jun 22, 2024
@jason-capsule42 jason-capsule42 removed the Type: Bug Bug or Bug fixes label Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants