author
Rogier Venema
Developer

Three situations we encounter every week.

Why digital accessibility?

  • You’re not sure if you meet the requirements

    Since June 2025, European requirements have been tightened, and the question is no longer whether you’re working on it, but whether you can prove it. Without testing against WCAG 2.2, that’s just an assumption.

  • Some of your visitors get stuck

    People who use a keyboard, a screen reader, or a magnifier get stuck in places you’ll never encounter. These are visitors who don’t complain—they just click away.

  • Accessibility is always an afterthought

    Fixing things after the fact is more expensive than building them right from the start. If accessibility is built into your components, every new page will be accessible right away, and you won’t have to keep fixing it every quarter.

Digital accessibility as a starting point

A site that only works for someone with a mouse, good eyesight, and a fast connection won’t work for some of your visitors. Digital accessibility is about that portion: usable with a keyboard, readable with a screen reader, and understandable without relying solely on color as a cue. It’s not an extra layer on top of your design—it’s embedded in the choices you make during development.

We test against WCAG 2.2 manually and with tools. Automated scans catch about half of the issues: contrast, missing labels, structural errors. You can only find the other half by walking through the flow yourself using a keyboard and a screen reader—and, where possible, with people who do this every day. We fix what we find at the component level rather than on a per-page basis, so the issues don’t recur.

You’ll be working with Ruben, who is responsible for accessibility at Redkiwi. He prioritizes the findings by impact and compiles the status for each guideline into an overview that you can access yourself. The same applies to security: Redkiwi is ISO 27001-certified and operates in compliance with the GDPR, so data and privacy are demonstrably managed—not just promised.

  • 22+ year experience
  • 9,3 customer satisfaction
  • 55+ Kiwi specialists

What does a WCAG assessment entail?

Four layers. The audit: your site is assessed against WCAG 2.2 Levels A and AA, per guideline and per page, with findings and specific locations noted. The manual portion: walking through the most important user flows using only a keyboard and a screen reader, because that’s where the issues lie that a scan can’t detect. The remediation: adjustments to code, design, and content, implemented across all components so that new pages are immediately compliant. And the assurance: incorporate an audit at delivery into your process, so you don’t have to start from scratch every year.

From Audit to an Accessibility Statement

A report with findings is not yet an improvement—and certainly not proof. That’s why we end up with two things: a site where the fixes have been implemented, and an accessibility statement that matches what’s actually on the site. If you want to make your website accessible and be able to demonstrate it, that statement is the final piece of the puzzle: what has been tested, what complies, what doesn’t yet, and when it will. Being honest about the remaining issues is more effective than a claim that falls apart at the first audit. We’ll determine the scope of the European Accessibility Act for your organization together, as it varies by sector and type of service.

Three elements that underpin accessibility.

What Accessibility Rests On

Accessibility is never an isolated issue. Design determines whether it’s built into the components, the platform determines whether the code allows for it, and management determines whether it’s still correct after the next release. We address all three within the same team.

From audit to certification in five steps.

How we make your site accessible

  • 1. Audit and testing

    We test your site against WCAG 2.2 Levels A and AA, using tools and manual review. You’ll receive the findings organized by guideline and by page.

  • 2. Prioritization

    Not all issues are equally serious. We rank the findings by their impact on your users and in relation to the requirements, so you know where to start.

  • 3. Fixing Issues in the Components

    Make fixes in the code, design, and content, and implement them in the components. This ensures that every new page is right from the start and prevents you from having to fix the same error ten times.

  • 4. Testing with Users

    We walk through the most important workflows using a keyboard and a screen reader, and whenever possible, with people who work with them on a daily basis.

  • 5. Explanation and validation

    You’ll receive a report that accurately reflects the findings, and testing becomes part of your delivery process. This ensures it remains properly managed.

Three sites where accessibility has been built into the components.

Platforms we’ve made accessible

  • Life Outdoor Living

    The perfect synergy between the online environment and physical stores. 40% growth in revenue.

  • Zuiver

    Zuiver's new webshop on the throne

For cookie notifications and consent management that are themselves accessible.

How we manage consent and privacy

Let us test your website

In one hour, we’ll walk through your most important user flows using a keyboard and screen reader. You’ll learn where visitors get stuck and what needs to be addressed first. It takes just one hour and doesn’t commit you to anything.

Please enter your email so we can get in touch.

Please enter your comments.

Agreement 

Meet the team

Ilona Kater
Developer
Rogier Venema
Developer

How much does it cost to make your site accessible?

That depends on the number of templates, the condition of your current code, and whether any content needs to be updated. An audit of your key user flows is a different process than bringing an entire platform up to Level AA.

What you always get: findings organized by guideline with the specific location indicated, fixes implemented at the component level rather than per page, an explanation that accurately reflects the issue, and testing that remains integrated into your delivery process.

Want to know where your site stands right now? Schedule a call, and we’ll determine the scope together.

Frequently Asked Questions About Digital Accessibility

01/ What is digital accessibility and why is it important?

Digital accessibility means that a website or application is usable by everyone, including people with disabilities. It is important because it ensures that your platform is accessible to a wider audience and complies with legal requirements, such as the WCAG guidelines.

02/ How can I make my website accessible?

At Redkiwi, we ensure that your website complies with the WCAG guidelines. This means, among other things, that we pay attention to color contrast, alternative text for images, keyboard navigation, and more.

03/ What is ISO 27001 certification?

ISO 27001 is an international standard for information security. It demonstrates that we meet the strictest requirements for data security and risk management, ensuring that both your data and that of your users are secure.

04/ Why is digital security so important?

Digital security is crucial for protecting your data and that of your users against cyberattacks, data breaches, and other forms of digital threats. Ensuring digital security builds trust with your users and prevents the legal and financial consequences of data breaches.

05/ How do you ensure the security of my platform?

As an ISO 27001-certified agency, we implement advanced security measures, such as data encryption, secure connections, advanced firewalls, and regular security audits. We also ensure that your platform complies with the latest laws and best practices for privacy protection.