How this site is built for keyboards, screen readers and zoom

The catalogue here is one chain. Twenty seven trips sit in five rungs, ordered by how much of the trip the traveller runs, and the site turns on being able to follow that order. That order had to hold three further ways: by ear, at high magnification in one column, and with the tab key doing all the moving.

Everything below was checked by hand on this build, with two screen readers and the window dragged down to phone width. No audit sits behind it and no grade is claimed.

The chain, read in order

Each rung of the five rungs side by side is a heading with its trips under it, so the whole ladder, top to bottom comes through as five named groups in sequence rather than a diagram. Which rung a trip belongs to is written out on the line carrying that trip. Color says nothing on its own here, and neither does position: the figure, the rung and the number of nights are all set in text. The rungs are flat by design, none ranked above another, and that is stated in words rather than left to the order they appear in.

Focus, source order and one column

Things arrive under the tab key in the order they are printed, because source order and drawn order match on every template. No component grabs the keyboard and refuses to hand it back. The focus ring is drawn by the site rather than left to the browser default, so it survives on paper, on panels and on the picture bands. Type is set in relative units, so raising the default text size gives larger type instead of a broken column.

The request form

Labels sit above their fields and stay put while you type. Required fields say so in words, not by an asterisk alone. A rejected field is explained beside itself and again at the top, focus moves to the first one, and nothing already entered is lost. No step has to be finished in one sitting and no clock runs on it. how a request becomes a reservation sets out what happens to a request once it is sent.

Four things still wrong

The tile descriptions are thin and repeat one another. Several describe the photograph rather than the place it shows, which is backwards, and they are being rewritten one at a time.

The widest block on the catalogue page scrolls sideways inside itself on a narrow screen. In some browsers that scrolling area is not a tab stop, so a keyboard user can only move it by tabbing to a link inside. It needs its own stop and label.

The focus ring on the darkest caption band is dimmer than the ring used elsewhere. It can be seen, but without the margin the rest of the site keeps, and it should be redrawn at that weight.

The testing was narrow. One person, two screen readers, one laptop and one phone. Voice control, a braille display and a switch have all gone untested, and nobody who uses those daily has been asked. The list above is what was measured, a smaller thing than what is true.

Where a fault goes

Send it to corrections@thepinegazette.com: the page, what you were trying to do, what happened instead, and the browser and software in use. One sentence is plenty. It is answered within one business day by the people who take booking requests, and the answer says whether the fault is already known and what happens next. Telephone +1 (504) 832-6194 if that is easier.

If a page here stops you from getting a request through, it can be made in an email in your own words instead, and a trip is reserved that way on the same terms. the questions this office is asked most covers what the office does with a request once it lands, and request a trip quote 24/7 is the form itself.