Aglet

Investigate accessibility loss in processed document outputs

Investigation should compare source and processed representations through each boundary, including pending and failed states. Use a document with headings, tables, and meaningful text, then inspect what a semantic consumer receives. The brief should identify the first lost status, structure, or control.

Build a useful investigation brief

  1. Prepare a structured fixture

    Use a document with headings, paragraphs, a table, a meaningful image alternative, and a processing failure or delay path. Record the information and actions that must remain available after processing.

  2. Trace semantic output

    Inspect status announcements or text, headings, reading order, table relationships, control names, focus movement, and preview alternatives at each state. Mark where source meaning, processing state, or action guidance disappears or becomes ambiguous.

  3. Compare task completion

    Follow the tasks of understanding progress, reading content, operating controls, and obtaining the output using the supported semantic path. Identify the first boundary that blocks a task and distinguish absent content from an inspection limitation.

What to carry forward

The investigation is sufficient when a structured fixture and state trace show the first missing semantic content, status, or control tied to a blocked task. If a representation is intentionally visual-only, document the alternative boundary and test whether it carries equivalent meaning.

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