Let's Connect
Back to Projects

Research & Presentation *

Enhancing UX through Accessibility

A deep dive into why accessibility matters, the WCAG framework, and how to build it into a design process from day one — not bolt it on afterward.

Role

Researcher & Presenter

Format

Slide deck / presentation

Year

2024

Focus

WCAG principles, practical design & dev techniques

What is Accessibility?

Accessibility in UX design refers to the practice of creating digital products that can be used by people of all abilities and disabilities. This includes ensuring that all users, regardless of their physical, sensory, or cognitive abilities, can perceive, understand, navigate, and interact with digital content effectively.

Accessibility ensures that digital products are usable by people with a wide range of abilities, including those with:

  • Visual impairments — blindness, low vision, color blindness
  • Hearing impairments — deafness, hard of hearing
  • Motor impairments — limited dexterity, paralysis
  • Cognitive impairments — dyslexia, learning disabilities

Why It Matters — By the Numbers

1B+
people — about 15% of the world's population — live with some form of disability, per the World Health Organization.
26%
of U.S. adults have some type of disability, according to the CDC.
71%
of users with disabilities will leave a website that's difficult to use — a market with over $2 trillion in spending power globally (Click-Away Pound Survey).

Legal & ethical considerations: The Americans with Disabilities Act (ADA) prohibits discrimination against individuals with disabilities in all areas of public life. The Web Content Accessibility Guidelines (WCAG) provide the international standard for making web content more accessible. Designing with accessibility in mind promotes equal access to information and services, fostering a more inclusive society where everyone has the opportunity to participate fully.

Business Benefits

  • Wider audience reach. By making products accessible, businesses can tap into a larger market, including people with disabilities, their families, and friends.
  • Improved user satisfaction. Accessible designs often lead to better overall usability, benefiting all users, including those without disabilities.
  • Enhanced brand reputation. Companies known for their commitment to accessibility often enjoy a positive brand image and increased customer loyalty.

The WCAG Framework: POUR

WCAG provides guidelines for accessible web content, organized into four principles with guidelines and success criteria at levels A, AA, and AAA (best). The current version is WCAG 2.1, with 2.2 and 3.0 in development.

Perceivable — ensuring content can be seen and heard

  • Text alternatives: alt text for images, transcripts for audio.
  • Time-based media: captions for videos.
  • Adaptable content: content that can change layout without losing meaning.
  • Distinguishable: sufficient color contrast, audio control options.

Operable — making interfaces usable with all tools

  • Keyboard accessibility: all functions available via keyboard.
  • Navigable: consistent navigation, clear headings, focus indicators.
  • Input modalities: support for various input methods (e.g., voice, gestures).

Understandable — creating clear and predictable experiences

  • Readable: clear language, definitions for complex terms.
  • Predictable: consistent layout, no unexpected actions.
  • Input assistance: error suggestions, clear form instructions.

Robust — building content for long-term accessibility

  • Compatible: ensure compatibility with assistive technologies.
  • Clean code: use semantic HTML.
  • ARIA: enhance accessibility with ARIA where needed.

Practical Steps and Techniques

1. Design phase — planning for accessibility from the start

  • Color contrast: ensure sufficient contrast for visual clarity.
  • Typography: use readable fonts and sizes for all users.
  • Structure: organize content with clear headings and navigable elements.
  • Text alternatives: provide descriptive alt text for images and non-text content.

2. Development phase — coding for accessibility

  • ARIA roles and properties: enhance HTML for better interaction with assistive technologies.
  • Accessible forms: use clear labels and instructions for form fields.
  • Keyboard navigation: ensure all functionality is accessible via keyboard.

3. Testing phase — verifying accessibility

  • Automated tools: utilize tools like WAVE, Axe, and Lighthouse to check for accessibility issues.
  • User testing: collect feedback from users with disabilities to identify real-world issues.
  • Standards compliance: validate HTML and CSS to meet accessibility standards.

Tools & Resources

Design tools: accessibility features in Sketch, Figma, and Adobe XD.

Development tools: Chrome DevTools, Axe, and Lighthouse.

Educational resources: WCAG, WebAIM, and W3C WAI.

For checking contrast specifically, the WebAIM Contrast Checker is a quick, reliable way to validate text and background color pairs against WCAG's minimum contrast ratios.

Examples of Accessible Websites

BBC: comprehensive use of alt text for images, high contrast between text and background, full keyboard navigability, and transcripts/captions for audio and video content.

Apple: clear and readable typography, VoiceOver and other assistive technology integration, structured content with headings and landmarks, and high contrast, scalable fonts.

Deque: a company dedicated to digital accessibility — comprehensive resources and tools, clear layout and structured content, and high-contrast, accessible color schemes throughout.

Conclusion

Embracing accessibility in UX design comes down to a few core ideas: accessibility ensures inclusivity, legal compliance, and real business benefits. Following WCAG's four principles — Perceivable, Operable, Understandable, and Robust — gives teams a concrete framework rather than a vague aspiration. And it has to be integrated from design through development to testing, using the right tools and educational resources along the way, learning from industry leaders like BBC, Apple, and Deque.

Call to action:

  • Integrate accessibility. Make it a core part of your design process, not an afterthought.
  • Educate and advocate. Share knowledge and advocate for accessibility within your organization.
  • Continuously improve. Regularly test and update your designs to maintain and improve accessibility over time.
View Original Slides Back to Projects