ujans
Blog
Web and software

What is web accessibility and how do you achieve it? A practical WCAG checklist

Accessibility is a better experience for everyone, not only users with disabilities, and it overlaps with SEO and conversion. Here is a starter checklist.

ujans team··4 min read

Web accessibility means your site can also be used by people with visual, hearing, motor or cognitive differences. Its benefit is not limited to that: someone using a phone in bright sun, someone navigating with one hand, someone on a slow connection or an older user also benefits from accessible design. Accessibility overlaps heavily with usability, SEO and conversion.

What is WCAG?

WCAG (Web Content Accessibility Guidelines) are the internationally accepted guidelines for accessibility. They rest on four principles:

  1. Perceivable: Information must be presented in ways users can perceive (text alternatives, sufficient contrast, captions).
  2. Operable: All functions must be usable in different ways including the keyboard.
  3. Understandable: Content and interface must be consistent and clear.
  4. Robust: Content must work with different browsers and assistive technologies such as screen readers.

Conformance levels are graded A, AA and AAA; for most businesses the target is AA. Legal obligations vary by country and sector; determine the scope you need with your legal adviser and the relevant regulation.

Starter checklist

1. Colour contrast

There must be enough contrast between text and background. As a general rule, a ratio of at least 4.5:1 is targeted for normal text. Light grey text on white is a common mistake. Do not convey information by colour alone (for example, use an asterisk and text instead of "red fields are required").

2. Alternative text

Add short, descriptive alternative text (alt) to meaningful images. Mark decorative images with empty alt so screen readers skip them. For charts and infographics, also give the main message as text.

3. Keyboard access

All links, buttons and forms must be reachable with the keyboard alone (Tab, Shift+Tab, Enter, Space, Esc). The focus indicator must be visible; do not remove it. Menus, dialogs and the mobile menu must open and close by keyboard with correct focus management.

4. Meaningful HTML structure

  • Use one main heading (H1) and a logical hierarchy (H2, H3); do not choose headings just for large type.
  • Use the right HTML elements for lists, tables, buttons and links; do not fake a button with a div.
  • Mark page regions (header, navigation, main content, footer) with meaningful landmarks.
  • Declare the page language correctly; on a multilingual site each page's language must be marked.

5. Forms

Each field needs a visible, programmatically associated label; a placeholder alone is not enough. Error messages must be clear, say what to do in which field and not rely on colour. Mark required fields and support autofill. For contact and quote forms you can align with the principles in the conversion-focused landing page guide.

6. Link and button text

Instead of "click here" or "read more", use text that describes the destination ("Request a quote", "See the cyber security service"). This helps both screen reader users and search engines.

7. Media

Add captions to videos and transcripts to audio. Avoid auto-playing moving content that cannot be stopped.

8. Text size and layout

The page must stay usable when text is enlarged and the screen zoomed. Avoid fragile layouts tied to fixed pixel sizes. On mobile, touch targets must be large enough and spaced.

9. Time limits and motion

If a session will expire, warn the user and allow extension. Limit sliding, blinking or fast-moving elements.

10. Error and status messages

Notifications (successful submission, errors) should be marked up so they are announced to screen readers.

How to test

  1. Automated tools: Browser-based accessibility checkers find many issues quickly, but catch only part of them.
  2. Keyboard test: Go through the site from start to end without a mouse.
  3. Screen reader test: If possible, try the main flows (navigation, form submission) with a screen reader.
  4. Zoom and mobile test: Check at 200 percent zoom and on a small screen.
  5. Real users: If possible, test with users with different needs.

Accessibility, SEO and speed

Meaningful headings, alternative text, clear link text and clean HTML also help search engines understand the page; see the SEO guide for small businesses. Fast, simple pages improve both accessibility and experience; see speeding up your website. To catch general gaps before launch use the new website checklist, and for regular care after launch website maintenance.

New project or existing site?

On a new site, including accessibility from the design stage is much cheaper than fixing it later. Technology choice matters here too; see WordPress or custom development?. On an existing site, improve gradually, starting with the most visited and most critical pages (home, contact, quote form, checkout). For project scope and budget, how to manage a software project and website cost guide you.

Common mistakes

  • Stylish low-contrast colours that are hard to read,
  • Removing the focus outline for aesthetic reasons,
  • Not adding alt text, or entering meaningless text such as "image1.jpg",
  • Using placeholder in place of a label,
  • Dropdown menus that work only with the mouse,
  • Treating accessibility as a one-time audit.

Conclusion

Accessibility is not a feature but part of quality web development. Start with small, regular steps: contrast, alternative text, keyboard access, form labels. You reach more people and raise the overall quality of your site.

ujans builds corporate websites that think about accessibility, speed and SEO from the start, and improves accessibility on existing sites.

Looking for help with this?

Tell us what you need and our team will get back to you within one business day.

Get a quote