Accessibility statement
Opportunity should include access.
viamu’s accessibility target, current measures, known limitations, and feedback route.
Reviewed August 8, 2026
On this page
This document is currently available only in English. We are not presenting an unreviewed machine translation as legal text. Contact us if you need help understanding it before creating an account or sharing information.
viamu is built for students with different languages, devices, abilities, and levels of application experience. We aim for the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. This is a target and design standard—not a claim that every page has passed an independent conformance audit.
Accessibility is part of product quality. We prioritize barriers that prevent a student from finding, understanding, saving, or preparing for an opportunity.
WCAG 2.2 AA target
Semantic structure, keyboard access, visible focus, readable contrast, and adaptable layouts guide the interface.
Core journeys first
Explore, sign-in and account creation, opportunity detail, account controls, and workspaces receive priority.
Feedback is actionable
Tell us the page, task, device or assistive technology, and the result you need.
Our commitment and standard
We use WCAG 2.2 Level AA as the baseline for the web service and consider keyboard-only use, screen readers, text zoom, reduced motion, contrast, touch targets, understandable authentication, and internationalized layouts. Legal and trust documents use semantic headings, a linked contents list, readable line lengths, visible focus, and a print or PDF option.
Measures built into viamu
Current design and engineering practices include:
- A skip target and semantic landmarks, headings, labels, lists, and buttons.
- Keyboard-operable controls with visible focus and logical order.
- Text and controls designed for 200% zoom and narrow screens without requiring a fixed desktop layout.
- Reduced-motion support and restrained animation.
- Locale-aware dates, right-to-left interface support, and persistent language selection.
- Text alternatives for meaningful images and decorative treatment for non-informative graphics.
- Plain-language errors near the affected field and status messages for important updates.
- Touch targets designed for coarse-pointer use.
- Automated checks plus manual keyboard and responsive review for critical changes.
Known limitations
We are transparent about areas that are not yet complete:
- Long-form legal and trust documents are currently maintained only in reviewed English. The interface explains this rather than presenting an unreviewed translation as authoritative.
- External provider sites, forms, documents, and payment systems are outside viamu’s control and may not meet the same standard.
- Uploaded third-party documents may not contain accessible structure or text alternatives.
- The service has not yet completed an independent end-to-end WCAG conformance audit across every supported browser and assistive-technology combination.
- New or planned AI, billing, and recommendation experiences require accessibility review before launch.
Compatibility
viamu is intended to work with current major browsers, keyboard navigation, browser zoom, and common screen-reader/browser combinations. Very old browsers, browser extensions, translated third-party content, and external provider systems may behave differently. If a feature blocks your task, contact us for a reasonable alternative rather than assuming the task cannot be completed.
Accessibility feedback and alternatives
Email onviamu@gmail.com. Helpful details let us reproduce and prioritize the barrier:
- The page URL and the task you were trying to complete.
- What happened and what result you expected.
- Your browser, device, operating system, and assistive technology, if you are comfortable sharing them.
- Whether the deadline or task is time-sensitive.
- The alternative format or assistance that would let you continue.
- Do not include passwords, private documents, or unnecessary medical details.
Assessment and review
We review accessibility during design and implementation, use automated detection for common failures, and prioritize manual testing for sign-in and account creation, account controls, opportunity discovery, details, and workspaces. Automated tools cannot prove conformance. Material barriers should be tracked to resolution, and this statement should be updated after a formal audit or when known limitations materially change.
Questions or requests?
To report an accessibility barrier or request information in another usable format, email
onviamu@gmail.com