Accessibility statement
How MyUniBridge is built for accessibility, what we have tested, and how to report a barrier.
MyUniBridge aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Accessibility is treated as part of the product, not an afterthought.
What we have implemented
- Semantic landmarks on every page: one banner, one main region, one contentinfo, and a single H1 per page.
- A visible 'Skip to main content' link as the first focusable element.
- Keyboard operation for every interactive control, with visible focus rings that meet contrast requirements.
- Colour contrast of at least 4.5:1 for body text and 3:1 for large text and interface borders, verified in both light and dark themes.
- A light and a dark theme, plus a system option, with no information conveyed by colour alone — status is always also given as text.
- All motion, including scroll-linked and cinematic animation, is disabled automatically when the operating system reports prefers-reduced-motion.
- Form fields have programmatic labels, validation errors are announced in text next to the field, and errors never rely on colour alone.
- Decorative images and background effects are hidden from assistive technology; informative images carry descriptive alternative text.
- Live regions announce dynamic changes such as saved records, deck position and support-message confirmation.
- Interface language is set on the html element and updates when you change language, so screen readers pronounce content correctly.
- Touch targets are at least 44 by 44 pixels on mobile layouts, and content reflows to 320px without horizontal scrolling.
- The interface is fully usable at 200% zoom and respects browser text-size settings.
Known limitations
- Some official source documents we link to are published as third-party PDFs whose accessibility we do not control.
- Automated testing covers our own interface only; we re-test manually with keyboard and screen readers before each release.
Reporting a barrier
If any part of MyUniBridge prevents you from completing a task, contact support with the page address and what you were trying to do. We aim to respond within 2 to 4 working days.
[email protected]