Skip to content

Accessibility Conformance Report

Voluntary Product Accessibility Template (VPAT) — ITI Edition 2.5

Product
Praxity
Version
Alpha
Last Evaluated
March 2026
Contact
hello@praxity.io
Last reviewed
Review frequency
With each major release, no less than quarterly

WCAG 2.2 Level AA

Evaluated against: Published course output (learner experience)

Principle 1: Perceivable
Criteria Level Conformance Remarks and Explanations
1.1.1 Non-text Content A Supports Images render with author-provided alt text or role="presentation" for decorative images. Charts provide role="img" with aria-label descriptions. Diagram blocks render as static SVG with role="img" and structured alt text auto-generated from node/edge data. Figures use figcaption when captions are provided. Math equations render with MathML and an aria-label speech string (e.g. "start fraction, 1, divided by, 2, end fraction") so screen readers can announce equations even without native MathML support.
1.2.1 Audio-only and Video-only (Prerecorded) A Supports Audio and video blocks render an expandable transcript section below the media when the author provides transcript content.
1.2.2 Captions (Prerecorded) A Supports Uploaded videos auto-generate captions in the author's chosen language. All video and audio sources support manually uploaded caption tracks. YouTube and Vimeo embeds support platform-provided captions.
1.2.3 Audio Description or Media Alternative (Prerecorded) A Supports Transcripts serve as text-based media alternative. Audio description tracks are supported.
1.2.4 Captions (Live) AA Not Applicable Published courses contain prerecorded media only.
1.2.5 Audio Description (Prerecorded) AA Supports Authors can add audio description tracks to video blocks. Tracks are rendered in published output.
1.3.1 Info and Relationships A Supports Published courses use semantic HTML with proper headings, table headers, figure captions, form labels, and landmark regions.
1.3.2 Meaningful Sequence A Supports Blocks render in document order matching the visual presentation. DOM reading order preserves the author's intended sequence.
1.3.3 Sensory Characteristics A Supports Assessment feedback uses both color and text labels (Correct/Incorrect). Required indicators use an icon plus screen-reader text, not color alone.
1.3.4 Orientation AA Supports No CSS orientation locks. Published content renders in both portrait and landscape orientations.
1.3.5 Identify Input Purpose AA Supports Course access gates identify input purpose for email, name, and password fields. Assessment inputs collect quiz responses, not personal data, so they are not in scope.
1.4.1 Use of Color A Supports Assessment feedback conveys correctness via text labels alongside color. Required indicators use icons and screen-reader text, not color alone.
1.4.2 Audio Control A Supports Audio and video elements use native controls and do not autoplay. Learners must manually start playback.
1.4.3 Contrast (Minimum) AA Supports Default theme text exceeds 4.5:1 contrast ratio. Link colors are derived from the theme accent and validated to meet 4.5:1 against the background.
1.4.4 Resize Text AA Supports Layout uses max-width with relative units. Text resizes up to 200% via browser zoom without loss of content. Columns stack on narrow viewports.
1.4.5 Images of Text AA Supports Published content uses real text for headings, body copy, labels, and assessments. No images of text are generated by the platform.
1.4.10 Reflow AA Supports Content reflows at 320px CSS width. Columns stack below 576px, tabs become horizontally scrollable, and the sidebar switches to a mobile drawer below 768px.
1.4.11 Non-text Contrast AA Supports Focus indicators use a dual-contrast ring visible against both light and dark backgrounds. Buttons and form controls have visible borders. Progress bars include a visible track border.
1.4.12 Text Spacing AA Supports No fixed heights on text containers. Text blocks use margin and padding only, allowing increased line height, letter spacing, and word spacing without clipping.
1.4.13 Content on Hover or Focus AA Supports Tooltips and hover content are dismissible via Escape, hoverable, and persistent until dismissed.
Principle 2: Operable
Criteria Level Conformance Remarks and Explanations
2.1.1 Keyboard A Supports Page navigation uses ArrowLeft/ArrowRight keys with RTL support. All interactive blocks (tabs, accordion, flashcards, slides, assessments, interactive video, rating, image comparison) have keyboard handlers for arrow keys, Enter, Space, and Tab.
2.1.2 No Keyboard Trap A Supports Interactive video panels use focus traps with explicit exit paths (Continue button after completing required interactions, Escape for non-required panels). Accordion and tabs use standard disclosure patterns. Mobile menu closes on Escape.
2.1.4 Character Key Shortcuts A Supports No single printable character key shortcuts. Page navigation uses non-printable arrow keys only.
2.2.1 Timing Adjustable A Supports No timed interactions. Interactive video cue points pause the video and wait for user action. Assessment attempts are count-limited, not time-limited.
2.2.2 Pause, Stop, Hide A Supports Audio and video use native controls with no autoplay. Slides do not auto-advance. No auto-scrolling or blinking content.
2.3.1 Three Flashes or Below Threshold A Supports No flashing content. CSS transitions use gentle timing (opacity, transform).
2.4.1 Bypass Blocks A Supports A skip-to-content link targets the main content landmark. The page uses main, nav, and footer landmark regions.
2.4.2 Page Titled A Supports Every page has a descriptive title element derived from the page name.
2.4.3 Focus Order A Supports DOM order matches visual order. The main content area receives programmatic focus on page load. Interactive elements follow a logical tab sequence.
2.4.4 Link Purpose (In Context) A Supports Navigation buttons include aria-labels with target page names. Document download links include the file title. Buttons display visible descriptive text. The checker flags generic link text, empty links, and duplicate URLs pointing to the same destination on a page.
2.4.5 Multiple Ways AA Supports Courses provide sidebar navigation, sequential Previous/Next buttons, keyboard arrow shortcuts, and direct page deep-links.
2.4.6 Headings and Labels AA Supports Pages render an h1 page title. Heading blocks use semantic h1–h3 elements. The checker flags skipped heading levels, H1 used inside page content (since the page title already serves as H1), and headings longer than 120 characters. Assessment fieldsets have aria-labels derived from question text.
2.4.7 Focus Visible AA Supports All interactive elements show a dual-contrast focus ring via :focus-visible. Mouse-click focus outlines are suppressed to show focus only for keyboard navigation.
2.4.11 Focus Not Obscured (Minimum) AA Supports Blocks have scroll-margin-top to clear the sticky course menu. The fixed badge is positioned to avoid obscuring content areas.
2.5.1 Pointer Gestures A Supports No multipoint or path-based gestures required. The image comparison slider uses single-pointer drag with keyboard alternatives.
2.5.2 Pointer Cancellation A Supports Interactive actions use standard click handlers that fire on pointer release.
2.5.3 Label in Name A Supports Visible button text matches accessible names. Icon-only buttons have descriptive aria-labels.
2.5.4 Motion Actuation A Not Applicable No device motion triggers any functionality.
2.5.7 Dragging Movements AA Supports Sequence assessments provide up/down button alternatives. The image comparison slider supports ArrowLeft/ArrowRight keyboard control.
2.5.8 Target Size (Minimum) AA Supports All interactive targets meet the 24x24 CSS pixel minimum. Slide progress dots use transparent padding to reach the minimum while maintaining compact visual size.
Principle 3: Understandable
Criteria Level Conformance Remarks and Explanations
3.1.1 Language of Page A Supports Pages declare their language. Right-to-left languages are supported.
3.1.2 Language of Parts AA Supports Per-block language selector available in the block context menu. Published output emits lang and dir attributes when block locale differs from course locale.
3.2.1 On Focus A Supports Focusing an element does not trigger navigation, submission, or other context changes.
3.2.2 On Input A Supports Assessment selections do not trigger submission. A separate Check/Submit button is required. Select dropdowns update state without navigating.
3.2.3 Consistent Navigation AA Supports The course menu and page navigation render from the same components on every page, maintaining consistent structure and position.
3.2.4 Consistent Identification AA Supports Navigation buttons, menu controls, and slide indicators use consistent labels and icons throughout.
3.2.6 Consistent Help A Not Applicable Published courses do not include a help mechanism. This criterion would apply if help were added.
3.3.1 Error Identification A Supports Assessment feedback displays Correct/Incorrect text labels alongside color indicators. Required field validation shows error messages linked to the relevant input.
3.3.2 Labels or Instructions A Supports Assessment inputs use fieldset with aria-label containing the question stem. Text inputs and textareas have descriptive aria-labels. Matching selects are labeled per prompt.
3.3.3 Error Suggestion AA Supports Auto-scored assessments (choice, hotspot, matching, sequence) show correctness feedback with author-provided explanations. Text response assessments display author feedback when configured.
3.3.4 Error Prevention (Legal, Financial, Data) AA Supports Payment processing redirects to Stripe's hosted checkout, which provides its own review and confirmation steps. Assessment submissions allow retakes by default. Courses do not collect legal agreements or user-deletable data during the learning experience.
3.3.7 Redundant Entry A Not Applicable Each page's assessments are independent. No cross-page data re-entry is required.
Principle 4: Robust
Criteria Level Conformance Remarks and Explanations
4.1.2 Name, Role, Value A Supports Interactive controls use semantic HTML and ARIA. Assessment feedback is programmatically linked to questions via aria-describedby. Signature block provides equivalent draw and type modes for all learners. Math equations use role="math" with aria-label speech strings and MathML markup.
4.1.3 Status Messages AA Supports Screen reader users are notified of page changes, assessment feedback, validation errors, and interactive video events through live region announcements.

Revised Section 508

Chapter 3: Functional Performance Criteria
Criteria Conformance Remarks and Explanations
302.1 Without Vision Supports Published output uses semantic HTML, landmarks, and ARIA. Signature block type mode provides keyboard/screen-reader accessible signing.
302.2 With Limited Vision Supports Browser zoom supported. Contrast checker enforces WCAG AA ratios.
302.3 Without Perception of Color Supports Color is never the only way to convey information. Checker results use icons and text alongside color.
302.4 Without Hearing Supports Transcripts provided for audio/video. Caption and audio description tracks supported.
302.5 With Limited Hearing Supports Caption tracks with language labels. Transcript text expandable below media.
302.6 Without Speech Supports No speech input is required.
302.7 With Limited Manipulation Supports Full keyboard access. Signature block type mode available alongside draw mode. Arrow key tab navigation between signature methods.
302.8 With Limited Reach and Strength Supports Standard input devices supported. No special hardware or sustained physical effort required.
302.9 With Limited Language, Cognitive, and Learning Abilities Supports Clear labels, simple navigation, consistent layout. The editor follows familiar document-editing patterns.
Chapter 5: Software
Criteria Conformance Remarks and Explanations
501.1 Scope Supports Web application using standard browser technologies. No platform-specific software required.
502.3.1 Object Information Supports Standard HTML and ARIA attributes expose information to assistive technologies.
502.3.2 Modification of Object Information Supports Standard form controls allow assistive technologies to interact with all editable fields.
504.2 Content Creation or Editing Partially Supports The accessibility checker validates 45 rules covering images, links, tables, headings, media, assessments, diagrams, social blocks, and layout. It offers smart suggestions and one-click fixes. Enforcement is advisory, not blocking.
504.2.1 Preservation of Information Provided for Accessibility Supports Alt text, headings, landmarks, and language attributes are preserved through the export pipeline.
504.2.2 PDF Export Supports Certificate PDFs are generated as tagged PDF/UA-1 documents with logical structure (headings, paragraphs, figures with alt text), embedded fonts matching the course theme, document language, and title. Decorative elements are marked as artifacts. An accessible HTML verification page is also available at each certificate's unique URL. Course content is exported as HTML, not PDF.
Chapter 6: Support Documentation and Services
Criteria Conformance Remarks and Explanations
602.2 Accessibility and Compatibility Features Supports Accessibility features are documented in the help center, including the built-in checker, keyboard navigation, alt text requirements, caption support, and colour contrast validation. A keyboard shortcuts modal is available in the editor.
602.3 Electronic Support Documentation Supports Support documentation follows WCAG 2.2 AA guidelines.
602.4 Functional Performance Statements Supports This VPAT documents functional performance criteria and conformance levels.

EN 301 549

Clause 5: Generic Requirements
Criteria Conformance Remarks and Explanations
5.2 Activation of accessibility features Supports Accessibility features are always on. No special activation needed.
5.3 Biometrics Not Applicable No biometric input is used.
5.4 Preservation of accessibility information during conversion Supports The export pipeline preserves alt text, headings, landmarks, and language attributes.
Clause 6: ICT with Two-Way Voice Communication
Criteria Conformance Remarks and Explanations
6.1 Audio bandwidth for speech Not Applicable Praxity does not include voice communication.
6.2 Real-time text (RTT) Not Applicable Praxity does not include real-time text communication.
Clause 7: ICT with Video Capabilities
Criteria Conformance Remarks and Explanations
7.1.1 Captioning playback Supports Video and audio elements render caption tracks via native controls. The video player provides built-in caption display and toggle.
7.1.2 Captioning synchronization Supports Caption tracks use WebVTT format with time-synchronized cues. Auto-generated captions are synchronized during upload.
7.2.1 Audio description playback Supports Audio description tracks are rendered and playable in the published output video player.
7.3 User controls for captions and audio description Supports Caption and audio description track controls available via native video player controls. Authors manage tracks in the editor.
Clause 9: Web (WCAG 2.2 AA)
Criteria Conformance Remarks and Explanations
9.1–9.4 WCAG 2.2 Level AA Supports See WCAG 2.2 AA table above for per-criterion detail.
Clause 11: Software — Authoring Tool
Criteria Conformance Remarks and Explanations
11.8.1 Content technology Supports Exports standard HTML, CSS, and JavaScript in SCORM packages.
11.8.2 Accessible content creation Supports The accessibility checker validates 45 rules with severity levels and actionable suggestions. Enforcement is advisory, not blocking.
11.8.3 Preservation of accessibility information Supports Alt text, headings, landmarks, and language attributes are preserved through the export pipeline.
11.8.4 Repair assistance Supports The checker provides inline annotations with specific suggestions and one-click fixes for common issues.
11.8.5 Templates Does Not Support Templates are not yet designed with accessibility-optimized content.
Clause 12: Documentation and Support Services
Criteria Conformance Remarks and Explanations
12.1.1 Accessibility and compatibility features Supports Accessibility features are documented in the help center, including the built-in checker, keyboard navigation, alt text requirements, caption support, and colour contrast validation.
12.1.2 Accessible documentation Supports Documentation follows WCAG 2.2 AA guidelines.
12.2.2 Information on accessibility features Supports This VPAT documents all accessibility features and their conformance status.
12.2.3 Effective communication Supports Email support is available for accessibility inquiries.
12.2.4 Accessible documentation Supports The marketing site and documentation follow WCAG guidelines.

ATAG 2.0

Part A: Make the authoring tool user interface accessible
Criteria Conformance Remarks and Explanations
A.1.1 Web-Based Functionality Supports Built with standard web technologies. All editing workflows are keyboard accessible, including block reordering via keyboard shortcuts and a Move To dialog.
A.1.2 Platform Accessibility Services Supports Uses standard browser APIs and ARIA attributes. Compatible with platform accessibility services.
A.2.1 Accessible Editing Views Partially Supports The editor uses semantic HTML and landmark regions. Some form fields in block editors do not yet programmatically associate with their error messages via aria-describedby.
A.2.2 Editing View Presentation Supports Browser zoom and text resize work correctly. No content loss at 200% zoom.
A.3.1 Keyboard Access Supports All editor workflows are keyboard accessible. Shortcuts are documented in the help modal. Tab order follows a logical flow. Block reordering, move-to-lesson, and all container editing support keyboard shortcuts.
A.3.2 Content Structure Access Supports The lesson panel provides tree-structured navigation of course content for screen readers.
A.3.3 Text Search Supports Course search is available in the dashboard.
A.3.4 Navigate by Structure Supports The lesson panel and heading navigation allow structural navigation within the editor.
A.3.5 Content Searchability Supports Dashboard search and block-level content discovery are available.
A.3.6 Preferences Supports Authors can customize course colors. The contrast checker validates their choices against WCAG ratios.
A.3.7 Previews Supports Preview mode renders accessible output matching the final export.
A.4.1 Help with Accessibility Features Supports Accessibility features are documented in the help center. The keyboard shortcuts modal is available in the editor. The accessibility checker provides in-context guidance with links to WCAG criteria.
A.4.2 Document Accessibility Features Supports This VPAT documents all accessibility features and their status.
Part B: Support the production of accessible content
Criteria Conformance Remarks and Explanations
B.1.1 Accessible Content Possible Supports All content types support accessibility attributes: alt text, headings, transcripts, and language settings.
B.1.2 Accessibility Info Preserved Supports Alt text, headings, landmarks, and language attributes are preserved through the export pipeline.
B.2.1 Accessible Content Auto-Generated Supports The export pipeline produces semantic HTML with skip links, landmarks, heading hierarchy, and proper document structure.
B.2.2 Accessibility Guidance Provided Supports The checker provides inline guidance with descriptive messages and actionable suggestions.
B.2.3 Accessibility Checking Supports 45 rules across 24 content types, categorized by severity, with actionable suggestions.
B.2.4 Repair Assistance Supports One-click fixes for common issues: mark an image as decorative, enable table headers, add a missing transcript. AI-assisted alt text generation is available.
B.2.5 Accessibility Checking Prominence Supports The toolbar shows an accessibility button with an issue count badge. The export dialog warns of unresolved issues.
B.3.1 Accessible Templates Does Not Support Course templates are on the product roadmap. When available, they will be built with the same accessibility checker and semantic output that all Praxity content uses.
B.3.2 Accessible Template Options Does Not Support Course templates are on the product roadmap. Accessibility compliance will be a baseline requirement for all templates.
B.4.1 Accessible Documentation Supports Product documentation is published in an accessible help center with semantic HTML, keyboard navigation, and proper heading structure.
B.4.2 Accessible Feature Descriptions Supports Accessibility features are described in the help center, including the checker, keyboard shortcuts, alt text, captions, and contrast validation. The help content itself is accessible.

Accessibility Roadmap

Known gaps with planned fixes, organized by priority. This list is our commitment to continuous improvement.

Programmatic error association on form fields

High

Link error messages to published output assessment form fields so screen readers announce errors in context.

Improves: 3.3.1 Error Identification

Evaluation Methods