Accessibility Statement

1. Our approach#

Accessibility is treated as a design, content and engineering requirement. The Website aims for clear structure, readable language, keyboard operation, visible focus, sufficient contrast, adaptable layout and alternatives for motion. Product and legal content should remain usable without relying on a single sensory cue.

2. Standards-oriented baseline#

SRC AI uses WCAG 2.2 Level AA as a quality target where applicable to the Website. A target is not a certification. Conformance must be evaluated against the final production content, Providers and assistive-technology behavior and may change as the site evolves.

3. Current features#

The current baseline includes semantic landmarks and headings, a skip link, labeled forms, keyboard-operable navigation and dialogs, visible focus, status announcements, responsive touch targets, reduced-motion handling, a pause control for the 3D experience, text alternatives and printable legal content. Long policies include a table of contents and section anchors.

4. Assistive technologies reviewed#

Automated checks and keyboard review cover modern Chromium rendering at desktop, tablet and mobile sizes, including reduced-motion preferences. Screen-reader and broader cross-browser user testing remain required before production. SRC AI does not claim support for a named assistive technology that has not yet been tested.

5. Known limitations#

The optional 3D canvas is decorative and has a static fallback, but complex visual motion may not convey useful information to every user. Third-party destinations and future embedded Providers can have accessibility characteristics outside SRC AI’s control. Protected administrative experiences require continued accessibility review. Production legal review may add long or complex language that requires continued readability work.

6. Feedback#

If you encounter a barrier, use the contact form and select Support. Describe the page, task, device, browser and assistive technology if you are comfortable doing so, and state the format or help you need. Do not include unnecessary medical or sensitive information.

7. Response and alternatives#

SRC AI will review an accessibility report, prioritize barriers by impact and provide a reasonable accessible alternative where practical. Response and remediation timing depend on severity, complexity and Provider involvement; this Statement does not promise a universal deadline.

8. Ongoing improvement#

Accessibility regression covers changed public and protected administrative interfaces, long legal documents, forms, dialogs, navigation, Assistant interactions and responsive layouts. SRC AI should continue screen-reader testing, browser coverage, content review and a process for tracking and verifying reported barriers.

9. Contact and updates#

Questions, notices, complaints and requests may be sent through the SRC AI contact form. Use the category that best matches the request and provide enough information for SRC AI to identify the relevant interaction. Do not send account credentials, payment-card data, identity documents or other sensitive records through a public form. SRC AI may ask for proportionate evidence of identity or authority through an appropriate protected channel before acting on a request.

Material accessibility changes and known limitations should be reflected in the version and Last Updated date. Formal legal or accessibility contact details will come from the verified Company Profile when published.

10. Testing method and release checks#

Changed interfaces should be reviewed with keyboard-only navigation, visible focus, zoom and reflow, reduced motion, common desktop and mobile widths, semantic inspection and automated rules. Long legal pages, forms, dialogs, validation messages, the Assistant and protected administrative flows receive focused regression because failures there can block important tasks.

Automated tools find only part of the problem. Production readiness also requires representative screen-reader and user testing, browser coverage and manual review of content order, names, instructions and error recovery. Results should record the version and scope rather than imply permanent certification.

11. Content and document accessibility#

Writers and editors should use descriptive headings, meaningful link text, plain explanations, lists and tables only where structure helps, and text alternatives that communicate function without duplicating decoration. Legal documents include landmarks, a section table of contents, anchor links, readable line length, visible dates/version and print rules.

A published revision should be checked after editing because long words, URLs, tables and copied formatting can introduce overflow or confusing hierarchy. An accessible alternative should preserve the substance and version of the authoritative content.

12. Third-party and future service accessibility#

External social sites, email clients, registries, payment services and future Providers control their own interfaces. SRC AI should consider accessibility during selection and configuration and provide an alternate support path where practical, but cannot certify a third-party service it does not control.

A new embedded widget, document workflow or model interface must pass release review before activation. Provider branding or technical convenience does not justify an unlabeled control, keyboard trap, inaccessible challenge or motion that cannot be stopped.

13. Governance and progress reporting#

Accessibility issues should be recorded with affected task, impact, workaround, owner, priority and verification result. Severe barriers to authentication, legal information, privacy choice or contact deserve prompt attention. Lower-impact improvements remain part of planned maintenance rather than disappearing after acknowledgement.

SRC AI may publish meaningful progress and known limitations when supported by evidence. It should not claim WCAG conformance, universal assistive-technology support or a remediation deadline that has not been tested and approved.