Skip to content

feat(accessibility): use correct aria properties #349

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 3 commits into from
Dec 19, 2018

Conversation

AdminXVII
Copy link
Contributor

Description

Based on aXe recommendations, fix accessibility:

  • Use proper roles for the various components (ex: role="button" not needed on buttons).
  • Reorder navigation and pagination to better match the tabbing order.
  • Make navigation accessible by tabbing.
  • Change the HTML elements to better match W3's recommended organization

Motivation and Context

Accessibility of the carousel.

How Has This Been Tested?

Tested using vue-play in Firefox and Chrome on Linux.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly.
  • I have included a vue-play example (if this is a new feature)

@quinnlangille quinnlangille changed the base branch from master to v0.17.0 December 18, 2018 16:28
@quinnlangille
Copy link
Member

^ resolved some small conflicts caused by the base branch switch

@coveralls
Copy link

coveralls commented Dec 18, 2018

Coverage Status

Coverage remained the same at 67.593% when pulling bb826df on AdminXVII:feat-fix-aria into a895b28 on SSENSE:v0.17.0.

@quinnlangille
Copy link
Member

Ah dang looks like this will need a rebase with v0.17.0. Do you mind rebasing and pushing back up when you get a sec?

Based on [aXe](https://www.deque.com/axe/) recommendations, fix accessibility:
 - Use proper roles for the various components (ex: role="button" not needed on buttons).
 - Reorder navigation and pagination to better match the tabbing order.
 - Make navigation accessible by tabbing.
 - Change the HTML elements to better match [W3's recommended organization](https://www.w3.org/TR/wai-aria-practices/examples/tabs/tabs-1/tabs.html)
@AdminXVII
Copy link
Contributor Author

Done

@quinnlangille
Copy link
Member

Perfect @AdminXVII, will merge into the working branch! Thanks for the upgrade 🚀

@quinnlangille quinnlangille merged commit ff8f6d3 into SSENSE:v0.17.0 Dec 19, 2018
quinnlangille pushed a commit that referenced this pull request Dec 19, 2018
* chore: build

* feat(accessibility): use correct aria properties

Based on [aXe](https://www.deque.com/axe/) recommendations, fix accessibility:
 - Use proper roles for the various components (ex: role="button" not needed on buttons).
 - Reorder navigation and pagination to better match the tabbing order.
 - Make navigation accessible by tabbing.
 - Change the HTML elements to better match [W3's recommended organization](https://www.w3.org/TR/wai-aria-practices/examples/tabs/tabs-1/tabs.html)
josephting added a commit to josephting/vue-carousel that referenced this pull request Dec 20, 2018
* tags adjustments from SSENSE#349

* pre jest-serializer-vue test from SSENSE#322
quinnlangille pushed a commit that referenced this pull request Dec 27, 2018
* chore: build

* feat(accessibility): use correct aria properties

Based on [aXe](https://www.deque.com/axe/) recommendations, fix accessibility:
 - Use proper roles for the various components (ex: role="button" not needed on buttons).
 - Reorder navigation and pagination to better match the tabbing order.
 - Make navigation accessible by tabbing.
 - Change the HTML elements to better match [W3's recommended organization](https://www.w3.org/TR/wai-aria-practices/examples/tabs/tabs-1/tabs.html)
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.

3 participants