Accessibility
Accessibility statement
Last updated 20 September 2026. Next review 20 March 2027.
FOGLE is sold to public bodies, which means accessibility is a procurement requirement rather than a nice to have. This page says what we have done, what we have tested, and what still needs work.
Standard we are working to
We target WCAG 2.1 Level AA, which is the standard referenced by Section 508 of the Rehabilitation Act and by most state and municipal procurement rules. Where a municipality needs a formal accessibility conformance report, write to us and we will provide one for the current release.
What is in place
- Keyboard. Every control can be reached and operated by keyboard, in a logical order. A skip link jumps past the navigation to the main content. The 3D model can be rotated and zoomed with the arrow keys once focused.
- Focus. Focus is always visible, with a two pixel outline and an offset, and it is never removed.
- Contrast. Body text, headings and interface labels meet or exceed the 4.5 to 1 ratio for normal text, in both light and dark appearance. Both themes were built as full palettes rather than one being derived from the other by inversion.
- Structure. Headings are properly nested, landmarks are used, and tables have header cells and scopes.
- Forms. Every field has a visible, associated label. Errors are announced, described in words rather than by colour alone, and the first field needing attention receives focus.
- Images. Meaningful images carry alternative text. Decorative ones are hidden from assistive technology.
- Motion. All animation respects
prefers-reduced-motion. With it set, the model stops rotating on its own and page transitions are removed. - Zoom and reflow. The site reflows to 320 pixels wide and remains usable at 200 per cent zoom, with no horizontal scrolling.
- Colour. No information is conveyed by colour alone. View modes carry text labels, and legends name each band.
- Language and titles. Each page declares its language and has a unique, descriptive title.
- Print. A print stylesheet produces a readable document, with link destinations written out.
Known limitations
Stating these plainly is more useful than claiming full conformance.
- The 3D model is visual. The interactive model is drawn on a canvas. It carries a text description of what it shows and its controls work by keyboard, but the spatial relationships in it cannot be conveyed fully to a screen reader. Where a decision depends on reading the model, the underlying figures are available in tabular form on request, and we will supply them in an accessible format for any municipality that needs one.
- Map imagery. Satellite and terrain imagery in the full viewer is inherently visual and carries no text equivalent.
- Third party components. The map library used in the full viewer has its own accessibility characteristics, which we do not control. We test what we can and report upstream.
We are working on a tabular companion view for the model so that every figure shown graphically is also available as structured text in the product itself.
How this has been tested
- Keyboard only navigation through every page and flow.
- Contrast ratios checked against the WCAG formula for every text and interface colour pair, in both themes.
- Reflow and zoom checked from 320 pixels upward.
- Reduced motion and forced colour preferences exercised.
- Automated checks run against each page.
We have not yet commissioned an independent audit by a third party specialist, and we will say so rather than imply otherwise. That is planned, and a municipality requiring one before purchase should tell us so we can schedule it.
Reporting a barrier
If something here blocks you, tell us and we will fix it.
Write to Fogle.HQ@gmail.com with the subject line Accessibility. Describe the page, what you were trying to do, and the assistive technology and browser you were using if you know them.
- We will acknowledge within 2 business days.
- We will give you an assessment and a plan within 10 business days.
- If a fix will take longer, we will offer the information you needed in another format in the meantime.
If you are not satisfied with our response, tell us and it will be escalated. For a barrier on a municipal deployment, you may also raise it with that municipality's ADA coordinator.