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

deps(axe): bump axe to latest #5565

Closed
wants to merge 1 commit into from
Closed

deps(axe): bump axe to latest #5565

wants to merge 1 commit into from

Conversation

paulirish
Copy link
Member

changes here: https://github.com/dequelabs/axe-core/releases

Nothing in particular triggered me to bump, though "Prevent color rules from crashing Chrome 66+" looks certainly worthwhile. :)

Copy link
Member

@brendankenny brendankenny left a comment

Choose a reason for hiding this comment

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

some smoke test expectation changes

@paulirish
Copy link
Member Author

@robdodson questions for you. we have two failures with the latest here.

  1. accesskeys. fix: Update tags to accesskey & link-name rules dequelabs/axe-core#922 removed it from wcag tags, so its never included. luckily your smoketest caught this. could have been a silent failure for a while otherwise. :) since its not wcag anymore should we remove it? or explicitly include. up to you.
  2. layout-table. fix(layout-table): check for presentation, none roles and isfocusable for matches dequelabs/axe-core#828 changed it's implementation and now the smoketest returns it as nonApplicable suggesting that the new matches fn doesn't match our table. I don't totally follow why... so what should we do about this?

@robdodson
Copy link
Contributor

robdodson commented Jun 28, 2018 via email

@robdodson
Copy link
Contributor

I think removing role=presentation could fix 2. If not, also try removing the th. I think it's testing that folks aren't using a table to lay stuff out without putting data inside of it.

@brendankenny
Copy link
Member

Will also fix #5940

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.

None yet

3 participants