Accessibility Statement
Last updated: October 5, 2026. Matola Tools is committed to ensuring digital accessibility for all users, including individuals with disabilities.
1. Our Commitment to Accessible Design
We believe utility tools should be accessible to everyone, regardless of physical ability, device, or assistive technology. We continually improve the user experience across Matola Tools, applying the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our baseline standard.
2. Key Accessibility Measures We Implement
To support an inclusive browsing experience, we incorporate accessible design practices into every page:
- Semantic HTML5 Structure: We use appropriate semantic elements—such as
<header>,<main>,<nav>,<article>, and<footer>—to provide clear landmarks for screen readers and assistive devices. - Full Keyboard Navigability: All interactive controls—including form inputs, sliders, dropdowns, copy buttons, and accordion toggles—are fully navigable using standard keyboard commands (
Tab,Shift+Tab,Enter, andSpace). - Visible Focus Indicators: High-contrast focus rings appear around active elements during keyboard navigation, ensuring users can clearly track their position on the page.
- Color Contrast Standards: Our light theme uses dark slate typography (
#0f172a) against clean white and light slate backgrounds, comfortably exceeding WCAG 2.1 AA contrast ratio requirements (at least 4.5:1 for body copy and 3:1 for large headings). - Multi-Sensory Status Feedback: Status messages, validation errors, and calculation results use clear text and iconography in addition to color, ensuring users with color vision deficiencies can interpret feedback accurately.
- Respect for User Preferences: Our stylesheets include
prefers-reduced-motionmedia queries that automatically disable transitions and animations for users who prefer reduced motion. - Accessible Form Controls: Every form input features an associated
<label>element with clear descriptive text and ARIA attributes where needed.
3. WCAG 2.1 Principles in Practice
We organize our accessibility implementation around the four core WCAG principles:
- Perceivable: All non-text content (such as icons) includes text alternatives or ARIA labels. Text is formatted with clean typography, responsive rem units, and high color contrast. Users can zoom page text up to 200% without breaking layouts or truncating critical interactive tools.
- Operable: The entire interface can be navigated using only a keyboard. A skip link allows users to jump directly to primary content, and all controls provide comfortable touch target sizes (minimum 44 × 44 pixels). No interactive elements require complex multi-finger gestures.
- Understandable: Interface labels, error notifications, and tool instructions are written in plain, clear language. Form inputs validate clearly without confusing error codes, and breadcrumbs indicate clear location in the site hierarchy.
- Robust: Pages use standard, valid HTML5 that parses predictably across diverse browsers, operating systems, and assistive technologies without relying on fragile custom plugins.
4. Keyboard Navigation Quick Reference
Users navigating Matola Tools without a mouse can utilize standard keyboard interactions:
Tab: Move focus forward to the next interactive link, button, or form field.Shift + Tab: Move focus backward to the previous element.Enter: Activate buttons, trigger links, and toggle category pills.Space: Toggle checkboxes and expand or collapse FAQ details accordions.Escape: Close the mobile navigation menu when open.Arrow Keys: Adjust range sliders (such as compression quality) with precision.
5. Screen Magnification, Reflow, and High-Contrast Themes
Low-vision users frequently rely on browser zooming and operating system high-contrast display modes. Matola Tools is engineered to seamlessly accommodate these assistive configurations:
- Zoom and Responsive Reflow: Our layout uses relative CSS units (
remand percentages) that allow users to zoom page content up to 400% without horizontal scrolling or text overlap, conforming to WCAG 1.4.10 Reflow standards. - Operating System Contrast Themes: Our styling respects Windows High Contrast Mode and OS-level forced colors mode (
forced-colors: active). System colors automatically override custom palettes to ensure vital interface elements, focus boundaries, and buttons remain distinct. - Touch Target Accommodations: All interactive buttons, checkboxes, and slider thumbs feature generous minimum target dimensions (at least 44 × 44 pixels) with ample surrounding spacing, aiding users with tremors or fine motor control challenges.
6. Assistive Technology Testing Workflows
To verify real-world accessibility, we test our pages across multiple screen reader environments:
- NVDA (NonVisual Desktop Access) on Windows: Verified speech output for heading navigation, form labeling, and dynamic live-region toast announcements.
- VoiceOver on Apple macOS & iOS: Tested rotor navigation by headings, landmarks, and form controls, ensuring smooth touch-swiping interactions on mobile.
- TalkBack on Android: Checked responsive touch navigation, screen magnification, and high-contrast system settings.
7. Color Contrast and Visual Ergonomics
Visual fatigue and low-contrast text present significant barriers for individuals with visual impairments or those working in brightly lit environments. Our design system adheres to strict contrast ratios:
- Body text (
#0f172a) on light background (#f8fafc) yields an exceptional contrast ratio of over 14:1, vastly exceeding the WCAG AA minimum of 4.5:1. - Primary action buttons (
#2563eb) on white text maintain a contrast ratio greater than 4.6:1, ensuring crisp readability. - Interactive links feature clear color distinctions and hover/focus underline indicators, avoiding reliance on color alone to communicate interactivity.
8. Ongoing Evaluation and Accessibility Roadmap
We regularly audit our pages using automated accessibility evaluation tools, keyboard-only testing passes, and manual code reviews. We continually refine our interfaces to eliminate potential accessibility barriers as new tools are added to the platform. Our ongoing roadmap includes testing with specialized braille display devices and refining screen reader announcements for complex interactive widgets.
9. Feedback and Contact Information
If you encounter an accessibility barrier on Matola Tools, find an interface difficult to navigate with assistive technology, or have suggestions for improvement, please let us know via our Contact Page. We review all accessibility feedback promptly and prioritize fixes for any identified barriers.