Accessibility
Accessibility statement
What we are aiming for, where we currently fall short, and how to tell us if something does not work for you.
Last reviewed 14 September 2026
Our commitment
We aim to meet WCAG 2.1 Level AA across containaura.com. Buying a home should not require a mouse, perfect eyesight or a particular device.
What we have built for
- Headings in a logical order, so screen reader users can navigate by structure
- Data tables with proper header cells and captions
- Form fields with visible, associated labels — never placeholder text alone
- Text that reflows on small screens and at high zoom
- Alternative text on images that carry information
Where we currently fall short
We have not yet had this site audited against WCAG 2.1 AA by anyone independent, and we are not going to claim conformance we have not measured. An accessibility statement listing no known issues is usually a statement nobody has tested.
Known gaps as of 14 September 2026:
- No independent audit and no formal screen reader testing has been completed
- Colour contrast has been designed for, but not verified page by page against the AA ratios
- Keyboard focus order and focus visibility have not been tested on every interactive element
- Some decorative photography carries no alternative text, which is correct, but the distinction has not been reviewed image by image
If something does not work
Email contact@containaura.com or call +1 479-581-4872 and tell us the page and what happened. We aim to respond within 5 business days. If a page is unusable for you, we will provide the same information in another format — a phone call, a plain-text email, or a document — at no cost and without requiring you to explain why.
How we test
Today: manual checks by the people who build the site, against the list above. That is not enough, and we are saying so rather than implying more. Our next step is an audit by someone who is not us, covering automated tooling, keyboard-only navigation and screen reader testing. When it is done, its date, its author and the issues it found will be published on this page — including the ones we have not fixed yet.