A reserved car with a ramp, and pages that read aloud

1 Pages that work with a keyboard

Each page is laid out so that someone using a screen reader, or moving through it with the Tab key and no mouse, can reach every part a mouse user can, and the pages are built toward WCAG 2.1 level AA. On the request form that matters most, because a reservation request is why most people come here. What that means in practice:

• Every form field carries a written label that a screen reader reads aloud
• Headings run in one steady order, so you can jump from section to section
• A skip link at the top of each page goes straight past the menu to the content
• Nothing on the form runs on a timer or clears itself while you think

2 Words behind the chart and drawings

The chart on the service areas page places all 25 corners on the county grid. A chart like that says nothing to a screen reader, so the same corners stand below it in three tables, row by row: grid point, road miles, minutes at a quiet hour, main road to the airport, and the sedan and SUV fares from, per car, each way.

The drawings of the terminal carry a written description too. It says in words where a reserved car sets you down for departures, on the commercial lane on the ground level, and where to find it on arrival: bags come out on the second level, and the same commercial lane is a short walk down.

3 Asking for a ramp or a lift

A vehicle with a ramp or a lift is asked for in the request itself: say so there, along with the number of riders and how many checked bags are coming. The office passes it to the car company that serves your corner, and the company confirms in writing whether it can send one for your pickup time. Until it does, nothing is held for you, and if it cannot, the written reply tells you so.

4 Reporting a barrier you run into

If a label is missing, a drawing has no words, or a key does nothing where it should, tell us. Call +1 (801) 363-4718 on weekdays from 3 p.m. to 9 p.m. or on Saturday and Sunday from 8 a.m. to 2 p.m., Mountain time, or write to rides@travelsbytracie.com at any hour with the page address and what happened. If the form itself is the barrier, the person on the phone can take your ride request.

Your note follows the same reply rule as a ride request. Write while the phone is answered, with at least 90 minutes still to go before it closes, and the written reply comes within 90 minutes. At any other time it comes within the first hour after the phone opens again, by 4 p.m. on a weekday or 9 a.m. on a weekend day.