Status and scope
Morrow publishes this page as current, procurement-readable accessibility conformance evidence. It is intentionally not described as a certification. ITI treats the VPAT as a reporting template.
Once a product owner completes it with testing results, the completed document is an Accessibility Conformance Report, or ACR.
Plain status: Morrow maintains ACR evidence using the ITI VPAT 2.5 WCAG edition. The current public packet is suitable for an initial accessibility or procurement screen.
Contract review packets can include the Word-form response your institution requires.
Evaluation method
The evaluation method combines product inspection, keyboard walkthroughs, screen-reader-oriented markup checks, color contrast review, responsive viewport checks, and regression review of generated document surfaces.
Morrow uses the same practical bar institutions apply during procurement: can an instructor or reviewer operate the feature, understand the state, recover from errors, and export evidence?
The answer should not rely on sight, pointer precision, color alone, or hidden instructions.
| Method | Coverage | Current evidence |
|---|---|---|
| Keyboard navigation | Header navigation, side-panel controls, dialogs, overlays, tables, report actions, and footer links. | Interactive controls are built from buttons/links with visible focus states and non-color-only labels. |
| Semantic structure | Landmarks, headings, tables, form labels, status tags, and generated report sections. | Marketing pages and trust docs use one h1, structured sections, worded status tags, and table headers. |
| Visual contrast | Primary text, secondary text, status tags, buttons, borders, table rows, and focus rings. | Current site tokens are tuned for restrained contrast without relying on pale decorative text for meaning. |
| Responsive layout | 390px mobile through desktop site widths and extension side-panel constraints. | Layouts avoid horizontal page overflow and keep document tables scrollable when needed. |
WCAG conformance summary
The table below is a procurement summary, not the full VPAT matrix. It states how the current product is designed against the WCAG principles and where final per-criterion evidence belongs in the formal ACR.
| Principle | Current support | ACR evidence detail |
|---|---|---|
| Perceivable | Text content is rendered as text, status meaning is worded, decorative icons are hidden from assistive tech, and generated reports keep readable headings. | The ACR packet tracks contrast evidence for the extension panel, report previews, exported PDFs, and the public trust pages. |
| Operable | Core controls use native interactive elements, visible focus treatment, predictable navigation order, and reduced-motion fallbacks. | The ACR packet tracks keyboard walkthroughs for audit, plan edit, evidence export, settings, and modal workflows. |
| Understandable | Actions are labeled in plain language, destructive or course-changing operations require user approval, and status language avoids color-only meaning. | The ACR packet documents error-state handling, form help text, and validation copy across onboarding and report generation. |
| Robust | Markup is componentized around headings, lists, tables, links, buttons, and ARIA only where needed. | The ACR packet tracks screen-reader spot checks in Chrome with current assistive technology combinations. |
Keyboard and focus behavior
Morrow treats keyboard access as a product requirement, not an afterthought. The side panel is designed around repeated operational use: open a course, ask for an audit, inspect changes, and approve what should happen.
Evidence export remains part of that same keyboard path, without pointer-only controls.
- Primary commands are rendered as buttons or links, not inert divs.
- Tables expose row and column relationships with table headers.
- Focus states are visible and paired with hover treatment where a row or link has an affordance.
- Motion is optional; reduced-motion users keep static content and no transform-dependent state.
- Icons are decorative unless they carry a named control, and named controls receive accessible labels.
ACR evidence status
The current ACR packet separates product support from formal evidence detail. The per-criterion matrix is organized around the evidence below:
- Per-criterion VPAT 2.5 WCAG support levels and remarks.
- Contrast evidence across the extension side panel, generated reports, and the public site.
- Keyboard walkthrough evidence for course-changing workflows.
- Assistive technology spot checks on the most important reading and approval flows.
- Generated PDF/Word export review for heading structure, reading order, and table labeling.
| Criterion | Current assessment | Evidence summary | ACR evidence detail |
|---|---|---|---|
| 1.3.1 Info and Relationships Semantic structure | Documented in current ACR evidence | Pages use landmarks, headings, table headers, labelled form fields, and worded status tags. | Per-surface screen-reader spot checks and formal remarks. |
| 1.4.3 Contrast Text and component contrast | Covered in current ACR evidence | Site tokens are designed for AA-oriented contrast and the email system has contrast gates. | Contrast evidence for the extension panel, public trust pages, and exports. |
| 2.1.1 Keyboard Keyboard operation | Documented in current ACR evidence | Controls use native buttons and links with visible focus states; document tables remain keyboard reachable. | Full keyboard walkthroughs for audit, approval, settings, and export workflows. |
| 2.4.7 Focus Visible Focus indication | Documented in current ACR evidence | Navigation, artifact links, form controls, and table interactions keep visible focus treatment. | Focus order and focus visibility review in extension and report preview surfaces. |
| 3.3.1 Error Identification Forms and recovery | Covered in current ACR evidence | Public forms and status surfaces use explicit labels and plain-language feedback patterns. | Validation behavior and error messaging for onboarding and report generation. |
| 4.1.2 Name, Role, Value Interactive control semantics | Documented in current ACR evidence | Generated accessibility gates check interactive names, form labels, and ARIA references across built pages. | Assistive-technology spot checks for the most important extension workflows. |
Procurement request
If your review requires a specific VPAT edition, a Word attachment, a signed accessibility statement, or third-party review language, request the packet through the trust center.
Morrow will identify the exact artifact status rather than presenting a draft as a completed certification.