Skip to content
Digital Accessibility cover

Digital Accessibility

Designing more inclusive digital experiences.

Role
UX / Accessibility Designer
Scope
Accessibility review, UX recommendations, interface improvements
Tools
Figma

Overview

Work gathered around inclusive product thinking, accessibility reviews, UX recommendations, and interface improvements that make digital services usable for more people.

Goals

Improve clarity

Make interfaces easier to understand and navigate.

Reduce exclusion

Identify patterns that make services harder to use for people with different needs.

Create practical recommendations

Translate accessibility principles into design decisions teams can implement.

Landing screen of the Digital Accessibility resource with a "Get started" and "Quick checklist" call to action.

Framed as product decisions, because compliance loses roadmaps

Accessibility pitched as compliance gets scheduled for later. Recommendations here were written as product improvements, clearer hierarchy, visible focus states, predictable interactions, benefits every user can feel. The same change, framed as usability, ships quarters earlier. That framing was a deliberate choice, and it's the difference between an audit that gets implemented and one that gets archived.

Wall of collected research pages and reference articles on disability and inclusive design.

Research

The resource sits on a broad reading of disability, not as a fixed trait but as a mismatch between a person and their environment. That framing, drawn from inclusive-design literature, is what lets the guidelines apply to temporary and situational limitations too, not just permanent ones.

Spread from the resource explaining corporate identity versus corporate image. Chapter divider for the Animation section in bold violet and black.

A flexible visual system

The identity deliberately avoids the usual accessibility clichés. Each category in the design system gets its own visual treatment while staying part of one coherent whole, so the guidelines stay legible and easy to scan across chapters.

Design-methodology page pairing guidance text with focus-state and voice-input examples.

Inclusive patterns

Reusable patterns make accessibility improvements consistent rather than one-off.

Guideline page showing why color alone should never carry information, with good and bad examples.

Practical scope

Hierarchy, contrast, focus states, content clarity, interaction predictability.

Voice-input microphone icon next to the international symbol of accessibility.
Introduction screen defining digital accessibility over a blue and black header. Grid of source articles reviewed while building the guidelines.

Outcome

The result is a set of guidelines teams can actually ship, because every recommendation is written as a product improvement rather than a compliance item. That framing is the real outcome here. An accessibility audit that reads like a usability plan gets built, and the people it was written for feel the difference without ever seeing the document.

Interested in exploring more?

Show all