In October of 2017, Amar Trivedi gave a presentation at the Baltimore WordCamp on how designing for accessibility improves the user experience.
In part two of this two-part series, we continue to unpeel the layers of accessibility in regard to the user experience. We also provide a number of valuable resources you can use to check your website for accessibility.
In part one, we dispelled myths about who is responsible for accessibility, present some startling facts and outline reasons for why you should consider accessibility.
As we had mentioned in part one, accessibility should be the responsibility of everyone within your organization.
Whether your website is being currently being built or has been around for some time you can still apply the below tips to your website.
- Be consistent
As you update existing content or upload new content it is important to always be consistent. Make sure your labels and tags are done & all of your graphics, photos, and documents have alternative text.
- Don’t solely rely on color cues
Make sure your forms use “NAME OF POPUP BOX” as well as color to alert the user to any missing or incorrectly entered fields
- Use H1, H2, H3, H4 as ways to highlight important headings or information.
While it is tempting to use any of the H styles for design purposes, we highly recommend staying away from this practice. H tags are used to call out the extra important information on your site, not for design aesthetics.
- Be careful with all capitals
They can be difficult to read and may be read incorrectly by screen readers
- Provide transcripts of any video or podcasts
Whether it is offered on-screen through in-sync captioning or posted below the description it’s important to include these transcripts.
- Test, test, & test
Use different plugins to check your website for a variety of disabilities. What does it look like without images? How does it sound if you used a screen reader to read everything out loud? Can you navigate only using your keyboard?
Free recommended resources for checking accessibility.
Other resources you may be interested in…