Prioritizing document accessibility work

Prioritization organizes work; it does not change the rule

A work plan is not a substitute for required conformance and does not establish an exception. Determine the applicable deadline, scope, and specific exception conditions separately. Read the Title II web provisions.

Use explicit decision inputs

The following is suggested operational guidance, not a federal scoring formula:

• User task: what must a person be able to do?
• Current use and urgency: is the content needed for an active service or time-sensitive step?
• Barrier severity: what is prevented, and for whom?
• Dependencies: what source, owner, vendor, or approval is needed?
• Evidence: which checks support the finding, and what remains unknown?

An illustrative planning comparison

A currently used application with inaccessible required controls may need urgent attention because it blocks an immediate task. A historical report requires its own scope and exception review. This example is not a universal legal ranking: the purpose, applicable provisions, barriers, and affected people can change the decision.

Address existing barriers and new publishing

Assign owners for existing corrections while improving templates and authoring practices. A newer file is not necessarily easier to fix; an old file is not necessarily excepted. Measure representative work before committing to cost or duration estimates. DOJ’s first-steps guide provides preparation suggestions.

Keep decisions reviewable

Record why work is prioritized, unresolved access needs, dependencies, and triggers for reassessment. Do not delete or alter records without required authorization. Download counts can inform an inventory but do not determine exception eligibility or eliminate someone’s need for access.