Web accessibility gets treated as either a legal compliance checkbox or an issue that only matters for a small share of visitors, and both framings undersell what's actually at stake. WCAG, the internationally recognised accessibility standard, covers a wide range of needs, and a meaningful share of any site's visitors benefit from at least some of its recommendations, whether or not they'd describe themselves as having a disability.
Colour contrast: the easiest fix with the broadest benefit
Text that doesn't have enough contrast against its background is difficult to read for people with low vision, and genuinely harder to read for everyone in bright sunlight or on a lower-quality screen. WCAG's minimum contrast ratio, 4.5 to 1 for normal text, is checkable with free tools in seconds and is one of the most common accessibility failures on business websites, usually introduced by a design choice that prioritised aesthetic subtlety over legibility.
Alt text on images: not just for accessibility
Descriptive alt text lets a screen reader convey what an image shows to someone who can't see it, and it's also read by search engines trying to understand page content. A product photo with alt text reading "IMG_4021.jpg" or left entirely blank serves neither purpose. Writing a genuine, brief description of what the image actually shows takes seconds and serves both accessibility and SEO simultaneously.
Keyboard navigation: can the site be used without a mouse at all
Some visitors, whether due to a motor impairment or simply a preference, navigate entirely by keyboard, tabbing through links and buttons rather than clicking. A site where focus states aren't visible, or where a dropdown menu genuinely can't be opened without a mouse, locks these visitors out of a meaningful part of the experience. Testing this takes a few minutes: unplug the mouse and try to complete the site's main conversion action using only the Tab and Enter keys.
Heading structure that actually describes the page, not just styles text
Headings should follow a logical order, H1 for the page title, H2 for major sections, H3 for subsections, not skipped around purely for visual sizing preferences. Screen reader users often navigate a page by jumping between headings, and a structure that doesn't reflect the actual content hierarchy makes that navigation genuinely confusing rather than just visually inconsistent.
Form labels and error messages that are actually connected to their fields
A form field without a properly associated label, or an error message that appears without being programmatically linked to the field it refers to, is confusing for a screen reader user in a way that's invisible to a sighted visitor filling in the same form. This is a common gap even on otherwise well-designed sites, since it's easy to get right visually while getting it wrong in the underlying code.
A realistic starting point, not a full audit
These five checks, contrast, alt text, keyboard navigation, heading structure and form labels, cover a meaningful share of common accessibility gaps without requiring a formal audit to start addressing. A full WCAG audit is worth doing eventually, particularly for larger sites or ones in regulated industries, but these fundamentals are worth building into every new page from the start, which is exactly how they're handled in every web design project we run rather than treated as a separate, later phase.
Why treating this as a launch requirement works better than a retrofit
Fixing accessibility issues after a site has already launched, once dozens or hundreds of pages exist, is considerably more work than building these five checks into a template from the start. A single template fix, applied once at the component level, cascades correctly across every page built from it, while retrofitting the same fix page by page after launch multiplies the effort by however many pages exist.