One in six people can't use your
website the way you built it.
Disabled people navigate the web differently. Barriers you've never noticed are stopping them every day. OYNK SE exists to find those barriers — with the people who experience them — and pay them properly for what they know.
of people have a disability
of barriers found by automated tools
access need areas tested
Why This Exists
B Lab now requires lived experience testing. Most B Corps don't know what that means yet.
B Lab's JEDI Standards V2.2 introduced four requirements that directly affect your digital presence, applying to every B Corp, at every size, from Year 0. There are no exemptions. JEDI2.m says your public-facing website must be assessed for accessibility. JEDI2.l says your internal digital tools must meet the same standard. JEDI2.p says you must have an inclusive communications and ethical content guide. JEDI2.q says you must assess at least one product or service for inclusivity using stakeholder feedback.
These aren't tick-box exercises. B Lab is explicit about what counts. For JEDI2.m, the assessment must include four things: confirmation of WCAG compliance, a specialist assessor, manual testing by a human, and feedback from people with disabilities. Running a Lighthouse scan satisfies one of those four. Hiring a consultant who doesn't involve disabled people satisfies two, maybe three. The fourth — actual feedback from disabled people — is where most B Corps get stuck.
Not because they don't care. Because they don't know how. Who do you recruit? How do you brief them? How do you turn their feedback into evidence that a B Lab assessor will accept? This is new territory for most organisations, and the guidance doesn't come with a shortcut.
OYNK SE is the shortcut. But it's one built on something real.
The Story Behind OYNK SE
This isn't a compliance workaround. It's a jobs programme disguised as one.
OYNK SE was founded by someone who is AuDHD. Not as an ally project. Not as a corporate initiative. As someone who knows what it's like to navigate systems that weren't built for the way your brain works — and who got tired of watching other disabled people's expertise go unpaid.
The disability employment gap in the UK has barely moved in a decade. Around 53% of disabled people are in employment, compared to 82% of non-disabled people. When disabled people do find work, they're more likely to be in lower-paid, lower-security roles. And the expertise they've built — navigating a web that wasn't designed for them, learning assistive technologies out of necessity, developing a forensic understanding of digital barriers — is almost never treated as a professional skill.
OYNK SE treats it as one.
Our testers are not volunteers. They are not participants in a focus group. They are paid experts whose knowledge of screen readers, switch controls, magnification software, and cognitive accessibility cannot be replicated by any automated tool or any sighted consultant, however skilled. We pay above market rate, because the work is skilled work and the insight is irreplaceable.
Every B Corp that commissions lived experience testing through OYNK SE creates paid work for disabled people. The more B Corps meet this requirement properly, the more that money flows to people whose expertise has been consistently undervalued. That is the model. Compliance that funds inclusion. Evidence that creates employment.
Nothing about us without us isn't just a disability rights principle. For us, it's an operating model.
What This Means for Testers
This isn't gig work. It's a career path built around expertise that already exists.
Work on your terms
Testers choose how many hours they work. There are no minimum commitments and no fixed schedules. Some testers complete one assessment a month. Others do several a week. The work fits around their life, their energy, and their capacity — not the other way around.
Paid for every test
Every completed test is paid work. No unpaid trials. No exposure-based arrangements. Testers are paid £200 per session because their insight is worth it. For someone who completes two tests a week, that is £1,600 a month of skilled, flexible income — work that fits around benefits, care responsibilities, or other commitments.
We invest in our testers
We don't just pay testers and move on. We reinvest into the people who make this work possible. That means funding better tools for the job — laptops, assistive technology, software licences, whatever a tester needs to do their best work. If a tester's screen reader is outdated, we replace it. If they need a newer machine, we provide one. The tools improve their testing and their daily life.
Expertise recognised, not extracted
Disabled people are routinely asked to share their experience for free — in consultations, surveys, advisory panels, and user research. OYNK SE does the opposite. We treat lived experience as a professional skill, pay accordingly, and build long-term working relationships with our testers. Their names go on the reports. Their expertise shapes the outcomes.
For many of our testers, this is life-changing money. Not because the individual payments are extraordinary, but because the work is consistent, flexible, and respects their circumstances. A disabled person who cannot commit to a 9-to-5 can still build a genuine income stream. A tester who needs to work from bed some days can do exactly that. Someone whose benefits cap limits their options can take on work that fits within those constraints.
The more B Corps commission OYNK SE, the more testing work exists. The more testing work exists, the more testers we can bring on, equip, and pay. Every engagement grows the programme. Every pound spent on compliance becomes a pound invested in disabled people's livelihoods.
The Problem with Automated Testing
Automated tools catch about 30% of real barriers. The rest are invisible to them.
A scanner can check whether an image has an alt tag. It cannot tell you whether the alt tag makes any sense when read aloud by NVDA. It can flag a low contrast ratio. It cannot tell you that your navigation announces itself in a completely illogical order to someone relying on a screen reader, or that your contact form is impossible to complete using keyboard-only input, or that your checkout flow falls apart entirely for someone using a switch device.
Expert review helps. But a sighted accessibility consultant using a screen reader is not the same as a blind person who uses one every day. An expert who tests keyboard navigation is not the same as someone with a motor disability whose entire digital life depends on it. Experts know the WCAG criteria. Disabled people know the lived reality. Both are necessary. Neither replaces the other.
B Lab knows this. That's why feedback from people with disabilities is a mandatory component of JEDI2.m — not a recommended one, not a nice-to-have. Mandatory. And it's also why automated testing alone is explicitly stated as insufficient.
What OYNK SE Delivers
OYNK SE covers all four of the B Lab JEDI requirements that affect your digital presence. One engagement, properly documented, formatted for B Lab submission.
Lived Experience Testing
JEDI2.m — requirement 2.m.2.d
Real people with real access needs use your website and report what works and what doesn't. We cover four access need areas — vision, hearing, motor, and cognitive — each tested by people who navigate the web this way every day. We define the scope, brief the testers, structure the feedback, and produce a written report that maps every barrier to a specific page, element, and WCAG criterion. This is the evidence for JEDI2.m requirement 2.m.2.d.
Vision
Testers who are blind, have low vision, or are colour blind. Testing with screen readers including NVDA, JAWS, and VoiceOver, alongside magnification software and high-contrast settings. They find problems that no sighted person would notice, however technically expert.
Hearing
Testers who are deaf or hard of hearing. They check whether video content has captions, whether audio content has transcripts, and whether alerts rely solely on sound. They test the full experience of your site without audio.
Motor
Testers with limited dexterity who use adaptive devices, switch controls, or keyboard-only navigation. They check whether every interactive element can be reached and operated without fine motor control or a mouse.
Cognitive
Testers with dyslexia, ADHD, or other cognitive access needs. They check readability, navigation logic, consistency, and whether the site creates unnecessary complexity that becomes a barrier to understanding.
Inclusive Communications & Ethical Content Guide
JEDI2.p
B Lab requires every B Corp to have a guide for inclusive external communications. This is a document your whole team can use. It covers the language you use, how you gather and manage content ethically, how you represent social identities across imagery, illustrations, and non-written content, and — if you use AI for any creative content — what checks and human review are required. We build this guide for you, or review an existing one and close the gaps.
One document can serve as both your external guide (JEDI2.p) and your internal guide (JEDI2.i), which is a separate Within the Workplace requirement. If you need both, the additional work is minimal.
Product Inclusivity Assessment
JEDI2.q
B Lab requires you to assess at least one product or service for inclusivity using stakeholder feedback. The assessment must identify which groups face barriers and what those barriers are. If your website is your main product or service, the lived experience testing covers this too. One round of testing. Two requirements evidenced.
Internal Tools Accessibility
JEDI2.l
JEDI2.l is a separate Within the Workplace requirement that applies to every B Corp with employees, from Year 0. It has the same four assessment criteria as JEDI2.m — WCAG compliance, specialist assessor, manual testing, and feedback from disabled people — but applied to your internal digital tools: your intranet, email platform, Slack or Teams, HR system, internal dashboards, and anything else your team uses daily.
Testing internal tools is different from testing a public website. You can't ask a disabled tester to learn a completely unfamiliar system — that tests their patience, not the tool's accessibility. So we take a different approach.
We audit what you use
We map every internal digital tool your team relies on — messaging, email, intranet, HR platform, project management, shared drives. We review vendor accessibility conformance reports (VPATs) for off-the-shelf tools and flag where the vendor falls short.
Expert review of customised parts
The parts you've built or customised — intranet pages, internal dashboards, email templates, onboarding flows — get a manual expert review against WCAG criteria. These are the parts the vendor didn't build, and they're usually where the barriers are.
Interview-based lived experience feedback
Instead of dropping testers into an unfamiliar system, we gather lived experience feedback through structured interviews. If your company already has disabled employees, they become the testers for 2.l — and get paid for it through OYNK SE. If not, we interview people who use the same tools in their own workplaces. "Do you use Teams with a screen reader? What breaks? What workarounds have you built?" Real insight from real daily use, not a simulated walkthrough.
Cognitive and neurodivergent review
OYNK SE's founder is AuDHD. The cognitive accessibility review of internal tools — navigation logic, information overload, notification management, workflow clarity, whether something just doesn't make sense — is conducted from genuine lived experience. When a workflow is confusing, when a dashboard has too much competing information, when a process requires you to hold three things in working memory at once, that's something you spot instantly when your brain works this way. But we're transparent about what we can and can't cover: screen reader testing, switch device testing, and magnification testing are done by testers whose daily experience is with those specific technologies. Nobody claims expertise they don't have.
JEDI2.l is often overlooked because it's internal. But if your disabled employees can't use the same tools as everyone else, they're being excluded from the workplace itself. B Lab treats this with the same weight as your public website — and so do we.
How It Works
Four to six weeks from discovery call to final evidence pack.
Scope and brief
We identify the key user journeys on your site: the pages and flows that matter most. We brief testers on what to test, but we do not tell them how to navigate it. The point is to observe how they actually use your site, not how you intended them to.
Lived experience testing
Testers from our panel work through your site independently. Each one reports on the barriers they encounter: what the barrier is, where it is, how severe it is, and what would fix it. Structured feedback, not vague impressions. Every finding is mapped to a specific page, element, and WCAG criterion.
Expert manual review
Alongside the lived experience testing, a qualified specialist conducts a manual expert review. This covers the technical accessibility criteria that structured testing addresses systematically. Combined with the automated scan from EcoPigs, this gives you all four components B Lab requires for JEDI2.m.
Evidence pack
You receive a full set of reports formatted for B Lab submission: the lived experience report, a WCAG conformance statement, the manual testing report, the inclusive communications guide, and the product inclusivity assessment. Everything your certification application needs, with nothing missing.
What You Receive
Everything formatted for B Lab submission.
| Deliverable | JEDI2 Requirement | What It Covers |
|---|---|---|
| Lived experience report | 2.m.2.d | Structured feedback from disabled testers across vision, hearing, motor, and cognitive access needs |
| WCAG conformance statement | 2.m.1, 2.m.2.a | Formal statement of WCAG 2.2 AA/AAA conformance level with findings |
| Manual testing report | 2.m.2.b, 2.m.2.c | Expert manual review by a qualified accessibility specialist |
| Inclusive communications guide | 2.p.1, 2.p.2 | Language guidance, ethical content management, representation standards, AI content rules |
| Product inclusivity assessment | 2.q.1, 2.q.2 | Stakeholder feedback identifying barriers and affected groups |
| Internal tools accessibility report | 2.l.1, 2.l.2 | VPAT review, expert assessment, and interview-based lived experience feedback on internal digital tools |
| B Lab evidence pack | All | All reports formatted for B Lab submission, ready for your certification application |
The Full Scope of What's Delivered
Every tier includes the complete nine-phase process — baseline scan, manual review, lived experience testing, re-scan, comms guide, product inclusivity assessment, and evidence pack. What changes between tiers is the depth: how many testers, how many journeys, how many pages in scope, whether the comms guide is built from template or bespoke.
Tier 1 — Micro / Small
Under 50 workers
- EcoPigs baseline scan and re-scan
- Manual expert review of up to 5 key pages / journeys
- 2 lived experience testers (vision + one other based on site type)
- Structured tester feedback mapped to WCAG criteria
- WCAG 2.2 AA conformance statement
- Inclusive communications guide (template-based, client-reviewed)
- Product inclusivity assessment (derived from tester findings)
- Internal tools assessment — VPAT review and expert check of up to 3 core tools (2.l)
- B Lab evidence pack covering 2.m, 2.l, 2.p, 2.q
Tester pay: 2 × £200 = £400
Tier 2 — Small / Medium
50–249 workers, or any renewal
- EcoPigs baseline scan and re-scan
- Manual expert review of up to 10 key pages / journeys
- 4 lived experience testers (vision, hearing, motor, cognitive)
- Structured tester feedback mapped to WCAG criteria
- WCAG 2.2 AA/AAA conformance statement
- Inclusive communications guide (template-based with bespoke sections)
- Product inclusivity assessment (derived from tester findings)
- Internal tools assessment — VPAT review, expert check, and interview-based lived experience feedback on up to 5 tools (2.l)
- B Lab evidence pack covering 2.m, 2.l, 2.p, 2.q
- Internal communications guide (2.i) included at no extra cost
Tester pay: 4 × £200 = £800
Tier 3 — Medium / Large
250+ workers, complex sites, or multi-site
- EcoPigs baseline scan and re-scan across all public-facing domains
- Manual expert review of up to 20 key pages / journeys
- 4 lived experience testers with 2 testers per access need area (8 total)
- Structured tester feedback mapped to WCAG criteria
- WCAG 2.2 AA/AAA conformance statement
- Fully bespoke inclusive communications guide covering all external languages
- Internal communications guide (2.i) included
- Bespoke product inclusivity assessment with stakeholder interview component
- Full internal tools assessment — VPAT review, expert review, and interview-based lived experience feedback across all internal platforms (2.l)
- B Lab evidence pack covering 2.m, 2.l, 2.p, 2.q
- Submission support — we liaise with your B Lab assessor directly if needed
Tester pay: 8 × £200 = £1,600
Add-ons available at any tier
| Internal communications guide only (2.i) | £650 | if not already included |
| Additional tester (any access need area) | £400 | per tester |
| Remediation priority report | £450 | ranked fix list with effort estimates for your dev team |
| Annual re-test (evidence for renewal cycle) | 20% off | discount on original tier |
Common Questions
Does this apply to my B Corp if we're small?
Yes. JEDI2.m, 2.l, 2.p, and 2.q apply to every B Corp at every size (2.l applies to all companies with employees). There are no exemptions. These four are among the most universally applicable requirements in the entire JEDI framework.
Can I just run an automated scan?
No. B Lab is explicit: automated testing alone does not meet JEDI2.m. You need all four components — automated testing, WCAG confirmation, manual review by a specialist, and feedback from disabled people. OYNK SE delivers all four together.
What if I'm renewing, not certifying for the first time?
The requirements don't expire. If you're at Year 3 or Year 5, you'll need to demonstrate continued or new JEDI actions. OYNK SE gives you fresh evidence that your site has been properly tested, by the people it affects, since your last certification. For growing companies, the number of required actions also increases at each renewal — OYNK SE covers four of them in one engagement.
Can one round of testing cover both JEDI2.m and JEDI2.q?
Yes. If your main product or service is delivered through your website, the lived experience testing provides stakeholder feedback on both website accessibility (JEDI2.m) and product inclusivity (JEDI2.q). One engagement, two requirements evidenced.
I already have the PEER automated audit. Do I still need OYNK SE?
They do different things. PEER covers the technical checks — WCAG rules, contrast ratios, performance, carbon. OYNK SE covers the human components that B Lab also requires: lived experience testing, expert manual review, and the inclusive communications guide. PEER shows where you stand technically. OYNK SE provides the human evidence that completes the picture. You need both for a complete JEDI2.m submission.
How much do testers get paid?
Above market rate. We pay testers properly for their expertise, their time, and the value of their lived experience. This is skilled professional work, not volunteering. Exact rates depend on scope and complexity, and we'll be transparent about that from the first conversation.
The evidence B Lab needs. The employment disabled people deserve.
Lived experience testing, inclusive communications guidance, and product inclusivity assessment — all in one engagement. Properly paid disabled testers. Audit-grade evidence for your B Corp certification application.
Book a discovery call and we'll walk you through exactly what's needed for your size, your sector, and where you are in your certification cycle.
Social enterprise. Paid testers. Real evidence.