Keep the lesson for the next incident
Cluster the access gaps
Group findings by status, text extraction, headings, tables, image alternatives, focus order, control names, preview, download, and failure recovery. Record the blocked task and the first boundary where its meaning disappeared.
Document the semantic contract
For each processing state and output, state status meaning, required text or structure, control names, focus path, and equivalent alternatives. Include a structured source and pending, failed, and ready examples.
Trigger inclusive review
Require the fixtures when changing processors, previews, text extraction, status labels, controls, or output formats. Assign an owner for semantic quality and record how a reviewer verifies task completion instead of only checking visual similarity.
What to carry forward
The learning record is useful when document states, content structure, controls, and alternatives have explicit semantic requirements with lifecycle fixtures. If an output cannot preserve a source feature, document the equivalent information and the affected task before delivery.
Technical background: W3C guidance.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow