Guides
WCAG fix guides
Step-by-step fixes for some of the most common accessibility issues that automated checks find. Each guide explains what the WCAG 2.2 success criteria ask for, shows the fix (with code examples where they help), and gives steps for WordPress, Shopify, Webflow, Squarespace and Wix.
In the WebAIM Million 2026, 96% of all detected errors fell into six categories (WebAIM). These are errors that WebAIM's WAVE tool detected automatically on the top one million home pages, not all accessibility problems. The six are low-contrast text, missing alt text, missing form labels, empty links, empty buttons and missing document language; the guides below cover all six.
Automated tests find only some accessibility issues; manual testing is still required. Not legal advice.
Colour and contrast
How to fix colour contrast issues
Meet the 4.5:1 and 3:1 contrast minimums for text, controls and focus indicators, and fix them at the theme level.
WCAG 2.2 SC 1.4.3, 1.4.11 (AA)
Images
How to fix missing alt text
Decide what each image needs (a description, the link's destination, or an empty alt) and add it in your CMS.
WCAG 2.2 SC 1.1.1 (A)
Forms
How to fix missing form labels
Give every field a programmatic label, visible wherever possible. Why placeholders don't count, and how to group radio buttons and checkboxes.
WCAG 2.2 SC 1.3.1, 3.3.2, 4.1.2 (A)
Links
How to fix empty links and unclear link text
Name icon links and linked images, and replace vague "read more" text.
WCAG 2.2 SC 2.4.4, 4.1.2 (A)
Page structure
How to fix heading structure
Turn visual headings into real ones and build a logical outline, including what WCAG requires and what is only best practice.
WCAG 2.2 SC 1.3.1 (A), 2.4.6 (AA)
Buttons
How to fix empty buttons and missing button names
Give icon buttons and toggles a name and state, and see which button problems automated checks pass.
WCAG 2.2 SC 4.1.2, 2.5.3 (A)
Language
How to fix a missing or wrong page language
Set a valid lang on every template, choose the right language tag, and mark passages in other languages.
WCAG 2.2 SC 3.1.1 (A), 3.1.2 (AA)
Automated testing
What automated accessibility testing can and can't catch
What checkers like axe-core can and can't detect, what still needs a person, and a manual checklist to fill the gaps.
WCAG 2.2 Level A and AA (overview)
Images
How to add alt text in WordPress
Set alt text in the Media Library and Image block, fix featured images, galleries and logos, and check WooCommerce.
WCAG 2.2 SC 1.1.1 (A)
Images
How to add alt text in Shopify
Set alt text on product and variant photos, bulk-edit with CSV, fix theme, banner and description images, and review AI suggestions.
WCAG 2.2 SC 1.1.1 (A)
By CMS
Issue guides above include steps for WordPress, Shopify, Webflow, Squarespace and Wix.
WordPress, Shopify, Webflow, Squarespace and Wix are trademarks of their respective owners. Glimscope is not affiliated with or endorsed by any of them.
Check your own site
Run a free automated scan of one page to check it for some of these issues.
Automated tests find only some accessibility issues; manual testing is still required. Not legal advice. What our automated checks cover