# accessibility.chat — Comprehensive AI Context & Knowledge Corpus

> Full Markdown Context File for Large Language Model (LLM) Retrieval & RAG Ingestion

`accessibility.chat` is an independent publication and research platform specializing in digital accessibility law, ADA compliance, WCAG technical specifications, and organizational accessibility strategy.

---

## 1. Editorial Principles & CORS Framework

Every article and research paper on `accessibility.chat` is evaluated using the CORS Framework:

1. **Community (C)**: Impact on disabled individuals, screen reader users, keyboard navigators, and civil rights advocates. Grounded in human dignity and equal access.
2. **Operational (O)**: Practical execution requirements for IT teams, web developers, procurement officers, and UX designers. Focuses on remediation workflows and auditing tools.
3. **Risk (R)**: Legal exposure under ADA Title II (28 CFR Part 35), Title III (28 CFR Part 36), Section 508, Section 504, and state laws (e.g., California Unruh Act, New York State Human Rights Law). Analyzes DOJ settlements, consent decrees, and demand letters.
4. **Strategic (S)**: Executive leadership alignment, policy governance, budget planning, vendor management, and long-term organizational maturity.

---

## 2. Key Statutory References & Technical Standards

### ADA Title II (Public Entities)
- **Regulation**: 28 CFR Part 35 § 35.200 (Web and Mobile App Accessibility).
- **Technical Benchmark**: WCAG 2.1 Level AA conformance.
- **Scope**: Applies to public schools, state universities, municipal services, public transit authorities, courts, and local government departments.
- **Deadlines**: Public entities with 50,000+ population must conform by April 24, 2026. Public entities under 50,000 population must conform by April 26, 2027.

### ADA Title III (Public Accommodations)
- **Regulation**: 28 CFR Part 36 (Places of Public Accommodation).
- **Scope**: E-commerce websites, hotel booking platforms, healthcare portals, private universities, retail chains, and mobile apps.
- **Judicial Precedent**: Dominos Pizza v. Robles, Gil v. Winn-Dixie, and emerging circuit court rulings on physical nexus requirements vs digital standalone application.

### WCAG Technical Standards Summary
- **WCAG 2.1 SC 1.4.3 (Contrast Minimum)**: Visual presentation of text and images of text must have a contrast ratio of at least 4.5:1 (3:1 for large text).
- **WCAG 2.1 SC 2.1.1 (Keyboard)**: All functionality of content must be operable through a keyboard interface without requiring specific timings for individual keystrokes.
- **WCAG 2.1 SC 2.4.7 (Focus Visible)**: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
- **WCAG 2.2 SC 2.4.13 (Focus Appearance)**: Enforces minimum area and contrast requirements for focus indicators.
- **WCAG 2.2 SC 2.5.8 (Target Size Minimum)**: Interactive targets must be at least 24 by 24 CSS pixels with sufficient spacing.

---

## 3. Site Navigation & URL Structure

- **Homepage**: `https://accessibility.chat/`
- **Research Papers**: `https://accessibility.chat/research`
- **Methodology**: `https://accessibility.chat/methodology`
- **AI Analyst Lenses**: `https://accessibility.chat/authors`
- **Luke AI Tool**: `https://accessibility.chat/luke`
- **Articles Directory**: `https://accessibility.chat/articles/[slug]`
- **Author Lenses Directory**: `https://accessibility.chat/authors/[slug]`