Our Commitment

M-Convert targets WCAG 2.2 Level AA conformance. We test the site with keyboard navigation, screen readers (VoiceOver, NVDA), and automated accessibility tools (axe DevTools, WAVE, Lighthouse). Where issues are found, we fix them.

What We Implement

  • Semantic HTML. Every page uses proper landmarks (header, main, footer, nav) and heading hierarchy.
  • Keyboard navigation. All controls are reachable and operable by keyboard alone. Focus indicators are visible throughout.
  • Screen reader support. Form inputs have labels, dynamic results are announced via aria-live, and decorative images are hidden from assistive technology.
  • Color contrast. Text meets AA contrast ratios (4.5:1 for body text, 3:1 for large text and UI controls).
  • Touch targets. Interactive controls are at least 44×44 CSS pixels on mobile.
  • Motion sensitivity. The site respects prefers-reduced-motion and disables nonessential transitions when requested.
  • Responsive layout. The site works at 320px width and scales up to large desktops without horizontal scroll or content loss.
  • No forced zoom. The viewport meta tag allows users to zoom freely.

Known Limitations

  • Some tables require horizontal scrolling on small screens. This is unavoidable for wide data tables but scroll containers are keyboard-accessible and labeled.
  • Very old browsers (Internet Explorer, pre-Chromium Edge) are not supported.
  • Print stylesheets are optimized for A4/Letter but may not fit every custom page size perfectly.

How to Report an Accessibility Issue

If you encounter an accessibility barrier on M-Convert, please report it via the Contact page. Include the page URL, the assistive technology you use, and a description of the problem. We treat accessibility bugs as high priority.

Feedback

We welcome suggestions for improving accessibility. If there is a specific feature or content type that is not accessible to you, please tell us — we will evaluate and address it.