Fast. Simple. No meetings. No delays.
Home / Blog / USA / Building Accessible Websites: WCAG Basics for US Businesses

Building Accessible Websites: WCAG Basics for US Businesses

The practical building blocks of an accessible website — structure, contrast, keyboard use, forms, media — and how to test them.

Cover graphic for the article: Building Accessible Websites: WCAG Basics for US Businesses

WCAG accessible website development means building pages so people can perceive, operate and understand them, whatever device, ability or assistive technology they use. In practice that comes down to semantic HTML, readable contrast, full keyboard support, properly labelled forms, text alternatives for media, and regular testing with both tools and real people.

Why WCAG accessible website development is a build concern

WCAG, the Web Content Accessibility Guidelines, is published by the W3C and is the most widely referenced technical standard for web accessibility. It is organised around four principles: content should be perceivable, operable, understandable and robust. For the exact wording of the current success criteria, use the W3C's own WCAG documentation rather than summaries from third parties.

Accessibility is cheapest when it is part of how components are built, not a separate audit at the end. A button built as a real button element works with keyboards and screen readers automatically. A button faked from a styled container needs extra code to approximate the same behaviour, and usually still falls short. Whether and how accessibility rules apply to your organisation is a legal question; confirm current requirements with a qualified adviser. This article covers the engineering side.

Semantic structure and headings

Screen reader users navigate by headings, landmarks and lists, so structure is how they find their way. Aim for:

  • One main heading per page, followed by headings in logical order without skipping levels for visual effect.
  • Landmarks such as header, nav, main and footer, so users can jump between regions.
  • Real lists for lists, and real tables, with header cells, for tabular data.
  • Links that make sense out of context. Avoid link text such as click here.
  • A page title that describes the page, and a declared page language.
  • A skip link at the top that lets keyboard users bypass repeated navigation.

Choose elements for their meaning, then style them. Styling is a separate decision.

Colour, contrast and text size

WCAG sets minimum contrast ratios between text and its background, with a lower requirement for large text. Check them with a contrast tool during design, not after build, and test your actual brand colours. Remember:

  • Do not use colour as the only way to convey meaning. Add text, icons or patterns for errors, status and required fields.
  • Check contrast for hover, focus, disabled and placeholder states, not only the default look.
  • Let users resize text and zoom the page without losing content or functionality. Use relative units and flexible layouts.
  • Avoid placing text over images without a reliable background treatment.

Our article on website accessibility for New York businesses adds a practical starting point for businesses prioritising fixes.

Keyboard and focus

Many people never use a mouse: keyboard-only users, screen reader users and people using switch devices. Everything interactive must work with the keyboard alone. Build in the following:

  1. Logical tab order that follows the visual order.
  2. Visible focus. Never remove the focus outline without providing a clear replacement.
  3. No keyboard traps. Users must be able to leave modals, menus and embedded widgets.
  4. Focus management. When a dialog opens, move focus into it and return focus to the trigger when it closes.
  5. Standard keys. Enter and Space activate buttons, Escape closes dialogs, arrow keys move within menus and tab lists when appropriate.
  6. Adequate target size so controls are easy to hit on touch screens.

Forms, errors and labels

Forms are where inaccessible sites lose customers, particularly at checkout and sign-up. Good practice:

  • Associate every input with a visible label. Placeholder text is not a label.
  • Mark required fields in text, and group related fields, such as address parts or radio buttons, with a fieldset and legend.
  • Show errors next to the field, in text, and explain how to fix them. Move focus to the first error or an error summary after a failed submit.
  • Use appropriate input types and autocomplete attributes so browsers and assistive tools can help.
  • Do not rely on time limits, or allow users to extend them.
  • Keep authentication manageable: allow password managers and avoid puzzles that depend on memory or perception alone.

Images, media and motion

Provide text alternatives that serve the same purpose as the image. Informative images need meaningful alt text; decorative images should have empty alt text so screen readers skip them. For images of text, charts and diagrams, summarise the content nearby. For media:

  • Provide captions for video and transcripts for audio.
  • Do not auto-play audio, and give users controls to pause, stop or hide moving content.
  • Avoid content that flashes rapidly, and respect the reduced-motion preference in the operating system.
  • Make sure custom players are keyboard operable and labelled.

Testing with tools and people

Automated tools catch only some problems, such as missing alt text, low contrast and empty labels. They cannot judge whether alt text is meaningful or whether a flow makes sense. Combine methods:

  • Automated checks in the browser and in your build pipeline, to catch regressions early.
  • Keyboard-only pass. Unplug the mouse and complete your key journeys using Tab, Shift+Tab, Enter, Space and Escape.
  • Screen reader pass on key pages, using at least one common screen reader and browser pairing.
  • Zoom and reflow checks at larger text sizes and on small screens.
  • Testing with disabled users where possible, which reveals problems no checklist will.

Be cautious about overlay plugins that promise instant compliance. They cannot fix poor underlying structure, and they may interfere with assistive technology users already have. Fixing the source code is the durable approach. Build accessibility checks into delivery too, as described in our launch checklist for landing pages.

Putting it together

Pick your most important journey, such as buying, booking or contacting you, and test it by keyboard today. Fix what breaks, then add the checks to your definition of done. Read the W3C's official WCAG guidance for current criteria. If you want help building or auditing a site, see our software development services for US businesses and the contact page.

Frequently asked questions

What is WCAG?

WCAG stands for Web Content Accessibility Guidelines, a technical standard published by the W3C. It sets testable success criteria, grouped under four principles: perceivable, operable, understandable and robust, at several conformance levels. Check the W3C's official documentation for the current version and exact criteria.

How do I test keyboard accessibility?

Put the mouse aside and use Tab, Shift+Tab, Enter, Space, arrow keys and Escape to complete your main journeys. Check that focus is always visible, the order is logical, nothing traps you, dialogs return focus when closed, and every control you can click can also be reached and activated.

Is an overlay plugin enough?

No. Overlays add a layer on top of the page but cannot repair missing labels, broken heading structure, keyboard traps or unclear content. They can also conflict with the assistive technology people already use. Fixing the underlying code and testing with real users is the more reliable route.

Does accessibility make a website more expensive to build?

Built in from the start, accessibility adds modest effort, because it largely means using correct HTML, checking contrast in design and testing as you go. Retrofitting an inaccessible site usually costs more, since structure, components and content may all need rework.

Related articles

Web Development USA

Website Redesign or Rebuild? How to Decide

When a visual refresh is enough and when the underlying platform needs rebuilding: performance, maintainability, SEO and content structure.

5 min read

🚀 Start Now