Accessibility Statement
The accessibility goals, implemented features and known limitations of the London SAM launch build.
Our goal
London SAM aims to provide a strong WCAG-aligned browsing experience across keyboard, screen-reader, touch and reduced-motion contexts. Accessibility is treated as part of quality, not as a decorative compliance badge.
Features in this build
- Semantic header, navigation, main and footer landmarks.
- A keyboard-visible skip link and focus states.
- Responsive navigation with an explicit expanded state.
- Meaningful alternative text for editorial images and empty alt text for decorative logo marks where the brand name is already present.
- FAQ buttons with expanded-state semantics.
- A
prefers-reduced-motionmode that suppresses long animation behaviour. - Fluid typography and layouts designed to avoid horizontal scrolling at narrow widths.
Known limitations
Accessibility should be tested again after deployment because hosting banners, advertising, consent platforms or third-party embeds can change keyboard order, contrast and screen-reader output. The supplied project intentionally avoids those dependencies.
Feedback
Before public launch, connect the verified contact workflow so users can report barriers. Accessibility reports should identify the page, task and assistive technology where possible.