Access

Effective August 4, 2026. Two subjects, and the second is the harder one.

This website

The benchmark is WCAG 2.2 at level AA. The site was built and tested against it, though no outside audit has been carried out, so treat this as a description of work done rather than certification.

Working. One first level heading per page with no skipped levels. A skip link as the first keyboard stop. Complete keyboard operation of the menu, the forms and the storage card, with a thick visible focus outline. Text scaling with the browser setting and a layout holding at 200 percent zoom without sideways scrolling. Alternative text on every photograph, describing what is in the frame rather than repeating the caption. Real labels on fields, errors stated in words rather than by colour, and results announced through a live region. One brief fade as the only motion, switched off entirely when the system asks for reduced motion. Scripts disabled and every page still renders, every link still works.

Not working well enough yet. The reach listings use a numbered layout that reads cleanly but puts the walking distance last, which is late for somebody deciding whether a trip is possible. The long pages have no jump list. And self testing is not an audit.

The ground itself

This is where honesty is more useful than reassurance.

Most of what this paper describes is not accessible. Levee roads are gravel with no surfacing. Bottomland paths are mud for much of the year. River access is frequently down a bank with no steps. There is no version of these pieces where that changes, and pretending otherwise would send somebody on a wasted or unsafe trip.

What is reachable, and where a piece says so explicitly: several river overlooks with paved parking and level surfaces, one long paved path along the bluff, and both ferry landings, which are level by necessity. Where a place has a hard surface, a bench or a rail, the piece says so in the text rather than leaving it to be discovered.

What the desk will do. Ask, and you get a straight answer about the surface, the gradient, the distance from parking and whether there is shade, based on having walked it. Where the answer is that it will not work, that is what you will be told.

Telling the desk about a problem

Write to [email protected] naming the page, what you were doing and what happened instead. Mentioning the Say which browser and which assistive software, if you are willing. A report carrying those two facts can be sat down with and repeated; one without them has to be guessed at. Reading happens Thursday through Monday, with a reply inside two working days. Straightforward repairs generally ship that week. Where a repair is awkward, you get told what the obstacle is instead of a polite acknowledgement and silence.

If a page will not work for you

Ask for the text. Any piece here, including the legal pages, can be sent as plain text or a simple document by email, at no charge and without conditions. Write to [email protected] and name the page.