Aglet

Verify processed document status, text, and controls are accessible

Verification should cover the processing lifecycle and the document content a reader must understand. Test normal, delayed, failed, and ready states with structured source material. Confirm semantic output, control operation, and equivalent text remain available without relying on visual appearance alone in any state.

Check whether the outcome improved

  1. Exercise lifecycle states

    Process a structured document through pending, ready, and failed or delayed states. Record expected status, action guidance, extracted text, and preview alternative for each state before inspecting the semantic result.

  2. Check document structure

    Inspect headings, paragraphs, tables, reading order, meaningful images, and text search in the processed representation. Verify structure communicates the source's important relationships and that missing text has a clear equivalent path.

  3. Operate controls semantically

    Navigate status, preview, download, retry, and replacement controls with the supported keyboard and accessibility inspection path. Confirm names, roles, focus order, state changes, and result announcements make each action understandable.

What to carry forward

Accept accessibility behavior when representative states expose equivalent status, content, structure, and controls through the supported semantic path. Fail when visual-only information blocks a required task, focus cannot reach an action, or processed text loses essential 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