Melbourne Website Accessibility Obligations for Contractors

Civil Rights and Equity Victoria 3 Minutes Read · published February 11, 2026 Flag of Victoria

In Melbourne, Victoria, contractors who build, host or manage websites for the City or other municipal clients must consider accessibility obligations from the Disability Discrimination Act and accepted standards such as WCAG. This guide explains practical steps contractors should take when delivering digital services to local government, what compliance evidence to keep, how enforcement and complaints typically operate, and where to find official forms and contacts in Melbourne and Victoria.

Keep accessibility evidence and test reports linked to each contract deliverable.

What contractors must do

Contract obligations vary by tender and contract but commonly require:

  • Include accessibility requirements in scope, specifications and acceptance criteria.
  • Test deliverables against WCAG (commonly WCAG 2.0 or 2.1 AA) and retain test reports.
  • Maintain timelines for remediation if accessibility issues are identified during acceptance or operation.
  • Provide contact details for ongoing accessibility support and updates.

Penalties & Enforcement

Enforcement for web accessibility complaints may proceed through the Australian Human Rights Commission (AHRC) under the Disability Discrimination Act or via civil proceedings; specific monetary fines or daily penalties are not detailed on the cited complaint guidance page. Complaints typically begin with conciliation and may lead to remedies or court orders if unresolved.[1]

If you receive a complaint from a council user, act promptly to document and begin remediation.
  • Fines and monetary penalties: not specified on the cited page.
  • Escalation: first complaints often go to conciliation; repeat or unremedied matters can progress to court—specific ranges not specified on the cited page.
  • Non-monetary sanctions: orders to remedy, declarations, or injunctions may be sought by complainants or courts.
  • Enforcer / complaint pathway: AHRC handles DDA complaints and conciliation; local council contract breach actions are handled by the contracting council's contract management or legal team.[1]
  • Appeal / review routes and time limits: time limits for lodging complaints or appeals are not specified on the cited page; check the enforcing agency or contract terms.
  • Defences and discretion: defences such as reasonable excuse, undue hardship or specific contract variations may apply depending on the legislation and contract; check legal advice and the enforcing body's guidance.

Applications & Forms

There is no single universal City of Melbourne "website accessibility certification" form published; contractors should follow contract deliverable checklists and keep test reports and remediation plans. For external complaints and conciliation processes, use the official AHRC complaints pathway listed in Resources below.[1]

How contractors document compliance

Document accessibility in the project lifecycle:

  • Include accessibility in requirement documents and acceptance tests.
  • Supply WCAG test reports, user testing records and remediation logs.
  • Attach accessibility statements and change logs to deliverables.
Store accessibility evidence with the contract file for at least the duration specified by the contract.

FAQ

Do contractors need to meet WCAG for City of Melbourne contracts?
Many contracts require adherence to recognised accessibility standards such as WCAG; check the contract specification and council procurement documents for exact requirements.
Who enforces accessibility complaints for websites used by Melbourne residents?
Complaints about discrimination or inaccessible services can be made to the Australian Human Rights Commission for DDA matters; contract breaches are handled by the contracting council.
Are there set fines for non-compliant websites?
Specific fine amounts are not listed on the cited complaint guidance page and often depend on court outcomes or contractual penalty clauses.

How-To

  1. Review the contract and identify stated accessibility standards and acceptance criteria.
  2. Run automated and manual WCAG tests and record results.
  3. Remediate issues within the agreed timeframe and update acceptance evidence.
  4. Provide an accessibility statement and contact details for ongoing reports and fixes.
  5. If a complaint arises, engage the council's contract manager and use the AHRC conciliation pathway if relevant.[1]
Start accessibility testing at the prototype stage to avoid late remediation costs.

Key Takeaways

  • Check contract specifications for WCAG and accessibility acceptance criteria.
  • Keep test reports, user evidence and remediation logs with deliverables.
  • If a complaint occurs, follow the council contract process and AHRC complaint pathways.

Help and Support / Resources

    Categories

    General Governance and Administration Public Safety Public Health and Welfare Land Use and Zoning Housing and Building Standards Transportation Environmental Protection Parks and Public Spaces Business and Consumer Protection Taxation and Finance Labor and Employment Education Civil Rights and Equity Elections and Campaign Finance Events and Special Uses Signs and Advertising Utilities and Infrastructure Technology and Data