For those who know the project well, this will come as no surprise. It’s no secret that we think that accessibility is an integral part of quality code. Ember.js is committed to providing a well-lit path for developer success, and our plans to make it easier for developers to write accessible code are part of that. In 2020, the Ember Accessibility Strike Team became the Ember Accessibility Working Group, demonstrating our commitment to long-term accessibility growth in the framework.
What We've Done So Far
Ember has also been shipping improvements with the “accessibility by default” developer experience in mind. These improvements include support for default app language (RFC #635), default page titles (RFC #645), added content to the guides specifically for accessibility, changes to the website design for better accessibility, and addition of accessibility-related linting rules to Ember Template Lint. Members of the Accessibility Working Group also published two new addons, ember-context-id-helper and ember-select-light, to give developers more tools to craft accessible code.
What We Have Planned
Looking forward, we have even more accessibility-related work planned. Two RFCs have been merged that target specific improvements; one addresses a way to make it easier to associate elements through unique id attributes in template-only components (RFC #659), and the other proposes an interactive way to create new Ember apps, ensuring that accessible outcomes are front and center (RFC #638).
We will continue on our journey of accessibility with more improvements to the guide prose and code samples, as well as implement targeted improvements to the design of the guides and API documentation. Our goal is to reach WCAG’s AA level of conformance on our official project websites, and we are determined to see this through to completion.
How You Can Help
We also invite everyone to help make Ember a more accessible framework. There are lots of ways to get involved! Here are a few ideas:
- Help maintain a11y-specific addons in the Ember A11y organization.
- Contribute additional template linting rules to Ember Template Lint
- Tackle an accessibility-related Help Wanted issue
- Add accessible component patterns to the Ember Component Patterns Project
- Provide feedback to the team
Today we reaffirm our commitment to accessibility by taking the GAAD Pledge. As we continually improve Ember, accessibility is an integral part of our core values. No matter where you are on your accessibility journey, we invite you to take a closer look at Ember and see the many ways that the framework supports developers to build high-quality applications that are accessible for everyone.