Last updated: 2026-09-12 — Version v1.1
1. Our commitment
MiCCA OÜ wants Screen Browser to be usable by everyone, including people who use screen readers, keyboard-only navigation, magnification, voice control or reduced-motion settings. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across this website and the Screen Browser app.
2. Conformance status
Screen Browser is partially conformant with WCAG 2.2 Level AA. Partially conformant means that most content conforms, but some parts do not yet fully meet the standard. The known gaps are listed in section 4, and we work through them as part of normal development.
3. What we have done
- A skip-to-content link on every page so keyboard users can bypass the navigation.
- Visible focus indicators on all interactive elements, and a logical tab order.
- Page regions that screen readers can jump between (header, navigation, main content, footer) on every page, and one main heading per page with headings in order.
- Form fields with associated labels; validation errors are announced to assistive technology and never shown by colour alone.
- Modal dialogs that trap focus while open and return focus to the element that opened them.
- Status changes on the run page are announced to screen readers as a run progresses.
- State communicated in text as well as colour, for example run status badges and credit balances.
- Decorative images marked with empty alternative text; informative images with descriptive alternative text.
- Colour contrast of at least 4.5:1 for body text and 3:1 for large text and interface components on the tested colour pairs.
- Transitions and animated effects are suppressed when the operating system asks for reduced motion.
4. Known limitations
- Recorded videos reflect your application. A video shows the customer's own web application as it is. Its colours, contrast, text size and structure are those of the recorded application, and we cannot change them. The narration describes what happens on screen, which helps, but the video itself is only as accessible as the application it records.
- Captions and subtitles are generated automatically. They are produced from the narration script, delivered as SRT and VTT files, and can be edited before you publish. They may contain errors, particularly with product names and unusual terms, and they do not describe sounds other than the narration. Check them before you rely on them.
- The embedded video player supports keyboard control (Space to play or pause, arrow keys to seek), but these shortcuts are not yet documented in an accessible help panel inside the player.
- Some tables in the admin area do not yet have complete row and column header associations.
- Checkout and invoice pages are provided by Stripe and are outside our direct control. Stripe publishes its own accessibility information.
- Third-party content such as embedded dashboards may not fully conform.
5. Videos and captions
Every finished video comes with auto-generated caption files in SRT and VTT formats that you can download, correct in any subtitle editor and attach to the video wherever you publish it. The narration is spoken, and its text is what the captions contain, so a corrected caption file can also serve as a transcript.
6. How we test
- Automated axe-core scans of every major page in our automated checks, with a zero-tolerance rule for WCAG A and AA violations.
- Keyboard-only walkthroughs of the main user journeys (sign-up, creating a project, starting a run, downloading a video, billing) in every release cycle.
- Manual screen-reader checks with NVDA on Windows and VoiceOver on macOS at least quarterly and after major interface changes.
This statement was reviewed on 2026-09-12 against the current app and site.
7. Feedback and help
If you find a barrier, or you need content in another format, write to [email protected]. Tell us the page or feature, what you were trying to do, and the assistive technology or browser you used. We reply within 5 business days, and we tell you what we intend to do about it and when.
8. Formal complaints
If you are not satisfied with our answer, you can contact the body responsible for enforcing web accessibility rules in your country.