| Table of Contents | ||||
|---|---|---|---|---|
|
...
Alert the content editor via the Jira ticket Service Desk publishing request that the page does not meet our standards by sending the below template.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Jira response templateHi ______, Unfortunately, the page you have submitted for review does not meet accessibility requirements and is unable to be published at this time. [Describe where the standards are not being met] The Disability Discrimination Act 1992 requires agencies 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. To meet the requirements and have your page published, you will need to [add guidance, e.g. “provide the contents of the PDF as a web page.”] If you are unable to make your page accessible at this time and would still like to proceed with publishing, we require you to respond to this email with the following acknowledgement. A disclaimer notice will be placed on the page with the contact information. I understand that the following page does not meet WCAG AA standards and is in breach of the Disability Discrimination Act 1992. I accept the responsibility for any action that may be initiated by failing to comply. I also agree to provide contact details for anybody seeking an accessible version of our information. These contact details will be published publicly on the web page, along with an accessibility disclaimer. I commit to providing an accessible version by: [date] Page title & link: Contact email: Authorised by: If you have any questions, please let me know. If you or your team needs any guidance on meeting accessibility requirements, you can book in for a consultation with an SDP content team member: https://outlook.office365.com/owa/calendar/SingleDigitalPresencevicgovau@vicgov.onmicrosoft.com/bookings/ Many thanks, [your name] |
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
This page does not meet accessibility requirements and cannot be published. Please see my check the Service Desk customer portal or auto-generated email for further detail. |
...
Publishing with disclaimer
Before publishing, the content
...
editor will need to respond to your message about the breach with:
acknowledgement that they are in breach and would still like to proceed with publishing
contact details to include in the published accessibility failure disclaimer
Add the accessibility disclaimer to the page with
...
‘call-
...
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: |
...
Steps to follow in the service desk
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 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
...
Your first point of call should be your digital manager. They will make a decision on behalf of your department that should be recorded in the CMS and Jira ticket. If an exemption is needed it should be brought to the publishing round table so we can start to understand the most common accessibility issues and look at ways to help improve our product and government systems.
If an exemption is granted, it should be recorded in the revisions field in the CMS so that other approvers are aware of it.
...
In some instances, a separate discussion can be had with a department or agency if the content is niche or if a HTML summary covering key messages could suffice for large/complex documents.
If an exception has been discussed and approved, update the Decision log - exceptions tab on the accessibility process and register spreadsheet.
Examples of appropriate exemptions
...
4-page fact sheets not in html
Translated content not in html
Closed captions and transcripts missing for video/audio
Missing alt text for images that aren’t descriptive, including diagrams and infographics
Any documents created for a digital and/or inclusive audience e.g. digital strategies, inclusion guides for family violence, LGBTI equality, etc.
Publishing round table
...
.