Accessibility Statement

Our Commitment

MySmartCalculators is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.

Under our Core 20 policy, accessibility testing and remediation are prioritized on twenty high-intent calculator workflows. This improves consistency for critical tasks such as mortgage, tax, BMI, calorie, and pregnancy-related calculations.

Non-core routes remain available, but accessibility enhancements may be scheduled after Core 20 updates depending on severity, user impact, and maintenance capacity.

Measures We Take

• Semantic HTML structure for screen reader compatibility
• High contrast color schemes in our dark mode interface
• Keyboard navigation support for all interactive elements
• Clear, readable fonts and text sizing
• Descriptive labels for form inputs and buttons

Conformance Status

We aim to conform to WCAG 2.1 Level AA guidelines. We recognize that not all accessibility standards may be fully met at all times, and we are actively working to identify and address any barriers.

Feedback & Contact

We welcome your feedback on the accessibility of MySmartCalculators. If you encounter any accessibility barriers or have suggestions for improvement, please contact us:

Assistive Technology Compatibility

Our website is designed to be compatible with the following assistive technologies:

• Screen readers (NVDA, JAWS, VoiceOver)
• Screen magnification software
• Voice recognition software
• Keyboard-only navigation

Limitations

Despite our best efforts, there may be some limitations. We are committed to addressing accessibility issues as quickly as possible. If you need information in an alternative format, please contact us.

Accessibility Responsibility

Accessibility improvements are managed by the MySmartCalculators team. Reported barriers are triaged by severity and reviewed in scheduled update cycles.

Triage order follows our Core 20 governance model: high-impact blockers on Core 20 pages are handled first, then broader non-core improvements are queued.