Plan and Manage For executives, directors, product and project managers
How do I get accessibility on the executive agenda?
Frame accessibility in the language executives already act on: legal exposure under the Disability Discrimination Act, government compliance obligations (DDA, DSP, WCAG 2.2 AA), customer reach (around 1 in 5 Australians have a disability), and operational risk. Pair the framing with a current-state audit and a costed remediation roadmap so the conversation is about a defensible plan, not abstract risk.
What is my organisation’s legal exposure from inaccessible digital services?
In Australia, inaccessible digital services may breach the Disability Discrimination Act 1992 and, for government, the Digital Service Standard. Exposure includes Australian Human Rights Commission complaints, reputational damage, and (for government) investment oversight findings. WCAG 2.2 Level AA is the benchmark referenced by the AHRC and most Australian Government policy.
How do I plan an accessibility budget?
A defensible accessibility budget covers four streams: audit and conformance documentation, remediation effort (developer time and content rework), capability uplift (training and governance), and ongoing validation. Start with an audit so the remediation cost is grounded in real findings rather than guesswork. Most organisations under-fund remediation effort relative to audit cost - plan for 3-5x audit effort in remediation.
I’m a project or product manager new to accessibility - where do I start?
Start by getting a current-state position: an audit against WCAG 2.2 AA. From there, build a prioritised backlog tied to the standard, allocate dedicated remediation capacity in your delivery cadence, add an accessibility acceptance criterion to your definition of done, and run validation testing before each release. Engage an accessibility lead early - accessibility decisions made late are expensive to reverse.
What KPIs measure accessibility programme success?
Useful KPIs include: WCAG 2.2 Level AA conformance percentage, number of open critical or high-severity findings, time-to-remediate by severity, percentage of releases with no accessibility regressions, training coverage by role, and W3C Accessibility Maturity Model band. Pair quantitative measures with qualitative user testing outcomes - a high conformance score does not always mean a usable product.