W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2015

Ember.js and Accessibility

From: Nathan Hammond <nathan@nathanhammond.com>
Date: Thu, 18 Jun 2015 00:38:35 -0400
Message-Id: <F18CE4F0-5855-43D6-8CAB-D8BD59F528BB@nathanhammond.com>
To: w3c-wai-ig@w3.org
Hello W3C WAI!
Inside of the Ember.js community we're starting a conversation about how we can become "accessible by default." This will become a significant priority for my employer, LinkedIn, as well as the broader Ember.js community. We intend to run numerous experiments, gather data, and work to port all of our learnings into the core of Ember.js so that it is more difficult to be inaccessible than it is to be accessible.

This is both a lazyweb request to point me in the direction of ongoing conversations we should participate in as well as a request for this community's participation in the research we're doing. Note that my approach and intent is very pragmatic and must meet our needs now, and hopefully we can take what we learn as input for ongoing iterations.

My presentation to kick off the topic:

Current research projects:

Looking forward to many fruitful conversations!
Nathan Hammond
Received on Thursday, 18 June 2015 04:39:17 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 25 May 2017 01:54:15 UTC