Accessibility

State the accessibility commitment and scope

The central question for Accessibility is this: How can people identify barriers and request accessible information or participation? That question is more useful than a broad definition because it identifies the decision a sponsor or project team must make. In this guide, accessibility is treated as part of delivery work—with constraints, consequences and ownership—not as a fashionable label added to an existing plan.

Consider a learner needing captioning, keyboard access, an alternate document format or a course accommodation. The team cannot resolve that situation by selecting a template first. It must understand what is changing, who experiences the result, where authority sits and which assumptions could overturn the preferred response. The purpose of “State the accessibility commitment and scope” is to frame that context before effort and money narrow the available choices.

Describe website and document accessibility

For Accessibility, the pivotal management choice is to publish confirmed accessibility practices, request routes, response process and known limits. Write that choice as a decision statement: the outcome sought, the person authorized to decide, the information required and the date after which delay creates a different consequence. This prevents a recommendation, workshop or technical preference from quietly becoming an approved commitment.

Use the scenario—a learner needing captioning, keyboard access, an alternate document format or a course accommodation—to test the decision route. Ask who recommends, who contributes knowledge, who can approve, who may be affected and who must operate the result. If those roles disagree, record the trade-off and escalation path. “Describe website and document accessibility” should leave the reader knowing what must be settled, not merely which terminology to use.

Explain course and communication accommodations

A defensible approach to accessibility needs evidence that is close to the real decision. For this page, that means accessibility review, platform capability, document tests, accommodation workflow and feedback records. Record the source, date, owner, scope and known limitation of each important input. Evidence from a different population, location, system or project phase may still be useful, but its transfer limits should be visible rather than assumed away.

Do not wait until the final report to discover whether the information can answer the question. During “Explain course and communication accommodations,” review whether the evidence distinguishes a genuine change from normal variation, whether affected people can challenge the interpretation and whether missing data should lead to more research, a bounded test or a more cautious commitment.

Provide a monitored request route

Turn “Provide a monitored request route” into owned project work. Translate the intended result into deliverables, dependencies, acceptance conditions and decision points. In the case of a learner needing captioning, keyboard access, an alternate document format or a course accommodation, the schedule should expose the moments when new evidence can still alter design, procurement, rollout or transition. A milestone that records only activity is weaker than one that tests a meaningful assumption.

Select predictive, iterative, agile or hybrid practices according to the uncertainty in accessibility, not according to habit. Name the people responsible for integration, quality, risk and stakeholder commitments. Make constraints and exclusions explicit. When specialist, legal, technical, cultural or community authority is required, bring it into the work instead of allowing a general project process to impersonate it.

• Decision: Publish confirmed accessibility practices, request routes, response process and known limits.
• Working evidence: Accessibility review, platform capability, document tests, accommodation workflow and feedback records.
• Success test: Requests answered, barriers removed, conformance problems tracked and learners can participate.

Respond to feedback and unresolved barriers

The measurement question for Accessibility is whether the project achieved requests answered, barriers removed, conformance problems tracked and learners can participate. Build a small set of indicators around that statement. Include an early signal that can change delivery, an outcome measure that tests value and a balancing measure that reveals displaced cost, harm, overload or unequal impact. Activity counts may explain effort, but they should not be presented as the outcome.

For every measure used in “Respond to feedback and unresolved barriers,” specify the calculation, boundary, baseline, frequency, data owner and decision it informs. Add structured qualitative evidence where experience or context cannot be reduced honestly to a single number. Review patterns and exceptions together; an average can conceal the group, location or operating condition where accessibility is failing.

Review conformance as services change

Use “Review conformance as services change” to decide what happens after the first result. Compare the evidence with the original question—How can people identify barriers and request accessible information or participation?—and with the decision to publish confirmed accessibility practices, request routes, response process and known limits. Continue, adapt, expand, pause or stop for an explicit reason. Record which assumptions were supported, which were disproved and which remain too uncertain for a larger commitment.

Close the loop with the people who supplied information, accepted impact or inherited the result. In the working case of a learner needing captioning, keyboard access, an alternate document format or a course accommodation, assign ownership for unresolved issues, future measurement and the next review date. Retain the rationale as well as the approval. That final discipline makes accessibility a source of organizational learning rather than another page, report or project that appears complete only because delivery activity ended.