# Ember.js - Accessibility Working Group Update

**URL:** <https://discuss.emberjs.com/t/ember-js-accessibility-working-group-update/18165>\
**Category:** Blog\
**Created:** [August 25, 2020, 10:44pm UTC](https://discuss.emberjs.com/t/ember-js-accessibility-working-group-update/18165 "2020-08-25T22:44:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ember-blog](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/ember-blog/32/16286_2.png) [@ember-blog](https://discuss.emberjs.com/u/ember-blog)\
**Post date:** [August 25, 2020, 10:44pm UTC](https://discuss.emberjs.com/t/ember-js-accessibility-working-group-update/18165/1 "2020-08-25T22:44:39Z")

</div>

Back in March, an Accessibility (A11y) Strike Team was formed to address the issues outlined in [Ember RFC Issue 595 - Technical Accessibility Issues in New Ember Apps](https://github.com/emberjs/rfcs/issues/595). This blog post is to update the community on that group's work.

* * *
This is a companion discussion topic for the original entry at [https://emberjs.com/blog/2020/08/25/accessibility-working-group-update.html](https://emberjs.com/blog/2020/08/25/accessibility-working-group-update.html)