Accessibility and bilingual readiness

MetaSolve Accessibility Conformance Report

VPAT-style conformance summary for MetaSolve VaaS customer-facing services, documentation, reports, and procurement artifacts. This report is an internal readiness artifact and does not represent third-party certification.

Status Readiness support

Controls are designed to support WCAG 2.2 AA procurement review and government accessibility expectations.

Scope Public web, dashboard, API docs, PDFs

Includes customer-facing navigation, keyboard operation, screen-reader labels, generated reports, and procurement materials.

Languages English primary, French ready

French customer-facing government materials are tracked as a readiness requirement before formal procurement submission.

WCAG 2.2 AA Conformance Matrix

Criterion Area Target Current Evidence Status
Keyboard accessibility All controls reachable and operable by keyboard Semantic links/buttons, focus styles, skip-link support, no mouse-only required workflows Implemented, monitor continuously
Screen-reader support Names, roles, labels, landmarks, and live-region messages ARIA labels on icon actions, semantic landmarks, form labels, status regions Implemented, audit before release
Contrast AA contrast for normal text and UI controls High-contrast text tokens, visible focus states, non-color status text Readiness support
Accessible PDFs Tagged structure, document title, headings, tables, alt text, reading order PDF generation checklist and manual validation requirement before customer delivery Pending formal PDF audit
Captions and transcripts Captions/transcripts for demos, onboarding videos, and training material Requirement recorded for sales, support, and government procurement materials Governance requirement
Error identification Clear field errors and recovery guidance Registration, verification, and assurance workflows use explicit validation copy Implemented, monitor continuously

English and French Government Materials

MetaSolve maintains bilingual readiness for public-sector customer-facing artifacts. French material must be reviewed before submission to procurement teams.

  • Customer-facing web pages: English production content with French readiness backlog.
  • Procurement documents: Accessible procurement documents tracked for WCAG and bilingual review.
  • API documentation: English API docs with return navigation, keyboard access, and screen-reader-friendly structure.
  • Generated evidence reports: PDF accessibility validation required before regulated customer delivery.

Limitations and Next Reviews

  • This VPAT-style report is not an independent accessibility certification.
  • Accessible PDF output requires a separate tagged-PDF validation pass before contractual reliance.
  • French content is readiness-scoped until formal translation and reviewer approval are recorded.
  • Next review: before any public-sector procurement submission or major user-interface release.