https://github.com/melsumner/ember-a11y-roadmap
Roadmap for all things a11y in ember.js
https://github.com/melsumner/ember-a11y-roadmap
Last synced: 4 months ago
JSON representation
Roadmap for all things a11y in ember.js
- Host: GitHub
- URL: https://github.com/melsumner/ember-a11y-roadmap
- Owner: MelSumner
- Created: 2019-01-28T18:07:12.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2020-02-19T21:17:03.000Z (over 6 years ago)
- Last Synced: 2025-09-07T16:51:40.637Z (10 months ago)
- Size: 378 KB
- Stars: 12
- Watchers: 4
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# ember-a11y-roadmap
A Potential Roadmap for all things a11y in ember.js.
First, if you are not familiar with digital accessibility, please reference the [conversation prep document](https://github.com/MelSumner/ember-a11y-roadmap/blob/master/conversation-prep.md) first. **You will likely be ill-equipped to think about the problem space without some introduction to the topic.**
If you wish to contribute to this repository, PRs are welcome.
## Low-effort changes
These are low-effort changes that would immediately improve the default conformance of new Ember applications, and demonstrate commitment to accessibility in EmberJS. All of the changes proposed may need iteration toward a long-term solution.
- Add OOB support for page titles (should be unique per page as per [WCAG 2.4.2- Page Titled](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=242#page-titled)). Similar is provided by [ember-page-title](https://github.com/adopted-ember-addons/ember-page-title).
- Add default language attribute on the `` element - [basic documentation](https://github.com/MelSumner/ember-a11y-roadmap/blob/master/rfc-research/language/default-language.md)
- Add `aria-label`, `aria-labelledby`, and `aria-describedby` attributes to the `...attributes` exceptions (like `class`) - [proposed draft RFC](https://github.com/MelSumner/ember-a11y-roadmap/blob/master/rfc-research/attribute-support/0000-improved-aria-attribute-support.md)
- Release an official framework statement regarding A11y in Ember.js
- Publishing a "roadmap" or "intent to improve" list (along with an invitation to contribute)
## Long-term changes
After some discussion, these things need a larger effort refactor, and accessibility should be part of that re-design:
- Ember Router (and ensure support for assistive tech)
- refactor the way the `...attributes` feature works
- create a locale-aware start to Ember apps?
## Other useful improvements
- focus management
- keyboard navigation
- semantic test helpers (improves code in general but could specifically be used to better test for accessibility conformance)
- A11y in the guides
- component patterns for accessible components
- linting
- ember language server support
## Innovation Opportunities
Right now, only about 30% of accessibility issues can be automatically tested. We have the opportunity to improve that through innovative tooling.
- we should at least get the 30% right, then innovate on the other 70%
- CLI tool for http://adrianroselli.com/2019/04/reading-order-bookmarklet.html
## RFCs
### Existing
- [accessible routing in Ember.js](https://github.com/emberjs/rfcs/pull/433)
- [semantic test helpers](https://github.com/emberjs/rfcs/pull/327)
### Research/write
- vocalizing support for assistive technology (screen readers, specifically) in the same way we list browser support
- dialogs/modals (parent window inert, focus management) [[RFC Research]](dialogs/modals.md)
- keyboard nav
- focus management
## Documentation
- [guides & developer education](documentation/guides.md)
- a11y for the [emberjs.com guides](https://guides.emberjs.com/release/reference/accessibility-guide/)
- Add a11y check/section to RFC process
- update ember-a11y website
- add best practices for ember components
- give helpful information for ember addons
- improved [developer experience](linting-and-testing/approach.md)
## Addons
ui addon with a11y-first approach
- https://github.com/MelSumner/e-a11y-modal