Accessibility Standards vs. the Deadline
A content team must publish a large set of help-center articles and a downloadable PDF guide in three weeks for a product launch. A standards review flags: images without alt text, color contrast below WCAG AA on callout boxes, headings used for visual sizing rather than structure, and an auto-generated PDF that is not screen-reader accessible. The product manager argues that fixing all of this will miss the launch and that 'we can do accessibility in a fast-follow.' The team has two content writers and no dedicated accessibility specialist.
1. Assess which flagged issues are launch-blocking versus deferrable, and justify the split on standards grounds.
Read the worked answer
Split by severity and remediation cost, not by convenience.
Fix before launch (low cost, high impact):
- Heading structure: using headings for visual size breaks screen-reader navigation. It is cheap to fix (apply correct heading levels, use CSS for size). Do it now.
- Alt text: missing alt text blocks non-visual users from understanding images. Writers can add it during editing. Do it now.
- Color contrast on callouts: a CSS/token change, not per-article work. Fix the style once; it propagates. Do it now.
Highest-risk deferral:
- Inaccessible PDF: this is the most consequential and the hardest to fix, and 'fast-follow' often never happens. A non-accessible PDF is a hard barrier for screen-reader users. At minimum, publish an accessible HTML version of the guide alongside the PDF now, and remediate or replace the PDF on a dated commitment.
The PM's framing treats accessibility as optional polish. Standards treat access as a baseline, and three of the four issues are cheap enough that the deadline argument does not hold.
2. The team has no specialist and two writers. Propose a practical process to meet the launch without dropping the blocking fixes.
Read the worked answer
- Fix the systemic issue once: correct the callout color tokens and heading styles in the template, so every article inherits the fix without per-article edits.
- Bake checks into the existing workflow: add alt text and heading checks to the article template and to the writer's pre-publish checklist, so it is part of editing rather than a separate pass.
- Triage by template: since many articles share templates, fixing the template addresses most instances; spot-check a sample rather than auditing every page manually.
- Handle the PDF separately: ship an accessible HTML version of the guide at launch; assign PDF remediation an owner and a date.
- Escalate the trade-off explicitly: tell the PM which fixes are in and which are deferred with a dated plan, so the decision is visible rather than silent.
This keeps the deadline while refusing to ship known, cheap-to-fix barriers.