Adopt an accessibility charter and assign ownership

Proposed charter wording for adoption review

For the services and content included in its approved scope, BuildLACCD will incorporate accessibility into planning, procurement, content creation, development, review and maintenance. The proposed technical target is WCAG 2.2 Level AA. Assigned owners will maintain accessible source materials, evaluate representative user tasks, record and resolve barriers, provide an approved assistance route and review results regularly.

The Program owner maintains an inventory and annual plan, assigns review and training responsibilities, retains decisions and test evidence, and reports unresolved barriers and resource needs to the approving authority. Any temporary alternative-access arrangement will identify the affected task, responsible owner, validation, remediation plan and review date.

This is draft policy wording for an authorized decision. The adoption record must identify the exact approved version, covered scope, owners, resources, effective date and review date. Until that decision is recorded, this text remains proposed.

Confirm scope, authority and resources

Before adoption, the approving authority should confirm which domains, services, documents, embedded tools and workflows the charter covers, and whether the proposed WCAG 2.2 Level AA target applies to each. Assign an accountable owner and backup; define release and urgent-issue authority; identify resources, training responsibility, records location and retention rules; name the reporting audience; and set the review date.

Route legal interpretations and formal exception decisions to the District’s designated policy and legal personnel. Record the approval and effective date, then start the recurring work in the companion procedures.

Assign a role to each part of the work

Assign a person and backup to each role after District review. One person may hold multiple roles; a high-impact form or shared component should receive an independent review. The Content editor confirms the accuracy and meaning of image descriptions and document content; the Website team implements those approved requirements.

Record adoption and keep decisions current

Store the approved charter with its review record. Use this field set so later staff can tell which version applied and what was actually decided:

• Record ID; document title and version; decision date; effective date; approving authority and approval evidence.
• Covered sites, services, content types and known exclusions, with an owner for each exclusion.
• WCAG version and level; named accountable owner and backup; delegated release and escalation authority.
• Approved staff time, tools, specialist support and training resources, or items still awaiting allocation.
• Monitoring cadence, reporting audience, record location, retention reference and next review date.
• Open decisions, interim owner, due date and evidence needed to close each decision.

At governance meetings, review new or retired services, unresolved high-impact issues, resource needs, upcoming releases and overdue actions. Record decisions, dissent or deferred questions, owners and next dates. Revisit the charter after a major redesign, a new supplier or a change in scope. See roles and responsibilities for the day-to-day handoff and WCAG 2.2 basics for the difference between the standard and proposed local procedures.

Use a working record

Complete a record when the activity occurs, download it and retain it in the approved team location.

• Policy and responsibility approval
• Governance meeting and decisions