Accessibility blog
Six posts on ADA compliance, cognitive accessibility and the way testing actually goes. Written by the people who run the audits, and dated.
The guides on this site answer a question once. These posts are where we write down the longer argument: what a law asks for, why a testing method is built the way it is, and which beliefs in a product team cause the same defect twice.
All posts
-
What cognitive psychology says about interface memory load
Working memory holds only a few things at once. Most forms ask the reader to hold more than that, and then blame them for the error.
-
Cognitive distortions that hide accessibility problems
A cognitive distortion is a shortcut in judgement that feels true and is not. The same shortcuts decide most accessibility budgets.
-
Accessible digital CBT: testing a therapy product
Cognitive behavioural therapy (CBT) delivered as an app or a website is still software, and it breaks in the ways software breaks.
-
Website ADA compliance: an order of work that holds up
Bringing a website to ADA compliance is a sequence, not a scramble. This is the order that survives contact with a deadline.
-
Cognitive accessibility in a digital product
Cognitive accessibility is the part of the work that concerns attention, memory, language and learning. It is where most products fail without knowing.
-
ADA compliance: what it asks of a digital product
The Americans with Disabilities Act names no web standard. Here is what an auditor tests, and where the risk really sits.
What we write about
-
Compliance, without the promises
What the ADA and the European Accessibility Act ask of a digital product, where the deadlines stand, and why we hand the legal question back to your counsel every time. Start with ADA compliance.
-
Cognition, which tools miss
Attention, memory, language and learning. The part of accessibility that no scanner can see, and the WCAG criteria that carry it. Start with cognitive accessibility.
-
Method, in the open
What we test with, what we refuse to claim, and the mistakes product teams repeat. How we test.
Test the page that matters
One free page, tested by hand, with the findings written out and a scope for the rest.