WCAG – what is required for an accessible website?

An accessible website makes it easier for more people to use your digital services. Here we explain the basics of WCAG and what is important to get right from the start.

Accessibility is about both usability and responsibility

WCAG is a set of guidelines for making digital services more accessible to people with different needs and abilities. This includes making content perceivable, understandable and usable, whether the user navigates with a keyboard, screen reader or other assistive technologies.

Common issues include low contrast, unclear forms, missing alt text, incorrect heading structure and functions that cannot be used without a mouse. Many of these problems affect not only accessibility, but also the overall user experience for all visitors.

Working with accessibility early in a project saves both time and money. It reduces the need for late fixes and creates a more sustainable website that works better for more people.

WCAG 2025, SEO and web development – how it all connects

As of 28 June 2025, the requirements under the European Accessibility Act (EAA) were strengthened. This means that most websites, e-commerce solutions and digital services need to comply with WCAG 2.1 level AA.

Alt texts. Help both screen readers and search engines understand content.

Heading structure (H1–H3). Makes navigation easier for users and improves indexing.

Semantic structure in the code. The code behind the website should be structured in a way that helps search engines and different types of assistive technologies for visitors with disabilities, for example screen readers.

Procurement of web development

If accessibility is not specified from the start, it becomes more expensive, more difficult and sometimes legally risky.

Requirements specification. WCAG 2.1 AA should be a clear requirement.

Accessibility analyses. Should be carried out before delivery.

Training. Editors should learn how to structure content, layout and graphic elements so they do not negatively affect accessibility.

Web development and long-term maintenance

Tillgänglighetsarbetet är inget som slutar efter lansering.

Testing tools. Use tools such as AXE or Siteimprove to monitor accessibility over time.

Future-proofing. Build with the future in mind, for example WCAG 2.2 and upcoming standards.

When you integrate accessibility into web development, SEO and procurement, you do not just meet legal requirements, you build a website that works better for everyone.

Accessible web basics

Ensure sufficient colour contrast between text and background
Use clear headings in a logical structure
Write alt text for meaningful images
Make sure the entire website can be used with a keyboard
Label form fields and error messages clearly
Avoid links and buttons with unclear purpose
Test content with screen readers and other assistive technologies

Learn more about how we work with WCAG, audits and advisory services to make digital services more inclusive and usable.

Learn more about our accessibility services

Need support with accessibility?

We help organisations and companies understand requirements, prioritise the right actions and build more accessible websites.