Accessibility
Using Rounds with assistive technology
EMS is a field people enter with all kinds of bodies and all kinds of ways of reading. If any part of Rounds is getting in your way, we want to hear it directly, and we will tell you honestly what we have and have not fixed.
What we aim for
We work toward the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, on roundsems.com and in the Rounds EMS iPhone app. That is the standard courts and the US Department of Justice point to, and it is the one we measure ourselves against.
We are not claiming to have finished. Any site that tells you it is fully compliant is either not testing or not telling you the truth.
What we have done
- Every page on this site is tested with axe-core, an automated accessibility engine, and currently reports no violations at WCAG 2.1 AA.
- Every interactive control can be reached and operated with a keyboard alone, and shows a visible focus outline when you get there.
- Controls are named for screen readers rather than announced as unlabelled buttons.
- Decorative duplicates of content are removed from the tab order, so keyboard focus cannot disappear into something that is not really there.
- In the iPhone app, the text size you have set on your phone is now respected rather than overridden, and every screen is tested at the largest size we support.
What we know is not finished
Being straight with you about this is more useful than a badge:
- The app caps text scaling rather than supporting the full range of iOS Dynamic Type. Some screens are still built to fixed heights and would break above that cap. Reflowing them is real work and it is on our list.
- Screen reader labelling in the app is in progress. Shared controls are labelled; some screen-specific graphics are not yet.
- Automated testing catches a lot but it does not catch everything. Nothing replaces someone actually using the product with a screen reader and telling us where it fell apart.
Tell us about a barrier
Email hello@roundsems.com
Tell us the page or screen, what you were trying to do, and what you use to browse (for example VoiceOver on iPhone, or NVDA on Windows). We will reply, and if we cannot fix something quickly we will tell you what the workaround is in the meantime.
Last reviewed 8 August 2026.