Built for everyone, everywhere
MYQER is built so that anyone can use it, including people with disabilities, people using assistive technology, and people in low connectivity or high stress situations.
Our commitment
We believe being known in an emergency should never depend on perfect vision, hearing, or a good phone. Every design and code decision is made to keep MYQER inclusive, usable, and readable for as many people as possible.
Standards we build to
- Built to meet WCAG 2.2 AA, the international accessibility standard.
- Designed with the UK Equality Act 2010 and reasonable adjustments in mind.
- Guided by the NHS Service Manual approach to clear, accessible content.
What that means in practice
- Keyboard friendly navigation with a visible focus outline.
- Screen reader support through semantic HTML and ARIA roles.
- Colour contrast that meets WCAG AA.
- Resizable text and a layout that works on any screen size.
- Full left to right and right to left support, for languages such as Arabic and Urdu.
- A reduced motion mode for people sensitive to animation.
- An offline option, so essential information works even with no signal.
- Information shown in 26 languages, so more people can understand it.
Continuous improvement
We test MYQER with both automated and manual tools to find and fix accessibility issues. Feedback from real people helps us most, especially where assistive technology behaves differently from one browser to the next. Accessibility is never finished, and we treat it as ongoing work.
Known limitations
We would rather be honest than perfect on paper. Some third party components, such as certain browser sign in dialogs, may not yet meet every accessibility target. We monitor these and work to close the gaps. If something gets in your way, please tell us, because real reports help us fix the right things first.
Feedback and contact
If you meet any barrier while using MYQER, please tell us. We want to know, and we will help.
Email us at hello@myqer.com. We will reply as soon as we can, and we will work with you to find a resolution or an accessible alternative within a reasonable time.
What is in place, and what is next
We separate what is true today from what is on our roadmap, because we will never present a future plan as a present fact.
In place today
- Built to meet WCAG 2.2 AA.
- Keyboard, screen reader, and reduced motion support.
- Full RTL support and 26 languages.
- A known limitations list we keep honest.
On our roadmap
- An independent accessibility audit.
- User testing with people who use assistive technology.
- Ongoing alignment with established accessibility patterns.
Tell us how we can do better
Your feedback shapes what we fix next. We read every message.