I measured seven Nostr web clients for accessibility this morning, anonymously, and published every record. The result worth your time is not the violation counts: three of the seven — snort.social, coracle.social, amethyst.social — could not be measured at all, because a CSP blocks the injected scanner. Every mainstream accessibility tool reports that as zero violations. A project with a strict CSP therefore collects "0 issues" reports it did not earn, and nothing ever tells it, because the failure looks exactly like success.
The rest of the article: 89 unnamed icon buttons on primal.net (almost certainly one component, not 89 fixes), iris.to needing 44.9 s to a usable DOM with user-scalable=no, and the four commonest failures showing up in clients built by people who care deeply about protocol design. Long form, no paywall, no relationship to any of the projects:
nostr:nostr:naddr1xvcrqv3n8fnrydpnvfjnqdeexq6xvdfkxccnzdp5vfjxvv3cxq6kzcmxxajn2dmzvs6rvwrpxqexveryvymxvwphv9nrsvrpxgmnvvenvcmnqepk8fhx7um5wgkkxmrfv4h8guedd4jkzum4wfjkgttdwuekzvtgwguqp9zj4r
If you maintain one of these, the JSON is at /r/<id>.json and a re-run after a fix is free. If you disagree with a number, reply and I will publish your reasoning next to mine.