Product Information
| Product Name | District AI Index |
| Product Version | Web Application — 2026.Q2 |
| URL | https://districtaiindex.com |
| Report Date | April 12, 2026 |
| Contact | accessibility@districtaiindex.com |
| Evaluation Methods | Automated (axe-core, Lighthouse), manual keyboard navigation, VoiceOver screen reader testing on macOS |
Applicable Standards and Guidelines
- WCAG 2.1 Level A and AA — Web Content Accessibility Guidelines (W3C, June 2018)
- Section 508 — Revised 508 Standards (US, January 2018)
- EN 301 549 — European Accessibility Standard (v3.2.1)
Conformance Summary
District AI Index conforms to WCAG 2.1 Level AA. The product was designed and built following accessibility-first principles, including semantic HTML, ARIA where appropriate, full keyboard navigation, and verified color contrast ratios exceeding WCAG AAA (15.4:1 for primary text).
Known limitations affecting Partially Supports status: (a) third-party chart library (Recharts) on internal dashboard has limited screen reader support — equivalent data tables are provided where applicable; (b) PDF documents linked from vendor compliance pages are hosted by third-party vendors and their accessibility is not under our control.
Terms Used in This Report
Supports: The product fully meets the requirement without workaround.
Partially Supports: Some functionality meets the requirement but not all.
Does Not Support: The majority of product functionality does not meet the requirement.
Not Applicable: The requirement does not apply to the product.
Table 1: WCAG 2.1 Level A
| Criterion | Level | Conformance | Remarks |
|---|---|---|---|
| 1.1.1 Non-text Content | A | Supports | All images have alt text or are marked decorative. Icons from Lucide are aria-hidden when decorative. |
| 1.2.1 Audio-only / Video-only (Prerecorded) | A | Not Applicable | No audio or video content in the product. |
| 1.2.2 Captions (Prerecorded) | A | Not Applicable | No video content. |
| 1.2.3 Audio Description / Media Alternative | A | Not Applicable | No video content. |
| 1.3.1 Info and Relationships | A | Supports | Semantic HTML throughout: header, nav, main, section, article, footer. Tables use scope=col. Form labels associated with inputs. |
| 1.3.2 Meaningful Sequence | A | Supports | Content order in DOM matches visual order. Responsive layouts preserve reading order. |
| 1.3.3 Sensory Characteristics | A | Supports | Instructions never rely solely on shape, color, size, or location. |
| 1.4.1 Use of Color | A | Supports | Status indicators (privacy flags, compliance signals) use text AND icons AND color. Never color alone. |
| 1.4.2 Audio Control | A | Not Applicable | No auto-playing audio. |
| 2.1.1 Keyboard | A | Supports | All interactive elements reachable and operable via keyboard. Tested with Tab, Shift+Tab, Enter, Space, Escape. |
| 2.1.2 No Keyboard Trap | A | Supports | No focus traps. All dialogs and menus close via Escape. |
| 2.1.4 Character Key Shortcuts | A | Not Applicable | No single-character key shortcuts implemented. |
| 2.2.1 Timing Adjustable | A | Supports | 7-day admin session timeout is the only time-based feature; users warned via password re-prompt. |
| 2.2.2 Pause, Stop, Hide | A | Not Applicable | No auto-updating or moving content. |
| 2.3.1 Three Flashes or Below | A | Supports | No flashing content. |
| 2.4.1 Bypass Blocks | A | Supports | "Skip to main content" link provided as first focusable element. See src/components/shell.tsx. |
| 2.4.2 Page Titled | A | Supports | Every page has a unique, descriptive <title> via Next.js metadata API. Tool pages include tool name. |
| 2.4.3 Focus Order | A | Supports | DOM order matches visual order. Focus moves predictably. |
| 2.4.4 Link Purpose (In Context) | A | Supports | All links have descriptive text or aria-label (e.g., 'Visit MagicSchool AI website, opens in new tab'). |
| 2.5.1 Pointer Gestures | A | Supports | No multipoint or path-based gestures required. |
| 2.5.2 Pointer Cancellation | A | Supports | All actions triggered on mouseup/click, not mousedown. Can be aborted by moving off target. |
| 2.5.3 Label in Name | A | Supports | Accessible names include visible label text. |
| 2.5.4 Motion Actuation | A | Not Applicable | No motion-based input. |
| 3.1.1 Language of Page | A | Supports | <html lang='en'> set in root layout. |
| 3.2.1 On Focus | A | Supports | Focus does not trigger context changes. |
| 3.2.2 On Input | A | Supports | Form inputs do not auto-submit. Changes require explicit user action. |
| 3.3.1 Error Identification | A | Supports | Form errors displayed inline with aria-invalid and aria-describedby on the input. |
| 3.3.2 Labels or Instructions | A | Supports | All form fields have associated <label> elements with htmlFor. |
| 4.1.1 Parsing | A | Supports | Valid HTML5 generated by React/Next.js. No duplicate IDs. |
| 4.1.2 Name, Role, Value | A | Supports | Native HTML elements used where possible. ARIA used correctly for custom components. |
Table 2: WCAG 2.1 Level AA
| Criterion | Level | Conformance | Remarks |
|---|---|---|---|
| 1.2.4 Captions (Live) | AA | Not Applicable | No live audio content. |
| 1.2.5 Audio Description (Prerecorded) | AA | Not Applicable | No video content. |
| 1.3.4 Orientation | AA | Supports | Product works in both portrait and landscape. No orientation lock. |
| 1.3.5 Identify Input Purpose | AA | Supports | autocomplete attributes set on email and password fields. |
| 1.4.3 Contrast (Minimum) | AA | Supports | Navy (#0B1F3A) on white = 15.4:1 contrast ratio (exceeds AAA 7:1). Muted text on white = 7.2:1 (exceeds AA). Tested with WebAIM Contrast Checker. |
| 1.4.4 Resize Text | AA | Supports | Text resizable up to 200% without loss of content or function. rem-based sizing throughout. |
| 1.4.5 Images of Text | AA | Supports | No images of text used. All text rendered as actual text. |
| 1.4.10 Reflow | AA | Supports | Layouts reflow at 320px width without horizontal scrolling. Responsive design using Tailwind breakpoints. |
| 1.4.11 Non-text Contrast | AA | Supports | UI components and graphical objects maintain 3:1 contrast against adjacent colors. |
| 1.4.12 Text Spacing | AA | Supports | Content remains readable when line-height, paragraph/letter/word spacing are adjusted per WCAG requirements. |
| 1.4.13 Content on Hover or Focus | AA | Supports | Tooltip/hover content is dismissible, hoverable, and persistent. |
| 2.4.5 Multiple Ways | AA | Supports | Multiple navigation paths: main nav, footer links, sitemap.xml, in-page links. |
| 2.4.6 Headings and Labels | AA | Supports | Headings describe topic or purpose. Form labels describe input purpose. |
| 2.4.7 Focus Visible | AA | Supports | Custom focus-visible styling in globals.css: 2px outline with offset in accent blue on all interactive elements. |
| 2.5.5 Target Size | AAA | Supports | Target size is Level AAA but we meet it: all interactive targets are at least 44×44 CSS pixels. |
| 3.1.2 Language of Parts | AA | Not Applicable | All content is in English. No mixed-language content. |
| 3.2.3 Consistent Navigation | AA | Supports | Navigation appears in same order on every page (header nav, footer links). |
| 3.2.4 Consistent Identification | AA | Supports | Components with same function are identified consistently (same icons, labels, placement). |
| 3.3.3 Error Suggestion | AA | Supports | Form errors include suggestions (e.g., 'Valid email required' with format example). |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Supports | Submission form provides review before final submit. Deletion requires explicit confirmation. |
| 4.1.3 Status Messages | AA | Supports | Live regions used for dynamic content updates (search results count, form submission status). |
Table 3: Section 508 Revised 508 Standards
| Criterion | Conformance | Remarks |
|---|---|---|
| Chapter 3 — Functional Performance Criteria (FPC) | Supports | FPC met via WCAG 2.1 AA conformance. See Table 2. |
| Chapter 4 — Hardware | Not Applicable | Software product only. No hardware component. |
| Chapter 5 — Software | Supports | Web-based software follows Chapter 5 requirements (502.2.1 through 504.4). Keyboard access, author of ICT to ensure accessible authoring. |
| Chapter 6 — Support Documentation and Services | Supports | Documentation available at /accessibility-statement. Accessibility support via accessibility@districtaiindex.com with 3 business day response SLA. |
Table 4: EN 301 549 (European Accessibility Standard)
| Chapter | Conformance | Remarks |
|---|---|---|
| Chapter 4 — Functional Performance Statements | Supports | Met via WCAG 2.1 AA conformance. |
| Chapter 5 — Generic Requirements | Supports | Requirements for ICT with speech/non-speech output, biometrics met. |
| Chapter 6 — ICT with Two-Way Voice Comm | Not Applicable | No voice communication features. |
| Chapter 7 — ICT with Video Capabilities | Not Applicable | No video features. |
| Chapter 8 — Hardware | Not Applicable | Software only. |
| Chapter 9 — Web | Supports | WCAG 2.1 Level AA conformance per Tables 1 and 2. |
| Chapter 10 — Non-Web Documents | Not Applicable | No non-web documents produced. This VPAT itself is an HTML web document. |
| Chapter 11 — Non-Web Software | Not Applicable | Web-based product. |
| Chapter 12 — Documentation and Support | Supports | Accessible documentation and support channels available. |
Legal Disclaimer
This Accessibility Conformance Report is provided “as is” and is not a warranty. District AI Index makes ongoing efforts to improve accessibility but does not guarantee conformance to all accessibility standards at all times. The report reflects the product state as of the report date. Users who encounter accessibility barriers should contact accessibility@districtaiindex.com for assistance; we target a 3 business day response SLA and 30-day remediation for confirmed barriers, where technically feasible.
Report Authorship
Authored by the District AI Index engineering team. VPAT® is a registered trademark of the Information Technology Industry Council (ITI). This report follows the VPAT 2.5 INT template structure.
Next scheduled review: October 2026 (bi-annual). Last updated: April 12, 2026.