Accessibility widgets and overlays: will one make your website accessible?

Ask what the product actually changes

An accessibility widget may offer controls such as display adjustments or other assistance. The buying question is which barriers it removes for real users, which remain in the underlying website and what evidence supports the vendor's claims. Do not treat installing a script or displaying a badge as proof that forms, navigation, documents and interactive components are accessible. W3C guidance says automated tools cannot check every accessibility aspect and human judgement is required.

Keep readingRun a practical first check yourself

Use current Australian guidance as the context

The Australian Human Rights Commission published updated digital-accessibility guidelines in 2025, replacing its 2014 web advisory note. The guidelines discuss equal access to digital goods and services and relevant standards; they are not themselves legally binding. The Commission also recommends including accessibility requirements and verifiable evidence in procurement. Buying a third-party product does not remove the need to consider the accessibility of the service customers actually receive. Ask which requirements, pages and user journeys the proposal covers rather than accepting a generic claim about the whole website.

Test the customer task, including the difficult parts

Choose a representative route: find the service, understand it, complete an enquiry, correct an error and receive confirmation. Include any booking tool, uploaded document, embedded form or payment step within the agreed scope.

This is a starting task checklist, not a complete WCAG audit. Combine suitable automated testing with knowledgeable manual evaluation and, where appropriate, testing with people with disability.

• Keyboard: can a user reach and operate the required controls with a clear focus state?
• Screen reader: do headings, labels, errors and status messages communicate useful meaning?
• Zoom and layout: does content remain usable at relevant magnification and small-screen sizes?
• Visual information: are meaning and instructions available without relying only on colour or an image?
• Third-party components: who will fix barriers the website supplier does not control?

Require a remediation plan with owners

Ask the provider to identify the actual barriers, the standard and version being assessed, the proposed fix, the responsible party and the retest evidence. Separate source-level improvements from optional assistance features. For a form, a proper fix may involve its labels, error handling, keyboard behaviour and confirmation messaging. Adding a floating accessibility button does not demonstrate that those particular problems have been resolved. Ask to see the same task retested after the work.

Understand the limits of a compliance promise

A useful historical example comes from the United States: in January 2025, the FTC announced a proposed settlement over accessiBe's claims about its AI-powered accessibility product, including a proposed $1 million payment. This is a US enforcement example, not an Australian legal rule or a finding that every widget has the same behaviour. The practical lesson is to request evidence for the exact claim. A vendor should be able to explain what was tested, what was excluded, what remains unresolved and how ongoing changes will be checked.

Keep readingPut accessibility in the brief

Put continuing accessibility into maintenance

New pages, documents, plugins and form updates can introduce new barriers. Agree how staff will create accessible content, how complaints reach the responsible team and how important journeys will be retested. The purchase decision should leave the business with measurable improvements and a maintained process. A one-off score or badge is less useful than evidence that customers can complete the task.