Accessibility Conformance Report

Most marketing and app imagery is decorative or text-backed, but a complete alt-text audit of all feature mockups, charts, and generated images is still required.

The scoped product does not include prerecorded audio-only or video-only content.

The scoped product does not include prerecorded video with audio.

The scoped product does not include prerecorded synchronized media.

Pages generally use semantic headings, labels, and native controls. Custom quiz choices and feature mockups still need a full screen-reader structure pass.

Core pages are built in a logical document order, but the full quiz and responsive layouts still need keyboard and screen-reader sequence verification.

Instructions are conveyed with text labels and visible UI copy rather than relying only on shape, color, location, or sound.

Most statuses pair color with text, but charts, maps, and selected-state treatments still need a complete review.

The scoped product does not auto-play audio.

Native links, buttons, and forms are keyboard reachable. Full keyboard verification remains needed for custom quiz controls and interactive mockups.

No known keyboard traps are documented in scoped flows, but a complete keyboard-only pass has not yet been completed.

Blueprint does not expose single-character keyboard shortcuts in the scoped public flows.

The scoped product does not require users to complete quiz, login, or marketing-page tasks within a short timed window.

Animations are primarily decorative and do not block task completion. A reduced-motion and persistent animation review is still required.

No scoped content is designed to flash more than three times per second.

Some pages include skip links, but skip navigation is not yet verified across every public route and quiz step.

Public pages and scoped flows provide page metadata or route-level titles through the Next.js app structure.

The general layout follows DOM order, but every quiz step and responsive state still needs manual keyboard-order verification.

Most links use descriptive visible text. Icon-only and repeated links still need a full accessible-name audit.

The scoped product does not require multipoint or path-based pointer gestures.

Most interactions use native click controls. Custom controls still need review for cancellation and accidental activation behavior.

Visible labels generally match control purpose. A complete audit is still needed for icon buttons, quiz chips, and custom inputs.

The scoped product does not use device motion or user motion as an input method.

The root application layout declares English with html lang="en".

Focused controls are not intended to trigger unexpected navigation or major context changes.

Forms and quiz controls generally require explicit actions to continue, but autosave and step transitions still need an accessibility behavior review.

Forms show visible errors in key flows. A full pass is needed to confirm every error is programmatically associated with its field.

Most fields have visible prompts or labels. A full audit is still needed for every quiz input, email field, and custom selector.

The app is built with React and Next.js, but automated accessibility validation is not yet wired into CI.

Native controls provide names and roles. Custom controls still require full screen-reader and automated accessibility verification.

The scoped product does not include live audio or live video.

The scoped product does not include prerecorded synchronized media.

The scoped product is responsive and does not restrict use to one display orientation.

Common auth fields can be identified visually. Autocomplete and programmatic input-purpose coverage still need verification.

The design uses high-contrast dark surfaces, but a route-by-route contrast audit has not yet been completed.

Responsive layouts generally support browser zoom. Full verification at 200 percent zoom is still required.

Primary product and marketing copy is rendered as real text rather than images of text.

Pages are responsive across common mobile and desktop widths. Full reflow testing at WCAG target widths is still needed.

Focus states and controls are visually distinct in many places. A full non-text contrast audit is still needed for all controls, charts, and icons.

Layouts use flexible text containers, but text-spacing overrides have not yet been manually verified across all scoped pages.

Most content is visible without hover-only disclosure. Any hover, tooltip, or focus-revealed content still needs a full review.

Public content is reachable through navigation, footer links, direct URLs, and sitemap entries where appropriate.

Most headings and labels describe their topic or purpose. A full page-by-page heading hierarchy audit remains open.

Many links and controls have visible focus styles. Full verification is still needed for every custom control and quiz state.

The scoped product content is primarily English and does not include meaningful passages in other languages.

Public pages use consistent navigation and footer patterns. Quiz steps intentionally use a focused flow.

Repeated actions are generally labeled consistently. A full copy and accessible-name pass remains open.

Many errors include next-step guidance. A full validation pass is still needed for all forms and quiz inputs.

High-impact actions should use confirmation or recovery patterns. Current data export and account flows need formal review before this can be marked Supports.

The app shows loading, saving, and error states visually. Programmatic announcement coverage for status messages still needs verification.