This site should be readable and usable for everyone, including people who use a screen reader, a keyboard or a magnifier. This page explains what is in place and how to report a problem.
How is the site built for accessibility?
The site uses real headings in a logical order, descriptive link text and alt text on meaningful images. Color contrast is checked for body text and buttons. The layout works at a phone width and at a desktop width, and it does not rely on a mouse. Form fields have visible labels, and the form can be reached with the keyboard. The phone number is a real link, so it can be activated without copying digits. The site avoids autoplay video and flashing content. Animation is limited and does not carry information that is unavailable elsewhere. If a page uses a table, the table has headers. If a page uses an icon, the icon has a text label or an accessible name.
What should I do if something does not work?
Send a message through the contact form or call the number on the site and describe the page and the problem. Tell us what device and browser you used, what you expected and what happened instead. A screenshot helps if you can take one. If a form field blocks you, say which field and what the screen reader announced. If a page is hard to read, say which text and which zoom level. The report goes to the person who maintains the site, and the issue is reviewed. You can report a problem without disclosing a disability. You can ask for the information on a page in a different format, such as a plain text version.
What is the plan for fixes?
Accessibility is an ongoing check. The site reviews headings, contrast, focus order and form labels when a page is added or changed. If a fix needs a design change, the issue is prioritized against the pages that carry the most important information, such as contact and cost. Each report is reviewed. If a third-party tool, such as a form provider or a phone system, is the source of the problem, the other channel, the contact form or the phone line, is an alternative path. A fix that affects a shared component is tested on every page that uses it. The goal is a site that works.
Related
- Privacy policy explains how information is handled.
- Terms of use covers the limits of the content on this site.
- Complaints policy explains how to raise a concern.
- Contact is where to report an accessibility problem.
