Last updated: 29 April 2026
Our accessibility commitment
SomeTech.work is committed to making this site usable by as many people as possible, including people using screen readers, keyboard navigation, zoom, and reduced-motion settings. Accessibility is treated as a product quality requirement from day one.
Standards we target
We target conformance with WCAG 2.2 Level AA for user-facing journeys on sometech.work. We also work to align with relevant requirements under the European Accessibility Act and other applicable local accessibility expectations.
How we test
We use a combination of automated and manual checks:
- Automated scanning: lint rules and accessibility audits on key pages to identify missing labels, landmark issues, contrast risks, and structural defects.
- Keyboard testing: tab sequence, visible focus, skip links, modal and menu control, and no-trap navigation checks.
- Assistive technology checks: spot testing with screen readers for landmarks, heading hierarchy, link/button names, and form control announcements.
- Responsive and zoom behavior: checks at mobile breakpoints and at higher zoom levels to preserve readability and interaction.
- Reduced-motion behavior: verifying animations and transitions respect user motion preferences where supported.
Compatibility expectations
The site is designed to work with current versions of modern browsers and common assistive tools. We prioritize support for recent versions of Chrome, Safari, Firefox, and Edge, plus operating-system level accessibility settings.
Known limitations
We continuously improve accessibility and may have temporary gaps while new components are being introduced or updated. If you find a barrier, we want to hear about it quickly.
Reporting issues and escalation
Report accessibility issues to email us. Include the page URL, your device/browser, the assistive technology used (if any), and what you were trying to do.
We aim to acknowledge accessibility reports within 2 business days, provide an initial remediation direction within 10 business days, and prioritize critical access blockers ahead of non-critical enhancements.
Review and update policy
We review this statement at least annually and whenever there are material site changes. If testing identifies new limitations, this page is updated with current status and dates.
