Accessibility Statement

Our Commitment

MouseTester Pro is committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability. We strive to meet or exceed the requirements of the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Accessibility is not an afterthought for us — it is a core part of how we design and build every feature on this site.

We believe that everyone deserves equal access to tools that help them understand and optimize their hardware. Whether you use assistive technology, have a visual or motor impairment, or simply prefer keyboard navigation, our goal is to make MouseTester Pro work for you.

Accessibility Features

We have implemented the following accessibility features across our website:

  • Semantic HTML: We use proper heading hierarchy, landmark regions, and semantic elements (nav, main, article, section, footer) so screen readers can navigate the page structure efficiently.
  • ARIA Attributes: Interactive elements include appropriate ARIA labels, roles, and states to convey their purpose and current status to assistive technologies.
  • Keyboard Navigation: All interactive elements — buttons, links, form fields, and the test interface — are fully accessible via keyboard. You can tab through the interface, activate buttons with Enter or Space, and close modals with Escape.
  • Color Contrast: We maintain a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text throughout the site, meeting WCAG AA standards. Our dark theme was designed with contrast accessibility in mind from the beginning.
  • Focus Indicators: Visible focus indicators are provided on all interactive elements so keyboard users can always see which element is currently active.
  • Responsive Design: The site adapts to different screen sizes and supports text resizing up to 200% without loss of content or functionality.
  • Alternative Text: All meaningful images include descriptive alt text. Decorative images are properly marked so screen readers skip them.

Assistive Technology Support

MouseTester Pro is designed to work with common assistive technologies including:

  • Screen readers (NVDA, JAWS, VoiceOver, TalkBack)
  • Screen magnification software
  • Speech recognition software
  • Keyboard-only navigation
  • Browser-based accessibility extensions

We test regularly with VoiceOver on macOS and periodically with NVDA on Windows to identify and resolve issues. Our testing interface is designed to announce results to screen readers as they are generated.

Known Limitations

While we work to ensure comprehensive accessibility, some aspects of MouseTester Pro present inherent challenges:

  • Mouse Testing Interface: The core latency test requires physical mouse clicks by nature. We provide clear instructions and results that are fully accessible via screen reader, but the test interaction itself requires mouse input.
  • Real-Time Data Visualizations: Some chart and graph elements may not be fully accessible to all assistive technologies. We provide text-based alternatives for all key data points alongside visual representations.

We are actively working to improve these areas and welcome suggestions on how to make them more accessible.

Ongoing Efforts

Accessibility is an ongoing process. We regularly audit our site for compliance issues, incorporate accessibility into our development workflow, and train our team on best practices. When we add new features, accessibility is part of the design and review process — not a post-launch fix.

Feedback and Contact

If you experience any difficulty accessing content on this site, or if you have suggestions for how we can improve accessibility, please let us know. We take every report seriously and aim to respond within two business days.

You can reach us through our Contact page. When reporting an accessibility issue, please include:

  • The page URL where you encountered the issue
  • A description of the problem
  • The assistive technology and browser you were using

This information helps us reproduce and fix the issue as quickly as possible.

Last updated: April 2026