Accessibility Quick Wins

Accessibility Does Not Require a Redesign

You can improve website accessibility significantly without a full redesign or months of work. Five targeted fixes — alt text, colour contrast, form labels, descriptive link text, and keyboard navigation — can be implemented in under an hour and deliver immediate benefits for users with disabilities. Each change maps directly to WCAG 2.1 Level AA success criteria.

1. Add Meaningful Alt Text (10 minutes)

What to do: Review the most visible images on your site or app and add concise, descriptive alt text. Focus on what the image communicates, not just what it depicts.

Why it matters: Screen reader users rely on alt text to understand non-text content. A phrase like "Customer using our mobile app at checkout" is more helpful than "image123.png."

Tip: Avoid starting with "image of" or "picture of." Screen readers already identify images. For decorative images, use empty alt="" to skip them entirely.

2. Fix Colour Contrast (15 minutes)

What to do: Run a quick audit with the WebAIM Contrast Checker or similar tool. Check your most-used text and background combinations. Aim for at least 4.5:1 contrast for normal text and 3:1 for large text.

Why it matters: Low-contrast text is one of the most common accessibility issues. It affects people with low vision and also anyone using a screen in bright conditions.

Tip: Small colour adjustments often resolve issues. A slightly darker text or lighter background can make a huge difference.

3. Label Form Fields Properly (10 minutes)

What to do: Make sure every form field has a visible label that persists, even when the user begins typing. Connect labels to inputs using the for attribute so assistive technologies can correctly associate them.

Why it matters: Labels give essential context for screen reader users and help reduce errors for everyone. Placeholder text disappears as soon as users type, which can cause confusion.

Tip: Placeholder text is not a substitute for a label. Always have a visible, persistent label.

4. Make Links Descriptive (10 minutes)

What to do: Replace vague link text such as "Click here" or "Read more" with clear, descriptive wording. For example, use "View pricing plans" instead of "Learn more."

Why it matters: Screen reader users often navigate by scanning links. Non-descriptive text provides no context, making it harder to understand where a link leads.

Tip: Front-load key words. "Pricing page" is better than "Page about pricing." If repeated links are unavoidable, add visually hidden text for clarity.

5. Check Keyboard Navigation (15 minutes)

What to do: Test your site or app using only the keyboard. Tab through your entire page. Can you reach everything? Is focus visible? Can you activate all controls?

Why it matters: Many people use keyboards or assistive devices that emulate keyboard input. If the interface is not keyboard-accessible, those users may be completely blocked.

Tip: Ensure focus indicators (the outlines that show which element is selected) are clearly visible. Avoid removing them in CSS.

Bonus: Try a Screen Reader (5-10 minutes)

Spend a few minutes navigating a page with a screen reader. NVDA is free for Windows. VoiceOver is built into Mac and iOS. This exercise provides valuable insight into how content is announced and where users might encounter barriers.

VPAT Connection

The Real Value

Improving accessibility does not always require sweeping changes. By dedicating an hour to the areas above, you make visual content understandable to screen reader users, improve readability through better contrast, simplify form completion with proper labels, provide clarity with meaningful links, and ensure navigation works for people who do not use a mouse.

Each of these adjustments strengthens inclusivity while also reducing friction for all users. Small steps, taken consistently, create lasting improvements.