Accessibility remediation across 21 publisher sites
A repeatable WCAG audit and fix workflow for a shared publishing platform.
Role: Front-end developer, accessibility lead
Read the transcript
What NVDA says in the recording, copied from NVDA's Speech Viewer log, in the order it was spoken.
- This Digital Database Cracks Open Early Medieval Texts | Katina Magazine
- visited link Katina home - Librarianship Elevated
- Katina Magazine
- same page link Skip to main content
- banner landmark link Annual Reviews
- visited same page link Katina home - Librarianship Elevated
- visited link Login or register
- button Open Search
- link SIGN UP
- Main Site navigation landmark list with 6 items visited link RESOURCE ADVISOR
- visited link OPEN KNOWLEDGE
- link THE FUTURE OF WORK
- visited link ABOUT KATINA
- THE FUTURE OF WORK
- clickable banner landmark Annual Reviews link
- Katina home - Librarianship Elevated visited same page link
- Login or register visited link
- Open Search button Search
- SIGN UP link
- Main Site navigation landmark list with 6 items RESOURCE ADVISOR visited link
- OPEN KNOWLEDGE visited link
- THE FUTURE OF WORK link
- ABOUT KATINA visited link
- INSTITUTIONAL SUBSCRIPTIONS visited link
- ADVERTISING link
- main landmark clickable This Digital Database Cracks Open Early Medieval Texts visited link heading level 1
- Sofia Fagiolo link
- Open without paywalls through S2O. Secure your 2026 institutional subscription! LEARN MORE visited link
- Knowledge Comes at a Cost. What Are We Really Paying For? visited link heading level 2
- By link The Open Knowledge Editorial Committee
- In this Open Access Week reflection, Katina editors grapple with the costs of knowledge, invisible
- The Unacknowledged Costs of Knowledge visited link heading level 2
- The Unacknowledged Costs of Knowledge | Katina Magazine - Google Chrome region
- The Unacknowledged Costs of Knowledge | Katina Magazine - Google Chrome region
- The Unacknowledged Costs of Knowledge | Katina Magazine
The problem
One platform powers many publisher sites, each with its own skin. Fixes made in one place drifted or never reached the others.
What I did
- Audited templates and shared JS against WCAG 2.2 AA and logged findings per instance.
- Replaced ad hoc dropdowns with the disclosure navigation pattern, with proper focus handling.
- Updated legacy markup and JavaScript to ensure there are no keyboard traps, no content that cannot be operated with a keyboard, and that everything interactive receives keyboard focus.
- Implemented template logic to keep the heading hierarchy correct on pages built from reused template fragments, so assistive technology users get a logical structure to navigate.
- Advised customers and stakeholders on colour contrast issues, where applicable.
- Made sure every site has a "Skip to content" link that appears on the first Tab press on a page, so keyboard users can jump past the header and navigation. Screen readers can override this behaviour, which is expected.
- Documented which instances inherit shared code and which keep their own fork.
- Tested every change with Lighthouse, SiteImprove, WAVE and axe-core, then manually with the keyboard and with the JAWS, NVDA and Windows Narrator screen readers.
The outcome
A tracked backlog of tickets, consistent keyboard behaviour, and a checklist new skins start from.
Training
W3Cx WAI0.1x: Introduction to Web Accessibility, verified certificate. Course by the World Wide Web Consortium (W3C) Web Accessibility Initiative, passed with a verified certificate issued September 19, 2025.