# Intro to accessibility slides/resource links shared at Brigade Congress

**URL:** <https://discourse.codeforamerica.org/t/intro-to-accessibility-slides-resource-links-shared-at-brigade-congress/315>\
**Category:** Diversity and Inclusion\
**Tags:** accessibility, brigadecongress-2018\
**Created:** [October 20, 2018, 8:48pm UTC](https://discourse.codeforamerica.org/t/intro-to-accessibility-slides-resource-links-shared-at-brigade-congress/315 "2018-10-20T20:48:53Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![mmazanec22](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/mmazanec22/32/506_2.png) [@mmazanec22](https://discourse.codeforamerica.org/u/mmazanec22)\
**Post date:** [October 20, 2018, 8:48pm UTC](https://discourse.codeforamerica.org/t/intro-to-accessibility-slides-resource-links-shared-at-brigade-congress/315/1 "2018-10-20T20:48:53Z")

</div>

The following is a list of resources to help devs make accessible things:

- [aXe audit for Chrome](https://chrome.google.com/webstore/detail/axe/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US)
- [Firefox has some new tools](https://www.marcozehe.de/2018/04/11/introducing-the-accessibility-inspector-in-the-firefox-developer-tools/)
- [WebAIM’s WCAG 2 checklist](https://webaim.org/standards/wcag/checklist)
- [18F’s accessibility checklist](https://accessibility.18f.gov/checklist/)
- [W3C’s easy checklist](https://www.w3.org/WAI/test-evaluate/preliminary/)
- [W3C’s WCAG overview](https://www.w3.org/WAI/standards-guidelines/wcag/)

[The slide deck I used at NC Open Pass’s Civic Camp](https://docs.google.com/presentation/d/1lULuVGvJU-nWhPOQxObz01yfG-IeqN9jqQPZTeqhkZM/edit?usp=sharing) is almost the same as the one I presented at Brigade Congress. It contains some context and a few additional links that aren’t mentioned above.

I’ve also been working with Elijah Meeks to help figure out how to make [his library, Semiotic](https://github.com/emeeks/semiotic), accessible. We are at a bit of a rethinking stage, but also lots of people have expressed interest in the effort. So now we’re trying to collaborate with other folks/libraries on accessible data vis standards.

If you’re interested in accessible data vis or want to chat generally, contact me at [mmazanec@ashevillenc.gov](mailto:mmazanec@ashevillenc.gov).

PS-- I’m not an accessibility expert. Just a front end dev who was appalled to find out how inaccessible most websites are and thinks we can do better!

---

_[View the full topic](https://discourse.codeforamerica.org/t/intro-to-accessibility-slides-resource-links-shared-at-brigade-congress/315)._