ACR · WCAG 2.2
Accessibility conformance statement (VPAT-style)
A VPAT-style Accessibility Conformance Report for Evolve learner and admin surfaces, including Arabic RTL — Supports / Partially / Does not / N/A, with remarks.
A VPAT (Voluntary Product Accessibility Template) or ACR states, criterion by criterion, whether a product Supports, Partially Supports, or Does Not Support WCAG success criteria. For a bilingual LMS, the report must cover Arabic RTL layout, keyboard paths, focus, contrast, and captions — an English-only audit is not enough for Gulf programmes.
Innovito Evolve — learner and admin web application
WCAG 2.2 Level A and AA (selected criteria published here)
Internal design review, keyboard walkthrough of core learner/admin flows, Arabic RTL layout pass, and caption/transcript checks where video is in scope. This is a VPAT-style ACR, not a third-party certification. Independent audit letters, when commissioned, are evaluator files.
Export this pack · No gate. No nurture sequence. Downloads are generated in your browser.
| Criterion | Conformance | Remarks |
|---|---|---|
1.1.1 · Non-text content A | Partially supports | Product UI controls have accessible names on core flows. Buyer-uploaded SCORM/media inherits the package author’s alt text — Innovito cannot certify third-party packages. |
1.3.1 · Info and relationships A | Partially supports | Headings and labels on core Evolve screens. Complex custom dashboards and imported content vary; UAT should include a screen-reader spot check in Arabic and English. |
1.3.2 · Meaningful sequence (incl. RTL) A | Partially supports | Arabic locale sets dir=rtl on public and product surfaces. Reading order is verified on core learner/admin screens; edge widgets are listed as residual risk. |
1.4.3 · Contrast (minimum) AA | Partially supports | Brand tokens target WCAG contrast on primary text. Charts, heatmaps, and buyer-branded themes can fail — treat theme customisation as a scored UAT item. |
1.4.4 · Resize text AA | Supports | Browser zoom to 200% on core flows without loss of primary actions. Horizontal scrolling may appear on dense admin tables — known residual. |
1.4.10 · Reflow AA | Partially supports | Learner flows reflow. Some admin data tables remain two-dimensional by design. |
2.1.1 · Keyboard A | Partially supports | Core assign / launch / complete / report paths are keyboard reachable. Drag-and-drop authoring in Studio has an alternative (select then place). Unreachable widgets are defects, not “won’t fix”. |
2.1.2 · No keyboard trap A | Supports | Modals and drawers expose a close control and Escape. Embedded SCORM players follow the package; traps inside third-party content are the package author’s responsibility. |
2.4.1 · Bypass blocks A | Partially supports | Skip-to-content on public marketing chrome. Product app navigation is persistent; skip patterns on dense admin shells are on the improvement list. |
2.4.3 · Focus order A | Partially supports | Focus order follows visual order on core RTL and LTR screens. Custom HTML in content lots is the buyer’s QC. |
2.4.7 · Focus visible AA | Supports | Visible focus rings on interactive product controls. Buyer themes must not remove them. |
2.5.7 · Dragging movements (WCAG 2.2) AA | Partially supports | Studio and academy practice activities provide tap/select alternatives to drag. Some imported games may still require drag — score those packages separately. |
3.1.1 · Language of page A | Supports | html lang is set to ar or en from the locale. Mixed-language certificates follow the template under UAT. |
3.2.2 · On input A | Supports | Changing a control does not unexpectedly change context on core forms. |
3.3.1 · Error identification A | Partially supports | Form errors are text, not colour alone, on core admin/learner forms. Imported SCORM quizzes depend on the package. |
3.3.2 · Labels or instructions A | Supports | Visible labels on core fields in both locales. |
3.3.8 · Accessible authentication (minimum) — WCAG 2.2 AA | Partially supports | SSO via the buyer IdP is the enterprise path (no cognitive password tests in Evolve when federated). Local-account password rules follow the contracted IdP or platform policy. |
4.1.2 · Name, role, value A | Partially supports | Standard controls expose name/role/value. Custom widgets are inventoried; gaps are treated as defects. |
1.2.2 / 1.2.5 · Captions / audio description (media lots) A | Partially supports | When video is in a Convert or Ready lot, captions/transcripts are scoped as deliverables. Platform chrome does not caption arbitrary buyer uploads unless that lot is bought. |
2.3.1 · Three flashes or below threshold A | Supports | Product UI does not intentionally flash. Buyer-uploaded video remains the buyer’s QC. |
Is this an official ITI VPAT 2.5 file?
It is a VPAT-style Accessibility Conformance Report covering Evolve web surfaces and Arabic RTL. A filled ITI template can be issued as an evaluator file if your tender requires that exact form.
Do English-only VPATs satisfy Gulf LMS tenders?
No. Arabic RTL sequence, truncation, and certificates must be in the remarks. An English-only audit is a partial score.
Educational and evidentiary material for procurement and IT evaluators. Adapt with your legal, privacy, and information-security counsel. Commercial terms, SLAs, and certificate serials are confirmed in the bid — not invented on this page. · Accessibility and inclusion reviewers