Aglet

Prioritize processed document accessibility gaps by blocked task

Accessibility gaps deserve attention according to the task they block: understanding status, reading text, operating controls, or obtaining the processed file. Prioritization should record available alternatives and workflow consequence, separating a minor label refinement from a missing path to complete a required document action.

Decide where the work belongs

  1. Name the blocked task

    Record whether the person cannot determine status, read extracted text, operate preview controls, download a result, or recover from failure. Note the document stage and whether another accessible representation provides the same information.

  2. Assess independence and reach

    List affected states, formats, controls, focus paths, and document structures. Mark whether the gap affects one optional preview or the full processing workflow, and whether the alternative requires another person or a separate manual reconstruction.

  3. Choose the queue

    Queue semantic status or control repair when the task is blocked, derivative accessibility work when content is missing, or copy and structure review when an equivalent path exists but is unclear. Attach the observed state and task evidence.

What to carry forward

Prioritize the issue when a person cannot independently understand or complete a required document task through the supported workflow. A small wording refinement can wait when a clear equivalent path remains available and the blocked information is nonessential.

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