Accessibility statement
How arch2video.com supports keyboard, screen-reader and low-vision use, what has been done so far, known limitations, and how to report a problem.
Arch2Video wants every architect and designer to be able to read this site, watch the example films and use the product with the tools they prefer. We work toward the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA and treat reported problems as bugs.
What is in place
- A "Skip to content" link is the first focusable element on every page, and every page has one main landmark.
- All navigation, the example-film chooser (arrow keys move between projects), plan buttons, forms and dialogs work with a keyboard, with visible focus outlines.
- Form fields carry programmatic labels; validation errors are announced, marked with
aria-invalidand focus moves to the first problem field. - Text colors meet the AA contrast ratio against their backgrounds, including small labels.
- Interactive targets on phones are at least 44 pixels tall.
- Pages declare their language, so screen readers switch voices correctly when you change the site language.
- Animations respect the operating-system "reduce motion" setting.
- Example films use the browser's native video player with standard controls.
Known limitations
- The example films have no captions or audio description; they contain music only, no speech.
- Payment happens on Stripe's hosted checkout and Google sign-in uses Google's own button; their accessibility is maintained by those companies.
- Generated films are delivered as MP4 files without captions; add captions in the platform you publish to if your audience needs them.
Report a problem
If something on this site or in the product does not work with your assistive technology, use the contact form and mention the page, the browser and the tool you use. We reply within one business day and fix confirmed problems in the next release.