Accessibility Statement
Last updated: April 2026
LycianWay is committed to making our website and mobile apps usable by as many people as possible, including people with disabilities. This statement describes our current level of conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, which is the international benchmark for digital accessibility.
LycianWay is operated by Pixelo Mobile Ltd. As a private-sector website not classified as a public-sector body, our compliance is voluntary, but we treat it as a commitment rather than a suggestion.
1. Current conformance status
Partial conformance
lycianway.co.uk — aiming for WCAG 2.1 AA. Most pages meet or exceed AA; some marketplace and community pages have known shortcomings listed below.
Partial conformance
LycianWay iOS app — aiming for WCAG 2.1 AA via native iOS accessibility APIs. The offline map feature has known barriers (see s.5).
Planned
Third-party external audit — we plan an independent accessibility audit in H2 2026 and will publish the findings and remediation plan.
2. What works well
- Keyboard navigation: all core flows (browse routes, book a tour, sign in, contact form, Ask Lycia Live registration) are fully keyboard-accessible with visible focus states.
- Semantic HTML: pages use headings (
<h1>…<h3>) in order, landmark regions (<nav>, <main>, <footer>), and ARIA labels on interactive non-text controls.
- Colour contrast: our primary colours (green #2D5016, cream #F5F0E8, terracotta #C0623A) pass AA contrast on body text. Small-text warnings on colour-only signals have been addressed with icons + labels.
- Text scaling: pages respond to browser text-zoom up to 200% without horizontal scroll or content loss.
- Forms: every input has a programmatically-linked label; errors are announced via
aria-live regions; required fields are marked.
- Images: content images include
alt text; decorative images use alt="".
- Language & locale: the site supports 8 languages (English, Turkish, German, Italian, French, Spanish, Russian, Ukrainian). Page
<html lang="…"> is set correctly per locale.
- Mobile touch targets: interactive elements follow Apple HIG (44×44 pt minimum) in the iOS app.
- VoiceOver: the iOS app has been tested with VoiceOver on common flows (onboarding, map, check-in, booking).
3. Known issues we're actively fixing
| Area | Issue | Planned fix |
|---|
| Trail map (interactive) |
Mapbox canvas is not directly screen-reader accessible. We provide a text alternative (stage list + directions) but the map itself is not fully announced. |
Add per-stage text equivalents, skip link to "view all stages as a list". H2 2026. |
| Marketplace provider cards |
Star ratings rendered as Unicode characters — screen readers announce them character by character. |
Add aria-label="4.8 out of 5 stars" fallback. H2 2026. |
| Community Trail Feed |
Infinite scroll — reliance on intersection observer may confuse some assistive tech. No "load more" button. |
Add a visible "Load more" button with aria-live. H2 2026. |
| Photo galleries |
Lightbox gallery (GLightbox) focus trap works, but escape-key hint isn't announced. |
Add aria-label="Press Escape to close". H2 2026. |
| PDFs (guidebook snippets) |
Some downloadable PDFs were generated without tagged structure. |
Regenerate with pdf library structure tags, starting Q3 2026. |
| Video content (stage videos) |
Some user-uploaded stage videos don't have captions. |
Require captions as a condition for publishing new videos from Q3 2026. Legacy content will stay until uploader adds captions. |
4. iOS app accessibility
The LycianWay iOS app is built with Flutter. We use the Flutter Semantics widget tree, which bridges to iOS UIAccessibility:
- VoiceOver reads all buttons, list items, headings, and form fields with meaningful labels.
- Dynamic Type is supported on text-based screens. The map and navigation UI use a fixed type size because GPS coordinates must stay readable at arm's length.
- Reduce Motion is honoured where we use animations (e.g. card transitions).
- High contrast mode is respected.
5. Known iOS issues
- Offline map: pinch-to-zoom gestures are not equivalent to keyboard zoom. We expose a two-button zoom control visually but it is hidden from VoiceOver. Workaround: use iOS Zoom accessibility feature or ask for a spoken-route alternative in Settings → Accessibility (planned).
- Passive compass: the analogue compass visual isn't announced numerically. Workaround: the direction is also shown as a cardinal letter (N, NE, E…) which VoiceOver reads.
- Emergency contact setup: the "swipe to remove" gesture in the contact list is not discoverable for VoiceOver users. Planned: add a visible delete button when VoiceOver is active.
6. Need help using LycianWay?
If you can't complete something because of an accessibility barrier, we want to help you directly while we work on the fix:
- Email access@lycianway.co.uk — we aim to reply within 2 working days.
- Describe the page or screen and what you were trying to do.
- If it's time-sensitive (e.g. finalising a booking), we'll complete the action for you manually by email or phone.
7. Report a new accessibility issue
Please send new barriers to access@lycianway.co.uk with:
- The URL or app screen
- The assistive tech you use (e.g. VoiceOver iOS 18, NVDA, keyboard only)
- What you expected to happen vs what did happen
We triage every report. Fixes for critical barriers (anything that blocks you from completing a task) are prioritised in our next release.
8. Enforcement
If you are not satisfied with our response, you can contact the UK Equality Advisory and Support Service, which provides free guidance on disability discrimination under the Equality Act 2010.
9. Technical specification
LycianWay is built using HTML5, CSS, JavaScript (vanilla — no heavy framework on the marketing site), Flutter/Dart (iOS app), and Django (back-end). These pages are tested against WCAG 2.1 AA criteria using a combination of:
- Manual keyboard-only testing
- axe DevTools browser extension
- Lighthouse Accessibility audit
- NVDA (Windows) and VoiceOver (macOS, iOS) screen readers
- Color Contrast Analyser for custom palette decisions
10. Commitment to improve
We prepared this statement on 24 April 2026. We review it every 6 months and update it when new features ship. The next scheduled review is October 2026.
Pixelo Mobile Ltd, company number 10585806. Registered office: Demsa Accounts, 565 Green Lanes, Haringey, London, England, N8 0RL.