In this talk, Kayla will address some common unintentionally exclusive web design and development practices and how to fix those problems to avoid being another website that SUX. Kayla will also present some resources to help developers create more inclusive websites.
This talk seems to interest people by just explaining to them accessibility and why we need to worry about it. It offers some simple ways to start thinking about designing and developing websites more inclusively. Accessibility is a large, sometimes complex, topic. I try to make it seem less daunting!
Kayla Sween is a front-end developer who is passionate about UX and inclusive web design. She strives to make the web easier to use for everyone. Kayla also is a competitive powerlifter, proud dog mom, and wife.
Web accessibility is about designing and building for every kind of person. It isn't restricted only to the visually/hearing impaired or people with disabilities.
We want everyone to be able to navigate, use, and consume the contents of our website. So we need to make sure that we're developing with everybody in mind. Not just the common case.
The Web Content Accessibility Guidelines 2.1 are a set of standards for designers and developers to follow so that they can design and build inclusive experiences.
They are the set of hardware or software that help users to consume content. Some examples are:
<head> tag of your HTML, make sure that you add a title because this is the first thing that will be read by a screen reader.
Also, setting the title allows users to manage their tabs easily since they can understand what each tab is for and what website they're on.
HTML<head> <title>Home | My Website</title> </head>
If you're using React.js, react-helmet helps in managing the titles of your React App
Text over images looks nice; however, if we're not careful, we might have a low contrast between the foreground and the background image. This will make the text less visible and much harder to read.
A cool browser extension you can use to test whether or not you have sufficient contrast is color contrast analyzer
The good news is you don't have to sacrifice aesthetics for accessibility.
Adding an overlay to the background image makes the foreground text a lot easier to read.
Here's an example:
On the other hand, if you're using solid colors as your background, you can test the contrast between the text color and the background color using tools like Colorable or WebAIM Color Contrast Checker
To further enhance the inclusiveness of your website, you should add meaningful content to your links. Some users set the screen readers only to read headings and links when they visit a page.
Using "click here" is not considered descriptive, and is ineffective for a screen reader user. So now, they will have to adjust their screen reader settings to read the entire content to understand the context.
Non-screen reader users share a similar experience, because "click here" links are not easily scannable.
Here are two examples of important links:
"For a complete list of all available HTML tags, visit our HTML Tag Reference" (source: w3schools )
"The IRS recommends using its online Where's My Refund Tool or the mobile app, IRS2Go. These systems are updated once every 24 hours and are the fastest ways to track your refund." (source: USA Gov )
Having meaningful names for links is also useful for SEO (Search Engine Optimization) and will make your webpage rank higher in search engines.
Associating form elements with their labels increases the clickable area. This is crucial for mobile users since they use smaller screens.
HTML<label for="name">Name:</label> <input type="text" id="name"/>
Here's an example of an accessible checkbox. Much easier to use on mobile because users can click the label to check the box.
All you need to do to achieve this is to use the
for attribute on your label and match it to the id on your input.
To test that everything works correctly, clicking on the label will bring focus (a border will surround the element) to the input.
Some users only use a keyboard to navigate a website by using the
Tab key. These users might have dexterity issues, or they might be using a screen reader.
You need to make sure that every element a user can interact with can receive visual focus, an indicator that this element is clickable.
<img> tag in HTML has an
"alt" attribute that will render a description of the image in case the image doesn't load.
However, this attribute is important for screen reader users because it helps them determine what the images are and what their context is.
When setting the "alt" attribute, make sure you give it a value that is relevant to the context that it's in.
Here's an example of an image with good alt text:
HTML<img src="pancakes.png" alt="Stack of blueberry pancakes with powdered sugar">
The exception to this is when you have a purely decorative image, like a line separator or an image that you're using as a bullet inside a list. Then you can use an empty
Some cool tools you can use to check the accessibility of your site automatically:
While these tools are awesome, the best way to test if your website is accessible is to use it the same way a user will.
Tab key to navigate the entire website; make sure that everything is readable, and that everything works.
For screen readers, you can use:
And to check the color contrast you can use: