A study guide should work for every student.

• Use semantic headings, landmarks, labels and native controls.
• Support keyboard navigation and visible focus states.
• Maintain readable contrast, responsive text and meaningful image descriptions.
• Test important journeys at desktop and mobile sizes.
• Fix barriers as part of normal design and engineering work.

Odin has not yet completed an independent accessibility audit, so we do not claim full conformance. Automated checks, code review and manual keyboard checks are part of release preparation.

The site is designed to remain usable at narrow widths and with text zoom. Core navigation, application guides and university content use structured HTML rather than image-only text.

• Interactive maps: Mapbox content can be difficult with some assistive technology. Campus addresses remain available as text.
• Dense comparison data: University tables and filters may require additional navigation improvements for screen-reader and keyboard users.
• Third-party services: Authentication and payment steps include interfaces supplied by Supabase, Google and Stripe.
• Older content: A small number of legacy components are still being brought into the current component system.

If something prevents you from using Odin, email hello@viaodin.com. Include the page address, what you were trying to do, your browser or assistive technology if relevant, and the format or adjustment that would help.

We will acknowledge accessibility reports and aim to provide the information another way while we investigate the underlying issue.

Our working reference is the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. Sweden’s Webbriktlinjer provides practical guidance based on WCAG and the European EN 301 549 standard.