PulseSignal should work for everyone.

Standard

What we conform to.

PulseSignal targets the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across all customer-facing surfaces. Where Level AAA criteria are reasonable without sacrificing usability (for example, contrast on body copy), we adopt them.

Our long-term commitment also covers EN 301 549 (EU accessibility standard) and the relevant Section 508 refresh criteria for U.S. federal procurement.

Commitments

The non-negotiables.

• WCAG 2.2 Level AA is our baseline target across marketing pages, the dashboard, and authenticated workflows.
• Every interactive element is reachable by keyboard alone, with a visible focus indicator that meets 3:1 contrast against its background.
• Modals and drawers trap focus while open and return focus to the trigger element on close.
• Form fields are associated with labels via `<label htmlFor>` or `aria-labelledby`; error messages are wired via `aria-describedby`.
• Status and severity never rely on color alone — we pair color with an icon and a text label.
• Animations respect `prefers-reduced-motion`. Motion is decorative, not load-bearing.
• Images carry meaningful `alt` text. Decorative images use `alt=""` so screen readers skip them.
• Page structure uses semantic landmarks (`<main>`, `<nav>`, `<footer>`) and a sensible heading hierarchy.

How we test

Assistive technologies in our loop.

• axe-core (automated)

  Runs in CI on every pull request against the public marketing pages and authenticated dashboard shells.

• VoiceOver (macOS / iOS)

  Manual smoke pass on critical user flows: sign-up, first company add, briefing read, billing.

• NVDA (Windows)

  Manual smoke pass on the same critical flows quarterly.

• Keyboard only

  Full Tab / Shift+Tab / Enter / Space traversal of every interactive page.

• Browser zoom 200%

  Layout must remain usable at 200% zoom in Chrome, Safari, and Firefox.

Known gaps

We will be honest with you.

We will not claim full conformance we have not yet earned. Here is what we know is incomplete today:

• High-contrast and full dark-mode coverage are not yet implemented across the dashboard. Marketing pages render correctly in OS-level dark mode but the dashboard surfaces are tuned for light backgrounds.
• A subset of complex chart components (heatmaps, timeline scrubs) do not yet expose tabular data alternatives. We provide a CSV export for every chart-driven view as the current screen-reader-friendly fallback.
• Some marketing animations (the hero globe, the signal-flow diagram) do not have a static-still fallback. They are decorative and skipping them with `prefers-reduced-motion` removes them entirely.
• Video captions and transcripts will be required once we publish marketing videos. There are no published videos at the time of writing.

Roadmap

In flight.

• Storybook a11y addon (axe + jest-axe) integrated for component-level checks alongside the page-level CI gate.
• Per-route Lighthouse a11y score gate ≥95 in CI.
• Skip-to-main-content link audit across every layout.
• Color contrast verification of the full token palette against WCAG 2.2 AA and AAA where feasible.
• Documented accessible patterns for charts (tabular fallback, data download, ARIA live regions for updates).