Accessibility Statement

Last updated: 2026-09-04

4Dev.net is committed to making its tools usable by everyone, including people who use assistive technology. We aim to meet WCAG 2.1 Level AA across the site, and treat accessibility as an ongoing effort rather than a one-time checklist.

Measures We've Taken

  • Keyboard navigation: every interactive control - including the searchable currency picker - is operable without a mouse, with visible focus indicators that only appear for keyboard users (so mouse users don't see a distracting outline on every click).
  • Skip links: every page includes a "Skip to main content" link as the first focusable element, letting keyboard and screen-reader users bypass repeated navigation.
  • Semantic structure: pages use proper heading hierarchy (a single h1, followed by properly nested h2/h3), landmark regions (header, main, footer, nav), and ARIA roles/labels on custom controls like the currency combobox.
  • Labels on every control: form inputs, buttons, and toggles have associated text labels or aria-label attributes - not placeholder text alone.
  • Color contrast: text colors are chosen to meet WCAG AA contrast ratios (4.5:1 for normal text) against their backgrounds.
  • Reduced motion: anyone with prefers-reduced-motion enabled in their operating system automatically gets all animations (including decorative ones) disabled site-wide.
  • Status announcements: live regions (aria-live) announce conversion results and errors to screen-reader users without requiring a page reload.
  • Decorative icons: purely decorative icons (like flag or cryptocurrency images) use empty alt text, since the currency code and name next to them already convey the same information in text.
  • Non-blocking feedback: every button provides a visible pressed/active state, so it's clear a click registered even before a result appears.

Known Limitations

Some tools embed third-party JavaScript libraries (for spreadsheet, Word, and XML processing) that we don't fully control the accessibility of. We test the surrounding interface we build, but can't guarantee every third-party component meets the same standard.

Feedback

If you encounter an accessibility barrier anywhere on the Website, please tell us via the Contact and Error Reporting page - accessibility reports are treated as a priority.