Accessibility Working Group Update


As early as March, an accessibility (A11y) assault team was established to solve Ember RFC Issue 595-Technical accessibility issues in the new Ember application. This blog post is to let the community know about the work of the group.

The commando meets once a week March 25 with June 24. We even managed to celebrate Global Accessibility Awareness Day!

Five items listed Episode 595:

  1. App language support
  2. Label/input support
  3. Page title support
  4. stand by ...attributes
  5. Accessible routing support

Active work

App language support

The goal of application language support is to provide a way for new Ember applications WCAG Success Criteria 3.1.1-Page Language. To achieve this goal, Joseph Sumner, Jamie White, Written by Ava with Melanie Sumner Created RFC 635, proposed a --lang Marked as ember-cli. This flag will enable developers to declare the language of the application when creating the application, making it easier for them to meet this specific success criterion.The RFC was merged on June 12; the function itself, the author Joseph Sumner With help Rob JacksonMerged on August 24.

In order to add another layer of support and enhance the overall developer experience, the team also decided that it would be useful to create new Ember applications interactively. After some discussion, Melanie Sumner Created RFC 638. On August 10, the RFC was accepted and merged. Implementation is still awaiting.

Additional support comes from Update Ember guide, Whether it’s prose or art, thanks to the team members Written by Ava with Lenora Porter. Melanie Sumner also New rule added To Ember template Lint plugin call require-lang. It checks to make sure lang Attribute exists in <html> Attributes.This rule will take effect in v3.0 of the plugin, thanks Alex Kanunnikov Add lint function .html File in Public Relations 1232.

Label and input support

The team decided to do three things in this regard:

  • Update guidelines to provide clearer guidance
  • Provide a plugin that helps provide idIn a specific context
  • Write an RFC to propose a more durable solution

Benjamin Jagad created Ember context ID helper plugin. This {{context-id}} Produce a unique id For the given context.Because it uses Ember’s guidFor Function under the hood, it will always return the same id For the same context.A use case context-id Assistant is programmatically associated <label>sand <input> Element usage <label> for Attributes and <input>second id Attributes.

This plugin is inspired by the pre-RFC guid-for Helper, this leads to RFC 659, which proposes a new built-in template helper, Author: Steve Szczecin.

Rajasthan Chandran with Jane Weber updated Official Ember Guide Clearer information on how to connect <label> with <input> element. Melanie Sumner Also created Embers component mode Reflect best practices <input> field.

Finally, support has been added to Ember template Lint plugin Needed rules <input> Elements to have Valid label And have No duplicate tags. Now additional work is being done to check if there are No duplicate ID and also Effective use of form groups.

Page title support

in our Meeting on April 8, The team discussed how we think we should deal with page title support. More discussions throughout the month prompted us to support template-driven support for page titles in the Ember app.

Benjamin Jagad, Melanie Sumner with Ricardo Mendes Created RFC 645, It is recommended to add the Ember page title plug-in to the blueprint of the new Ember application. After the framework core team discussed it, it was decided that the plug-in needed some work to be accepted.Outlines the work In a question And is Currently ongoing, Thanks to community members Redoculi!

Back to drawing board

After discussion and some analysis, it is determined that some issues require attention Framework core team solve. These issues may require reconsideration of important Ember features, so there should be some workarounds before solving these issues.

stand by ...attributes

As mentioned in Ember Issue 19026, ...attributes There is no guaranteed order of merging. This is problematic for the 5 ARIA attributes because they can have multiple values ​​in the form of an ID reference list, and the order of these values ​​is important.

This may lead to some additional discussions about how Ember handles attributes and attributes, and rethink the method to better support attributes.

Barrier-free routing

We are currently discussing how to best solve this problem in a permanent manner.Despite the large number Research on the problem with RFC Attempts to solve this problem, but no solution has been reached yet. However, the framework core team has accepted that accessibility is a design constraint for the work of any new router.

Until then, developers are encouraged to review Accessibility section of the Ember guide, And consider using one of the plug-ins related to routing.Options include Focus on yourself, a11y-Announcer, man-a11y, with ember-a11y-refocus.

A11y Working Group

At the last Strike Team meeting, we decided to continue Ember’s accessibility work and became the Ember A11y working group.We coordinate in the #dev-ember-a11y channel Ember’s Discord server And meet as needed. Interested friends are welcome to join!

Work is still in progress to upgrade the plugins in the plugin Ember-A11y GitHub organization!We are still continuing to add first-class accessibility support to ember-template-lint; what’s coming is to support users Run only linting rules related to accessibility On the code base.

thank you

Thank you very much to all community members who participated in the Ember A11y Strike Team: Abilash Ramesh, Emilyn, Written by Ava, Benjamin Jagad, Emanuel Patrick, Eric Kelly, Frederic Sumaré, Jamie White, Jane Weber, John Costanza, Joseph Sumner, Lenex Zinyondo, Lenora Porter, Melanie Sumner, Plascoviagen, Rajasthan Chandran, Robert Jackson, Steve Szczecin, with Sima Sharia.

Leave a Reply

Your email address will not be published. Required fields are marked *