At Clique, one of our 3 values is “make somebody’s job easier.” Every time we build something, we challenge ourselves to keep this value at the forefront. Why build, if not to make things easier, simpler, and more accessible? Maybe you—like us—want to build accessible stuff too. That’s awesome.
WHAT IS ACCESSIBILITY?
Accessibility is the practice of designing products, devices, services, or environments for people who experience disabilities. It’s about removing barriers that might prevent people with disabilities from accessing something. It’s about creating opportunity for everyone to participate in x, y, or z.
It’s about inclusion.
Our intention with this guide is to help a beginning devs and non-devs begin their accessibility initiative. It’s a great place to start, but—to be clear—it’s just that: a start. It outlines important stuff they need to know, from why they should care (hint: many, many reasons) to how they can have the biggest impact on web accessibility efforts in your role.
Since we started sharing this article with a few friends last week, two of the coolest things we've noticed are:
- There are multiple interpretations of various parts of WCAG 2.0 and we've had some really healthy discussions about how our site fits with those.
- Our own site's accessibility is getting better and better from more devs eyes on it, something we hadn't considered.
One Ask: What's missing from this guide? What else should we include that was left out? (We hope the answer is "nothing," but if there's an overlooked aspect, I know this is the place to find it!)
If you're interested in checking out the guide, I'd love your thoughts: https://cliquestudios.com/accessibility/