Voluntary Product Accessibility Template (VPAT) — Édition ITI 2.5, limité à Praxity Studio et aux cours exportés
Evaluated against: Standalone HTML and SCORM course output generated by Praxity Studio.
| Critères | Niveau | Conformité | Remarques et explications |
|---|---|---|---|
| 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 | Partially Supports | Exported video embeds preserve accessible titles and can rely on captions provided by the embedded media platform. Praxity Studio does not currently generate captions inside the desktop app; authors are responsible for using captioned source media. |
| 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 | Partially Supports | Exported courses can include author-provided text alternatives or described media, but Praxity Studio does not yet provide a dedicated audio-description authoring workflow. |
| 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 | Not Applicable | Desktop-generated standalone and SCORM courses do not collect personal profile information. Assessment inputs collect learning responses rather than user profile data. |
| 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. |
| Critères | Niveau | Conformité | Remarques et explications |
|---|---|---|---|
| 2.1.1 Keyboard | A | Supports | Exported course pages support keyboard navigation through page controls, links, embedded controls, accordions, tabs, checklist items, and assessment controls. The desktop app was also tested by keyboard across onboarding, editor, panels, preview, export/import, settings, and workspace flows. |
| 2.1.2 No Keyboard Trap | A | Supports | Keyboard focus can move into and out of desktop panels, dialogs, preview controls, exported navigation, tabs, accordions, and assessment controls. Dialogs and transient panels provide normal close or Escape paths. |
| 2.1.4 Character Key Shortcuts | A | Supports | No single printable character key shortcuts are required. Desktop shortcuts use modifier keys, and exported course navigation uses standard Tab, Enter, Space, and arrow-key behavior. |
| 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 | Exported course pages include a skip-to-content link and main/navigation landmarks. The desktop authoring interface also includes a skip link that moves focus past application chrome into the editor area. |
| 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 | Multi-page exported courses provide more than one navigation path, including the course navigation menu and sequential Previous/Next controls. Navigation variants were tested across sidebar, bottom bar, slides, scroll, minimal, embedded, and no-navigation configurations. |
| 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. |
| Critères | Niveau | Conformité | Remarques et explications |
|---|---|---|---|
| 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 | Not Applicable | Desktop-generated standalone and SCORM courses do not perform legal, financial, or user-data deletion transactions. Assessment responses can be changed or retried according to the author's course settings. |
| 3.3.7 Redundant Entry | A | Not Applicable | Each page's assessments are independent. No cross-page data re-entry is required. |
| Critères | Niveau | Conformité | Remarques et explications |
|---|---|---|---|
| 4.1.2 Name, Role, Value | A | Supports | Interactive controls in generated output expose clear names, roles, and values. Assessment feedback is programmatically linked to questions, and desktop authoring controls use labels, states, and focus handling that can be exposed to assistive technologies. |
| 4.1.3 Status Messages | AA | Supports | Screen reader users are notified of page changes, assessment feedback, validation errors, and important desktop authoring status changes through live region announcements. |
| Critères | Conformité | Remarques et explications |
|---|---|---|
| 302.1 Without Vision | Supports | Generated output uses semantic HTML, landmarks, headings, labels, and ARIA where needed. Desktop authoring controls expose visible labels and keyboard focus states. |
| 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 | Desktop authoring and generated output support keyboard operation for core workflows and interactive controls. Pointer-only gestures are not required for tested workflows. |
| 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. |
| Critères | Conformité | Remarques et explications |
|---|---|---|
| 501.1 Scope | Supports | Desktop authoring application for macOS, with standalone HTML and SCORM output generated for browser-based learner delivery. |
| 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 desktop accessibility review helps authors find issues before export, including missing image alternatives, heading structure, link quality, table structure, assessment labels, media alternatives, and color contrast. The checker is advisory rather than a hard publishing blocker. |
| 504.2.1 Preservation of Information Provided for Accessibility | Supports | Author-provided accessibility information such as image alternatives, headings, captions, labels, landmarks, and language settings is preserved in generated HTML and SCORM output. |
| 504.2.2 PDF Export | Not Applicable | Praxity Studio exports courses as HTML and SCORM packages. Course PDF export is not included in the current desktop product scope. |
| Critères | Conformité | Remarques et explications |
|---|---|---|
| 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. |
| Critères | Conformité | Remarques et explications |
|---|---|---|
| 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. |
| Critères | Conformité | Remarques et explications |
|---|---|---|
| 6.1 Audio bandwidth for speech | Not Applicable | Praxity Studio does not include voice communication. |
| 6.2 Real-time text (RTT) | Not Applicable | Praxity Studio does not include real-time text communication. |
| Critères | Conformité | Remarques et explications |
|---|---|---|
| 7.1.1 Captioning playback | Partially Supports | Embedded videos can expose captions when the source media platform provides them. Praxity Studio does not currently include a dedicated caption-track authoring or validation workflow. |
| 7.1.2 Captioning synchronization | Partially Supports | Caption synchronization depends on the captioned source media used by the author. |
| 7.2.1 Audio description playback | Partially Supports | Authors can provide described media or text alternatives, but the desktop app does not currently provide a dedicated audio-description track workflow. |
| 7.3 User controls for captions and audio description | Partially Supports | Caption controls may be available through embedded media players when captions are provided by the source. Dedicated in-app controls for authoring caption and audio-description tracks are not yet included in the desktop product. |
| Critères | Conformité | Remarques et explications |
|---|---|---|
| 9.1–9.4 WCAG 2.2 Level AA | Supports | See WCAG 2.2 AA table above for per-criterion detail. |
| Critères | Conformité | Remarques et explications |
|---|---|---|
| 11.8.1 Content technology | Supports | Exports standard HTML, CSS, and JavaScript in standalone HTML and SCORM packages. |
| 11.8.2 Accessible content creation | Partially Supports | The desktop accessibility review provides issue counts, severity, and repair guidance for common course accessibility problems. It is advisory rather than blocking, so authors remain responsible for resolving issues before distribution. |
| 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 accessibility review gives specific guidance for common issues such as missing image alternatives, heading structure problems, poor link text, table headers, missing media alternatives, and contrast problems. |
| 11.8.5 Templates | Partially Supports | Praxity Studio provides accessible starting points through reusable compositions and design-tab theme presets with contrast-tested colors. Full course templates with accessibility-specific instructional guidance are still on the roadmap. |
| Critères | Conformité | Remarques et explications |
|---|---|---|
| 12.1.1 Accessibility and compatibility features | Supports | Accessibility features are documented in the help center, including the desktop accessibility review, keyboard navigation, image alternatives, media alternatives, and color 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. |
| Critères | Conformité | Remarques et explications |
|---|---|---|
| A.1.1 Web-Based Functionality | Supports | Praxity Studio uses standard accessible interface patterns within the desktop application shell. Core editing workflows were tested by keyboard, including project creation, editor navigation, slash commands, preview, settings, export/import, workspace navigation, and panel controls. |
| A.1.2 Platform Accessibility Services | Supports | Uses standard controls, labels, focus management, live regions, and ARIA attributes where needed so the desktop interface can be exposed through platform accessibility services. |
| A.2.1 Accessible Editing Views | Supports | The desktop editor provides a keyboard-reachable editing view with skip link support, visible focus states, labeled panels, resizable regions, page navigation, file tree navigation, and live status messages for important changes. |
| 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 | Desktop QA covers keyboard access through onboarding, project lifecycle, editor typing, slash commands, panel toggles, focus cycling, preview modes, settings, workspace flows, import/export, shortcuts panel, and security dialogs. Shortcuts are documented in the keyboard shortcuts panel. |
| A.3.2 Content Structure Access | Supports | The page navigator and project file tree expose course structure through keyboard-reachable controls with visible labels and focus states. |
| A.3.3 Text Search | Supports | Desktop search controls are keyboard reachable and labeled. Search focus and panel behavior are included in the desktop accessibility review. |
| A.3.4 Navigate by Structure | Supports | The page navigator, project file tree, editor, preview, and panel ribbons provide keyboard-reachable structure for moving through a project and its content. |
| A.3.5 Content Searchability | Supports | Desktop search and project file navigation help authors locate files and content without relying on pointer-only interaction. |
| A.3.6 Preferences | Supports | Authors can customize course themes and preview display preferences. Desktop themes and exported output are tested for contrast in representative light, dark, and custom configurations. |
| 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 desktop keyboard shortcuts panel is available in the app, and the accessibility review provides in-context guidance for course issues. |
| A.4.2 Document Accessibility Features | Supports | This VPAT documents all accessibility features and their status. |
| Critères | Conformité | Remarques et explications |
|---|---|---|
| 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 | The desktop accessibility review checks common course issues across images, headings, links, tables, media, assessments, and design choices, with severity and repair guidance. |
| B.2.4 Repair Assistance | Supports | The accessibility review provides direct repair guidance for common issues such as marking decorative images, adding alternatives, improving headings, labeling assessments, and fixing low contrast. |
| B.2.5 Accessibility Checking Prominence | Supports | The desktop interface exposes accessibility review from the authoring workflow so authors can check issues before distributing HTML or SCORM output. |
| B.3.1 Accessible Templates | Partially Supports | Reusable compositions and design-tab theme presets give authors accessible, template-like starting points for common content patterns and visual design. Complete course templates with accessibility-specific instructional guidance are still planned. |
| B.3.2 Accessible Template Options | Partially Supports | Authors can choose from accessible compositions and contrast-tested theme presets. Praxity Studio does not yet provide a full catalogue of course-level templates with accessibility notes for each option. |
| 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. |
Lacunes connues avec corrections planifiées, classées par priorité. Cette liste est notre engagement envers l’amélioration continue.
Add desktop authoring controls for caption tracks, transcript review, and audio-description metadata so media alternatives are easier to verify before export.
Améliore: 1.2.2 Captions, 1.2.5 Audio Description, EN 301 549 Clause 7