Aglet

Triage processed document accessibility status and text gaps

A document can look complete while its status, text, preview controls, or processing errors remain unavailable to people using assistive technology. Triage should compare visual and semantic output for one document, including processing states. The objective is to identify the missing accessible information, not infer a user's ability from appearance.

Establish what is happening

  1. Record the visible workflow

    Capture source, processing state, preview or text result, controls, and error messages as a sighted reader encounters them. Note the information needed to choose wait, retry, download, or review and where it appears visually.

  2. Inspect semantic exposure

    Check accessible names, roles, state text, headings, table or document structure, focus order, and extracted text through the supported accessibility inspection path. Record information present visually but absent or ambiguous semantically.

  3. Classify the gap

    Classify the case as missing status, unavailable text, unlabeled control, focus order failure, structural loss, or unclear alternative. Preserve the document state and the specific action or content a reader cannot access.

What to carry forward

Triage is complete when visual information, semantic exposure, document state, and blocked action are compared for one case. If the output's accessible contract is undefined, record the missing expectation before selecting a particular implementation remedy.

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