Skip to main content
Dev Utilities Pro

Accessibility Statement

Dev Utilities Pro is committed to making our calculators and content usable by the widest possible audience, including people who rely on assistive technologies. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and review the site against these criteria on an ongoing basis.

Features we've built in

  • Keyboard navigation: every interactive element — inputs, buttons, toggles, accordion triggers, copy-to-clipboard buttons — can be reached and operated with the keyboard alone. Focus outlines are visible and never suppressed.
  • Screen-reader labels: every form control has a programmatically-associated label, every button has an accessible name, and dynamic result panels use aria-live so calculation updates are announced without requiring focus shift.
  • Heading hierarchy: each page has a single H1 and a logical H2 / H3 structure that matches the visual hierarchy, so screen-reader users can navigate by heading.
  • Color contrast: body text and interactive elements meet at least the WCAG AA contrast ratios (4.5:1 for body text, 3:1 for large text and UI elements).
  • Resizable text: the site is responsive to browser zoom up to 200% without loss of content or functionality.
  • Reduced motion: non-essential animations respect the prefers-reduced-motion media query.
  • Semantic HTML: we use native elements (form, button, table, nav, main, code, pre) before reaching for ARIA. Code blocks use semantic <pre><code> markup for screen-reader compatibility.

Known limitations

Bit-layout visualization panels (for the number base converter) use CSS grid to render individual bit cells. We provide a text-based alternative representation alongside every bit-layout display so the information is never diagram-only. We continue to improve screen-reader experience for these visual components.

Feedback

If you encounter an accessibility barrier anywhere on the site, please tell us so we can fix it. Email info@bedrockatools.com with the page URL, a short description of the issue, and the assistive technology you're using (if relevant). We aim to respond within 3 business days.