Accessibility for developers

A page can look organised while offering little structure to someone navigating by headings or regions. In this workshop page, the apparent headings are paragraphs and the main content is a generic group.

An arrow, a link called “More” and an image filename all ask the reader to supply missing context. Useful names and alternatives explain the job an item does here.

Someone booking a repair workshop needs to read what to bring, close the details and continue to booking. The current trigger works with a pointer, but is missing from the normal keyboard route.

The session list looks restrained, but its faint text is hard to read and the coloured dots do not explain which session can be booked. Those are two separate problems.

A fixed width pushes this page beyond a narrow viewport. Its introduction is also clipped to a fixed height. Increasing the text size exposes why those choices can prevent someone from reading the whole message.

The booking form has placeholders that disappear when someone types, a red border when something is wrong and a confirmation that changes only visually. The visitor has to work out what happened at each step.

The ordinary confirmation slides into view when requested. The reduced-motion branch removes the entire message. The movement is gone, but so is the information someone needs to understand the result.

Eastbank Library has a new room-booking page. Its longer content, room availability and booking-reference field change the details, but the inspection method still applies. Decide where the barriers are before adjusting the controls.