Accessibility
We want everyone to be able to use BuildVue, including people who use a keyboard instead of a mouse, a screen reader, screen magnification or voice control.
The standard we aim for
BuildVue aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. Every page type is checked automatically against that standard before each release and every night, and the main tasks (finding a project, searching and filtering, reading a project page, signing in and downloading a spreadsheet) are tested with a keyboard alone and with a screen reader.
What to expect
- Every page can be used with a keyboard, starts with a link that skips straight to the main content, and shows a clear outline around whatever you are on.
- Text meets the contrast the standard asks for.
- Our emails have headings and a language set, so screen readers read them in order.
- Spreadsheet downloads have one labelled header row set up as a table, so each value is read with its column name.
Known limits
- The map. You can move and zoom the map with the keyboard, and its buttons are labelled, but the project pins on it cannot be reached with a keyboard or read by a screen reader. The projects in view are also listed beside the map as ordinary links. Signed out, that list shows the first six. Signed in, it shows them all.
- Documents from city and county portals. Permit documents and plans we link to are published by the city or county. Many are scanned images without readable text, and we cannot change them.
Tell us about a problem
If something on BuildVue is hard to use, email support@buildvue.co or use the contact page. Tell us the page and what happened. We reply within five business days, and if you need information from the site in another format, we will send it to you.
Last reviewed 26 September 2026.