Building A Practical Accessibility Audit For A Small Business Website
A site accessibility audit examines whether a website can be used by people with disability across different devices, browsers and communication preferences. For a small business, the process should cover more than colour contrast or technical compliance. It should reveal where customers may be blocked from finding information, completing a form, making a booking or contacting staff.
Australian businesses need to consider the Disability Discrimination Act 1992, which applies to many goods and services offered online. The Web Content Accessibility Guidelines provide a useful technical benchmark, but a meaningful review also considers local audiences, including people who use Auslan, screen readers, captions, keyboard navigation, magnification or voice input.
A practical audit does not need an enterprise budget. A clear scope, a combination of automated checks and human testing, and a prioritised remediation report can give a small organisation a realistic path forward. The most valuable findings connect an accessibility barrier with a customer task and a specific repair.
Define The Website’s Scope And Users
Begin by recording what the audit covers. Include the public website, mobile layouts, landing pages, blog posts, booking tools, shop or payment pages, downloadable documents, embedded video, maps, chat widgets and third-party forms. A small business site may look simple while relying on several external services that create separate barriers.
Identify the most important user journeys before testing. These could include finding opening hours, comparing services, requesting a quote, registering for an event, paying an invoice or locating an emergency contact. Test each journey from the home page through to completion, because an accessible page is of limited value if the final form or confirmation message cannot be used.
User profiles should reflect the local market. A Melbourne theatre consultant may reach people on mobile devices while commuting, a regional Queensland business may serve customers with slower connections, and a Sydney practice may receive enquiries from a culturally and linguistically diverse audience. Include Deaf and hard-of-hearing users, people with vision, motor, cognitive or learning disabilities, and customers using older hardware.
Check Structure, Navigation And Keyboard Access
Review the page hierarchy, headings, landmarks, link text and navigation labels. Each page should have a logical heading order, a meaningful title and a clear main content area. Links such as “read more” should identify their destination, while repeated menus should work consistently across the site.
Keyboard testing is essential because many users cannot operate a mouse. A reviewer should move through menus, forms, pop-ups, carousels and media controls using the Tab, Shift-Tab, Enter and arrow keys. The focus indicator must remain visible, appear in a sensible order and never become trapped inside a component. A visitor should be able to dismiss a dialogue and return to the point where it opened.
Check whether touch targets are large enough and whether mobile controls have adequate spacing. Australian customers often browse on phones during travel between Sydney, Brisbane and other major centres, so a desktop-only review can miss serious problems. Orientation changes, zoom to 200 percent, text spacing and reflow should also be tested without hiding content or creating horizontal scrolling.
Review Text, Images, Audio And Video
Content accessibility depends on clear language as well as markup. Check that instructions are concise, headings describe the content below them, error messages explain how to fix a problem, and important information is not conveyed through colour alone. Avoid unexplained abbreviations and ensure promotional copy remains understandable when enlarged or read aloud.
Every meaningful image needs useful alternative text, while decorative images should be ignored by assistive technology. Complex diagrams may require a nearby text explanation. Infographics containing pricing, dates or service conditions should never be the sole source of essential information.
Video should include accurate captions, speaker identification where needed and a transcript for people who cannot hear the soundtrack. Audio information requires a text alternative, and autoplay should be avoided. Where a business communicates with Deaf customers, consider whether written English alone is sufficient for the purpose. A signed explanation may be appropriate for key public information, particularly when discussing rights, safety, health or complex procedures. Professional development for interpreters can also involve specialist settings, as shown in this discussion of theatre interpreting mentorship.
Test Forms, Transactions And Communication
Forms deserve their own audit because they often determine whether a visitor becomes a customer. Every field should have a persistent label, clear instructions, suitable autocomplete attributes and an accessible error message. Required fields need to be identified in text, and errors should be announced to screen readers and associated with the relevant controls.
Check date pickers, address fields, phone number validation and file uploads. A customer should be able to complete the process without relying on a visual calendar, remembering a complex format or dragging a slider. Where an appointment system is embedded from a third party, test the full interaction rather than assuming the provider has solved accessibility.
Review confirmation pages, emails and alternative contact channels. A small business should provide a practical way to request assistance without implying that disabled customers must disclose personal information or accept a slower service. Legal, medical and education-related websites need particular care with privacy, consent and plain-language explanations. For organisations handling formal proceedings, legal interpreting support can inform a broader review of communication access and customer pathways.
Payment flows should work with keyboard navigation, screen magnification and assistive technology. Captcha mechanisms need an accessible alternative, and time limits should be extendable or avoidable where possible. Test failed payments and session timeouts as carefully as successful transactions, since a confusing recovery process can exclude someone at the final step.
Combine Tools, Human Testing And Remediation
Automated tools can quickly identify missing alternative text, duplicate IDs, contrast failures, invalid attributes and some form-label issues. Use more than one checker, but treat the results as evidence rather than a final verdict. Automated testing cannot reliably assess whether alt text is meaningful, whether a heading makes sense, or whether a keyboard user can understand a complex widget.
Manual review should cover current versions of common browsers, a mobile device and at least one screen reader. Test zoom, text resizing, reduced motion and high-contrast settings where available. Ask disabled users or accessibility specialists to complete realistic tasks. Deaf reviewers can assess captions, written instructions, video presentation and the suitability of any signed content. Community organisations, including a St Maarten Deaf organisation, demonstrate why local Deaf perspectives should be treated as expertise rather than an optional final check.
The audit report should separate critical blockers from lower-priority improvements. For each finding, record the affected page or component, the user impact, the relevant WCAG success criterion, evidence such as a screenshot or test step, and a recommended fix. A useful priority system might classify an inaccessible enquiry form as urgent, inconsistent heading structure as high, and a minor decorative contrast issue as medium.
Finish with an action register that names an owner, estimated effort and target date. Re-test every repaired issue, then schedule a smaller review after major redesigns, new content, marketing campaigns or changes to booking and payment systems. Accessibility is easier to maintain when content writers, designers, developers and customer-service staff share responsibility for the experience.