Web Accessibility Guidelines

web accessibility
Mon Apr 10 2017

In the previous post we went over why does Web Accessibility makes sense. In this post we’ll go over some guidelines and checklists to get started.

The concepts that we’ll go over cover a broad scope of rules so it would be helpful for starters to know that there is a set of guidelines to guide us in our journey.

Fortunately W3C has created WCAG Documents that stands for the Web Content Accessibility Guideline Documents. WCAG Documents were created by Web Accessibility experts documenting best practices about Accessibility for Web Developers. These documents will convey 4 core principles.

Perceivable
If one user can perceive something with one sense, for example sight, it doesn’t mean every user can perceive it.

Operable
Can users operate your app? If something needs a hover to work, maybe some users with a touch screen cannot use it.

Understandable
Can users understand the content and use the interface with no confusion

Robust
Does it work with assistive technology?

These documents are very rich and verbose and may seem overwhelming at first. So there is a checklist called the WebAIM Checklist for a quick summary of the high-end points of the documents.

Documents although a great resource remain, well documents. You don’t have to blindly follow them or mechanically fill-in checkboxes but through these we can be more aware of the user experience and the diversity of the users interacting with our web apps.

We will go over examples of improving our apps in the next posts.

Full Stack Weekly Newsletter

A free weekly newsletter for full stack web developers!