Digital Accessibility: Why It Matters and Where to Start

About one in five Australians has a disability. Add in temporary impairments, older users with changing abilities, and people in situational limitations (like using a phone in bright sunlight), and you're talking about a significant portion of your audience who may struggle with a poorly built website.

Accessibility isn't a checkbox exercise. It's about building things that work for as many people as possible. We build it into everything we do, and here's how we think about it.

What accessibility actually means in practice

Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with your website. That includes people who are blind or have low vision, deaf or hard of hearing, have motor impairments that affect how they use a mouse or keyboard, or have cognitive disabilities that affect how they process information.

The Web Content Accessibility Guidelines (WCAG) 2.1 provide the framework. Most government and many not-for-profit organisations require Level AA compliance as a minimum. But the guidelines are a floor, not a ceiling. Real accessibility goes beyond ticking boxes.

Where most sites fall short

Images without alt text

Screen readers can't interpret images. Without descriptive alt text, a blind user gets nothing from your carefully chosen hero image or your infographic. Every meaningful image needs a text alternative that conveys the same information.

Poor heading structure

Screen reader users navigate by headings. If your page jumps from H1 to H4, or uses heading tags for styling rather than structure, the page becomes hard to navigate for anyone not looking at it visually.

Low contrast text

Grey text on a white background might look elegant, but for anyone with low vision, it's unreadable. WCAG requires a contrast ratio of at least 4.5:1 for normal text. Test your colour combinations and don't sacrifice readability for aesthetics.

Forms without labels

If your form inputs rely on placeholder text instead of proper labels, screen readers can't identify what each field is for. Every form field needs a visible, programmatically associated label.

Keyboard navigation that doesn't work

Not everyone uses a mouse. Some people navigate entirely by keyboard. If your dropdown menus, modal dialogs, or interactive elements can't be reached and operated with a keyboard, they're inaccessible.

How to start

If your current site hasn't been built with accessibility in mind, the prospect of making it compliant can feel overwhelming. Here's a practical starting point:

• Run an automated audit. Tools like axe or WAVE will catch the obvious issues: missing alt text, low contrast, missing form labels. These won't catch everything, but they'll give you a clear list of quick wins.
• Test with a keyboard. Unplug your mouse and try to navigate your site using only Tab, Enter, and Arrow keys. Can you reach everything? Can you tell where you are on the page? This reveals a lot.
• Test with a screen reader. VoiceOver is built into every Mac. Turn it on and try to use your site. The experience will be eye-opening.
• Fix the high-impact issues first. Heading structure, alt text, form labels, and contrast are usually the biggest wins for the least effort.
• Build accessibility into your process going forward. It's much cheaper to build accessible than to retrofit it.

The legal and ethical case

In Australia, the Disability Discrimination Act 1992 applies to websites. Organisations that provide goods, services, or information to the public are expected to make their digital presence accessible. The legal risk is real, but honestly, the ethical case is stronger. If your website excludes people with disabilities, you're failing part of your audience.

For government and not-for-profit organisations, the case is especially clear. If your mission involves serving the public or advocating for vulnerable people, an inaccessible website undermines that mission.

How we approach it

We build accessibility into our projects from the start. It's part of the design process, part of the code review process, and part of our testing. We've done this across projects for Elder Rights Advocacy, National Legal Aid, and the Older Persons Advocacy Network, where accessibility was a core requirement.

If you're concerned about the accessibility of your current site, or you want to make sure a new build gets it right from the start, we're happy to talk through it.