WCAG cognitive audit
WCAG Cognitive Audit for Consumer Apps: Behavioural Evidence Your Compliance Team Can Use
Consumer apps face growing scrutiny from regulators and app store gatekeepers alike. An OpenScouter cognitive audit gives your product and legal teams behavioural evidence of how real neurodivergent users experience your app, from onboarding through to checkout and account management. Reports are human-confirmed and structured for action, not filing.
Cognitive Accessibility in Consumer Apps Is a Regulatory and Commercial Blind Spot
UK consumer-facing apps that fall under FCA authorisation are subject to Consumer Duty, which requires FCA-regulated firms to demonstrate that products and communications deliver good outcomes for all customers, including those with characteristics of vulnerability. Cognitive differences such as ADHD, dyslexia, and processing difficulties are explicitly within scope of vulnerability guidance. Firms preparing for FCA supervisory review need evidence, not assertions, that their app journeys work for those users.
For consumer apps with EU distribution, the European Accessibility Act (EU Directive 2019/882) is the relevant instrument. National transposition acts, including the Barrierefreiheitsstärkungsgesetz (BFSG) in Germany and Dlgs 82/2022 in Italy, are the local enforcement mechanisms. The EAA deadline for in-scope services passed in June 2025, meaning EU-facing consumer apps are now expected to meet accessibility requirements under national law. WCAG 2.2 is the referenced technical standard, but conformance testing alone does not capture how users with cognitive differences actually behave inside an app.
WCAG 2.2 automated audits catch structural issues. They do not catch the moment a user abandons a multi-step checkout because the progress indicator is ambiguous, or when a push notification pattern causes a user with attention difficulties to lose their place in an onboarding flow. Those are behavioural failures, and they show up in drop-off rates before they show up in an audit report. Behavioural research with neurodivergent participants is the method that surfaces them.
The W3C identifies 8 cognitive accessibility user-need categories that WCAG 2.x partially addresses but does not fully test, including memory, attention, executive function and processing speed
Consumer apps are built around repeated, habitual use: daily check-ins, quick purchases, subscription renewals, notification-driven re-engagement. Those patterns assume a user who can hold context across sessions, filter irrelevant information quickly, and complete multi-step flows without losing their place. The W3C Cognitive Accessibility Task Force finding matters here precisely because consumer app design rarely stress-tests those assumptions. When cognitive user-need categories such as memory, attention, executive function, and processing speed are not fully addressed by WCAG 2.x testing, the gaps fall hardest on the journeys consumer apps depend on most: onboarding completion, first purchase, and subscription retention. A structural audit will not find those gaps. Behavioural sessions with neurodivergent participants will.
Our approach
Neurodivergent Participants on Your Actual App Journeys
OpenScouter recruits participants with ADHD, autism, dyslexia, and related cognitive differences. They complete real tasks inside your consumer app: account creation, identity verification, in-app purchase, subscription management, and similar journeys. These are not proxy tasks on a prototype. They are the flows your users hit every day.
Three Behavioural Streams Captured in Parallel
Every session captures interaction signals (clicks, scrolls, rage clicks, hesitation), think-aloud voice, and facial expression processed locally on the participant's device. An AI pipeline correlates the three streams to identify where cognitive load spikes, where users stall, and where they recover or abandon. No single stream tells the full story.
Human-Confirmed Reports Mapped to WCAG Cognitive Criteria
AI correlation surfaces candidate findings. A human researcher reviews every finding before it enters the report. Outputs are mapped to relevant WCAG 2.2 success criteria and, where applicable, to the W3C Cognitive Accessibility Task Force guidance. Reports are written for product, design, and compliance audiences simultaneously. They are evidence, not legal opinion.
What you receive
- Participant recruitment from OpenScouter's neurodivergent panel, screened for the cognitive profiles relevant to your app's user base
- Moderated remote sessions covering your nominated app journeys, with three-stream behavioural capture throughout
- AI-correlated session analysis reviewed and confirmed by a human researcher before any finding is included in the report
- A structured findings report mapping usability failures to WCAG 2.2 success criteria and W3C COGA guidance, with severity ratings and recommended fixes
- An executive summary formatted for compliance and legal review, suitable for use as supporting evidence in FCA Consumer Duty documentation or EAA conformance records
Frequently asked
- Does this audit constitute legal compliance with the European Accessibility Act or FCA Consumer Duty?
- No. OpenScouter reports are behavioural evidence, not legal opinion. They document how neurodivergent users experience your app and map findings to recognised technical standards. How you use that evidence in a compliance or regulatory context is a matter for your legal team. We are deliberately specialised in producing the evidence, not in interpreting its legal sufficiency.
- Which consumer apps are in scope for the EAA and its national transposition acts?
- EU Directive 2019/882 covers a defined list of products and services, including certain e-commerce services and consumer-facing digital services. National transposition acts such as the BFSG in Germany and Dlgs 82/2022 in Italy are the enforcement instruments. Whether your specific app falls within scope depends on its category and the jurisdictions you serve. We recommend confirming scope with legal counsel before treating any audit as a compliance filing.
- Our app already passes automated WCAG 2.2 scanning. Why do we need behavioural testing?
- Automated scanning checks structural conformance: colour contrast ratios, label presence, heading hierarchy. It cannot observe a user with ADHD losing track of a multi-step checkout, or a user with dyslexia misreading a confirmation screen and triggering an unintended action. The W3C Cognitive Accessibility Task Force has identified cognitive user-need categories that WCAG 2.x partially addresses but does not fully test. Behavioural sessions with neurodivergent participants are the method that reaches those gaps.
- How long does a cognitive audit engagement take?
- From study brief to delivered report, a standard engagement runs in days rather than months. The exact timeline depends on the number of journeys in scope, participant availability, and how quickly your team can provide access to the app. We will confirm a timeline at the briefing stage.
- Do participants test on iOS, Android, or both?
- We support both platforms. If your app has meaningful differences between iOS and Android builds, for example in notification permission flows or biometric authentication screens, we recommend testing both. Behavioural differences between platforms are common and worth capturing separately rather than averaging across them.
Keep reading
Research hub
Industry
Use case
Related research
Glossary
Talk to a behavioural researcher
Tell us about the vertical, the journey, and the evidence you need. We will scope a pilot in days, not weeks.