Skip to content
HomeServicesAboutPricingArticlesContactPerformance test

Web Development

Website accessibility: a practical guide

How to improve accessibility on your website. We cover common mistakes, what to fix first, tools for testing and a checklist for WCAG 2.1 AA.

Kevin A. Sommerstein8 min read

Introduction

Since the accessibility law took effect on June 28, 2025, the question has changed: it is no longer about preparing for a deadline, but about making sure your website actually meets the requirements. In this guide, we'll walk through concrete steps to improve accessibility on your website, regardless of the technology you're using.

We cover everything from WordPress optimization to modern alternatives like Next.js, with practical tools and techniques you can start using right away.

Key factsJuly 2026
Legal standard
WCAG 2.1 level AA
In effect since
June 28, 2025
Contrast, body text
at least 4.5:1
Contrast, large text
at least 3:1
Readable at zoom
up to 200%

Prioritize well: start with what delivers the most

Now that the law is in force, it's easy to feel overwhelmed by everything that should be fixed. But not all issues carry the same weight. Start with the failures that affect the most users and that an automated audit (with axe or WAVE, for example) almost always flags first.

  1. Text contrast: insufficient contrast is the most common failure and affects everyone with low vision. Fix any text that falls below 4.5:1.
  2. Alt text: make sure every meaningful image has descriptive alt text, and that purely decorative images are left empty (alt="").
  3. Keyboard navigation: check that everything can be reached and used without a mouse, with a visible focus indicator.
  4. Forms: connect every field to a visible label and provide clear error messages.
  5. Heading structure: one H1 per page and a logical order without skipped levels.

This order gives you the most accessibility per hour of work and quickly gets you past the most common failures. The rest of the guide goes deeper, platform by platform.

WordPress: a good foundation, but not always sufficient

WordPress is the world's most widely used CMS and has made significant strides in accessibility in recent years. With the right theme and plugin choices, you can go quite far.

What WordPress does well by default:

Semantic HTML structure: Modern WordPress themes often follow basic HTML semantics with correct use of headings (h1-h6), lists, and other structural elements.

Keyboard navigation: WordPress core functionality supports keyboard navigation, which is critical for users who cannot use a mouse.

Alt text for images: WordPress has built-in support for alt text, but it's up to the user to actually fill them in.

Customizable HTML: You can control HTML output via templates and hooks, providing flexibility for accessibility improvements.

Concrete steps to improve WordPress accessibility:

1. Choose an accessibility-aware theme

Look for themes that market themselves as "accessibility-ready" or "WCAG-compliant". Popular options include Twenty Twenty-Four and Astra.

2. Install accessibility plugins

  • WP Accessibility: Adds ARIA landmarks, skip links, and other basic improvements
  • One Click Accessibility: Gives users tools to customize the website's appearance
  • Accessibility Checker: Scans your content for common issues

3. Configure proper heading structure

Ensure each page has a logical heading structure (H1 → H2 → H3) without level skipping. Don't use headings just for styling.

4. Optimize color contrast

Check that text color and background color have sufficient contrast (at least 4.5:1 for normal text, 3:1 for large headings).

When WordPress becomes challenging

Challenge 1: visual page builders (Elementor, WPBakery, Divi)

Page builders are popular for their simplicity, but they often create accessibility problems:

Common problems:

  • Sloppy HTML structure with unnecessary div elements
  • Poor or incorrect ARIA attributes
  • Keyboard navigation that doesn't work properly
  • Semantic structure lost in visual design

Solutions:

  • Short-term: Add custom CSS and JavaScript to fix problems
  • Long-term: Migrate content to WordPress Gutenberg editor which has better accessibility support
  • Compromise: Use page builders sparingly and only for less critical sections

Challenge 2: old or custom-built themes

Older themes often lack modern accessibility functionality:

Common deficiencies:

  • Missing ARIA landmarks (navigation, main, complementary)
  • Incorrect or missing skip navigation
  • Poor keyboard focus handling
  • Insufficient color contrast

Solutions:

  • Update the theme: If a newer version is available
  • Manual improvements: Add ARIA attributes and landmarks via functions.php
  • Theme change: Invest in a modern, accessibility-aware theme

Challenge 3: old content that needs updating

Common problems:

  • Images without alt text from previous years
  • PDF documents that aren't accessible
  • Embedded videos without captions
  • Blog posts with poor heading structure

Systematic solution:

  1. Audit existing content: Use tools like Screaming Frog to identify images without alt text
  2. Prioritize: Start with most visited pages and critical content
  3. Bulk editing: Use WordPress bulk editing function to update metadata efficiently
  4. Content guidelines: Create guidelines for future content production

Tools for testing accessibility

Automated tools:

  • axe DevTools: Browser extension that identifies common problems
  • WAVE: Free web-based tool from WebAIM
  • Lighthouse: Built into Chrome Developer Tools

Manual testing:

  • Keyboard navigation: Test navigating the entire website without a mouse
  • Screen readers: Test with free screen readers like NVDA (Windows) or VoiceOver (Mac)
  • Color contrast: Check all text colors against backgrounds

Why WordPress isn't always enough

While WordPress is a good choice for many websites, there are limitations when it comes to accessibility:

Performance issues: WordPress sites often get sluggish as the plugin list grows, and a slow site affects every visitor.

Limited control: You depend on theme and plugin developers' understanding of accessibility.

Technical debt: Older WordPress installations can accumulate technical problems that are difficult to solve.

Growing pains: For larger websites with complex requirements, WordPress often becomes impractical.

Modern alternatives: Next.js and developer-focused solutions

For businesses that want full control over accessibility and performance, modern frameworks like Next.js are a better starting point:

Next.js advantages for accessibility:

Full control: The HTML structure and semantics are decided in the code, not by a theme or a page builder.

Built-in support: Next.js supports accessibility features and optimizations from the start.

Better performance: Server-side rendering and automatic optimization provide faster loading times.

Future-proof: Built to modern web standards.

Capacity: Handles everything from small business websites to large e-commerce platforms.

When Next.js is the best choice:

  • E-commerce platforms that need fast performance and complex functionality
  • Business websites with high security and performance requirements
  • Web applications requiring advanced interactivity
  • Websites where accessibility and SEO directly affect the business

How we help businesses with accessibility

As a web development agency specializing in Next.js and modern web solutions, we help businesses in several ways:

For existing WordPress websites:

  • Accessibility audits: Thorough review of current accessibility status
  • Optimization: Improvements without needing to change platforms
  • Migration consulting: Evaluation of whether and when a move to more modern technology is justified

For new projects or major rebuilds:

  • Next.js development: Building fast, accessible websites from the ground up
  • Accessibility from the start: WCAG 2.1 AA built into the whole development process
  • Performance optimization: Ensuring fast loading times for all users
  • Future-proofing: Technical solutions that grow with your business

Why we chose Next.js as our primary platform:

Quality over quantity: Instead of being generalists across every CMS, we do one thing properly, with modern technology.

Best possible accessibility: With Next.js we build accessibility into the code and can meet the WCAG requirements with margin to spare.

Long-term sustainability: Websites built with Next.js are better equipped for future accessibility requirements and technical development.

A measurable approach: with full control over the code, we can work systematically on both loading times and accessibility scores in tools like Lighthouse, instead of being limited by what a theme and its plugins allow.

Next steps for your business

If you have an existing WordPress website:

  1. Start with a basic accessibility audit
  2. Implement the most critical improvements
  3. Evaluate whether your current solution is sustainable long-term

If you're planning a new website or major rebuild:

  1. Consider modern alternatives like Next.js for best results
  2. Plan for accessibility from project start
  3. Invest in solutions that grow with your business

Regardless of situation:

The law already applies, and improvements take time to implement and test properly. The earlier you start, the smaller the risk of sitting on known failures.

Contact us for expert help

We help businesses with accessibility, whether you need to improve an existing WordPress website or build something entirely new with Next.js.

Want to understand which requirements apply and who the law covers before you work through the checklist in this guide?

The accessibility law: the requirements that apply in 2026 and how to meet them

Contact us for a free consultation where we'll discuss your specific situation and recommend the best path forward.

Read more about how we build websites at Developly

Accessibility is more than a legal requirement. A website more people can use brings more customers, happier visitors and better SEO.

Quick checklist: is your website accessible?

Basic structure:

  • Does each page have a clear H1 heading?
  • Does the heading structure follow logical order (H1 → H2 → H3)?
  • Are all images provided with descriptive alt text?

Navigation and interaction:

  • Can you navigate using only the keyboard?
  • Is there a "skip to main content" link?
  • Are all form fields clearly labeled?

Visual design:

  • Do text and background have sufficient color contrast?
  • Is information understandable even without colors?
  • Does the page work at 200% zoom?

Test yourself:

  • Have you tried navigating without a mouse?
  • Have you tested with a screen reader (e.g., free NVDA)?
  • Do all functions work with JavaScript disabled?

Frequently asked questions

Yes. The accessibility law has applied since June 28, 2025 and covers digital services aimed at consumers. The requirements follow WCAG 2.1 level AA.

Insufficient color contrast. Body text needs a contrast ratio of at least 4.5:1 against its background. It is easy to measure and often quick to fix.

WordPress can be made accessible with the right theme and plugins, but page builders and older themes often cause problems. With Next.js you have full control over the code and can build accessibility in from the ground up.

Start with automated tools like axe DevTools, WAVE or Lighthouse. Then add manual testing: navigate using only the keyboard and listen through the page with a screen reader such as NVDA or VoiceOver.

The supervisory authority can request corrections and order remediation. Just as important, inaccessible pages lock out customers and harm both your brand and your SEO.

Kevin A. Sommerstein

About the author

Kevin A. Sommerstein · Software Engineer

I have built websites and web apps for about ten years, mainly with Next.js, React and Node.js. At Developly I'm responsible for development and the technical decisions. You deal with me directly from the first call to launch.