Tips: Making Your Projects Web Accessible (2 of 3)
Tags: design, a11y, ux, html
Published: 2020-10-01 15:49:16

Web Accessibility is an important factor in your design and development. With 56 million people with a disability in the United States alone (almost 1 in 5), and 1 billion worldwide, making your website accessible is not something to merely dismiss. Not only is it a requirement for many, it is just plain good UX, leading to your sites ability to reach a wider audience, improve SEO and site search-ability, and maybe even increase conversions. Luckily, making your site accessible is not as hard as you might think!

I will be creating this list of web accessibility recommendations in a three part series, focused each part on: Order and Tags, Content and Labels, and Color and Contrast.

---

## Part 2 - Content and Labels

### Use Descriptive Links
When a screen reader hits a button that merely says "Click Here", the user may be questioning what "here" means, and where that link will take them! Throughout your website, it is best to make text in links as descriptive as possible. A link should be descriptive in a way that you would understand where it goes without the context of its surrounding elements. 

**_What to do_**
Plan out your links so that you can make them descriptive while still keeping your website content cohesive and simple. Try to make your links understandable even when out of context.

**_Resources_**
- [WebAIM: Links and Hypertext](https://webaim.org/techniques/hypertext/link_text)
- [Sitepoint: Making Accessible Links: 15 Golden Rules For Developers](https://www.sitepoint.com/15-rules-making-accessible-links/)


### Using Alt, Scope, Role and Aria Tags
Screen readers use a number of tags to communicate additional and often necessary information to visually impaired users. These tags are 'hidden' and do not display on the browser, but instead show up when a screen reader or robot scans the site. 

**_What to do_**
Alt (or alternative) Tags: Provides a description and meaning to an image or figure. Use them on every image.
`<alt="descriptive text">`

Scope Tags: Used on Table headers (th) to specify if is a header for a column or row.
`<th scope="col">`

Role and Aria Tags: Allows developers to include additional background information to an html element that a user on a screen reader may find useful, or to hide them when not needed.
`<img src="..." role="logo"/>`, `<button aria-label="close">`, `<span aria-hidden=”true”>`

**_Resources_**
- [W3C: Using Alt Attributions](https://www.w3.org/TR/WCAG20-TECHS/H37.html)
- [MDN Web Docs: Using Aria](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques)

### Include Labels on Forms
Many designers resort to using placeholder text to label input boxes on forms, as it can make the form feel cleaner or more modern, while reducing its size footprint on a page. This is a big mistake, and should be avoided with accessibility in mind. When a user with a screen reader tabs through a form, they jump between label and input box, but placeholder text is usually skipped over. Not using labels in your forms sacrifices usability for many potential users.

**_What to do_**
It is best to include labels for form input boxes, but if the goal is to de-clutter then the use of small and brief labels should be used instead. Brevity in your labels should not sacrifice usability and the user having a clear understanding.

**_Resources_**
- [Nielsen Norman Group: Placeholders in Form Fields Are Harmful](https://www.nngroup.com/articles/form-design-placeholders/)
- [freeCodeCamp: How to make an accessible form: it’s easier than you think](freecodecamp.org/news/how-to-make-an-accessible-form-its-easier-than-you-think-672d3f4ff573/)

---

## Conclusion
Part 2 complete! I hope you found this first set of recommendations useful in your journey into web accessibility. Web accessibility is always evolving and improving, and I am still trying to learn more about all of the requirements, options, and nuances available do designers and developers. Remember, making your website accessible opens doors to new users and is just plain good UX design, so implementing the basics is a great start.  Please respond with any comments or additional resources I can include that readers might find useful!

### Additional Resources
Below are some additional web accessibility resources, tools and guidelines for your site or project.
- [W3C Web Content Accessibility Guidelines (WCAG) 2.1](https://www.w3.org/TR/WCAG21/)
- [UX Collective: Designing for accessibility is not that hard](https://uxdesign.cc/designing-for-accessibility-is-not-that-hard-c04cc4779d94)
- [UX Pin: 8 Website Accessibility Best Practices to Improve UX](https://www.uxpin.com/studio/blog/8-website-accessibility-best-practices-to-improve-ux/)
- [Invision Design: A guide to color accessibility in product design](https://www.invisionapp.com/inside-design/color-accessibility-product-design/)
- [Inclusive Components: A library of ideas for making components accessible](https://inclusive-components.design/)
- [Vox Media: Accessibility Checklist for Designers, Engineers, and Project Managers](http://accessibility.voxmedia.com/)

### Additional Tools
- [AXE: Web Accessibility Testing Chrome Extension](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd)
- [Jxnblk Colorable: Color Contrast Checker](https://colorable.jxnblk.com/)
- [Sim Daltonism: A Color Blindness Simulator](https://michelf.ca/projects/sim-daltonism/)
- [SilkTide: Disability Simulator for the Web](https://silktide.com/resources/toolbar/)

---

[View Part 1](https://dev.to/lukekyl/tips-making-your-projects-web-accessible-1-of-3-2icc)
### Part 3 - Color and Contrast - Coming Soon...