A generated layout is not an accessibility audit
A website builder may offer accessible templates or automated suggestions, but a template does not prove that a particular site works for people with disabilities. The final result depends on content, colour choices, headings, controls, third-party widgets and how the owner changes the template. Accessibility must be checked on the actual pages and tasks that visitors use.
The World Wide Web Consortium’s WCAG guidance provides a framework for accessible web content. Businesses should identify the relevant standard and applicable obligations for their context. Do not advertise a legal compliance status based only on a builder badge or an automated scan; obtain qualified accessibility and legal advice where obligations are significant.
Test common tasks with keyboard and assistive technology
Try navigating menus, buttons, forms and dialogs using only the keyboard. Focus should remain visible and move in a logical order. Check headings for a meaningful outline and confirm that form fields have labels, instructions and clear error messages. Ensure that important information is not communicated by colour alone.
Test at multiple zoom levels and on a narrow screen. Listen to the page using a screen reader or invite people who use assistive technology to test it. Automated tools can flag certain code patterns, but they cannot tell you whether instructions make sense or whether a visitor can successfully complete an important task.
Review images, media and generated text
Write alternative text for informative images that explains their purpose in context; mark purely decorative images so they do not add unnecessary noise. Caption video when spoken information matters. Avoid using an image of text in place of real, selectable text. Check that generated labels describe the correct control and that link text makes sense out of context.
AI-written interface text can produce vague buttons, confusing error messages or instructions that assume visual ability. Ask a person unfamiliar with the design to complete the task and explain what each control will do. Keep text plain and direct, and make sure the page remains understandable when layout or styling changes.
Make accessibility part of ongoing maintenance
An accessible launch can become inaccessible after a new widget, campaign banner or content update. Assign an owner to review changes, keep templates and plugins current, and rerun the key manual tests after substantial edits. Keep a list of known issues and a route for visitors to request an accessible alternative.
If a builder cannot support a required feature, ask the vendor about its roadmap and export options before the site becomes dependent on it. Consider a specialist review for complex interactions or high-impact services. Accessibility is a continuing quality practice, not a one-time certification generated by software.
Practical checklist
- Test core tasks with a keyboard, at zoom and on a mobile viewport.
- Check headings, focus visibility, form labels, instructions and errors.
- Review image alternatives and captions in the context of the page.
- Do not claim compliance based only on an automated scan or template badge.
In short
An AI builder can help create a starting point, but accessibility depends on the finished content, configuration and human testing.
This article is general educational information, not legal, privacy, cybersecurity or financial advice. Confirm requirements for your situation with a qualified professional.