Skip to content

[Edit] Accessibility: Add Practicality and Challenges #6579

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ Title: 'Accessibility'
Description: 'Accessibility refers to designing devices, products, and environments such that individuals with disabilities or sensory impairments can successfully use them.'
Subjects:
- 'Web Design'
- 'Web Development'
Tags:
- 'UI'
- 'UX'
Expand All @@ -12,8 +13,6 @@ CatalogContent:
- 'paths/front-end-engineer-career-path'
---

<link rel="canonical" href="https://www.codecademy.com/article/what-is-digital-accessibility" />

**Accessibility** refers to designing devices, products, and environments such that individuals with disabilities or sensory impairments can successfully use them.

## Accessibility Guidelines
Expand All @@ -27,10 +26,23 @@ The Web Content Accessibility Guidelines (WCAG) break down accessibility into [f

[Inclusive design](https://www.codecademy.com/resources/docs/uiux/design-methodologies/inclusive-design) focuses on designing for users of all demographics and abilities, while accessibility is specifically focused on designing for people with disabilities. Any product that doesn't consider accessibility and equity may (whether intentionally or not) exclude a portion of the population who would otherwise find it useful.

## Resources
## What Accessibility Looks Like in Practice

Accessible UX design requires intentionality at every stage, from wireframing to testing:

- **Use semantic HTML structure and headings:** Proper use of elements like `<main>`, `<nav>`, `<section>`, and heading levels improves navigation for screen readers.
- **Ensure color contrast meets minimum thresholds:** Text and interactive elements must be readable in low-light conditions and by users with visual impairments.
- **Label form fields and inputs clearly:** Labels, placeholders, and instructions should be provided with screen-reader-accessible markup.
- **Avoid using color alone to convey meaning:** Use text, icons, or shapes in addition to color cues to support color-blind users.
- **Design keyboard-accessible navigation:** Users should be able to navigate and interact with all elements using just a keyboard.
- **Write meaningful link text:** Avoid vague labels like “click here”. Instead describe the purpose of each link clearly.

> **Note:** Accessibility is not just a legal or ethical requirement. It improves usability for all users, including those using small screens, older devices, or assistive technologies.

## Challenges Designers Should Consider

- [Codecademy: What is Digital Accessibility?](https://www.codecademy.com/article/what-is-digital-accessibility)
- [W3C: Web Content Accessibility Guidelines](https://www.w3.org/WAI/standards-guidelines/wcag/)
- [The A11Y Project](https://www.a11yproject.com/)
- [Interaction Design Foundation: What Is Accessibility?](https://www.interaction-design.org/literature/topics/accessibility)
- [UX Planet: A Primer to Web Accessibility for Designers](https://uxplanet.org/a-primer-to-web-accessibility-for-designers-2c548448c612)
- **Animations and motion:** Ensure that animations respect the user's motion preference settings and avoid triggering vestibular disorders.
- **Alt text and media description:** Every image, chart, or embedded media must include an appropriate description for non-visual consumption.
- **Language and cognitive load:** Avoid jargon, acronyms, or long blocks of text that can overwhelm users with cognitive disabilities or non-native fluency.
- **Touch targets:** Buttons and links must be large enough and spaced adequately for users with limited motor control.
- **Testing tools may not catch everything:** Automated tools like axe or Lighthouse can help, but manual testing with screen readers or diverse users is still essential.