A closer look at the work
Make the details visible.
Explore what a well-structured public document, a readable transcript and an actionable accessibility report can look like. These are fictional demonstrations, not client projects or compliance certifications.
01 / Document remediation
Same facts. Better structure.
A document can appear complete while lacking the semantic structure that assistive technology needs. This fictional council agenda shows headings, an ordered agenda, table headers and explicit participation information.
The PDF was generated from structured HTML with tagging enabled. It has not been independently certified for PDF/UA or WCAG conformance.
City Council
Meeting Agenda
Illustrative public meeting document
02 / Captioning & transcripts
Words with speakers, sequence and context.
Compare a small, scripted transcript excerpt with the companion WebVTT caption file. The example shows deliverable formats only; no actual audio was processed.
CHAIRWe will move to the next item on the agenda.
CLERKThe motion was made and seconded.
CHAIRIs there any discussion before the vote?
03 / Website audits
Findings people can actually fix.
Rather than an unexplained score, a useful audit describes the barrier, its impact, a reference criterion, an actionable fix and a way to retest. Every issue in this sample is invented.
Keyboard navigation
No visible focus on links
- Barrier
- Keyboard focus lacks a clear visual indicator.
- Reference
- WCAG 2.1 — 2.4.7 Focus Visible
- Fix
- Provide an unmistakable
:focus-visibleoutline. - Retest
- Navigate using Tab and observe the focus state.
What samples cannot prove
The real test is the work itself.
These examples are educational specimens, not verified customer results. A real deliverable requires an agreed scope, source material, validation as appropriate, and manual review. That is why each example is transparent about its limits.
No private documents needed to start; a public link is enough for an initial conversation.