Accessibility
Last updated: 13th July 2026
Our approach
AEM Living is committed to making this website accessible to everyone, including people with disabilities. This statement explains what we do to support that, and what to do if you run into problems.
We aim to meet WCAG 2.2, level AA. In practice, that means:
- The site uses semantic HTML and responsive design, so it displays and reads correctly across screen sizes, from phones to large monitors.
- All content and navigation can be operated by keyboard alone, as well as with a mouse or touchscreen.
- Text can be resized using your browser's zoom controls without loss of content or function.
- Colour and contrast choices are designed to remain readable for users with low vision or colour blindness.
- Images carry descriptive alt text, and page structure uses proper headings to support screen readers.
Adjusting how you view this site
Most browsers let you zoom in or out using Ctrl and +/- (Windows) or Cmd and +/- (Mac), or by pinch-zooming on a phone or tablet. Browsers and operating systems also have built-in accessibility tools - magnification, screen readers, high-contrast modes - which you can find via:
- Google Chrome accessibility features
- Microsoft Edge accessibility features
- Apple accessibility support
- Mozilla Firefox accessibility features
Popular screen readers include JAWS and NVDA (free).
For general guidance, AbilityNet has useful resources on making your device easier to use, whatever your needs.
Known limitations
There are some features, such as the interactive map, which users can find easier to use on a computer as opposed to a mobile or tablet.
If you have any difficulty using this site, please contact us at info@audleygroup.com, telling us the page involved and the problem you encountered. We'll aim to respond and address genuine issues as quickly as we reasonably can.
About this statement
This is a voluntary statement - as a private corporate group, AEM Living isn't subject to the Public Sector Bodies Accessibility Regulations, but we follow WCAG 2.2 AA as good practice.