Sitesy provides conversion rate optimisation, making website accessibility relevant to the technical path from a visitor's intent to a completed enquiry. For developers, accessible interaction belongs in acceptance criteria, not in a list of visual adjustments after launch.
Use native semantics before custom behaviour
Use buttons for actions and links for navigation. A clickable div does not automatically provide keyboard behaviour or an accessible role. Keep headings in a logical hierarchy so screen-reader users can navigate service information without hearing the entire page before finding the enquiry section.
Give inputs persistent, visible labels and associate them programmatically; for standard labelled inputs, the label's for attribute should match the input's id. Placeholders are not substitutes. Group related options with fieldset and legend so the question remains clear when focus moves between choices.
Manage focus throughout the interaction
Follow the document's logical order instead of using positive tabindex values to patch a confusing layout. Keep the focus indicator visible. Test links with Enter and buttons with Enter and Space, checking that every interactive element can be reached and operated without a mouse.
For a modal enquiry form, move focus inside, contain its tab sequence while open and return focus to the trigger on close. Provide a working Escape key and an accessible close button. Sticky banners must not obscure focused controls, especially when visitors enlarge the page.
Make validation recoverable and perceivable
Identify invalid fields in text, not colour alone. Associate error messages with the relevant inputs, for example through aria-describedby, and provide a navigable error summary for longer forms. Preserve entered values after failure rather than forcing visitors to rebuild the whole enquiry.
Announce asynchronous submission results through an appropriate status region when focus stays on the form. Do not silently replace the submit button or rely on a brief toast. Keep confirmation text available and tell users whether their enquiry was sent or whether another action is needed.
Test complete tasks before release
Combine automated checks with keyboard and screen-reader testing, plus feedback from disabled users. Check text enlargement and narrow-screen reflow. Include cookie controls, verification challenges and embedded booking tools: components from another supplier still belong to the visitor's journey.
Use WCAG 2.2 Level AA as a testing reference, not an automated pass certificate. Record reproducible defects and retest the route through to confirmation after fixes. For a conversion rate optimisation discussion with Sitesy, bring these findings alongside submission and lead-quality data.
Explore this topic across our social channels
See the Sitesy discussion and related posts:
Top comments (0)