Melbourne Website Accessibility Bylaws - WCAG Guide

Technology and Data Victoria 3 Minutes Read · published February 11, 2026 Flag of Victoria

Melbourne, Victoria organisations operating public-facing websites must consider digital accessibility under federal and local frameworks and follow WCAG best practice. This guide explains how municipal obligations interact with the Disability Discrimination Act and complaint routes, practical steps to assess and fix accessibility gaps, and how to engage City of Melbourne officers and regulators when disputes arise. It is written for council staff, web teams, vendors and community groups seeking clear action steps and official contacts to make sites usable for people with disability.

Legal framework & standards

Australian law treats access to goods and services, including websites, as subject to disability discrimination rules under federal law and administrative guidance. The Australian Human Rights Commission explains how discrimination law applies to digital access and provides complaint pathways and guidance for providers (see guidance)[1]. The primary statutory source is the Disability Discrimination Act 1992 (Cth), which underpins remedies and enforcement processes (legislation)[2]. Local council policies and procurement rules typically require compliance with WCAG 2.1 AA as a practical standard for public websites; check your council contract terms for obligations.

Begin accessibility work with a simple automated audit and a small manual test with assistive technology.

Penalties & Enforcement

Municipal bylaws in Melbourne do not normally specify web-accessibility fines; enforcement and remedies for inaccessible websites are generally pursued under federal discrimination law or by administrative complaint. Monetary fines for web accessibility are not specified on the cited pages; remedies and orders are described through the commission and courts (guidance)[1] and the Act (Disability Discrimination Act)[2].

  • Non-monetary remedies: conciliation agreements, compliance notices, injunctions and court orders to make services accessible.
  • Monetary remedies: damages may be ordered by courts, but specific fine amounts for municipalities regarding websites are not specified on the cited pages.
  • Enforcers: Australian Human Rights Commission and federal courts for discrimination matters; local council officers handle contractual or procurement breaches and local complaints.
  • Inspection and complaint pathways: complaints to AHRC, or report contractual non-compliance to the City of Melbourne compliance/contact office (City contact)[3].
  • Appeal/review: outcomes from conciliation or court decisions can be challenged in higher courts or via judicial review where available; time limits for complaints and proceedings are specified in the Act or commission rules and are not specified on the cited page.
If a user files an accessibility complaint, preserve change logs and remediation records as evidence.

Applications & Forms

There is no single national or City of Melbourne "accessibility remediation" permit form for websites. For discrimination complaints follow the AHRC complaint form and process; for contractual or procurement issues use the City of Melbourne contact or complaints form on the council site (contact page)[3]. Specific fee schedules for complaints or court filings are not specified on the cited pages.

Practical compliance steps

  • Plan: set a project timeline and scope covering WCAG 2.1 AA checkpoints.
  • Audit: run automated tools plus manual keyboard and screen reader testing.
  • Fix: prioritise high-impact issues (forms, navigation, images, labels).
  • Test: re-test after fixes and document results.
  • Maintain: include accessibility in procurement, contracts and release checklists.
Documenting fixes and publishing an accessibility statement improves trust and reduces complaints.

Common violations and typical outcomes

  • Missing alternative text for images — often corrected via prioritized remediation during conciliation.
  • Unlabelled form controls — commonly fixed with code updates and retesting.
  • Poor keyboard focus or inaccessible navigation — may result in orders to remediate within a timeframe.

FAQ

Do Melbourne councils have specific accessibility bylaws for websites?
No specific municipal bylaw imposing website fines is commonly published; accessibility enforcement is usually pursued under federal discrimination law and council procurement rules.
Which standard should my municipal website follow?
WCAG 2.1 AA is widely used by Australian public bodies as the practical standard; check your council procurement documents for any higher or specific requirements.
Where do I lodge a complaint about an inaccessible website?
You can lodge a discrimination complaint with the Australian Human Rights Commission or report contractual non-compliance to the City of Melbourne via its contact/complaints page.

How-To

  1. Run an automated accessibility scan to get an initial list of issues.
  2. Conduct manual tests: keyboard-only navigation and a screen reader walkthrough of core pages.
  3. Prioritise and fix critical barriers: forms, navigation, headings, and images.
  4. Publish an accessibility statement describing compliance level and remediation timeline.
  5. Embed accessibility checks into procurement and release checklists and schedule regular re-tests.

Key Takeaways

  • WCAG 2.1 AA is the practical benchmark for public websites in Melbourne.
  • Use both automated and manual testing and keep remediation records.

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