External website; opens in a new tab.

Websites

Which accessibility checks should happen before a website launch?

Use automated checks and real keyboard, zoom, form and mobile journeys together; a green score alone is not conformance.

Websites

Source review 21 November 2026

Accessibility work is most useful when it follows the tasks people actually need to complete. A visitor should be able to understand a service, navigate, find contact information and finish an enquiry using the controls and assistive technology they rely on. Checking only the homepage or only a machine-generated score misses much of that work.

Start with structure and keyboard use

Move through the page without a mouse. The focus indicator should be visible, the order understandable and every necessary control usable. Open and close menus, expand questions, follow the skip link and return from validation errors. A control that looks like a button but only responds to a mouse is a problem even if the layout looks polished.

Check headings and landmarks as a reading structure. A large bold paragraph is not a heading, and several unrelated top-level titles can make navigation confusing. Links need meaningful text in context. Images that communicate information need appropriate alternatives; decorative artwork should not force someone to listen to irrelevant descriptions.

Test the difficult states

Try an incomplete form, an invalid email, a failure response and a successful confirmation. Errors should explain the correction, be associated with the relevant field and avoid removing a person’s work unnecessarily. A receipt reference should remain readable when text is enlarged or the screen is narrow. Do not rely on colour alone for meaning.

At increased zoom and a narrow viewport, text should reflow without hiding controls or forcing routine reading sideways. Check long email addresses, menus, tables, printable documents and focused fields under sticky headers. A desktop layout scaled into a tiny image is not a mobile experience. Contrast and target spacing matter especially for small or closely placed actions.

Combine evidence rather than claim certainty

Automated tools can identify many structural and contrast issues quickly. They cannot decide whether every alternative description is useful, whether a workflow makes sense or whether all assistive-technology combinations work. Record what pages, states, browsers and manual checks were actually performed and what remains unknown. An empty scanner report is not proof of universal WCAG conformance or a legal certification.

For a small launch, prioritise the main customer tasks, repeated components and high-impact failure states. Correct defects and rerun affected checks. Keep an accessible contact route for difficulties and an owner for ongoing content changes. A site can regress when a new image, document, third-party widget or menu is added even if the first release was carefully tested.

Ask a supplier for the agreed target, test scope, findings and remediation process before accepting a broad “fully accessible” promise. Accessibility is a maintainable delivery responsibility, not a badge added after the build.

Sources and review

Prepared by Yellow Brick Tech. General guidance; the source and test conditions for your own situation still matter.

Next review: 4 May 2027

Related services

How Yellow Brick Tech can help.

Next step

Need to apply this to a real situation?

Ask a question or choose the closest project route. A short conversation can often clarify the next step.