As we be part of International Accessibility Consciousness Day (GAAD) in celebrating its tenth anniversary, we’re delighted to announce that the Ember JavaScript Framework has taken the GAAD pledge to make accessibility a core worth of our framework.
For individuals who know the undertaking nicely, this may come as no shock. It’s no secret that we expect that accessibility is an integral a part of high quality code. Ember.js is dedicated to offering a well-lit path for developer success, and our plans to make it simpler for builders to jot down accessible code are a part of that. In 2020, the Ember Accessibility Strike Crew grew to become the Ember Accessibility Working Group, demonstrating our dedication to long-term accessibility development within the framework.
What We have Executed So Far
Ember has additionally been transport enhancements with the “accessibility by default” developer expertise in thoughts. These enhancements embrace help for default app language (RFC #635), default web page titles (RFC #645), added content material to the guides particularly for accessibility, adjustments to the web site design for higher accessibility, and addition of accessibility-related linting guidelines to Ember Template Lint. Members of the Accessibility Working Group additionally printed two new addons, ember-context-id-helper and ember-select-light, to present builders extra instruments to craft accessible code.
What We Have Deliberate
Wanting ahead, we have now much more accessibility-related work deliberate. Two RFCs have been merged that concentrate on particular enhancements; one addresses a solution to make it simpler to affiliate components via distinctive id attributes in template-only elements (RFC #659), and the opposite proposes an interactive solution to create new Ember apps, making certain that accessible outcomes are entrance and heart (RFC #638).
We’ll proceed on our journey of accessibility with extra enhancements to the information prose and code samples, in addition to implement focused enhancements to the design of the guides and API documentation. Our objective is to achieve WCAG’s AA stage of conformance on our official undertaking web sites, and we’re decided to see this via to completion.
How You Can Assist
We additionally invite everybody to assist make Ember a extra accessible framework. There are many methods to get entangled! Listed below are a couple of concepts:
At this time we reaffirm our dedication to accessibility by taking the GAAD Pledge. As we frequently enhance Ember, accessibility is an integral a part of our core values. Regardless of the place you might be in your accessibility journey, we invite you to take a better have a look at Ember and see the numerous ways in which the framework helps builders to construct high-quality purposes which might be accessible for everybody.
