EVKii, Inc. wants emlOPS to be usable by everyone, including people who rely on assistive technology. This statement describes where we are, what we do, and how to reach us when something does not work.
Our target
The web application, the iPhone app, and this site aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We treat accessibility as part of the definition of done for every screen in the review flow: the queue, the reader, the composer, and the approval controls.
What is in place
Keyboard operation of the queue and reader with visible focus, labelled controls and landmarks for screen readers, a type scale that follows your browser and system settings, colour contrast at AA for text and controls, reduced-motion support, and, on iPhone, Dynamic Type and VoiceOver labels on the review flow.
Known limitations
Email is rendered as its sender built it, so the accessibility of a newsletter or an invoice inside the reader depends on that sender; the plain-text view is always available. Some third-party embeds in the marketing site, such as video, follow the host's accessibility. We list any open issue that affects a core task here until it is fixed.
How we check
Automated checks run on every build. Manual checks with a screen reader and keyboard-only use are part of each release of the review flow, and the iPhone app is checked with VoiceOver and the largest accessibility text size on a physical device before each TestFlight build.
Feedback
If you find something you cannot do with assistive technology, email info@emlops.com with the page or screen and what happened. We respond within five business days and treat a blocking issue in a core task as a production defect.