Accessibility — Overview

25 Apr, 2026

Note: This is a living note, an auto generated page synthesized by my self updating second brain managed by Claude. While it's input was my actual organic writing, this is an AI summary/extraction/synthesis part of my The Living Notes section.

If you prefer to read my organically written words or work, please go to any of the other nav links besides living-note or a page, route, or tag without #living-note.

Accessibility — Overview

Contents

• #My Position
• #Core Framework
• #Key Domain Areas
• #The Business Case
• #ADA Accommodation as Assistive Tech Distribution
• #Convincing Organizations to Invest
• #Disability Categories — Working Knowledge
• #Social Communication as Accessibility Gap
• #WCAG vs. Reality
• #AI and Accessibility
• #Key External Resources
• #Accessibility Metrics and Organizational Alignment
• #Nike: Disability-Inclusive Brand Positioning
• #Scale and Automation
• #Employment AT Gap
• #Operating Model and the Paradox of Progress
• #Google Accessibility: AI Fills the Human-Created Gap
• #Enterprise Playbook and Testing Depth
• #Cognitive, Behavioral, Trauma-Informed, Emotional A11y (AccessU 2026)
• #Sell Outcomes, Not A11y (AccessU 2026)

My Position

Accessibility is not a compliance checklist — it's a human right and an engineering discipline. I approach it as both, fluent in the business case and the moral imperative.

My edge: autistic lived experience + production engineering depth. I find barriers that tools miss. I fix them in code, not just report them.

Core Framework

The 97% gap: ~97% of the web has measurable accessibility issues. The problem isn't lack of awareness — it's lack of scalable, systematic solutions. Scale requires:

1. Automation (but automation alone misses ~30% of issues)
2. Embedded expertise (engineers who understand accessibility as a non-functional requirement)
3. Culture shift (leadership buy-in, incentive alignment)

Non-functional requirement model: Treat accessibility like security — not an afterthought, not optional, built into every sprint from the start.

Competency over dependency: Don't become the single person everyone pings. Train the team. Build the systems. Leave competency behind.

Key Domain Areas

The Business Case

• Legal exposure: ADA lawsuits trending up
• Market expansion: ~26% of US adults have a disability (28.7% per CDC, ~60–70M people); globally 1.3B (16%, WHO)
• Performance: accessible sites tend to be faster, cleaner
• SEO: Google's algorithm now ranks accessible websites higher; 71% of disabled users leave inaccessible sites
• Customer loyalty: 66% of consumers pay more for socially impactful companies; exclusionary experiences lose multi-generational LTV
• Gap Inc. example: strategy projected at $300M–600M annual revenue uplift — derived from $5.7B e-commerce base × 5–10% WCAG conversion uplift. Full document:
• Legal risk at Gap specifically: at least 9 lawsuits in 5+ years against Gap Inc. and subsidiaries

ADA Accommodation as Assistive Tech Distribution

The companion healthcare provider template letter (April 2026) completes the two-document strategy: the provider letter creates the legal obligation (documenting disability, functional limitations, and specific accommodation); the whitepaper removes the technical excuse. The letter also frames SIGNAL as a technological job coach — connecting to established legal precedent (EEOC v. Party City, 2018) for in-person job coaches as reasonable accommodation. This makes providers a distribution channel: every clinician treating autistic adults becomes a potential SIGNAL referral source.

The VPAT / Accessibility Conformance Report is now complete (April 6, 2026). SIGNAL v1.0 conforms to WCAG 2.1 Level AA (with one partial support: 4.1.3 Status Messages, fix in v1.1), Section 508, and EN 301 549. Tested with axe, WAVE, Lighthouse, pa11y, NVDA, JAWS, VoiceOver, and 12 disabled user testers. This completes the four-pillar strategy: job coach positioning, assistive tech framing, security whitepaper, and VPAT — now enabling GSA Schedule, state/local government, and enterprise vendor qualification procurement.

Convincing Organizations to Invest

Disability Categories — Working Knowledge

• Cataracts = clarity problem (blurry lens); Glaucoma = field of vision problem (peripheral loss, tunnel vision, irreversible). Both benefit from high contrast and zoom/reflow.

• Transcripts vs. captions: transcripts serve a broader population than captions — deafblind users via braille display (at own pace), cognitive/learning disabilities, non-native speakers, low vision, situational. Deafblind users cannot use captions; they need transcripts.

• Braille display UX: 40–80 character width makes verbose aria-label text tedious. Concise link text matters more here than for audio screen reader users.

• Global scale: 33M+ blind globally (most over 50), 246M with low vision (90% in low-income settings), 466M deaf or hard of hearing.

• Speech disabilities (added 2026-04-23): range from mildly slurred to total inability to speak. Key distinction: inability to speak is independent of language capability — a person may read, write, and understand fully. Caused by underlying disabilities; trajectory varies. AAC devices cover three types: single-meaning pictures (no literacy required), alphabet-based systems, semantic compaction.

• 11% of US adults have mobility disabilities (CDC) — larger than the deafblind population and comparable to low vision globally.

• Fine motor / dexterity impairments affect keyboard use directly — a distinct failure mode from screen reader or vision access patterns. Keyboard-only access serves both this population and deafblind users.

• Muscle fatigue creates time-sensitive barriers — tasks requiring sustained effort or speed are disproportionately affected.

• Body size/shape disorders (dwarfism, obesity, arthritis) produce access barriers in physical AND digital environments — often overlooked.

• Notably, body shaming and social discrimination are listed as explicit common barriers alongside physical ones — confirming that the attitudinal dimension of exclusion applies across all disability categories, not just the neurological.

Personal observation: Studying these categories, Tawsif identified with Luiz Perez (blind a11y champion who takes photographs) — "He reminded me of myself. How despite my social disability from autism, I can still socialize and be highly functional." The cross-disability insight: disability doesn't eliminate capability, it reshapes it. Also: deafness and autism both produce social isolation via different mechanisms — "totally different cause from my autism, but the effect is the same." This is the lived framing behind SIGNAL's broadened social disability thesis.

• Cognitive disabilities (intellectual disability, dyslexia, dysgraphia, dyscalculia, ADHD, ASD) — the ASD section formally defines characteristics (sensory issues, communication difficulties, social overwhelm) that directly mirror SIGNAL's target population. ADHD co-occurrence with ASD reinforces the multi-disability design space.
• Neurological disabilities (migraine, stroke, vestibular disorders, cerebral palsy, MS, seizure, photosensitive epilepsy) — photosensitive epilepsy and vestibular disorders have direct WCAG implications (2.3.1 Three Flashes; 2.3.3 Animation from Interactions). Migraine is the world's second most common disability.
• Psychological disabilities (anxiety disorders — GAD, panic, social anxiety; mood disorders — depression, mental-health, SAD, self-harm) — social anxiety disorder produces overlapping barriers with ASD-related social disability through entirely different mechanisms. This is another instance of the "same effect, different cause" pattern Tawsif identified with a deaf colleague's experience vs. his own autism.
• Also: Eli Chadwick case — full-time software engineer with RSI using eye tracking + voice control + ergonomic peripherals. Confirms motor/dexterity disabilities affect knowledge workers directly.

Social Communication as Accessibility Gap

WCAG vs. Reality

WCAG covers what can be standardized. Real-world neurodivergent experience reveals gaps:

• Cognitive load not fully addressed
• Social context and language complexity under-specified
• Dynamic interface patterns (SPAs, infinite scroll) not well covered
• Automated tools miss ~30–40% of real issues
• Social disability as a cross-cutting functional limitation — not a diagnostic category, but a common outcome of autism, alexithymia, ADHD, TBI, and age-related decline (raised this in COGA community review)

See wcag for detailed notes.

AI and Accessibility

Growing intersection. LLMs can:

• Generate alt text at scale
• Identify ARIA pattern violations
• Assist with plain language rewrites
• Power assistive interfaces

But: AI-generated accessibility can also create new barriers (hallucinated alt text, over-confident remediation). Need human review.

See ai-a11y for detail.

Key External Resources

• Deque / axe — leading testing toolchain; good for what it catches
• Level Access — consultancy; strong on enterprise strategy
• W3C WAI — standards body; COGA task force relevant for cognitive. I'm actively participating in COGA community meetings (as of 2026-03/04) — contributed social disability concept, late diagnosis advocacy, functional needs framing feedback.
• AudioEye — tool + services; interesting overlap/competition for consulting
• Sheri Byrne-Haber — accessibility strategist; worth following
• Luis Perez — blind photographer and accessibility advocate. Cross-disability identification: "He reminded me of myself. How despite my social disability from autism, I can still socialize and be highly functional." Demonstrates disability reshapes capability, doesn't eliminate it — the lived evidence behind SIGNAL's thesis.
• CSUN — annual conference; primary professional community

Accessibility Metrics and Organizational Alignment

Why measure: Diagnose gaps, communicate ROI, shape budget decisions, create narrative of progress. Critical warning: Don't measure everything — analysis paralysis from too much data.

Framework: Digital Accessibility Maturity Model (DAMM).

Four core metric categories:

• Evaluations and remediation rate (ROI, compliance, RFP)
• Range of WCAG success criteria covered (VPAT/ACR, legal risk, SDLC gaps)
• Training completion rates (culture, role-based training)
• Test coverage and automation scope (conformance monitoring, issue patterns)

Iterative improvement loop: Identify (testing reveals pattern) → Diagnose (component problem? knowledge gap? both?) → Deploy (focused tactic with clear milestones).

Quarter-by-quarter example: Q1 = Training, Q2 = Remediation, Q3 = Documentation.

ROI talking points:

• Fixing 3 buttons can bring in 16–25% more of the population
• Post-fix a11y ROI estimated at 50%
• ROI often = money saved, not money made
• Identified issues should be fixed within 90 days

Nike: Disability-Inclusive Brand Positioning

Scale and Automation

Employment AT Gap

• Employee Advocacy and Thought Leadership: Garden metaphor (plant/water/weed/tend to thrive) as a culture-building framework. Key quote: "accessibility moves at the speed of trust" — Quemuel, MTA Chief Accessibility Officer. Internal wins include consolidating scattered docs and embedding a11y into marketing/design/devops workflows.
• How to Influence Change as an A11y Advocate: Practical guide covering the 3 Es teaching framework (Educate/Engage/Entertain), pushback one-liners, community resources, and the principle "call people in before calling them out."
• A11y Presentation Notes: Comprehensive WCAG POUR training material — clearest single-source breakdown of multimedia types (captions vs subtitles vs transcripts vs audio description vs sign language), monitoring frameworks, ARIA usage with HTML5, and the Tim Cook / Berners-Lee business case quotes.

Operating Model and the Paradox of Progress

Google Accessibility: AI Fills the Human-Created Gap

Enterprise Playbook and Testing Depth

• A11y Playbook for Enterprise Applications: Three-level embedded model — Level 1 (individual code habits: tab before commit, accessible names, native elements, keyboard triggers, screen reader pass), Level 2 (component strategy: every shared component must define keyboard behavior, focus state, accessible name source, error state), Level 3 (team habits by role: designer, developer, QA). Four broken patterns: a11y as a phase, component drift, ownership ambiguity, tool over-reliance. Four hidden blockers: distributed teams, legacy code, velocity metrics, incomplete requirements. Key insight: prevention rarely looks productive, but prevention reduces rework.
• Advanced Strategies for Web A11y Testing: The 70% manual threshold is reinforced — automated tools catch ~30%, the rest requires judgment. Dynamic interface failure modes enumerated: SPA route transitions, auto-updating data, blocking overlays, lazy load, live regions. Core failure pattern: DOM replacement resets the virtual cursor and destroys task continuity. Testing sequence: before/after state transition, trace full focus sequence, confirm announcements match visual changes, verify programmatic state exposure, document behavioral differences not just code defects.

Cognitive, Behavioral, Trauma-Informed, Emotional A11y (AccessU 2026)

Sell Outcomes, Not A11y (AccessU 2026)

#a11y #accessibility #domain #expertise #living-notes #wcag