Skip to content

Accessibility Statement

FireAlertedLast Updated: May 31, 2026

FireAlerted is committed to making this site usable by everyone — regardless of device, assistive technology, or ability. This statement covers what we've done, what we know we haven't done yet, and how to tell us if you hit a barrier.

Our commitment

We conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA as the international standard for accessible web content. We also align with the Americans with Disabilities Act (ADA) Title III as it applies to public accommodations on the web, and with Section 508 of the Rehabilitation Act where it is relevant. Accessibility is an ongoing effort, and we re-test as the site evolves.

What we've done

  • Skip-to-content link on every page — The first focus stop on any page lets keyboard and screen-reader users jump past the navigation straight to the main content.
  • Keyboard navigation — The header navigation, footer, FAQ accordions, and forms are operable with Tab, Shift+Tab, Enter, and Escape — without focus traps.
  • One main landmark and one H1 per page — Each page exposes a single <main> region and a single top-level heading, with a logical heading order and semantic <nav>, <main>, and <footer> regions.
  • Screen-reader-friendly forms — Form fields use programmatic <label> associations, with aria-invalid and aria-describedby on validated fields and validation errors announced via role="alert".
  • Visible focus indicators — A global :focus-visible outline marks the focused control for keyboard users; we do not remove focus outlines.
  • Color contrast — Body and muted text are tuned at the design-token layer to meet the WCAG AA 4.5:1 minimum for normal text (we replaced a previously low-contrast gray).
  • Reduced motion — Every animation honors the prefers-reduced-motion setting. If your operating system asks for reduced motion, the site is delivered effectively static.
  • Current-page and breadcrumb cues — Active navigation links carry aria-current="page", and breadcrumb trails use a labeled <nav> with the current page marked.
  • Decorative graphics hidden from assistive tech — Decorative icons, SVGs, and background shapes are marked aria-hidden="true"; icon-only controls carry an accessible name.
  • Language declared — The document declares <html lang="en"> so assistive technology pronounces content correctly.
  • Accessible interactive map — The coverage map has a keyboard-operable text alternative — a list of covered states with live-announced details — so the same information and navigation are available without a mouse or any dragging (WCAG 2.5.7).
  • Minimum target sizes — Interactive controls meet the WCAG 2.2 minimum target size of 24×24 CSS pixels (2.5.8); small icon buttons were enlarged to a full tap area.
  • Focus is never obscured — Scroll padding keeps any focused or linked-to element clear of the sticky header, so the focused control is always visible (WCAG 2.2 — 2.4.11).
  • Accessible authentication — Login supports password managers (autocomplete) and never requires solving a cognitive puzzle; pasting is allowed (WCAG 2.2 — 3.3.8).
  • Consistent help & no redundant entry — Help and contact links appear in a consistent place across pages (3.2.6), and our forms never ask you to re-enter information you already provided in the same step (3.3.7).

What we know we haven't done yet

We test continuously with both automated tools (axe and Lighthouse) and manual keyboard and screen-reader checks. A small honesty layer remains:

  • Independent certification audit — Our conformance is verified by our own automated and manual testing. A formal audit by an external certified accessibility consultancy is planned as a periodic check.
  • Alternative formats on request — We do not auto-generate content in alternative formats (audio, braille, large-print), but we will provide any information through an alternative means promptly on request (see below).
  • Third-party widgets — The privacy-friendly CAPTCHA challenge on our forms is provided by a third party and is kept accessible, but its internals are partly outside our editorial control.

Report an access barrier

If you can't use part of this site, please tell us through our contact form. We aim to respond within 5 business days and will work with you to provide the information or function you need through an alternative means. Please include:

  • The URL (web address) where you hit the barrier.
  • A description of what you were trying to do and what happened.
  • Your browser, operating system, and assistive technology, if it helps.

Legal references

This statement aligns with WCAG 2.2 (W3C) and acknowledges the Americans with Disabilities Act, Title III (42 U.S.C. § 12181 et seq.) and Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. § 794d). Where any state or local accessibility regulation imposes a stricter standard, we aim to apply the higher bar.

Contact

Accessibility feedback and requests: firealerted.com/#contact. This statement is owned by the FireAlerted team and is reviewed as the site evolves.