Accessibility
Our conformance status, known issues and how we are fixing them
Our commitment
Tanitapps is committed to making Form Workflow Plus usable by everyone, including people who rely on assistive technology. We measure ourselves against WCAG 2.1 Level AA. This page states plainly where we conform today, where we do not, and what we are doing about it. If an accessibility barrier stops you using the product, contact us at contact@formworkflowplus.com and we will help you directly.
Conformance status
Form Workflow Plus is partially conformant with WCAG 2.1 Level AA: parts of the product do not yet fully conform. We publish this roadmap rather than claim a conformance we have not yet earned. This statement serves as our accessibility documentation and good-faith remediation plan, and is updated at least annually.
How we assessed it
- Automated: axe-core (WCAG 2.0/2.1 A and AA rulesets) run against the marketing site and the application sign-in page.
- Static analysis of the application templates and the Google Workspace add-on markup.
- Not yet performed: manual keyboard-only traversal of every workflow, screen-reader passes (NVDA, JAWS, VoiceOver), and zoom/reflow testing at 200–400%. Automated testing detects only a portion of accessibility issues, so the findings below are a floor rather than a complete list.
- Last assessed: 16 July 2026.
Known issues
Application:
| Issue | WCAG criterion | Level |
|---|---|---|
| Some controls are bound to non-interactive elements and cannot be operated with a keyboard | 2.1.1 Keyboard, 4.1.2 Name, Role, Value | A |
| Some icon-only buttons have no accessible name | 4.1.2 Name, Role, Value | A |
| Some images have no text alternative | 1.1.1 Non-text Content | A |
| Some form inputs are not programmatically labelled | 3.3.2 Labels or Instructions | A |
Google Workspace add-on:
| Issue | WCAG criterion | Level |
|---|---|---|
| Some images have no text alternative | 1.1.1 Non-text Content | A |
Marketing website:
| Issue | WCAG criterion | Level |
|---|---|---|
| Some text does not meet the minimum contrast ratio | 1.4.3 Contrast (Minimum) | AA |
| Some links are distinguished from surrounding text by colour alone | 1.4.1 Use of Colour | A |
What already works
- The application sign-in page returns no automated accessibility violations, and you sign in with your own Google account — so your existing assistive-technology setup carries over.
- Your workflow data lives in Google Forms and Google Sheets, which are themselves accessible Google products.
Interim workarounds
Until the items below are remediated, these paths are available today:
- Approvals can be completed entirely by email. Reviewers receive the approval request by email and can Approve or Decline directly from that email, without entering the web application at all. This is the recommended path for keyboard-only and screen-reader users.
- Data entry and review can happen in Google Sheets and Google Forms rather than in our interface.
- Assisted service: if an accessibility barrier blocks you, contact us and we will carry out the action on your behalf.
Remediation roadmap
| Item | WCAG | Target |
|---|---|---|
| Page language attribute and valid list markup on the website | 3.1.1, 1.3.1 | Completed 16 July 2026 |
| Accessible names for all icon-only buttons and links | 2.4.4, 4.1.2 | Within 30 days |
| Text alternatives for all images (application and add-on) | 1.1.1 | Within 30 days |
| Programmatic labels for all form inputs | 3.3.2, 4.1.2 | Within 45 days |
| Convert non-interactive click targets into real, keyboard-operable controls | 2.1.1, 4.1.2 | Within 90 days |
| Colour-contrast remediation on the marketing site | 1.4.3 | Within 60 days |
| Make links distinguishable without relying on colour | 1.4.1 | Within 60 days |
| Manual keyboard-only traversal of every application workflow | 2.1.1, 2.4.3, 2.4.7 | Within 90 days |
| Screen-reader passes (NVDA and VoiceOver) on core flows | 1.3.1, 4.1.2 | Within 120 days |
| Zoom and reflow testing at 200–400% | 1.4.4, 1.4.10 | Within 120 days |
| Automated accessibility testing in our CI pipeline to prevent regressions | — | Within 60 days |
| Publish a VPAT 2.5 / Accessibility Conformance Report | — | Within 150 days |
| Annual update of this statement | — | Annually |
Feedback, reports and documentation requests
We welcome feedback on the accessibility of Form Workflow Plus. To report a barrier, request this roadmap or a VPAT/ACR, or request a test account or live demonstration for verification, contact contact@formworkflowplus.com. Accessibility owner: Mohamed Bahri. We aim to respond promptly and will agree a resolution path with you.
Formal approvals
This statement is prepared as the accessibility documentation and good-faith remediation plan referred to in the Student Data Privacy Agreement, and is updated at least annually.