Back to Knowledge

B Corp website accessibility requirement (JEDI2.m) explained

If you’re B Corp certified, or working towards it, you’ve probably hit a line that reads: the company assesses the accessibility of its public-facing website. This sounds simple, but there are a few criteria you have to hit to pass it. It’s part of the JEDI2.m update, a “Beyond the Workplace” action under the new Justice, Equity, Diversity and Inclusion topic. It applies from Year 0, whatever your company size, and unlike some of the other standards, it has a precise definition of “done.”

JEDI2.m breaks down into four parts.

Your website needs to:

  1. Be confirmed against WCAG (Web Content Accessibility Guidelines) at AA or AAA criteria
  2. Be assessed by an internal or external specialist
  3. Go through manual testing
  4. Include feedback from people with disabilities

It must tick every one of the above in order to qualify for JEDI2.m.

Naturally, the instinct for most companies is to run a free automated scanner, get a clean-ish report, and submit it as evidence. But B Lab explicitly states that automated testing alone doesn’t satisfy the standard. Scanners can confirm your code is technically valid, but not whether a screen reader user or keyboard-only visitor can actually get through your checkout.

WCAG AA vs AAA

We’ll go into this briefly here, as there’s a more in depth post about WCAG AA vs AAA here, but on the whole AA is generally often enough. WCAG AA is the level referenced in most accessibility law, including the EU Accessibility Act, so it’s the sensible default regardless of legal obligation. AAA exists for some specific content types and is the strictest tier, offering maximum accessibility including specialised reading capacities and sign language interpretation, among other criteria. Even the guidelines’ own authors don’t recommend it as a whole-site target, since some AAA criteria can’t be met by every content type.

Getting feedback from people with disabilities

An expert testing your site with a screen reader is useful. But someone who relies on one every day, for everything, is testing something completely different – the same goes for keyboard navigation or cognitive accessibility. Expertise and lived experience aren’t interchangeable, and B Lab treats the second as mandatory for JEDI2.m. If you’re unsure how to find and brief disabled testers, build that time into your plan rather than leaving it to last, or work with a testing body who has that network in place. It’s how we handle this stage for our own audits.

How to work towards a JEDI2.m compliant website

  • Commission a manual audit against WCAG AA
  • Fix what’s flagged, and get fixes validated rather than just marked done
  • Document who carried out the assessment and how
  • Commission testing from someone with a disability, with a written report tying findings to specific pages and criteria

Keep the audit, validation, and testing report together as your evidence set.

JEDI2.m arrived with B Lab’s broader standards overhaul in April 2025, tightening requirements after criticism that strong scores in one area used to cover weak ones elsewhere. It’s also arriving as DEI language drops out of corporate reporting fast, particularly in the US. B Lab has tightly held onto this area as crucial for a business’s certification.

 

Not just a one-off

Accessibility trends change and compliancy drifts.

Not just a one-off

Accessibility trends change and compliancy drifts.

As sites pick up new pages and components over time, websites accumulate subtle failures nobody notices until an assistive technology user hits one. A light annual check costs far less than a full re-audit each time, and keeps your website accessible for everyone. This is, of course, a better commercial move as accessible design improves wider market opportunities, think anyone and everyone being able to access your content from any device, in any environment. Feels obvious, right?

Final notes to wrap up

Existing accessibility work isn't enough alone

Good contrast and alt text are of course necessary, but are not sufficient.

Automated tools are not evidence

Tools like WAVE are a great starting point, but won’t be enough for compliancy.

Budget time for finding testers

This is not the same as auditors and can take some time. We’ve built a list of trusted partners, get in touch to find out more.

Frequently asked questions

Does JEDI2.m apply to every B Corp?

Yes, it applies from Year 0, regardless of company size, with no exemptions for smaller businesses.

Does B Corp require WCAG AA or AAA compliance?

Either level satisfies the standard, but AA is the practical target most businesses should aim for. AAA isn’t achievable across all content types and AA is also the level referenced by most accessibility law, including the EU Accessibility Act.

Does an automated accessibility scan satisfy B Corp's JEDI2.m requirements?

No. Automated tools typically catch only around 30–40% of accessibility issues, depending on the tool. JEDI2.m requires manual testing, assessment by a specialist, and feedback from people with disabilities alongside the WCAG check.

How often should my website have an accessibility audit?

As a general rule, once a year at minimum, plus a check after any major redesign or new feature launch. Accessibility drifts over time as sites pick up new pages and components, so treating it as a one-off leaves small failures to build up unnoticed.

Does digital accessibility affect our B Corp score?

Yes. Digital accessibility sits within the JEDI (Justice, Equity, Diversity and Inclusion) topic of the updated B Corp standards, and JEDI2.m is one of the required actions companies can select to meet it – demonstrating evidenced improvement, not just intent.

Looking for a website that’s beautiful, functional and doesn’t cost the planet?

Let’s talk.

CTA form

This field is for validation purposes and should be left unchanged.
Name(Required)
Back to Knowledge