## Synthesis additions (2026-10-15 — accessible by default in a component library; revert-by-authority in WordPress core) - [[3. Resources/Permanent Notes/A Shared Accessible Component Library Makes the Accessible Choice the Default]] — the accessible choice must be what a developer gets by typing the obvious thing (giffgaff, LeadDev) - [[3. Resources/Permanent Notes/A Revert by Authority Needs a Stated Technical Reason Before It Reads as Technical]] — treat a revert as technical only if the person with authority states a technical reason on the record (The Repository, Rae Morey) - [[3. Resources/Readwise/Articles/Moving Accessibility From Debt to Done at Giffgaff]] — LeadDev talk: accessibility moved from debt to done at giffgaff; a shared component library made the accessible choice the default. - [[3. Resources/Readwise/Articles/Matt Mullenweg Orders Accessibility Revert, Tells Core Committer to “Contribute Your Talents to Another Project”]] — The Repository (Rae Morey): an accessibility-related Dashboard change reverted on Mullenweg's Trac instruction; the article keeps its own reporting apart from quoted parties. ## Synthesis additions (2026-10-01 — automation replacing human accessibility testing in public services) - [Bookmark A Trump Team Wants to Automate U.S. Web Design System Accessibility Testing. Experts Are Worried.](3.%20Resources/Readwise/Articles/Bookmark%20A%20Trump%20Team%20Wants%20to%20Automate%20U.S.%20Web%20Design%20System%20Accessibility%20Testing.%20Experts%20Are%20Worried..md) — Remy Sharp bookmarks a news story and says automating accessibility testing is a funding cut that falls on disabled users; the bookmark is a stance, and the linked story is not captured. ## Synthesis additions (2026-10-01 — accessibility in WordPress products and tools) - [[3. Resources/Readwise/Articles/Designing Accessibility Into WordPress Products With WP Engine]] — WP Accessibility Day sponsor livestream (vendor source, Whisper-only transcript): Amber Hinds interviews WP Engine's Jonny Waters on building accessibility into Newsroom, a WP Engine product; product claims are unverified. ## Event maps - [[3. Resources/MOCs/Events/WordPress Accessibility Day 2025 MOC]] — 20 WPAD 2025 talks (added 2026-09-24); the eight Permanents in the 2026-09-11 block below came from it. - [[3. Resources/MOCs/Events/Inclusive Design 24 2026 MOC]] — 22 #id24 2026 talks (added 2026-09-24, extended 2026-09-25): WCAG 3, HTML mechanics, cognition and plain language, documents, Kanji, speech, gaming, decolonizing design. Candidate claims listed there; none written yet. ## Synthesis additions (2026-09-11 — WordPress Accessibility Day 2025 batch) Eighteen conference sessions processed; six candidate claims were already covered by existing notes and were connected rather than duplicated. Eight new atoms: **Measurement and testing** - [[3. Resources/Permanent Notes/WCAG Conformance Is Not a Usability Measure]] — conformance tests for required properties, not task completion; the third tier below automated checking and manual audit. - [[3. Resources/Permanent Notes/Recruit Accessibility Testers by Input and Output Needs Not by Diagnosis]] — recruit by setup, not by label; one condition produces many configurations. **Design and components** - [[3. Resources/Permanent Notes/Colour-Only Signalling Fails at Population Scale Not at the Margin]] — the prevalence argument, not the compliance argument, is what settles colour-only encoding. - [[3. Resources/Permanent Notes/An Icon Needs a Visible Label Not Just an Accessible Name]] — an accessible name serves AT users and leaves sighted users guessing; two separate requirements. **Context and constraint** - [[3. Resources/Permanent Notes/Global South Accessibility Gaps Are Infrastructure Gaps First]] — guidance written for fast connections prescribes remedies that cannot be executed under bandwidth and device constraint. - [[3. Resources/Permanent Notes/A Hired Designer's Accessibility Reach Ends at the Client's Authority]] — the practical limit in client work is the authority structure, not the practitioner's knowledge. **Events** - [[3. Resources/Permanent Notes/Captioning Funded as a Line Item Survives Budget Pressure]] — budgeting decides whether access happens more reliably than the stated commitment does. - [[3. Resources/Permanent Notes/Tour an Event Venue With a Disabled Person Before Committing]] — a checklist records features; a tour reveals whether the route between them works. # Accessibility & Disability Inclusion MOC Access claims were scattered across eight domain MOCs — DevRel, Product, Open Source, Commons, Spiritual Formation — because they arrived through whatever subject brought them in. This map gathers them by their shared question instead: **who has to identify themselves, or fight, to be served?** Three of these notes had no MOC home at all before 2026-09-05. ## The organizing test - [[3. Resources/Permanent Notes/Disability Inclusion Is a Design-Authority Question]] — the root claim: inclusion is about who holds authority over the design, not what gets added afterward - [[3. Resources/Permanent Notes/A Support Is Systemic Only If It Works Without Disclosure]] — the procedural test — what must an employee reveal to benefit? Opt-in selects against the people under the most stigma - [[3. Resources/Permanent Notes/Universalizing Disability Language Risks Erasing Specific Hardship]] — the language boundary: empathy metaphors that flatten distinct legal, medical, and economic realities ## Disclosure, concealment, and invisible conditions - [[3. Resources/Permanent Notes/Concealment Trades a Certain Near Cost for a Diffuse Later One]] — why exhortation to disclose fails — it argues against a payoff structure, not a belief - [[3. Resources/Permanent Notes/Masking's Cost Scales Inversely With Its Visibility]] — the labor that good concealment hides, and why it goes uncompensated - [[3. Resources/Permanent Notes/Who Initiates A Disclosure Determines Who Holds Power]] — the same information means opposite things depending on who initiated the transfer - [[3. Resources/Permanent Notes/Absence of Assistive-Technology Users in Analytics Is Not Evidence of Absence]] — the measurement version: analytics cannot see assistive technology, so "we have no disabled users" is unfalsifiable from the data cited for it ## Verification — what a passing score does and does not establish - [[3. Resources/Permanent Notes/A Passing Automated Accessibility Score Is a Floor Not a Verdict]] — automation sets a floor; only manual assistive-technology testing makes a review trustworthy - [[3. Resources/Permanent Notes/Generated Accessibility Targets Do Not Transfer Verification Responsibility]] — a platform-generated accessible palette does not relieve the extension author of testing real combinations - [[3. Resources/Permanent Notes/An Accessible Interface Wrapping Inaccessible Content Relocates the Barrier]] — a conformant page linking to an untagged PDF moves the barrier rather than removing it - [[3. Resources/Permanent Notes/Accessibility for One Modality Is Not Accessibility]] — an affordance serving one assistive technology and no other is not partial coverage; a passing checker cannot see this failure because the affordance is present - [[3. Resources/Permanent Notes/Test With NVDA First Because It Hides the Fewest Markup Defects]] — which screen reader to start a manual pass on, and why the least forgiving one finds the most markup defects. - [[3. Resources/Permanent Notes/Icon-Family Swaps Need a Directionality QA Pass]] — a semantic defect automated diffing cannot see: both glyphs are valid and one points the wrong way. ## Build-time decisions that prevent remediation - [[3. Resources/Permanent Notes/Native HTML Semantics Beat Re-Implemented ARIA]] — reach for the element whose semantics already match; ARIA re-implementation tends to add errors - [[3. Resources/Permanent Notes/Format Choice Is an Accessibility Control Exercised Before Remediation]] — choosing a format that carries structure natively eliminates whole classes of later fixes - [[3. Resources/Permanent Notes/Visual Layout Must Preserve Sequential Meaning and Focus Order]] — a layout is inaccessible when visual sequence diverges from reading and focus order - [[3. Resources/Permanent Notes/Stabilization Is the Accessibility Deadline Not the Finish Line]] — once markup becomes public API, verification has to be funded before stabilization - [[3. Resources/Permanent Notes/Designing for Reading Disabilities Widens Access for Everyone]] — criterion-based typography and plain language measurably help beyond the target group - [[3. Resources/Permanent Notes/Readable Typography Depends on Letter Features Not a Branded Dyslexia Font]] — letterforms and spacing do the work, not a typeface marketed as universally accessible - [[3. Resources/Permanent Notes/Accessibility Prompting Fixes Attributes Not Interaction Patterns]] — what an accessibility prompt to an AI builder reliably buys (attributes) and reliably does not (keyboard and focus behaviour). - [[3. Resources/Permanent Notes/Icon Fonts Carry a Structural Accessibility Liability]] — format choice at selection time — private-use code points and font substitution are not patchable later. ## Making the case commercially - [[3. Resources/Permanent Notes/Machine Consumers Make Semantic Markup a Commercial Requirement]] — agents parse the same accessibility tree assistive tech reads, so semantics became a revenue condition - [[3. Resources/Permanent Notes/Accessibility Sells as Stewardship Tied to a Persona Not an Upsell]] — it closes when attached to a named user the client already wants to serve - [[3. Resources/Permanent Notes/Accessibility Remediation Inside Vendor Tooling Trades Speed for Client Autonomy]] — vendor-owned overlays move maintainability risk onto the client - [[3. Resources/Permanent Notes/Overlay Widgets Relocate Accessibility Risk Rather Than Reducing It]] — the counter-case: an overlay sits on top of the barrier, so the underlying code stays broken whatever the marketing claims - [[3. Resources/Permanent Notes/A Feature Plugin's Name Sets Expectations Its Code Cannot Meet]] — naming an accessibility feature plugin is a trust decision with disabled users, separate from what it implements. - [[3. Resources/Permanent Notes/WordPress Media Search Discards Its Best Descriptive Field]] — alt text as an unclaimed operational asset: verified in WP 7.0.2 source, Trac #22744 open. ## Procurement and conformance artifacts - [[3. Resources/Permanent Notes/A Point-in-Time Conformance Report Cannot Certify a Continuously Changing System]] — a VPAT describes the day it was written; for a site that deploys weekly, regulators want a process record instead - [[3. Resources/Permanent Notes/A Vendor Accessibility Report Is Disclosure Not Certification]] — its procurement value is that it names failures, and a vendor with none has told you something too ## Cognitive accessibility - [[3. Resources/Permanent Notes/Executive-Function Scaffolding Is a Coupled System That Fails All at Once]] — externalized executive-function supports are load-bearing and coupled, so removing one cascades rather than degrading proportionally ## Teaching and testing practice - [[3. Resources/Permanent Notes/Simulate the Barrier Not the Disability]] — an exercise teaches design when the learner hits the barrier, and stereotype when the learner performs the disability ## Gaps - Cognitive accessibility still has one note and needs more — nothing yet on memory load, plain-language thresholds, or timeout and session-expiry patterns. - Assistive-technology testing practice is now **partly** covered: [[3. Resources/Permanent Notes/Absence of Assistive-Technology Users in Analytics Is Not Evidence of Absence]] establishes why you cannot measure the audience, and the 2026-09-08 batch supplied sourced coverage numbers to the floor-not-verdict note. Still missing the operational half: which assistive technologies, which versions, who runs the test, and how screen readers differ in how much they compensate for bad markup (NVDA reading closer to the DOM than JAWS is a claim from the 2026-09-08 screen-reader session that has no note yet). - Nothing on procurement *after* selection: contractual remedies when a vendor's report proves wrong. - No note yet on event and venue accessibility as distinct from digital — the 2026-09-08 WordPress events session is a source waiting on a claim. ## Maintenance - Last tended: 2026-09-08 — added four Permanent notes from the WordPress Accessibility Day 2025 batch and strengthened the automated-coverage evidence. - [[3. Resources/Permanent Notes/Operational Uncertainty Falls Hardest on Those Who Must Plan Most]] — access failure located in operations and communication rather than in the artifact ## Synthesis additions (2026-10-05 — access in congregations and design) - [[3. Resources/Readwise/Articles/Access Sunday 2026 Get Your Resources Here!]] — Rev. Jacob Null of the UCC Disabilities Ministries Board says the Access Sunday kit supplies liturgy, a children's time script, sermon discussion videos and music, all written by volunteers with disabilities or caregiver experience, with free practices such as large print and assistive listening listed for congregations that cite cost. - [[3. Resources/Readwise/Articles/Website Redesign Phase 1 Accessibility in Figma Spindrift Blood Orange Black Tea]] — Equalize Digital's Accessibility Craft episode 184 (audio-only; the company sells Accessibility Checker) says it sent design vendors written accessibility requirements before bidding, then checked designs in review rounds. - [[3. Resources/Permanent Notes/A Low-Cost Worship Kit Lets a Congregation Without Budget Begin Disability Inclusion]] — A free denominational worship kit plus a list of no-cost practices lets a congregation that can't fund building work start disability inclusion now. - [[3. Resources/Permanent Notes/Accessibility Enforced at Authoring Time Beats Post-Hoc Auditing]] — Writing accessibility requirements into vendor briefs before design quotes is an authoring-stage control, the same upstream leverage this note describes for editor-level gates. ## Synthesis additions (2026-10-07 — theme directory policy) - [[3. Resources/Readwise/Articles/Accessibility-Ready Directory Changes Coming!]] — the WordPress Accessibility Team announces that the accessibility-ready tag becomes conditional in the Theme Directory, with no themes delisted and the tag treated as an application; the post gives the points for theme authors and reviewers (a team announcement of a plan, not a completed change) ## Synthesis additions (2026-10-07 — upstream design exclusion) - [[3. Resources/Readwise/Articles/Exclusion by Design - Michele A. Williams]] — Michele A. Williams argues in an A11yTalks session that disability drops out of products before design starts because personas, journey maps and user stories leave disabled people out, and offers a notice-question-interrupt-normalize cycle; her evidence is anecdotal. - [[3. Resources/Permanent Notes/A Persona Set Without Disabled People Is a Requirement Set Without Them]] — when personas, journey maps and user stories omit disabled people, their needs never become requirements, so no later audit sees the gap. ## Synthesis additions (2026-10-18 — registering previously unlisted notes) ### Permanent Notes - [[3. Resources/Permanent Notes/Legal-Standard and Target-Standard Are Two Separate Governance Positions]] — Organizations should document what they're legally required to meet and what they're tracking toward as separate positions, since WCAG versions reach regulators on different timelines. - [[3. Resources/Permanent Notes/The 10% Gap Names Imposter Syndrome as a Bounded Unknown]] — Naming the exact skill, credential, or circumstance you feel you're missing turns a vague sense of not belonging into a bounded gap you can address. Closest-fit placement. - [[3. Resources/Permanent Notes/Thriving Conditions Are Personal Not a Performance Signal]] — Judging a teammate by whether they thrive under your working conditions measures the fit of the environment, not the quality of the person. ### Literature Notes - [[3. Resources/Literature Notes/A Practical PDF Remediation Demo - Samantha Merrett]] — The author argues the most accessible PDF may be no PDF; when one is needed, remediate tags and reading order and test with automated tools and screen readers. - [[3. Resources/Literature Notes/ARIA, anti-patterns, and you]] — David Bushell argues the ARIA Authoring Practices Guide is a spec demonstration, not a cookbook, and native HTML should come first, especially when LLMs copy it. - [[3. Resources/Literature Notes/Autism is caused by sin (Dan McClellan)]] — Dan McClellan argues the claim that sin causes autism fails on its own terms, citing Exodus 4:11, and reframes autism as neurodivergence, not a defect. - [[3. Resources/Literature Notes/Autism with Kaelynn Partlow & Dr. Temple Grandin]] — Temple Grandin and Kaelynn Partlow argue high expectations plus accommodations help, and that credential screens remove capable people; Partlow notes limits of an employment-only focus. - [[3. Resources/Literature Notes/Designing for people with reading disabilities]] — Grace Snow argues reading disabilities sit on a spectrum, and plain language, layout rules, and letter-feature typography accommodate them at little cost with a curb-cut benefit. - [[3. Resources/Literature Notes/Oxygen Builder Accessibility Reality Check]] — Accessibility compliance is legally non-negotiable, and remediation on Oxygen Classic costs more than expected because page-builder architecture hides the controls remediators need. - [[3. Resources/Literature Notes/WCAG 3.0 Will Create a Governance Problem Most Organizations Aren't Ready For]] — The author argues WCAG 3.0's difficulty is organizational, since laws and contracts will keep citing WCAG 2.x for years while organizations track two timelines. - [[3. Resources/Literature Notes/Your Grid Lanes will likely fail WCAG 2.4.3]] — CSS Grid Lanes' shortest-lane placement ignores DOM order, so focus order diverges from visual order and will likely fail WCAG 2.4.3. ## Synthesis additions (2026-10-19 — decorative images and accessible defaults) - [[3. Resources/Readwise/Articles/Decorative Images…]] — Adrian Roselli on when an image counts as decorative and how to test it; the capture is truncated and the decision tree isn't in the text. - [[3. Resources/Readwise/Articles/Accessible by default]] — A short page from accessible-by-default.dev claiming browsers' defaults already cover much of WCAG, with live break-and-restore demos the capture can't show. The claim is unquantified. ## Synthesis additions (2026-10-19 — Permanents from the GameDev Day, agent-site and religious-history batch) - [[3. Resources/Permanent Notes/An Image Nobody Would Miss Should Be Removed and Any Other Image Isn't Decorative]] — Adrian Roselli's post gives two yes-or-no tests for an image in narrative content (not icons, not interactive controls): would any reader care if the image were removed, and would the author care if it were replaced with something unwanted.