Accessibility statement

• Color contrast: all body and interactive text meets WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text) in both light and dark mode.
• Color is never the sole signal: every severity and status indicator pairs color with text and an icon.
• Keyboard navigation: every interactive element is reachable with the keyboard and has a visible focus ring.
• Screen-reader support: semantic HTML, ARIA labels on icon-only controls, descriptive link text, and a logical heading hierarchy.
• Responsive design: fully usable at 375px and above. Tables collapse to stacked cards on mobile. No horizontal scroll on main content.
• Reduced motion: respects the prefers-reduced-motion media query — animations and transitions are reduced to near-zero when the OS preference is set.
• Tap targets: primary interactive controls meet WCAG 2.2 minimum target size (24×24 CSS px) on mobile breakpoints; most exceed 44×44.
• Forms: visible labels, descriptive errors, focus management on validation.

We test continuously, but areas under active improvement include:

• Embedded videos and rich data visualizations (when added) will need additional alternative-format support.
• Dynamically generated open-graph images include the headline as text in the rendered PNG; we plan to expose an HTML-text equivalent for assistive technology.
• The admin dashboard is currently optimized for sighted keyboard users; full screen-reader review is scheduled before public Pro launch.

If you encounter an accessibility barrier, please tell us so we can fix it. Email editorial@aiincidenttracker.com with the subject line "Accessibility" and include:

• The URL of the page where you encountered the issue.
• A description of the problem and what you were trying to do.
• The assistive technology you were using, if any (screen reader, voice control, etc.).
• The browser and operating system.

We aim to acknowledge accessibility reports within one business day and to prioritize fixes for blocking issues over normal feature work.

The Service is designed to be compatible with current versions of:

• Browsers: Chrome, Firefox, Safari, Edge — current and one previous major version.
• Screen readers: VoiceOver (macOS, iOS), NVDA (Windows), JAWS (Windows), TalkBack (Android).
• Operating systems: macOS, Windows, iOS, Android — current and one previous major version.

Accessibility is evaluated with a combination of automated tools (Lighthouse, axe DevTools, and our own visual-QA inspector that runs in CI on every commit) and manual review. See our Methodology for how we integrate quality gates into the publishing process.