Accessibility Across a Product Ecosystem

I connected accessibility audits, screen reader testing and practical guidance across Oxford's platforms, interfaces and learning content.

Accessibility (WCAG) Screen Reader Testing Documentation Developer Handoff

At a glance

Making barriers visible

Accessibility barriers appeared across interfaces, learning platforms and PDFs. Understanding them meant looking at how content was structured, built and read with assistive technology.

As a UX/UI Designer, I audited products, tested with screen readers and translated findings into component guidance and documentation for product, development, editorial, legal and multimedia teams.

Role: UX/UI Designer
Scope: Platforms, interfaces and PDFs
Methods: Audits and screen reader testing

Annotated Oxford interface mapping screen reader reading order, headings and regions with numbered overlays. — Making screen reader navigation visible: reading order, headings and regions.

The decisions

Three decisions behind the work

Specify accessible components

I documented focus states, contrast, labels and interaction guidance in the design system, giving development a reference for implementation.

Test across environments

I compared documents and platforms using NVDA, JAWS and Microsoft Narrator, recording how behaviour changed across formats and tools.

Give each team usable guidance

I adapted recommendations to each team's work, from document structure and image descriptions to component behaviour and development handoff.

Evidence

From findings to practical guidance

The same content could behave differently across a PDF reader, a browser and a learning platform. I documented those differences alongside component requirements and proposed fixes.

Focus-state documentation showing button variants, highlighted focus styles and CSS outline guidance. — Focus states: the behaviour, visual specification and implementation reference in one place.

Accessibility testing matrix comparing document versions, platforms and screen readers used in each test. — Testing matrix: recording the document, platform and screen reader for each comparison.

Accessibility audit tracker listing issues, severity, affected areas, examples and proposed solutions. — Audit tracker: connecting each issue with its impact, location and possible solutions.

A short demonstration of colour-vision simulation, contrast checking and alternative-text inspection on Oxford Premium using an accessibility plugin. The screen reader tests are documented in the images above.

Outcome

A practical reference for the teams

Accessibility reports linking issues, their impact and proposed fixes.
Documented screen reader tests across platforms and document formats.
Component guidance covering focus, labels, contrast and interaction states.
Recommendations adapted to editorial, multimedia, product and development workflows.

🔒 About the examples

The video uses Oxford Premium's demo account. The process examples have been adapted for sharing. Further documentation and context are available in the Deep Dive.