HANDMADE DESIGN

HANDMADE DESIGN / WEB DEVELOPMENT GUIDE

Website Accessibility Checklist: A Practical WCAG 2.2 Starting Point

An accessible website helps more people complete the tasks it was built for: reading a service description, comparing products, contacting a business or buying something. Accessibility should be part of design and implementation—not an automated score added after launch.

This checklist draws on WCAG 2.2 and practical front-end testing. It is a starting point rather than a claim that checking these items guarantees full legal or standards conformance.

Content structure

Use descriptive page titles. A browser tab should identify the page and business. “Services | Brand” is more informative than “Home” on every page.

Create a logical heading hierarchy. The main heading should identify the page’s subject. Subheadings should describe content sections; do not use heading elements only to make text bigger.

Use meaningful link text. “Read our Shopify migration process” communicates more than a screen full of “Click here” links.

Write plainly. Break up dense instructions, explain technical terms and identify what customers should do next. Accessibility includes cognitive usability, not just screen readers.

Keyboard and navigation

Try completing the page without a mouse. Use Tab, Shift+Tab, Enter, Space and Escape where appropriate. Can you open menus, close dialogs, move through forms and submit them?

Keep focus visible. Removing the browser focus outline without providing a clear replacement makes navigation harder.

Use semantic controls. Buttons should trigger actions; links should navigate. Do not make a generic container clickable and forget keyboard behavior.

Check the reading order. When visual columns change on mobile, the keyboard and screen-reader order should still make sense.

Add a skip link. A visible-on-focus “Skip to content” link helps keyboard users bypass repeated navigation.

Images, media and color

Write alternative text for meaningful images. Describe the useful information or function. Decorative imagery can use empty alt text if it adds no information.

Do not rely on color alone. An error should not be conveyed by a red border only; add a clear message explaining the problem.

Review text contrast. Light gray text on white may look minimalist but can become unreadable. Measure contrast against the applicable WCAG criterion instead of guessing from appearance.

Provide captions and transcripts when appropriate. If a video explains an important process, do not make the spoken content available only to people who can hear it.

Respect reduced motion. Nonessential animations should not prevent reading or form submission, and motion settings should be considered in the design.

Forms and feedback

Label every input. A placeholder is not a substitute for a persistent label. Use descriptive labels that remain visible when users begin typing.

Explain errors in plain language. Instead of “Invalid value”, say what needs to change, for example “Enter an email address such as [email protected].”

Do not lose user input unnecessarily. If submission fails, preserve entered values where safe and help the person recover.

Make success confirmation clear. After sending an enquiry, display a message that explains whether it was received and what happens next.

Mobile, zoom and touch

Test at increased zoom. Content should reflow without hiding controls. Fixed-width sections can become a serious barrier when text is enlarged.

Make interactive targets practical to tap. Avoid tiny or tightly packed controls.

Check screen orientation changes. Important content should remain available when a user rotates a device or uses a larger display setting.

Automated testing is only the first pass

Tools such as accessibility checkers can help find missing labels, contrast issues and certain structural defects. They cannot reliably judge whether your navigation is understandable, whether alt text conveys the right meaning or whether a person can complete a complex task.

A practical audit includes at least one manual keyboard pass, zoom and reflow testing, and a screen-reader walkthrough of the most important journey. For transactional sites, test the complete checkout or booking flow.

Prioritize fixes by impact

Start with blockers: inaccessible checkout, unusable navigation, broken forms and missing essential information. Then address widespread patterns in shared components, such as navigation menus, cards and modals. Finally improve isolated content issues and visual refinements.

Document each issue with a reproducible step, expected result, actual result and page URL. This makes remediation much faster than a vague report saying “accessibility needs improvement.”

Quick team checklist

For a broader explanation, see Modern Web Standards. If your business needs help improving accessibility as part of a website rebuild, discuss the project with Handmade Design.

Sources