Accessibility Statement

Conformance status

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. WCAG 2.1 defines requirements for designers and developers to improve accessibility for people with disabilities — visual, auditory, physical, speech, cognitive, language, learning, and neurological.

This site is partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not yet fully conform to the accessibility standard. The known limitations are listed below.

Measures taken to support accessibility

• Automated accessibility testing — axe-core runs against every release branch as a CI gate. The build fails if any page generates accessibility violations on the eight representative routes (/, /json-formatter, /regex, /jwt, /flow-visualizer, /markdown, /data-masker, /cron-builder). The full audit covers tags wcag2a, wcag2aa, wcag21a, and wcag21aa.
• Manual keyboard testing — every interactive element on every page is reachable and operable using a keyboard alone (Tab, Shift+Tab, Enter, Space, arrow keys).
• Screen-reader compatibility — pages have been spot-checked with VoiceOver (macOS) and NVDA (Windows). All form inputs have associated labels via either <label htmlFor> or aria-label. Icon-only buttons carry aria-label. Live regions for toast notifications use role="status".
• Colour contrast — semantic Tailwind tokens (bg-background, text-foreground, border-border) are tuned so that all text meets the WCAG AA contrast ratio (4.5:1 for normal text, 3:1 for large text and UI components). Both light and dark modes are checked.
• No-flash dark mode — the theme is bootstrapped before React hydration to prevent the white-flash → dark-flash sequence that can trigger vestibular and seizure conditions.
• Skip link — every page has a keyboard-only "Skip to main content" link as the first focusable element.
• Reduced motion — animations respect prefers-reduced-motion. Animations are not used to convey information.
• Open-source review — the codebase is open at github.com/usmt-cop. Anyone can audit the accessibility implementation and propose improvements.

Known limitations

We are aware of the following limitations and are working on them:

• Visualisation tools (Flow Visualizer, ERD Generator, Mermaid Playground, SF Dependencies, Regex Visualizer) — the Mermaid-rendered SVG diagrams do not currently include programmatic structure that screen readers can interpret. The text source from which the diagram is generated is always available alongside the diagram and is fully accessible. We plan to add ARIA descriptions to the rendered SVGs in a future release.
• Image-based tools (Image Converter, Favicon Generator) — the live previews of generated images are alt-text-described in their visual sense ("Preview at 32×32 px"), but the actual rendered pixels are not described. This is acceptable for a tool whose explicit purpose is to produce an image.
• Drag-and-drop interactions (Dashboard pinned-tool reordering, file upload zones) — keyboard alternatives exist (use the buttons next to drag handles, or the file picker), but the drag-and-drop affordance itself is mouse-first.
• Programmable text editors (Rich Editor, JSON Formatter) — line-numbered text editors are inherently complex for screen readers. We use <textarea> rather than custom contentEditable widgets specifically because <textarea> has well-defined screen-reader behaviour.

Compatibility with assistive technologies

The site is designed to be compatible with:

• Screen readers — VoiceOver (macOS, iOS), NVDA (Windows), JAWS (Windows), TalkBack (Android).
• Voice control — Voice Control (macOS), Dragon NaturallySpeaking.
• Keyboard-only navigation — full coverage on every page.
• Browser zoom — pages reflow correctly up to 200% zoom without horizontal scrolling on a desktop layout.
• High-contrast mode — respects the system high-contrast preference.

The site has been tested in the latest two major versions of Chrome, Firefox, Safari, and Edge.

How to report issues

If you encounter an accessibility barrier on this site, we want to know. Please report it via:

• Email — [email protected]. Use the subject line [A11y] for fastest routing.
• GitHub Issues — open an issue with the accessibility label.

When reporting, please include:

• The URL of the page where the issue occurred.
• The assistive technology you were using (if any).
• A description of what didn't work as expected.

We aim to acknowledge accessibility reports within 7 days and resolve them in a future release. Critical issues (a tool that is completely unusable for a user with assistive technology) are prioritised.

Formal complaints

If you are unable to access content on this site and our response does not satisfy you, you may file a formal complaint with the appropriate accessibility authority in your jurisdiction (for example, the U.S. Department of Justice for ADA, or the European Commission for the EU Web Accessibility Directive).