Accessibility Statement
Last updated: September 17, 2026
A map that only works with a mouse and a pair of working eyes is a map that excludes buyers. We build this site and every community map we deliver to be operable by keyboard, readable by a screen reader, and legible at real-world contrast. This page says what we have done, what we have not solved yet, and how to tell us when we get it wrong.
Our commitment
We want every person to be able to browse this site, explore a community map and contact us, regardless of how they use a computer.
Accessibility is part of how a map gets built here, not a pass at the end. When we ship a new feature, keyboard operation and a text equivalent are part of it being finished.
The standard we aim for
We target the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, published by the W3C. It is the standard most commonly referenced in the United States for websites.
To be straight about it: we are working toward that standard and we do not claim full conformance. We hold no accessibility certification, and no automated widget or overlay can grant one. Parts of this site meet Level AA today, and the known gaps are listed further down.
What we have built into this website
- Keyboard operation. Every link, button, form field, tab, accordion and dialog can be reached and operated with a keyboard alone. No keyboard traps.
- Visible focus. A clearly visible focus indicator follows the keyboard, and we never remove focus styling without replacing it with something stronger.
- A skip link. The first thing a keyboard or screen reader user hits is a link that jumps straight past the navigation to the main content.
- Real form labels. Every field has a real label element tied to it, not a placeholder pretending to be one. Required fields are marked in text, and errors are described in words next to the field, not by turning the border red.
- Alt text. Every meaningful image carries a text alternative. Decorative images are marked as decorative so screen readers skip them.
- Contrast. Body text and interactive elements meet the 4.5:1 contrast ratio, and large text meets 3:1. We check this on the dark theme, where it is easiest to get wrong.
- Structure. One h1 per page, headings in order, landmark regions, and a page title that says where you are.
- Zoom and reflow. The site is usable at 200 percent zoom and on a narrow window without horizontal scrolling.
- Reduced motion. If your system asks for reduced motion, the background animation, reveal effects and camera moves are turned off.
What we have built into the map viewer
The 3D map is the hardest part to get right, so it does not stand alone.
- An accessible lot table ships with every map. It lists every lot with its number, size in acres and square feet, dimensions, exposure and current status — reserved, under contract, sold, available. It is real HTML, sortable and filterable, it works without the 3D canvas, and it carries the same data the map does because it reads the same record.
- Keyboard operation of the map. Lots can be moved through and selected with the keyboard, and the detail panel that opens can be read and closed without a mouse.
- Visible focus on lots. The focused lot is outlined on the map, not just highlighted by a color shift.
- Status is never color alone. Every lot status is conveyed three ways: by color, by a distinct shape or pattern, and by a text label in the lot detail and in the table. A person who cannot distinguish green from red still sees which lots are sold.
- Reduced motion in the viewer. Camera fly-throughs and transitions are shortened or removed when your system asks for reduced motion.
- Text alternatives. The canvas has a text description, and the table is offered as the equivalent route to the same information rather than hidden behind a toggle.
- Captions on video. We publish no video on this site today. Any video added later carries captions and a transcript before it goes live, not afterwards.
Known limitations
Stating these honestly is more useful than claiming we have solved everything.
- A 3D canvas cannot convey shape and spatial relationships to a screen reader. No implementation can. The accessible lot table is the equivalent route to that information, and we treat it as required output, not as a fallback.
- Third-party embeds — a video player, a mapping service, a scheduling tool — are outside our code. We only add ones that are reasonably accessible, and we will replace anything that is not, but we do not control their markup.
- Older sample content may lag the current standard. Sample communities built early may have thinner alt text or lower-contrast labels than what we ship today. We fix these as we find them.
- Customer-supplied content. Text, images and documents a customer publishes through their own admin panel are written by them. We provide the accessible container and prompt for alt text; we cannot guarantee what goes in it.
- Downloadable documents. We publish no PDFs on this site. If we add one it will be tagged and readable, or paired with an HTML version that carries the same content — an untagged PDF is a barrier, not a download.
How we test
- Keyboard-only passes on every new page and component, tab from the top to the bottom of the page.
- Automated checks during the build to catch missing labels, missing alt text, bad heading order and contrast failures.
- Manual contrast checks against the dark theme in design, before code.
- Screen reader spot checks on key journeys: home, a community map, the lot table and the contact form. We test NVDA with Firefox and VoiceOver with Safari.
- We have not yet commissioned an independent accessibility audit or testing with people who use assistive technology daily. We intend to, and until we have, we are not going to claim a level of assurance we have not paid for.
Report a barrier
If any part of this site or of a Plotex map stops you from doing something, tell us. Email accessibility@plotex.us.
It helps if you can include the page address, what you were trying to do, and the browser and assistive technology you were using. If that is more detail than you have, send us what you can — a short description is enough to start.
We aim to acknowledge every report within 5 business days and to give you a plan or a fix date in that reply. If something takes longer to engineer, we will say so rather than go quiet, and where we can we will get you the information you needed another way in the meantime.
Feedback is welcome
We would rather hear that something is broken than have someone quietly leave. Suggestions, complaints and "this was annoying" notes are all useful, and none of them are unwelcome.
Email accessibility@plotex.us, or use any contact form on the site.
Ongoing work
This statement is reviewed whenever we make a significant change to the site or the viewer, and at least once a year. The date at the top shows the last review.
Questions
Email hello@plotex.us and we will route it to the right person. For privacy requests use privacy@plotex.us; for accessibility barriers use accessibility@plotex.us.