ACCESSIBILITY & RESPONSIVE UX

A website that works for every visitor, on every device, with every assistive technology

The Disability Discrimination Act makes WCAG 2.1 AA compliance an enforceable obligation for Australian businesses and public-facing services. We audit your site, fix what is non-compliant, and produce documentation you can put in front of a regulator.

WCAG 2.1 AA audits covering DDA compliance requirements · Screen reader tested on NVDA and VoiceOver · Responsive testing across desktop, tablet, and mobile breakpoints · Serving businesses across Sydney, Melbourne, and Brisbane
This is for you if

This service is for Australian organisations that cannot afford a complaint.

Government procurement in Australia, from federal to local council level, increasingly requires suppliers to demonstrate WCAG 2.1 AA compliance. If your site is part of a tender submission or supplier panel application, you need more than a claim of compliance. You need an audit report, a fix log, and a confirmation that the issues have been resolved.

The Australian Human Rights Commission handles complaints under the DDA. If you have received a complaint, a legal letter, or a notice from the ACCC relating to accessibility, the first step is documenting the current state of your site and demonstrating a remediation plan. We produce the audit and fix documentation that your legal team and any regulator will want to see.

You know your conversion rate on mobile is lower than it should be. Checkout flows that break on smaller screens, buttons that are hard to tap, text that overlaps at certain sizes. These are not just UX problems. They are barriers that affect users with motor impairments and low-vision users who zoom in. Fixing them improves conversion and reduces legal exposure at the same time.

What's broken

These are the most common failures we find on Australian business websites.

Images without alt text — invisible to screen reader users

Stock photography, product images, banner graphics, and decorative icons. All need to be handled correctly for screen reader users. Missing or incorrect alt text is the most common single failure we find, and it appears on sites that otherwise look polished and professional.

Colour contrast ratio below 4.5:1 — fails WCAG AA

Brand colour palettes often include light or muted tones that look refined in a design context and fail the 4.5:1 contrast ratio required for WCAG AA. Text on gradient backgrounds, white text on pale buttons, and grey captions on white backgrounds are where this appears most. The fix is a colour value adjustment, not a rebrand.

Form fields not labelled — keyboard and screen reader users cannot fill the form

Placeholder text disappears when a user types. If a field has no visible label and no programmatic label, a screen reader user cannot identify it, and a keyboard user navigating by tab order has no reference. Contact forms, quote request forms, and checkout fields are where this appears most often on Australian business sites.

Mobile layout breaks below 375px or has horizontal scroll

A layout that was designed and tested on an iPhone 14 may break on an older or smaller device. Horizontal scroll, text that does not reflow, and buttons that extend off-screen affect real users and are straightforward to diagnose. They are also the kind of issue that appears in accessibility complaints alongside the more technical ARIA failures.

What we engineer

Seven deliverables. All documented for regulatory and compliance purposes.

WCAG 2.1 AA Audit (Automated + Manual)

We run automated scans with Axe and WAVE, then conduct manual testing on top. Automated tools find 30 to 40 percent of accessibility issues. Manual testing finds the rest: logical focus order, meaningful alt text, form usability with a screen reader, and keyboard trap issues that no automated tool will flag.

Screen Reader Testing

We test with NVDA on Windows and VoiceOver on macOS and iOS, navigating the full site including menus, modals, forms, and dynamic content. We document what is announced, what is skipped, and what produces a confusing or misleading experience.

Keyboard Navigation Audit

We tab through the entire site using only a keyboard. We check that all interactive elements are reachable, focus indicators are visible, modals do not trap keyboard focus, and skip navigation links work. These are the checks a DDA-related complaint investigation will include.

Colour Contrast Report

Every text-background combination is checked against the WCAG AA standard. We provide the exact contrast ratio for each failure, the WCAG criterion it violates, and the corrected colour value that passes.

Alt Text and ARIA Implementation

We audit all images, icons, and non-text content for correct alt text. We implement ARIA roles, labels, and live regions where missing. We fix page landmark structure so screen reader users can navigate efficiently.

Responsive Layout Audit and Fixes

We test at breakpoints from 320px to 1440px, across real and emulated devices. We document layout failures, touch target failures (minimum 44x44px per WCAG 2.5.5), font scaling issues, and viewport meta problems. We implement fixes in your codebase or theme.

Retest and Confirmation Report

After fixes are implemented, we retest every issue in the original audit. The confirmation report provides a pass or fail status for each item. This document is what you submit to a procurement body, provide to your legal team, or file if a complaint is under review.

What changes

Four things that are different after the audit and fix cycle.

Before
After
Before Stock photography, product images, banner graphics, and decorative icons. All need to be handled correctly for screen reader users. Missing or incorrect alt text is the most common single failure we find, and it appears on sites that otherwise look polished and professional.
After Axe and WAVE will return no critical violations. This is the baseline documentation standard for DDA compliance purposes and the starting point for any formal compliance claim.
Before Brand colour palettes often include light or muted tones that look refined in a design context and fail the 4.5:1 contrast ratio required for WCAG AA. Text on gradient backgrounds, white text on pale buttons, and grey captions on white backgrounds are where this appears most. The fix is a colour value adjustment, not a rebrand.
After A user running NVDA or VoiceOver can find your services, read your content, navigate your menus, and complete your contact or checkout forms. We confirm this through screen reader testing before and after.
Before Placeholder text disappears when a user types. If a field has no visible label and no programmatic label, a screen reader user cannot identify it, and a keyboard user navigating by tab order has no reference. Contact forms, quote request forms, and checkout fields are where this appears most often on Australian business sites.
After Horizontal scroll is gone. Tap targets meet the minimum size. Text scales without overflow. The layout behaves correctly at every breakpoint your users are likely to encounter.
Before A layout that was designed and tested on an iPhone 14 may break on an older or smaller device. Horizontal scroll, text that does not reflow, and buttons that extend off-screen affect real users and are straightforward to diagnose. They are also the kind of issue that appears in accessibility complaints alongside the more technical ARIA failures.
After You have an audit report, a fix log, and a retest confirmation. Each document is structured for legal and regulatory use: issues are referenced to WCAG criteria, severity is stated, and resolution is confirmed. If the ACCC or Australian Human Rights Commission asks to see your compliance evidence, you have it.
How it works

Process

  1. 01

    Audit

    Week 1

    Automated scan plus manual testing. Screen reader navigation on NVDA and VoiceOver. Full keyboard navigation pass. Colour contrast check across every text-background combination. Responsive testing from 320px to 1440px. You receive the complete audit report at the end of the week, with every issue categorised as critical, major, or minor, and each one referenced to its WCAG 2.1 AA criterion.

  2. 02

    Fix Plan

    End of Week 1

    We review the audit report with you and agree on scope. We identify which fixes we implement directly and which require input from your team, such as alt text on images managed in your CMS. We give you a clear timeline for the implementation phase.

  3. 03

    Implementation

    Weeks 2 to 3

    We implement fixes in your codebase, CMS templates, or component library. Every change is documented. For complex ARIA or focus management fixes we work directly in your JavaScript components. For responsive layout fixes we work at the CSS and template level.

  4. 04

    Retest and Handover

    Week 3 to 4

    We retest every item from the original audit. The confirmation report records pass or fail for each issue. Items that involve ongoing content management, such as maintaining alt text on new images, are documented with instructions for your team. You receive the final report in a format suitable for compliance, procurement, or legal use.

Common questions

FAQ

Is WCAG 2.1 AA compliance legally required for Australian businesses?

The Disability Discrimination Act 1992 makes it unlawful to discriminate against people with disabilities in the provision of goods and services, and the Australian Human Rights Commission has confirmed that websites are covered. WCAG 2.1 AA is the de facto standard used to assess whether a website meets that obligation. Businesses do not need to self-certify, but if a complaint is made, WCAG compliance is the benchmark applied.

What documentation do we receive for procurement or DDA purposes?

You receive three documents: the original audit report with every issue categorised by severity and WCAG criterion, the implementation log documenting every fix made, and the retest confirmation report showing pass or fail for each original issue. These are formatted for use in procurement submissions, legal responses, and regulatory inquiries.

How quickly can you complete an audit if we have a procurement deadline?

A standard 10 to 20 page informational or business website can be audited within three to five business days. If you have a hard deadline, tell us upfront and we will tell you whether it is achievable. We do not commit to timelines we cannot meet.

Do you test with real screen reader users?

We test using NVDA and VoiceOver operated by our team members who are trained in screen reader navigation. We do not currently include testing with users who are blind or have low vision as a standard deliverable, but we can recommend organisations that provide that service for supplementary testing if required.

Can you fix our accessibility issues without rebuilding the site?

Most accessibility issues can be fixed without rebuilding anything. Alt text, ARIA labels, focus management, and colour contrast are typically code-level fixes in your existing templates or CMS. Responsive layout failures may require CSS changes to your existing stylesheets. A full rebuild is rarely necessary unless the site has fundamental structural problems that make targeted fixes more expensive than a rebuild.

Our team

The people behind the work

Not a black box. Real specialists you can call, with their names on the work.

Niraj Raut

Niraj Raut

Founder — Ecommerce SEO
Keshab Joshi

Keshab Joshi

PPC Expert
Hawrry Bhattarai

Hawrry Bhattarai

Google Ads Expert
Arogya Rijal

Arogya Rijal

SaaS SEO Expert
Start here

Get the audit report your compliance process requires

We audit your site against WCAG 2.1 AA, test it with screen readers and keyboard navigation, and give you a documented report of every failure by severity. The confirmation report you receive after fixes is structured for procurement submissions, DDA compliance, and legal use.