Accessibility statement

Fairview Audit wants everyone who needs to reach a partner firm to be able to use this site. This statement describes our target, what we have built in, what we do not control and how to tell us about a problem. Please read it as a status report, not as a claim of conformance. W3C guidance suggests a statement name its standard, its known limits and a contact for problems. The site has not yet been tested.

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG 2.2 is a W3C Recommendation with three levels: A, AA and AAA. That is a target. We have not yet tested the site against it, and we do not claim that it meets it. After testing, we will update this page with the result and the date.

Measures built into the design

The site was designed with these measures in mind. ADA.gov guidance lists contrast, keyboard use and labeled forms among common practices:

Text has a contrast ratio of at least 4.5:1 against its background.
Control borders and focus rings have a contrast ratio of at least 3:1, in both the light and dark themes.
Every interactive element shows a visible focus ring when you reach it with a keyboard.
Links are underlined, so they do not depend on color alone to stand out.
Status is never shown by color alone. Messages also use words or symbols.
Pages are designed to work at phone width, without sideways scrolling for ordinary text.

These are design measures, not test results. Until testing is done, some may not work as intended.

What has not yet been done

We have not yet carried out a full audit with automated tools, keyboard checks or screen reader checks. We have not asked disabled users to test the forms. These steps are planned. The date of the last review is [CONFIRM: last review date].

How we plan to test

Testing will combine automated checks with manual ones, because a clean automated report does not show that a site is accessible. Manual checks will cover keyboard-only use, zoom and text resizing, and at least one screen reader. We will check the light and dark themes separately, because contrast can differ between them. We will also review the request forms on a phone. Problems found will be logged and fixed in order of how much they block a task.

Known limits

Some content comes from sources we do not control. WCAG treats outside content as a reason a page may reach only partial conformance, so we will watch it.

Third-party embeds. If a form or other feature is provided by a third party, its accessibility depends on that provider.
Documents from firms. Checklists, reports and other documents supplied by partner firms may not be fully accessible. If you cannot use one, tell us and we will ask the firm for another format.
Site software. The site is built with a static site builder. Some elements may come from its default templates, and we may not be able to change them.

Forms

The request forms are the main task on the site. Each field should have a clear label, and errors should be described in words. If a form does not work for you, contact us and we will take your request in another way. See Request a professional for the three request paths.

How to report a barrier

If you cannot use part of this site, tell us. Include the page, what you tried to do, what happened and the device or assistive technology you used.

Email: [CONFIRM: contact email for accessibility reports]
Phone: [CONFIRM: phone for accessibility reports]
Response time: [CONFIRM: response time]

You can also use the Contact page. We will try to give you the information or service you need in another way while we fix the problem.

Changes to this statement

We will revise this page after each round of testing and whenever we change the site in a way that affects access. The date of the last review will be shown above once it is set.

The FAQ explains common points about requests. The Privacy policy explains how we handle the details you give us when you ask for help.

Note: This statement is a draft. It will be updated after testing and review.