How This Site Is Built, and Where to Send a Fault

01Keyboard and focus

Reach every control from the keyboard, in the order the page is written. Whatever currently holds focus is ringed in the darkest brown on the page, thickly, rather than hinted at.

The skip link is the first thing focus lands on, and it jumps past the header and the ticket to the body of the page.

02Structure

Headings climb one step at a time and never leap. Each numbered section heading carries its number in a filled square, which is decoration for a sighted reader and simply a number in the text for anybody else.

Switch the stylesheet off and the page still reads top to bottom in a sensible order. On the first screen the heading, the geography line and the independence statement come before the booking pre-check in the source, so the page says what it is before it asks anything.

03Movement

One thing moves: an eight pixel rise as a block scrolls into view. Ask the operating system for reduced motion and it stops happening at all. Every block is fully present with no script running whatsoever.

Nothing else animates. No carousel, no ticker, no clock counting anything down, no autoplay, nothing that arrives on top of the page.

04Text and color

Sizes are set relatively throughout, so browser zoom and a raised default size both enlarge the page instead of breaking it. Long tokens break rather than pushing the layout sideways, and wide tables scroll inside their own frame. No page moves horizontally at any width.

The page sits on a pale cool gray with a faint green cast rather than on white, which cuts glare over a long read. Body text against it clears the contrast requirement for normal text with room to spare.

Brown carries links, rules, list marks and the numbered squares. It is dark enough to serve as text on that ground. Nowhere is it the only carrier of meaning:

• a link is underlined as well as colored;
• a rejected field says what is wrong in words as well as turning red;
• the current navigation item is marked in the markup as well as filled in;
• the claims sheet prints the words true and false rather than relying on green and red.

05The two forms

Four fields in the pre-check, eleven on the reservation form. Every field has a real label tied to it. Nothing is required that is not genuinely needed to answer you, and neither form has anywhere to enter a card.

A rejected field gets a sentence directly beneath it, is marked so a screen reader announces the problem, and focus jumps to the first field wanting attention.

06The notice

The cookie notice is a card at the left edge on a wide screen and a strip across the bottom on a narrow one. It sits above nothing important, covers no heading, and traps focus nowhere, because it is not an overlay across the page.

07The lots themselves

Worth a paragraph, since this is a parking desk rather than an abstract website. Lots on the airport mile are ordinary commercial parking: graded ground or asphalt, painted stalls, a gate, a van.

Needing a particular arrangement is a question to ask before reserving. Telephone +1 (520) 886-3174 during desk hours, name the requirement, and the answer will be what the operator actually said rather than a general reassurance. What will not happen is a promise from this desk about ground it does not own.

08Reporting something

Write to stalls@heronjunction.com describing what you were doing and what happened, or telephone during desk hours. One person reads it. A genuine fault is repaired rather than filed, and you are told when it is.

The desk is worked Monday to Friday between 7:30 am and 5:30 pm. Arizona keeps Mountain Standard Time the whole year and never moves its clocks, so that window is the same in July as in January while the rest of the country shifts twice. Saturday and Sunday nobody is here, and anything sent then is answered on Monday.