This guide covers the process for identifying and correcting an accessibility failure, when a content editor is requesting to publish content that doesn’t meet accessibility standards.
| Info |
|---|
This guide is for Approvers or people managing publishing requests as part of a federated publishing queue. |
The Disability Discrimination Act 1992 requires content creators to ensure people with disabilities have the same access to information and services as others in the community. It is a requirement for all government sites to meet WCAG AA guidelines.
...
Set the CMS page back to Draft with the following revision note (this will let the rest of the team publishing team know that this person has already been contacted):
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
This page does not meet accessibility requirements and cannot be published. Please check the Service Desk customer portal or auto-generated email for further detail. |
The editor has the option to either:
update the page to meet the standards
proceed with publishing, with an accessibility failure disclaimer added to the page.
If the editor acknowledges they are in breach and wants to proceed with publishing, they will need to provide you with contact details to include in the published accessibility failure disclaimer.
...
Adding and publishing an accessibility disclaimer on a page
Once the editor has acknowledged they are in breach of the accessibility requirements and has provided you with contact details, add the accessibility disclaimer to the page with ‘callcall-out’ out formatting and publish.
| Note |
|---|
The Victorian Government is committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability. This page may not meet our minimum WCAG AA accessibility standards. If you are unable to read any of the content of this page, you can contact the content owners for an accessible version: Contact email: |
...
Managing the Jira ticket
Change the ticket status to On Hold.
Change the Component to Accessibility issue.
Change the Date required to the date the editor has committed to fix the issue.
The day before the Date required, the Service Desk will notify the Assignee to let them know that the date has arrived. Check to see if the issue has been resolved:
if resolved, you can close the ticket
if not resolved, use the comments to request an update.
Escalating non-compliance or other issues
...