March 24, 2016
Since Turing is such an intensive program, we often don't have the time to scrutinize every design choice for the applications we build. HTML and CSS are mostly self-taught, so it’s no surprise that most of us do not consider web accessibility when frantically trying to get a fully functional application running in three days.
Making sure your website is accessible means making it available and usable by everyone, including people of all different abilities. Would a person who can only use the keyboard be able to navigate your website? Is content available in different formats so that, for instance, a person who is hard of hearing can access a transcript or subtitles for audio content? There are many other considerations:
For more detail and a full list of considerations, see these accessibility principles on W3C’s Web Accessibility Initiative. Also take a look at these preliminary checks to see if your website meets some basic standards.
Besides opening up your application to more users, there is another benefit to making your website accessible, search engine optimization. With text alternatives and microdata, search engines can find content more easily and accurately. Microdata are simply descriptions of content on the page and you can implement them using attributes like this example from schema.org:
itemscope
defines the object, itemtype
describes that type of object, and itemprop
defines the property that the spanned content describes.
Government websites are required to adhere to the web accessibility principles, so I headed over to the CDC’s website to have a look. The site overall is easy to read with good contrast, there were text alternatives to the images, microdata, and I could navigate the site entirely without using my mouse (start with the tab key and options will appear at the top):
...back to posts