Accessibility on the Web
DevSnack #56: Ideally, web applications should be accessible to everyone. That means including people with disabilities. There are four main areas of disabilities to consider when building an application: visual, hearing, mobility and cognition. Front-end development has ways and tools to achieve this. There’s a standard on how to make web apps and content more accessible to people with disabilities, called ARIA (Accessible Rich Internet Applications).
In this post, Chris Northwood (@cnorthwood) lists some common mistakes and how to fix them. He also mentions that developing for accessibility is not as hard as it seems, and establishes a quick checklist to know if your web app is accessible or not.
There are aspects that change accessibility in many page components and parts, like images, forms, fields, tables, lists, headings and things like color contrasts. Marco Zehe (@MarcoZehe) explains ways of improving accessibility in each of these aspects.
Addy Osmani (@addyosmani) wrote this interesting post about creating Accessible UI Components. First off, he presents some key conditions a components must have to be accessible and provides a few examples. Then he presents a lot of useful tools, to test and debug the accessibility of your visual components.
In this post, Coleman Collins (@), criticises the current state of the web and Single Page Applications. It shows some examples on why current web apps are not being accessible and gives some tips and resources on how to fix that.
DevSnack by Moove-it is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.