Accessibility Statement

Our standard

We develop against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA as our working standard. WCAG 2.1 AA is the benchmark the Department of Justice has pointed to for web content; we work to 2.2 because it adds criteria that matter here, including focus appearance, target size, and not requiring information a visitor has already entered.

We describe this as our development standard and our ongoing commitment. We do not claim certification, and no automated tool or vendor overlay can substitute for that work.

What we have built in

• Semantic structure — real landmarks, one h1 per page, headings in order, and lists marked up as lists.
• Keyboard access — every control is reachable and operable by keyboard, with a visible focus indicator. The impact models follow the standard tabs pattern with arrow, Home, and End keys. The privacy dialog traps focus while open and returns it on close.
• Skip link — a “Skip to main content” link is the first thing in the tab order.
• Contrast — body text meets or exceeds 4.5:1 and large text 3:1. Brass is used for rules, marks, and large numerals, never for small text on light backgrounds.
• Forms — every field has a visible, programmatically associated label. Errors are announced, listed in a summary that receives focus, linked to their fields, and written to name the problem and the fix. Required fields are marked in the accessible name, not by color or an asterisk alone.
• Results are announced — modeled results are exposed to screen readers through a polite live region, including the statement that they are illustrative.
• Motion — all scroll animation, counting numerals, and the canvas field respect prefers-reduced-motion. Nothing loops or autoplays with sound.
• No script, no barrier — content is never hidden behind JavaScript. Reveal animations only hide content when scripting is available to reveal it.
• No CAPTCHA — spam is handled with a hidden field rather than a visual puzzle, which is a known barrier.
• Text and zoom — layouts use relative units and reflow to 400% zoom without loss of content.
• Images — meaningful images carry text alternatives; decorative graphics are hidden from assistive technology.

Known gaps

We would rather name these than imply they do not exist.

• Video captions. Testimonial videos are placeholders. When real video is added it must ship with accurate synchronized captions, a transcript, and audio description where visual information is not conveyed in the audio. This is a launch blocker.
• Photography alternatives. Image frames currently hold decorative placeholder artwork, which carries no information and is correctly hidden from assistive technology. Each final photograph will need a text alternative that conveys its purpose.
• Assistive technology testing. The site has been developed against the standard and checked programmatically. Testing with real users of screen readers has not yet been carried out. It should be, before launch.
• Horizontal scroll section. The brand section moves horizontally with vertical scroll. It is fully readable without that motion, and it flattens under reduced-motion, but it should be included in assistive technology testing.

Tell us about a barrier

If any part of this site is difficult or impossible for you to use, please tell us — we treat it as a defect, not a request.

Email contact@gonovo.ai. Please describe the page, what you were trying to do, and the assistive technology or settings you were using if you are comfortable sharing that. We aim to acknowledge within five business days and will tell you what we intend to do and when.

If you need information from this site in another format, or need help completing the application, ask and we will provide an alternative — including completing it with you directly by email or phone.

Assessment and review

This statement reflects a self-assessment. [Recommended before launch: an independent accessibility audit including manual screen reader testing, and a re-review of this statement afterward.]