Skip to content

remove .to.be.accessible() checks #71

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

Merged
merged 1 commit into from
Feb 14, 2024
Merged

Conversation

keithamus
Copy link
Contributor

While these checks are nice in theory, they actually aren't properly executed. They need to be awaited and doing so causes errant failures, for example the HTML under test does not have a <main> check. Consequently I don't think they'd be useful to get working, especially as axe has problems checking shadowdom, despite the shadowdom being accessible.

@keithamus keithamus requested a review from a team as a code owner February 14, 2024 17:02
@keithamus keithamus force-pushed the remove-to-be-accessible-checks branch from 26d6643 to d738639 Compare February 14, 2024 17:02
Copy link
Member

@owenniblock owenniblock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm torn with this one, I know you can test partial pages with axe without the rules like the main one.

The shadow DOM issue is a problem though. Maybe we can feed this back to Deque 🤔

Approving anyway, I guess this will still get tested by axe further down our stack anyway.

@keithamus keithamus merged commit 2f6ee23 into main Feb 14, 2024
@keithamus keithamus deleted the remove-to-be-accessible-checks branch February 14, 2024 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants