Accessibility

Our Commitment

Probe Toolkit is committed to making our tools accessible to everyone, including people with disabilities. The web was built to be universal, and we believe every tool on this site should be usable regardless of how you navigate, read, or interact with it.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards across all of our tools and pages. Accessibility is not an afterthought here — it is part of how we build from the start.

What We Do

Here are the specific steps we take to ensure Probe Toolkit is accessible:

  • Keyboard navigation — Every tool can be operated using only a keyboard. Tab through inputs, press Enter to probe, and navigate results without ever touching a mouse.
  • Semantic HTML — We use proper heading hierarchy, landmark regions, and native HTML elements so assistive technologies can parse our pages accurately.
  • ARIA labels — Interactive elements like buttons, toggles, and dynamic panels include ARIA attributes to convey their purpose and state to screen readers.
  • Screen reader friendly results — Tool results use aria-live regions so screen readers announce new content as it appears, without requiring a page refresh.
  • High contrast ratios — Text and interactive elements meet or exceed WCAG AA contrast requirements in both our dark and light themes.
  • Responsive design — Every page and tool works on all devices and screen sizes, from mobile phones to ultrawide monitors.
  • Dark and light theme support — Choose the theme that works best for your vision and environment. Both themes maintain accessible color contrast.
  • Skip-to-content link — A skip navigation link is available at the top of every page so keyboard users can bypass the header and jump straight to the main content.

Known Limitations

We are honest about where we can improve. Some tools that render complex or highly visual output — such as the Diff Checker and Markdown Preview — may have suboptimal screen reader experiences due to the nature of their rendered output. We are actively working to improve these tools and welcome specific feedback on what would make them more usable.

If you discover an issue we have not listed here, we want to know about it.

Feedback

If you encounter an accessibility barrier on Probe Toolkit, please let us know. We take every report seriously and will work to address it as quickly as we can.

You can reach us at ethan@dispatchdb.io with details about the issue you experienced, including:

  • The page or tool where you encountered the problem.
  • A description of what happened and what you expected.
  • The assistive technology you were using (if applicable), such as your screen reader and browser.

You can also reach us through our support page. We appreciate your help in making Probe Toolkit better for everyone.