GUIDES • ITINERARIES • SMARTER TRAVEL
Our accessibility goal
The Travels Tip aims to make its public website and account features usable by as many readers as practical, including people who navigate with a keyboard, screen reader, zoom, high-contrast settings or other assistive technologies.
How the CMS supports accessibility
The design system uses semantic headings, labelled form fields, visible focus states, alternative text fields for editorial images, keyboard-operable controls and responsive layouts. Administrative guidance encourages editors to keep a single page-level H1 and use descriptive H2 and H3 headings in order.
Content responsibilities
Accessibility depends on editorial choices as well as code. Authors and editors are expected to provide meaningful alternative text, avoid using images as the only way to communicate essential information, write descriptive links and preserve logical heading structure.
Known limitations
Some third-party embeds, maps, payment pages, social-login interfaces or external services may have accessibility behaviour controlled by their provider. Older imported editorial content may also need remediation if it was created before current standards were applied.
Report an accessibility problem
If you encounter a barrier, use the support contact on the Contact page. Include the page URL, the task you were trying to complete, the browser or assistive technology involved and a description of the problem. That information helps the team reproduce and fix the issue.
Continuous improvement
Accessibility is treated as an ongoing quality requirement. New templates, forms and navigation patterns should be tested for keyboard use, readable scaling and clear labels before they are considered complete.