Accessibility statement
Drafted — pending legal review
We wrote this page ourselves and a lawyer has not reviewed it yet. It describes how IncaTrail.com works today and applies from the effective date below. It may change after review; every change is dated in the history at the end.
Our WCAG 2.2 AA target, how we test (automated scans, keyboard tests and code reviews), the known gaps we have not fixed yet, how to report a barrier and when we reply.
The standard we aim for
We build IncaTrail.com to meet WCAG 2.2 at level AA, in English and Spanish, from phone screens up. We do not claim full conformance yet: the known gaps are listed below.
How we test
We test with automated browser and component tests that we run while we build the site. They cover:
- automated accessibility scans with axe on key pages, including the home page, trail and place guides and every legal page in both languages at phone width, which fail on any serious or critical issue;
- the language menu, scanned at phone, tablet and desktop widths in light and dark mode, with the menu closed and open;
- keyboard use of the site menu and the language menu with the Tab, Enter and Escape keys, including a visible focus ring;
- reduced motion and forced-colour modes on the language menu;
- touch target sizes for the footer and the secondary links on the permit pages;
- names, roles and labels of buttons, links and form fields in our component tests.
Screen readers
Our reviewers check names, roles, headings and reading order in the code and in the browser’s accessibility tree. We have not yet completed a full manual pass with a screen reader on every journey; that is the first item in the list of known gaps.
Known gaps
These are the issues our own reviews found and have not fixed yet:
- no full manual screen-reader pass has been completed yet;
- links inside sentences, such as the source lines under figures, are shorter than the recommended touch target; standalone links and buttons meet it;
- some headings in the planning guides are long statements, which makes them slower to scan on a phone;
- wide tables, such as the trek comparison and the tables on these legal pages, scroll sideways inside a labelled area on phones instead of reflowing.
Tell us about a barrier
If something on IncaTrail.com is hard or impossible for you to use, write to inquiries@incatrail.com. Tell us the page address, what you were trying to do and, if you like, the device and any assistive technology you use. We can also send you the information in another format while we fix the problem.
When we reply
We reply within 5 business days, with what we will change and when, or with the information you needed in a form you can use.
About this page
This statement is a draft written in-house and pending legal review. We update it when we fix a gap or find a new one.
Change history
- First published draft, written in-house and pending legal review.
Questions about this page? Write to inquiries@incatrail.com.
Sources
- Web Content Accessibility Guidelines (WCAG) 2.2World Wide Web Consortium (W3C)
- The accessibility standard we build and test against, at level AA