|
| 1 | +# Accessibility Conformance Report |
| 2 | +## WCAG 2.1 Level AA |
| 3 | +(Based on VPAT® Version 2.5 Rev) |
| 4 | + |
| 5 | +--- |
| 6 | + |
| 7 | +## Product Information |
| 8 | + |
| 9 | +- **Name of Product:** Ximera |
| 10 | +- **Product Type:** Web-based interactive educational content platform |
| 11 | +- **Product Description:** |
| 12 | + Ximera is an open-source platform for creating and delivering interactive STEM educational content using LaTeX-authored source files rendered as web pages with embedded interactivity. |
| 13 | +- **Primary Use Case:** Postsecondary and secondary education |
| 14 | +- **Hosting Model:** Self-hosted or institutionally hosted web application |
| 15 | +- **Contact Information:** https://ximera.org |
| 16 | +- **Report Date:** _(Insert date)_ |
| 17 | + |
| 18 | +--- |
| 19 | + |
| 20 | +## Evaluation Methods Used |
| 21 | + |
| 22 | +This report is based on: |
| 23 | + |
| 24 | +- Manual expert review by developers and educators familiar with Ximera’s internal architecture and content pipeline. |
| 25 | +- Review of rendered HTML output produced by Ximera’s LaTeX-to-HTML toolchain. |
| 26 | +- Targeted testing with screen readers (NVDA, VoiceOver) and keyboard-only navigation. |
| 27 | +- Reference to known accessibility constraints inherent to mathematical notation, interactive problem widgets, and third-party embedded tools. |
| 28 | + |
| 29 | +This report reflects the **current state of the platform** and acknowledges ongoing accessibility improvements. |
| 30 | + |
| 31 | +--- |
| 32 | + |
| 33 | +## Applicable Standards / Guidelines |
| 34 | + |
| 35 | +This report covers the degree of conformance with: |
| 36 | + |
| 37 | +| Standard | Included | |
| 38 | +|--------|----------| |
| 39 | +| WCAG 2.1 Level A | Yes | |
| 40 | +| WCAG 2.1 Level AA | Yes | |
| 41 | +| WCAG 2.1 Level AAA | Not Evaluated | |
| 42 | + |
| 43 | +--- |
| 44 | + |
| 45 | +## Conformance Terminology |
| 46 | + |
| 47 | +The terms used in this report are defined as follows: |
| 48 | + |
| 49 | +- **Supports:** The functionality meets the success criterion without known defects. |
| 50 | +- **Partially Supports:** Some functionality does not meet the criterion. |
| 51 | +- **Does Not Support:** The majority of functionality does not meet the criterion. |
| 52 | +- **Not Applicable:** The criterion does not apply to the product. |
| 53 | + |
| 54 | +--- |
| 55 | + |
| 56 | +## WCAG 2.1 Conformance: Level A and AA |
| 57 | + |
| 58 | +> **Note:** Conformance claims apply to Ximera-generated pages and workflows as authored. Accessibility outcomes may vary depending on content authoring choices and embedded third-party tools. |
| 59 | +
|
| 60 | +--- |
| 61 | + |
| 62 | +### **Table 1: WCAG 2.1 Level A Success Criteria** |
| 63 | + |
| 64 | +| Criteria | Conformance | Remarks | |
| 65 | +|--------|------------|--------| |
| 66 | +| **1.1.1 Non-text Content** | Partially Supports | Mathematical notation and diagrams are primarily rendered as MathML or SVG with assistive text support. Some authored images may lack sufficient alternative text depending on author practices. | |
| 67 | +| **1.2.1–1.2.3 Audio/Video (Prerecorded)** | Not Applicable | Ximera does not natively require audio or video for interaction. | |
| 68 | +| **1.3.1 Info and Relationships** | Partially Supports | Semantic structure is generally preserved via HTML and MathML. Some complex mathematical layouts may not fully expose relationships programmatically. | |
| 69 | +| **1.3.2 Meaningful Sequence** | Supports | Content order follows logical reading and navigation sequences. | |
| 70 | +| **1.3.3 Sensory Characteristics** | Supports | Instructions do not rely solely on sensory characteristics such as color or location. | |
| 71 | +| **1.4.1 Use of Color** | Partially Supports | Color is sometimes used to convey correctness or emphasis, but is generally accompanied by text or symbols. | |
| 72 | +| **2.1.1 Keyboard** | Partially Supports | Core navigation is keyboard accessible. Some interactive math widgets and embedded tools may have limited keyboard support. | |
| 73 | +| **2.1.2 No Keyboard Trap** | Supports | Users can navigate into and out of interactive components using standard keyboard controls. | |
| 74 | +| **2.1.4 Character Key Shortcuts (2.1)** | Supports | No unmodifiable single-character shortcuts are used. | |
| 75 | +| **2.2.1 Timing Adjustable** | Supports | No time limits are imposed on completing tasks. | |
| 76 | +| **2.2.2 Pause, Stop, Hide** | Supports | No automatically moving or updating content that requires pausing. | |
| 77 | +| **2.3.1 Three Flashes or Below Threshold** | Supports | No flashing content exceeding thresholds is used. | |
| 78 | +| **2.4.1 Bypass Blocks** | Partially Supports | Headings and landmarks are generally present, but skip links are not consistently implemented across all themes. | |
| 79 | +| **2.4.2 Page Titled** | Supports | Pages have descriptive titles reflecting content context. | |
| 80 | +| **2.4.3 Focus Order** | Supports | Focus order follows DOM order and reading sequence. | |
| 81 | +| **2.4.4 Link Purpose (In Context)** | Supports | Links are generally descriptive within context. | |
| 82 | +| **2.5.1 Pointer Gestures (2.1)** | Not Applicable | No multi-point or path-based gestures are required. | |
| 83 | +| **2.5.2 Pointer Cancellation** | Supports | Actions are triggered on release, not on initial contact. | |
| 84 | +| **2.5.3 Label in Name** | Partially Supports | Most controls expose accessible names; some math-specific controls may need improved labeling. | |
| 85 | +| **2.5.4 Motion Actuation** | Not Applicable | No motion-based input is used. | |
| 86 | +| **3.1.1 Language of Page** | Supports | Default language is programmatically identified. | |
| 87 | +| **3.2.1 On Focus** | Supports | Focus does not trigger unexpected context changes. | |
| 88 | +| **3.2.2 On Input** | Supports | Input does not automatically cause context changes without user initiation. | |
| 89 | +| **3.3.1 Error Identification** | Supports | Input errors are identified and described textually. | |
| 90 | +| **3.3.2 Labels or Instructions** | Partially Supports | Most form fields include labels; some author-created inputs may require improved instructions. | |
| 91 | +| **4.1.1 Parsing** | Supports | HTML output conforms to modern parsing requirements. | |
| 92 | +| **4.1.2 Name, Role, Value** | Partially Supports | Standard controls expose name/role/value; some custom math widgets are still under improvement. | |
| 93 | + |
| 94 | +--- |
| 95 | + |
| 96 | +### **Table 2: WCAG 2.1 Level AA Success Criteria** |
| 97 | + |
| 98 | +| Criteria | Conformance | Remarks | |
| 99 | +|--------|------------|--------| |
| 100 | +| **1.3.4 Orientation (2.1)** | Supports | Content reflows in both portrait and landscape orientations. | |
| 101 | +| **1.3.5 Identify Input Purpose (2.1)** | Partially Supports | Common input purposes are identified; specialized mathematical inputs may not map cleanly to autocomplete semantics. | |
| 102 | +| **1.4.3 Contrast (Minimum)** | Partially Supports | Default themes generally meet contrast requirements; custom themes or author styling may introduce issues. | |
| 103 | +| **1.4.4 Resize Text** | Supports | Text can be resized up to 200% without loss of content or functionality. | |
| 104 | +| **1.4.5 Images of Text** | Supports | Text is rendered as text rather than images. | |
| 105 | +| **1.4.10 Reflow (2.1)** | Partially Supports | Content generally reflows at 400% zoom; complex mathematical layouts may require horizontal scrolling. | |
| 106 | +| **1.4.11 Non-text Contrast (2.1)** | Partially Supports | Focus indicators and graphical controls generally meet contrast requirements, with some exceptions in embedded tools. | |
| 107 | +| **1.4.12 Text Spacing (2.1)** | Partially Supports | Increased spacing may cause minor layout issues in dense mathematical expressions. | |
| 108 | +| **1.4.13 Content on Hover or Focus (2.1)** | Supports | Tooltips and hover content are generally dismissible or non-essential. | |
| 109 | +| **2.4.5 Multiple Ways** | Supports | Content can be accessed through navigation, search, or direct linking. | |
| 110 | +| **2.4.6 Headings and Labels** | Partially Supports | Headings are generally descriptive; quality depends on authoring practices. | |
| 111 | +| **2.4.7 Focus Visible** | Supports | Keyboard focus is visually indicated. | |
| 112 | +| **3.1.2 Language of Parts** | Partially Supports | Mathematical symbols and notation are language-neutral; mixed-language text may not always be explicitly marked. | |
| 113 | +| **3.2.3 Consistent Navigation** | Supports | Navigation elements are consistent across pages. | |
| 114 | +| **3.2.4 Consistent Identification** | Supports | Controls with the same function are identified consistently. | |
| 115 | +| **3.3.3 Error Suggestion** | Supports | Where applicable, suggestions for correcting errors are provided. | |
| 116 | +| **3.3.4 Error Prevention (Legal, Financial, Data)** | **Supports** | Ximera provides confirmation, revision, and unlimited retry mechanisms for problem submissions. No irreversible legal or financial transactions occur. | |
| 117 | +| **4.1.3 Status Messages (2.1)** | Partially Supports | Some dynamic feedback is available to assistive technologies; improvements are ongoing for real-time math feedback. | |
| 118 | + |
| 119 | +--- |
| 120 | + |
| 121 | +## Additional Notes on Error Prevention (WCAG 2.1 SC 3.3.4) |
| 122 | + |
| 123 | +Ximera’s pedagogical model explicitly emphasizes **error tolerance and reversibility**: |
| 124 | + |
| 125 | +- Students may revise and resubmit responses without penalty. |
| 126 | +- No submissions result in irreversible consequences. |
| 127 | +- Incorrect inputs are treated as part of the learning process, not as final transactions. |
| 128 | + |
| 129 | +This aligns directly with the intent of |
| 130 | +**WCAG 2.1 Success Criterion 3.3.4 – Error Prevention (Legal, Financial, Data)** |
| 131 | +as described in the W3C specification. |
| 132 | + |
| 133 | +--- |
| 134 | + |
| 135 | +## Legal Disclaimer |
| 136 | + |
| 137 | +This document is provided for informational purposes only and does not constitute a warranty of accessibility compliance. Accessibility outcomes may vary depending on content authoring practices, third-party integrations, and user configurations. The Ximera Project continues to improve accessibility as part of its ongoing development roadmap. |
| 138 | + |
| 139 | +--- |
| 140 | + |
| 141 | +_End of Accessibility Conformance Report_ |
0 commit comments