Assign ownership and approve the process

Decisions to make before adoption

The assignments below are a proposed operating model, not an approved District policy or a statement about existing staff duties. Program leadership should name the responsible people, their backups and an escalation contact. One person may fill more than one role, but higher-risk work should still receive a separate review.

• Approve WCAG 2.2 Level AA as the website’s technical target and define the scope, including documents, media and third-party user journeys.
• Identify the policy approver and the person accountable for maintaining this guide.
• Set response and remediation timeframes based on impact, urgency and available resources.
• Confirm a monitored way to report barriers and request assistance.
• Approve the review schedule, record-retention rules and staff training plan.

Any legal determination about obligations or exceptions belongs with the District’s authorized policy and legal personnel.

Assign these responsibilities

Make the handoff specific

A request that says “make this accessible” leaves too much open. Send the page or file, the intended task, the problem encountered and any deadline. Identify which parts have already been checked and which need specialist review.

Do not ask editors to add unfamiliar ARIA attributes or patch theme code. Equally, do not assume a developer can invent the correct description of a project photograph or validate the facts in a financial report.

Give each role the right training

New editors should practice on a draft page containing a heading, image, document link and event notice. Document authors should practice exporting and checking a report. Reviewers need a repeatable keyboard and zoom test. The website team needs component-level and assistive-technology testing skills.

Keep approved templates and example files in a shared location. Revisit training when the editor interface changes, a recurring issue appears or a new content type is introduced.