| { | |
| "node" : true, | |
| "browser" : true, | |
| "es5" : true, | |
| "esnext" : true, | |
| "bitwise" : true, | |
| "camelcase": true, | |
| "curly" : true, | |
| "eqeqeq" : true, | |
| "immed" : true, |
Making the web accessible is important. We have ethical and, in some cases, legal obligations to ensuring access to all of users.
Luckily for us, it's easy to make an accessible Ember Component.
To understand the accessibility story around Ember Components, we have to start by talking about Web Components. Ember Components are designed to be interoperable with the final Web Components API.
This document is meant to be a brief "checklist" of things to setup for your Ember addon when beginning development in order to have the best possible architecture and workflow out of the gate. For more comprehensive material, the following are bookshelf-caliber:
Ember Addon Secrets - Written around the Ember 2.6 era, this article takes a much deeper dive into several of the topics mentioned here.
