Accessibility statement

In short

• Maps and 3D have text equals. The parcel page has a “Describe this view” panel. The Planner, Policy and Nonprofit maps have a Table view.
• Everything works from the keyboard, including moving the maps and the 3D view.
• Screen readers hear changes. New results are announced after a filter, slider or what-if change.
• The PDF report is tagged, with real text, bookmarks, a set language and alt text on the site plan and charts.
• It is not finished. We have not yet tested with disabled users. See what is not done yet.

What works today

Seeing the maps and 3D without seeing them

• On a parcel page, Describe this view (next to the view buttons) gives the view in words: lot size, slope, the share of the lot in each hazard or rule overlay, existing buildings, the setbacks, the area left to build on, and the studied building. It is built from the same numbers the map draws.
• The Planner has a Table view. The ranked table lists the same parcels as the map, in score order.
• The Policy page has a Table view. It hides the map and opens the neighborhood and council-district tables.
• The Nonprofit need map has a Table view. It lists the census tracts or block groups in the map's area, with every value.
• Score bands use words (Easy, Moderate, Hard), not color alone.

Keyboard

• 2D and terrain maps: Tab to the map, then use the arrow keys to pan and + or − to zoom. On the parcel terrain map, Shift with the arrow keys rotates and tilts.
• 3D Photoreal view: Tab to it, then the arrow keys orbit and tilt, + and − zoom, and Home resets the view. The on-screen camera buttons do the same things.
• Sliders never need dragging: the seat and Build it in 3D sliders have − and + buttons next to their value, and the build-quality slider has a button for each tier. All sliders also move with the arrow keys.
• Receipts, drawers and menus are buttons: they open with Enter or Space, not on hover.

Screen readers

• Pages have one main area, labeled regions and headings in order, so you can jump around by landmark or heading.
• Changes are announced politely: the number of parcels after a Planner filter, the headline ranges after a Policy lever, the new layout after a Build it in 3D change, and the new result after a “Does it pencil?” edit.

Motion

• If your device asks for reduced motion, the map fly-in, the slow orbit, the Policy map's “wave” and page animations are turned off. The view jumps straight to where it ends.

The PDF report

• The Feasibility Study PDF is a tagged PDF. It has real text (not pictures of text), bookmarks for each section, and its language set to English. The site plan and charts have alt text written from their own numbers.

How we checked

• An automated scan with axe-core (WCAG 2.0, 2.1 and 2.2, levels A and AA, plus best practices) on the main pages: home, a parcel page, its report, the Planner, Policy and Nonprofit pages, and the methods, limitations and AI pages.
• A reading of each page's accessibility tree, the structure a screen reader uses, along the main path: search, parcel page, a receipt, and the report.
• Keyboard checks of the maps, the 3D view, the sliders and the Table view buttons.

Automated tools find only some problems. These checks are a start, not proof that the site is fully accessible.

What is not done yet

• No testing with disabled users yet. We have not run a full session with VoiceOver, JAWS or NVDA by a person who uses them every day.
• The PDF uses the tags Chrome writes when it prints. We have not checked it with a PDF accessibility checker.
• Map dots on the Planner, Policy and Nonprofit maps can't be reached one by one with the keyboard. Use the tables, which list the same parcels (Planner) or the same totals by area (Policy, Nonprofit).
• The Policy map's hover card (one parcel's homes before and after) needs a mouse. The tables have the totals, not each parcel.
• The 3D Photoreal city comes from Google. We can describe our lot, rules and building, but not every detail of the photo mesh.
• Small screens and 200% zoom: the parcel page's floating panels can crowd the map on narrow screens. Scroll the side panel, or use the report.
• Language: the site is in English only; there is no translated version.

Tell us

If something doesn't work for you, open an issue on GitHub and say which page and what happened. See also Limitations and Data and methods.