Authoring captures intent
The authoring workspace has fields for alt text, captions, transcripts, glossary entries, and item accessibility data.
Assessment accessibility and accommodations
We are committed to making QFlowLearn accessible. We have automated accessibility testing in place, continue to improve the product, and are expanding human testing across authoring and learner delivery.
Our commitment to accessibility
Accessibility is ongoing work. Automated checks help us find problems, and we are working to expand testing with people who use assistive technology. We use findings and feedback to guide improvements.
Conformance report status
The public accessibility conformance report (ACR) is not available. A Voluntary Product Accessibility Template (VPAT) is the format used to prepare that report; support for accessibility metadata does not establish conformance.
Request the current test scope and known limitations for the authoring interface, learner delivery, and the item types you plan to use. Confirm the browser and assistive-technology combinations relevant to your institution.
Request accessibility evidenceReview each part of the experience
- Assessment content
- Authors provide useful alternative text, captions, transcripts, and understandable instructions.
- Learner accommodations
- The delivery setup applies the permitted timing, presentation, and support options.
- Interface access
- Keyboard, screen-reader, contrast, and zoom checks cover the interface itself.
If you encounter an access barrier, describe the page, task, browser, and assistive technology. Do not include learner records.
Report an accessibility barrier →Carry accessibility intent into delivery
PNP travels to delivery
Personal Needs and Preferences (PNP) profiles control extra time, masking, color themes, and read-aloud functions for each learner.
Evidence is exportable
The attempt evidence ledger records accommodation use and access events. Teams can use these records for a review or audit.
Accessibility support
Review the implementation and evidence status for each accessibility function.
| Capability | Notes | Status |
|---|---|---|
| Alt text and captions | QFlowLearn records this data with the item and includes it in delivery and exports. | Supported |
| Glossary / catalog support | Catalog support uses QTI 3 metadata to carry accessibility resources with the assessment content. | Supported |
| Color themes and contrast | The launch accommodation record contains the color theme and includes it in attempt exports. | Supported |
| Extra time | QFlowLearn records the time extension and effective time limit at launch. | Supported |
| Answer masking | The launch record contains the masking state. Instructor views and attempt CSV files show this state. | Supported |
| Screen reader support | We build for screen-reader and keyboard access and are expanding human testing. Ask about current coverage and known limitations for your workflows. | Supported |
| Read-aloud and TTS | Attempt reports and accommodation exports contain the text-to-speech and read-aloud state. | Supported |
| Captions and transcripts | The attempt accommodation summary contains caption and transcript availability. | Supported |
| Calculator and notes | The attempt evidence records the calculator and notes functions that were available to the learner. | Supported |
| Accommodation audit | Launch-time snapshot, source details, instructor timeline, learner reports, and CSV exports create defensible accommodation evidence. | Supported |
Accessibility requirements
The table connects each accommodation requirement to QTI 3, QFlowLearn behavior, and evidence.
| Procurement asks for | QTI 3 / PNP basis | QFlowLearn behavior | Status |
|---|---|---|---|
| Extra time and timing accommodations | PNP profile and delivery policy | Per-learner time extension resolved against attempt authority and receipt trail. | Supported |
| Answer masking or reduced answer set | Accessibility metadata and PNP-driven presentation | The launch accommodation record contains the masking state. Attempt exports include this state. | Supported |
| Text appearance, contrast, and color-safe themes | Access for All and presentation preferences | The learner profile controls presentation and does not change item content. Each attempt export contains the active color theme. | Supported |
| Read-aloud, captions, transcripts, glossary, and catalog resources | QTI accessibility metadata, glossary, catalog, and media alternatives | Authoring records alternate resources, and delivery provides them. The attempt record identifies read-aloud, caption, and transcript support. | Supported |
| Screen reader and keyboard operation | Semantic interaction markup and accessible delivery rendering | Screen-reader and keyboard access are part of our accessibility work. Human testing is expanding; confirm coverage for the browser and assistive technology you use. | Supported |
| Accommodation usage reporting | Attempt evidence tied to learner presentation and delivery policy | Launch-time accommodation snapshots appear in instructor review, learner reports, and attempt CSV exports. | Supported |
| Calculator, notes, and learner support tools | PNP-driven support tools and delivery presentation state | Report summaries identify the shell tools that were available to the learner. | Supported |
How we test and improve
Automated testing
Automated accessibility testing is in place. These checks help us identify issues and catch regressions as the product changes.
Expanding human testing
We are working on more human testing, including keyboard and assistive-technology use. Automated checks cannot establish whether every task works well for every user.
Ongoing improvements
We continue to address accessibility barriers. Tell us where you encounter difficulty so we can investigate the task and the tools you use.
Report an accessibility barrier →Standards and current evidence
WCAG 2.2 Level AA is our accessibility target. We do not claim full conformance based on automated testing alone. A public accessibility conformance report is not yet available.
For an institutional evaluation, ask about current test coverage and known limitations for the workflows, browsers, and assistive technology you intend to use.
Request current accessibility information → Read WCAG 2.2 →Request accessibility evidence
Ask about accessibility support, current testing, and known limitations for your evaluation.