Accessibility Statement

Our Commitment

Overplanned is committed to making travel planning accessible to everyone. We believe that a good travel experience starts with tools that work for all users, regardless of ability or the technology they use to access the web.

We are actively working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. These guidelines help us ensure that our content is perceivable, operable, understandable, and robust for all users.

What We Are Doing

• Semantic HTML: We use proper heading hierarchy, landmark regions, and ARIA attributes throughout the application.
• Keyboard navigation: All interactive elements are reachable and operable via keyboard. Focus indicators are visible on every focusable element.
• Color contrast: Our design system enforces a minimum 4.5:1 contrast ratio for normal text and 3:1 for large text, meeting WCAG AA requirements.
• Screen reader support: We test with VoiceOver and NVDA to ensure content is announced correctly and interactive components communicate their state.
• Responsive design: The interface adapts from 320px viewports up, with touch targets sized at a minimum of 44x44 CSS pixels on mobile.
• Motion sensitivity: We respect the prefers-reduced-motion media query and reduce or disable animations for users who request it.
• Text scaling: All text uses relative units and scales properly up to 200% zoom without loss of content or functionality.

Known Limitations

We are continually improving, but some areas of the application may not yet fully meet WCAG 2.1 AA standards:

• Interactive map components (powered by Mapbox) have limited keyboard and screen reader support. We provide text-based alternatives for all map-dependent features.
• Some third-party image content (Unsplash photos) may lack descriptive alt text. We are working on automated alt text generation for venue and destination imagery.
• Drag-and-drop itinerary reordering requires a mouse or touch. Keyboard-accessible reordering controls are available as an alternative.

Report an Issue

If you encounter an accessibility barrier or have suggestions for improvement, we want to hear from you. Please contact us with:

• A description of the issue you encountered
• The page or feature where it occurred
• The browser and assistive technology you were using

Standards and Testing

We test against WCAG 2.1 Level AA success criteria using a combination of automated tools (axe-core, Lighthouse) and manual testing with assistive technologies. Our target is full AA conformance. We conduct accessibility reviews as part of our development process and address issues before they ship to production.