Our current accessibility status.

Assessment and target

Current assessment status: not formally assessed. Metropolygonia has not completed a comprehensive manual and assistive-technology audit against the Web Content Accessibility Guidelines.

Our working target is WCAG 2.2 Level AA. A target is not the same as a conformance claim. We will only state conformance after the relevant pages and workflows have been evaluated against all applicable requirements and known failures have been addressed or disclosed.

Where access may be difficult

• The WebGL 3D editor is visually and pointer intensive. Camera orbit, object inspection, city placement and direct manipulation do not yet have a complete nonvisual equivalent. Some workflows may not be practical with a screen reader or keyboard alone.
• Keyboard coverage has not been comprehensively audited. Standard form controls and page navigation can be reached in many areas, but focus order, shortcuts and modal focus handling require broader testing across the complete editor.
• Dynamic status and model changes need further assistive-technology testing. Geometry generation, export progress, validation messages and changing 3D state may not always be announced with enough context.
• Product demonstration video alternatives are incomplete. Public video sections do not yet provide a complete captioned and text-transcript alternative for every visual step.
• Dense controls may be demanding at high zoom or on narrow screens. The generator contains many related parameters and some combinations still need responsive reflow testing.

If one of these limitations blocks your use, contact us with the page, task and preferred alternative. We can provide available documentation in plain text and use the report to prioritise a fix.

What the public content currently supports

The crawlable product and documentation pages use semantic headings, labelled navigation landmarks, a skip link, visible keyboard focus, descriptive link text and responsive layouts. Content remains readable without the 3D editor and respects the browser's reduced-motion preference.

Controls on these pages use native links and buttons. Decorative brand marks have empty alternative text, while page titles, breadcrumbs and unique headings identify the current location. Colour is not intended to be the only way that essential document meaning is conveyed.

These measures improve access but do not replace testing with disabled users, keyboard-only navigation, screen readers, magnification, voice control and different input devices.

Technical environment

The informational pages are built with HTML and CSS, with JavaScript used for consent-aware analytics and cookie settings. The interactive generator additionally requires JavaScript and a WebGL 2-capable browser. Its visual 3D canvas and live parameter controls are more demanding than the static documentation.

Accessibility depends on the combined behaviour of the site, browser, operating system and assistive technology. When reporting a problem, including those versions helps us reproduce it.

Report an accessibility problem

Email kunzdesign2017@gmail.com with the subject “Metropolygonia accessibility feedback”. Please include, when possible:

• the page address or part of the application;
• the task you were trying to complete;
• what happened and what you expected;
• your browser, operating system and assistive technology;
• the alternative format or support that would help.

We review accessibility reports and will reply with the information available, a workaround where practical, or the status of investigation. Complex 3D interaction may take longer to redesign than a documentation issue, but both kinds of report are useful.

How this statement will change

We will update the date, status and known limitations when a material accessibility review is completed or the product changes substantially. Future claims will distinguish automated checks, manual testing and assistive-technology testing rather than treating one scanner as proof of conformance.

This structure follows the W3C Web Accessibility Initiative's guidance on developing accessibility statements: communicate a commitment, name the applicable standard or target, describe the current status, acknowledge limitations and provide a feedback channel.