The web is empowering but some people are unable to access huge chunks of it in the same way as others, or even at all.
Creating accessible applications is vitally important, but is often low down the list of priorities. However, the law is starting to catch up with the worst offenders - with big brands Beyoncé and Domino's recently sued for a lack of accessibility on their websites.
A few weeks ago I attended a lecture by Aimée Wyld from Mayden as part of the coding bootcamp I am doing with IO Academy. Aimée inspired me to think about accessibility in a way I hadn't before, speaking passionately about the power improved accessibility can have.
I summed up her key points below.
We often think of screen readers when we think about accessibility - it's long been best practice to add
alt tags to images so that they can be described accurately but accessibility on the web goes much wider than that. As well as visual, auditory or physical impairment we shouldn't forget about cognitive or neurological disabilities. Similarly, those with mental health issues or learning difficulties such as dyslexia will have other needs - for example, they may need the content itself to be written in a certain way and displayed in a clear, concise format.
Broken arm. Lost your voice. Laser eye surgery. Driving and can't use your hands. You never know when you may need to benefit from a website or application's accessibility features yourself.
Accessible code is also well-written, well-structured code. As a developer, any one else working on your code in the future will also thank you.
HTML5 introduced increased options for structuring your page. Using the semantic elements
<section> to divide your content (instead of
<span>) means that assistive technology such as screen readers can use this extra information to better do its job. For example, listing all the headings on a page in advance, or telling a user how many items are about to appear in a table or list.
Sure, you can put your code through an automated service that checks that some accessibility guidelines are met. However, many parts of having a fully accessible website are not easily verified with a 'yes/no' answer. Although it is a good place to start, a website could pass one of these tests and still have significant barriers to accessibility. Get to know the Web Content Accessibility Guidelines (WCAG), and make sure you're ticking off as many as you can.
As well as rewarding those who really need it, if your website is built with accessibility in mind there are a whole host of other benefits. It will load faster, will be ranked higher by Google, is more compatible across a greater number of browsers and some evidence has shown it can even increase conversion rates. What's not to like?