# WordPress Accessibility Day 2025 MOC > Event map. Topic homes: [[3. Resources/MOCs/Accessibility & Disability Inclusion MOC]], [[3. Resources/MOCs/WordPress Platform Design MOC]] · Index: [[3. Resources/MOCs/MOCs|Maps of Content → Events & Conferences]] A map of the WordPress Accessibility Day 2025 session recordings captured to Reader and Obsidian: 20 talks deep-read on 2026-09-08; all 20 recordings were published to the WP Accessibility Day YouTube channel on 2026-09-08. WP Accessibility Day is the free, 24-hour online conference run by the WP Accessibility Day nonprofit; its recordings publish to YouTube after the event. This is a **session index + thematic map**: where each talk sits, what it argued, what it measured, and which durable claims it fed. The synthesis pass of 2026-09-11 wrote eight Permanent notes from this set and connected six more candidate claims to notes that already existed. ## Core Question Accessibility work in WordPress arrives through five different doors: law and risk, testing with disabled people, design perception, build tooling, and the community that runs the events. Which of these talks change what a practitioner does on Monday, and which repeat the compliance framing the best of them argue against? > [!note] Each linked note carries the video embed, the deep-read notes, and the auto-caption transcript. Speaker names and affiliations below come from the notes' Summaries. Timestamps are transcript positions where the notes give them. --- ## ⚖️ Risk, law, and the business case - [Accessibility Isn’t Extra Work. It’s Risk Management.](3.%20Resources/Readwise/Articles/Accessibility%20Isn’t%20Extra%20Work.%20It’s%20Risk%20Management..md) — Jennifer Wjertzoch (DKB Code Factory): accessibility as risk management rather than design polish; a 60-second keyboard test as the gate on plugin adoption; the 43% market-share figure is hers, unsourced in the talk - [[3. Resources/Readwise/Articles/Accessibility Lawsuits and WordPress The Violations Every Business Needs to Know]] — Vanessa Tillemans (POURPIS): US lawsuit mechanics (ADA standing, Title III, circuit splits), 2023 filings naming Shopify and WordPress as the two most-sued platforms, the five recurring violations, and why overlay widgets don't repair the underlying code ## 🧪 Testing with people, and what a standard can't see - [[3. Resources/Readwise/Articles/Real Inclusion How to Run Insightful and Respectful User Testing With Disabled People]] — Lucy Collins (Web Usability): WCAG 2.2 AA as floor, not finish line; recruiting testers by input and output setup rather than diagnosis. Origin of two Permanents below - [[3. Resources/Readwise/Articles/Demystifying Screen Readers Your Guided Intro to Manual Accessibility Testing for WordPress Sites]] — Deneb Pulsipher and Kosi Asabere: NVDA reads the DOM while JAWS compensates for bad code; a free "screen reader ropes course" practice tool for manual testing - [[3. Resources/Readwise/Articles/Why Accessibility Matters From a Blind Visually Impaired Perspective]] — James Warnken (CPACC): the blind and low-vision experience from a working consultant 19 years into vision loss; legally blind acuity is worse than the eye chart's largest line; six barrier categories with their WCAG criteria - [[3. Resources/Readwise/Articles/Built the Website With an AI, but Is It Accessible]] — Janaki Konar and Fahad Lambate (BarrierBreak): green, red, and yellow zones for what AI site builders get right, wrong, and need reviewed; automated tools catch 30–40% of issues (their figure); demo of their own A11yInspect scanner, a vendor interest ## 🎨 Perception and design patterns - [[3. Resources/Readwise/Articles/Accessible Design Patterns for 2025]] — Vitaly Friedman (Smashing Magazine, European Parliament): 48-minute keynote on patterns for colorblindness, motion, navigation; disabled, hidden, and read-only states are not interchangeable - [[3. Resources/Readwise/Articles/Being a Colourblind Designer]] — Matt Roberts (Sightsavers, BIMA Inclusive Design Council): designing with protanopia and deuteranopia as a built-in filter; the prevalence argument that settles colour-only encoding. Origin of a Permanent below - [[3. Resources/Readwise/Articles/Typography, Readability and Digital Accessibility]] — Giulia Laco: a visibility, legibility, readability model tied to mechanical and WCAG causes; familiarity predicts legibility more than font design - [[3. Resources/Readwise/Articles/Invisible Until It Hurts Rethinking Brand Design Through the Lens of Accessibility]] — Victoria Ottah: brand design as a sensory system across typography, imagery, layout, voice, and color; the practical limit in client work is the client's authority, not the designer's knowledge. Origin of a Permanent below - [[3. Resources/Readwise/Articles/Creating a Hyper-Accessible Website for Blind, Low Vision, and Sighted Users]] — Sandy Shin and Jeremy Perkins (Braille Institute, iFactory): a 700-page rebuild for blind, low-vision, and sighted visitors at once; users invent workaround tools when formal features are missing. Origin of a Permanent below ## 🛠️ Build, tooling, and AI - [[3. Resources/Readwise/Articles/Making Gutenberg Blocks Accessible Practical Techniques With AI and DevTools]] — Anam Hossain (Multidots): semantic HTML, ARIA, keyboard handling, live-region announcements, and AI-assisted DevTools for custom blocks; "a coding mindset, not a checklist task" - [[3. Resources/Readwise/Articles/Continuous AI for Accessibility Leveraging Tools for Faster, More Inclusive Development]] — Helen Hou-Sandí (GitHub, WordPress core lead): the open-source `github/accessibility-scanner` Action, a find-file-fix pipeline on axe-core and Playwright; axe-core catches about 25% of GitHub's audit-flagged issues - [[3. Resources/Readwise/Articles/The Future Is Automated — But Will It Be Accessible]] — Rose Kivuva (Nairobi): AI features spreading through WordPress will exclude disabled users unless designed for; an auto-launching chatbot trapping screen-reader focus as the worked case ## 📄 Documents - [[3. Resources/Readwise/Articles/The Art of Accessibility Making Documents Delightfully Inclusive]] — Samantha Merrett (UK Ministry of Justice): Word, PowerPoint, and Excel accessibility; documents stay in their native format. Her Inclusive Design 24 talk a year later covers the same ground with PDFs added; see [[3. Resources/MOCs/Events/Inclusive Design 24 2026 MOC]] ## 🌍 Community, context, and constraint - [[3. Resources/Readwise/Articles/Reality Check Building Accessibility That Works in the Global South]] — Yigakpoa Ikpae (CLENT Africa): Global North guidance assumes broadband, modern hardware, and stable power; 1.3 billion people with disabilities live mostly where those don't hold. Origin of a Permanent below - [[3. Resources/Readwise/Articles/Advancing Accessibility Through Community and Open Source]] — Samuel Osei (Kumasi): TechAble, a WordPress-based digital-skills program for people with disabilities in Ghana; universal design, not charity; the WHO 16% figure cited - [[3. Resources/Readwise/Articles/Build for Everyone or Build for No One]] — Kevin Andrews and Elaine Shannon (Georgetown): partial accessibility for one modality is tokenism; a screen-reader user and a developer with an invisible disability co-presenting - [[3. Resources/Readwise/Articles/A Game-Changing Approach to Accessibility Education]] — Olivia Richter: the case against disability simulations (blindfolds, dyslexia-scramble text) for closing the empathy gap; "exclusion is ignorance on autopilot, not malice" - [[3. Resources/Readwise/Articles/Make All WordPress Events Accessible]] — Joe Simpson Jr. (Make WordPress Accessible and Training teams): reframing the software project's name into a demand on WordCamps and meetups; captioning as a budget line item; tour the venue with a disabled person. Origin of two Permanents below --- ## 🧠 Permanent notes this conference fed Eight, written in the 2026-09-11 synthesis pass: - [[3. Resources/Permanent Notes/WCAG Conformance Is Not a Usability Measure]] — from Collins - [[3. Resources/Permanent Notes/Recruit Accessibility Testers by Input and Output Needs Not by Diagnosis]] — from Collins - [[3. Resources/Permanent Notes/Colour-Only Signalling Fails at Population Scale Not at the Margin]] — from Roberts - [[3. Resources/Permanent Notes/An Icon Needs a Visible Label Not Just an Accessible Name]] — from Shin and Perkins - [[3. Resources/Permanent Notes/Global South Accessibility Gaps Are Infrastructure Gaps First]] — from Ikpae - [[3. Resources/Permanent Notes/A Hired Designer's Accessibility Reach Ends at the Client's Authority]] — from Ottah - [[3. Resources/Permanent Notes/Captioning Funded as a Line Item Survives Budget Pressure]] — from Simpson - [[3. Resources/Permanent Notes/Tour an Event Venue With a Disabled Person Before Committing]] — from Simpson Six further candidates from the batch were already stated by existing Permanents and were connected rather than duplicated (the 2026-09-11 report records the count, not the pairs). Unwritten candidates worth a look: Hou-Sandí's 25% axe-core coverage figure as a bound on automated scanning, Konar and Lambate's 30–40% as the same claim from a vendor, Laco's familiarity-over-letterform finding, and Friedman's three-state distinction. ## 🔗 Related maps - [[3. Resources/MOCs/Accessibility & Disability Inclusion MOC]] — the topic map; the eight Permanents sit in its 2026-09-11 synthesis block - [[3. Resources/MOCs/WordPress Platform Design MOC]] — Hossain's block techniques and Hou-Sandí's core-adjacent tooling - [[3. Resources/MOCs/Documentation & Technical Writing MOC]] — Merrett's document accessibility and Maldonado's email audit are documentation claims - [[3. Resources/MOCs/Events/Inclusive Design 24 2026 MOC]] — the same field a year later; Merrett appears in both, and the automated-coverage figures here (25%, 30–40%) are the numbers the 2026 talks argue from - [[3. Resources/MOCs/Evidence & Claims Literacy MOC]] — the recurring pattern: market-share, prevalence, and tool-coverage percentages stated without a source ## Open threads - The 2026-09-11 report counted 18 sessions in this batch; the vault holds 20 mirrors dated 2026-09-08, all confirmed as WP Accessibility Day channel uploads. The two extra were most likely processed under another cluster that day. Not reconciled. - Maria Maldonado's "Email Accessibility in WordPress" (processed 2026-09-19) was first listed here; the recording is from Equalize Digital's own channel (2026-09-17), not the conference, so it was removed. It belongs with the Documentation map's email and transactional-content material. - Coverage of the 2025 program is partial; the event ran 24 hours. Sessions not captured are not listed here. - WP Accessibility Day 2026 has a preview note in the vault (Equalize Digital, 2026-09-21, with Ryan Bracey); when its recordings publish they belong in a sibling map, not this one.