Review and publish a website update

Use a review step before every release

This is a proposed BuildLACCD publishing procedure. The District should approve the process and assign the roles before treating it as an operating policy. Small text edits still need a quick check; a new form or document needs a fuller review.

Keep the request, source files, review results and release note together in the team’s approved tracking system. A completed checklist is useful evidence of work performed, not proof of WCAG conformance.

Prepare the content and the request

1. Identify the destination. Record the page URL, purpose, content owner and requested publication date. List every document, image, form or embedded service being added.
2. Choose the right format. Put event details, instructions and short announcements on the web page. Use a downloadable file when the document format serves a real purpose.
3. Supply accessible source material. Include the editable document, checked PDF if needed, meaningful link labels, image descriptions and reviewed captions. Do not leave these decisions until upload day.
4. State the review scope. A revised report needs document checks and a download-link check. A form replacement needs a complete submission test, including errors and confirmation.

Review the preview, then approve it

Use a draft or staging preview before changing the public page. The editor completes the relevant guide’s checklist. A second person checks the changed content in its page context. Include keyboard use, zoom and a small-screen view; use specialist testing for complex documents or interactive components.

If a visitor cannot read the information or complete the task, pause the affected update and assign the fix. Escalate urgent notices to the designated owner for an accessible publication plan. An inaccessible attachment plus a contact line is not an automatic exception.

The reviewer records either “ready to publish” for the stated scope or “changes required,” with the remaining issues. Technical changes to templates, plugins or forms go to the website team for testing and a recovery plan.

Publish and check the actual result

1. Publish the approved version. Record the live URL, date, editor, reviewer and a short description of the change.
2. Open the public page while signed out. Confirm that the correct file downloads, the image description is present in the rendered page, and links and controls work.
3. Recheck the changed task. Clear a stale cache through the website team if the old version is still visible.
4. Attach the live check results to the release record. If a problem appears, log it and correct or safely roll back the affected change.