search

Esri / calcite-web

Authoritative front-end development resources for Calcite design initiative. Includes extendable base components and styles, as well as a modular and efficient framework for ArcGIS properties.
http://esri.github.io/calcite-web/
Apache License 2.0
109 stars 58 forks source link

Accessibility built in! #108

Closed eleanorh closed 9 years ago

eleanorh commented 9 years ago

Read this article & wondered if the Esri Patterns & Calcite Web framework are being built in such a way that the patterns work with the different input/output devices? Or is this something that needs to be handled at the individual developer level when they build a site?

http://alistapart.com/article/reframing-accessibility-for-the-web

/cc @CassidyB, @paulcpederson, @nikolaswise

nikolaswise commented 9 years ago

@eleanorh I've also been keeping up on what List Apart has been publiushing re: accessibility. I think that making sure at the most basic level our framework works with and supports universal accessibility is a requirement on us at this stage.

I think we need to make this a priority in testing and refining patterns. I suggest @CassidyB takes this into account for ALL the patterns work we're doing, and find someone who can help us bring this to Calcite Web.

CassidyB commented 9 years ago

@nikolaswise @eleanorh @paulcpederson @fgarofalo10

I 100% agree that we need to test each element of our Pattern Library, our Frameworks and our implementation process to make sure that it works on a variety of level including Accessibility testing.

I feel that Paul and I have been very much keyed into the notion that while we are rapidly developing the beta version of the pattern library we are now going to have to spend time testing, evaluating and adjusting the patterns before a 1.0 release. Even after 1.0 we understand the need to be vigilant in keeping up with adjusting the Pattern site to keep it up-to-date with compliance issues and our internal and external needs.

We will have a Curation team to help us with this process. I will start to reach out and find us a tester for traditional accessibility testing as well as localization and internationalization.

eleanorh commented 9 years ago

Awesome. Just wanted to make sure it was planned. :-) I'll mark this issue as closed as my question has been answered.

nikolaswise commented 9 years ago

Reopening this so we dont forget about it!

CassidyB commented 9 years ago

Good call!

paulcpederson commented 9 years ago

Totally agree! This is very related to #59

I think once we start testing all of this we'll be able to open smaller, more focused issues that address specific problems we find during testing. Thanks for bringing this up @eleanorh

CassidyB commented 9 years ago

@nikolaswise @paulcpederson @eleanorh Update on this topic: I have a group coming in for a 508 review of Calcite Web as well as a team from Localization coming to take a look and offer feedback. I will follow up with Paul and team this week to talk about the details.

nikolaswise commented 9 years ago

@CassidyB How did this go?

paulcpederson commented 9 years ago

Note to self: we should probably use aria-label attributes on tooltips: http://primercss.io/tooltips/

paulcpederson commented 9 years ago

assigning to @CassidyB to add results of accessibility audit to this issue or break out into more issues.

CassidyB commented 9 years ago

I will send notes as soon as one more review takes place. Date coming soon.

paulcpederson commented 9 years ago

@eleanorh just to keep you updated, we had our accessibility review which went pretty well. I've opened an issue here: https://github.com/Esri/calcite-web/issues/173 which outlines the actionable items, and we'll be opening individual issues for all the things that need to be fixed with the current framework.

I'm going to close this issue now that we are addressing this stuff.

eleanorh commented 9 years ago

Great. Thx for the update @paulcpederson