PDF remediation
The remediated guide includes a title, language, semantic structure, logical reading order, meaningful links, sufficient contrast, and clear headings.
Project 02 · Document accessibility
Structure people can perceive and navigate
Paired PDF and PowerPoint artifacts show how document structure, reading order, descriptive language, contrast, and properties affect access to the same workshop information.
- My role
- Created the simulated files; introduced barriers, remediated, and compared them
- Formats
- PDF and PowerPoint
- Test matrix
- Tags, headings, reading order, links, contrast, metadata, keyboard, and screen reader
- Deliverables
- Accessible and intentionally inaccessible comparison files
Comparison artifacts
Review both experiences
PowerPoint remediation
The remediated deck uses unique slide titles, logical object order, readable type, sufficient contrast, explicit status language, and complete speaker notes.
Training note: Files labeled “inaccessible” intentionally contain barriers and are provided only for comparison and testing.
Remediation workflow
More than running a checker
- Establish purpose and reading sequence. Identify the information hierarchy and intended navigation before changing tags or object order.
- Inspect programmatic structure. Verify headings, lists, tables, links, language, titles, and alternative text.
- Evaluate visual access. Check contrast, text size, layout, magnification, and whether meaning depends on color or position.
- Test with assistive technology. Read and navigate the finished artifact in context rather than relying solely on an automated checker.
- Document limitations. Record what was tested, the application used, unresolved barriers, and any source-file dependencies.
Reporting sample
A developer- and stakeholder-ready deliverable
The sample audit report demonstrates scope, severity, reproducible steps, user impact, recommended remediation, acceptance criteria, and retest status.
Open sample accessibility audit report