Accessibility

This page says what we have actually done to make asta.homes usable, what we know is still wrong, and how to tell us when we have got it wrong somewhere we have not noticed.

What we are aiming at

We build against WCAG 2.2 Level AA as the standard. We are not claiming conformance to it. No independent audit has been carried out on this site, and a self-assessment is not the same thing as a conformance claim — so this page describes measures and known gaps rather than awarding ourselves a grade.

What is in place

Keyboard access

Every interactive control can be reached and operated with a keyboard. The navigation menu traps focus while it is open, returns focus to the button that opened it, and closes on Escape.

Visible focus

Focus is drawn with a 2px emerald outline, offset from the element and with a surrounding glow, rather than relying on the browser default against a dark background.

Skip to content

A skip link is the first thing in the tab order on the main pages, so a keyboard or screen-reader user is not walked through the navigation on every page.

Reduced motion

The site reads your prefers-reduced-motion setting. With it on, animations, transitions and scroll-triggered reveals are turned off rather than shortened.

Text alternatives

Every image on the site carries alt text describing what it shows. Decorative elements are hidden from assistive technology rather than given empty descriptions.

Language and structure

Every page declares its language, uses real headings in order, and uses landmarks — navigation, main, footer — so a screen reader can move by region.

What we know is not right yet

Listing these is the point of the page. An accessibility statement with no known issues is a statement nobody has checked.

  • The skip link is not on every page. It is present on the main pages and the articles, but a minority of older pages are still missing it.
  • No independent audit. Everything above is our own testing. We have not had the site assessed by anyone else, and we have not tested it with every combination of screen reader and browser.
  • The interactive map is a hard problem. Map-based property discovery is visual by nature. Anything that depends on reading a map is not currently usable without sight, and we do not want to imply otherwise. If this affects you, contact us — we would rather give you the information directly than leave you with nothing.
  • Some documents are PDFs. Our longer briefing material is not reliably tagged for screen readers. Ask us and we will send the content in a readable format.

Telling us about a problem

If something on this site stops you doing what you came to do, please tell us. You do not need to know why it is broken or use any particular words for it — “I cannot get past this form with a keyboard” is a complete bug report.

Email hello@asta.homes, or use the contact form if that is easier. It helps if you can tell us the page, what you were trying to do, and what you are using to browse — but send it even if you cannot.

We aim to reply within five working days, and we will tell you what we are going to do and roughly when. If a fix will take a while, we will say so rather than go quiet.

Asking for something another way

If part of the site is not working for you, we will get you the information another way — a property's details read out over the phone, a document in a different format, or help completing a form. Ask at hello@asta.homes. There is no process to go through and nothing to prove.

accessibility • wcag 2.2 aa • keyboard • reduced motion

Last reviewed: 13 November 2026. This statement is checked whenever the site's navigation or page structure changes, and at least twice a year. If it is more than six months old when you read it, it is overdue — tell us.