WCAG-EM Accessibility Evaluation – Custom Limb-Loss Recovery Web Application
About the Evaluation
- Report Creator
- Jeffery Aideyan-Ohonba
- Evaluation Commissioner
- University accessibility evaluation project
- Evaluation date
- Thu Dec 11 2025
Executive Summary
This evaluation assessed the accessibility of the Custom Limb-Loss Recovery Web Application against WCAG 2.2 Level A and AA using the WCAG-EM methodology, with a specific focus on motor accessibility for users with limb loss. A representative sample of pages was evaluated using automated testing to establish a baseline, followed by detailed manual keyboard-based testing.
Overall, the website demonstrates a good level of accessibility for basic navigation and informational content. The home page and article repository page generally support keyboard-only interaction, logical focus order, visible focus indicators, and adequately sized interactive targets. These aspects reduce physical effort and support users who rely on keyboard or alternative input methods.
However, significant motor accessibility barriers were identified on the individual article page. Several visually interactive components are not reachable or operable using the keyboard, focus order does not consistently follow the visual reading sequence, focus visibility is reduced in some components, and no mechanism is provided to bypass repeated content. These issues increase navigation effort and prevent task completion for users with limb loss.
In summary, while the application partially conforms to WCAG requirements relevant to motor accessibility, improvements are required, particularly for complex interactive components, to ensure consistent, reliable keyboard access across all pages.
Scope of the Evaluation
- Website name
- Custom Limb-Loss Recovery Web Application
- Scope of the website
- A representative sample of public-facing web content of the Custom Limb-Loss Recovery Web Application, located at: https://delightful-island-079d50603.2.azurestaticapps.net/ The evaluation includes the following key pages: 1. Home Page 2. Article Repository page 3. Individual Article Page These pages contain the core interaction model of the application, navigation, and access to support resources, and therefore represent the functional scope of this evaluation.
- WCAG Version
- 2.2
- Conformance target
- AA
- Accessibility support baseline
- The accessibility support baseline for this evaluation is: Browser: Google Chrome (latest version). Operating System: macOS (latest version). Primary interaction mode: Keyboard-only navigation. Inspection and analysis tools: Chrome DevTools for HTML, focus order, and ARIA inspection. This baseline reflects the evaluation context and the motor-impaired interaction scenarios relevant to users with limb loss (e.g., reliance on keyboard navigation, reduced precision pointing).
- Additional evaluation requirements
- This evaluation includes the following additional requirements: - The evaluation will focus specifically on motor-related WCAG 2.2 Level A and AA Success Criteria, as defined in Appendix A of the dissertation. - The evaluation will be supplemented by a usability-based heuristic review to identify motor-accessibility barriers not captured by WCAG alone. - The WCAG-EM Report Tool will be used as the primary documentation method, with additional screenshots or notes included in appendices.
Detailed Audit Results
Summary
Reported on 29 of 55 WCAG 2.2 AA Success Criteria.
- 13 Passed
- 4 Failed
- 2 Cannot tell
- 10 Not present
- 26 Not checked
All Results
1 Perceivable
1.1 Text Alternatives
| Success Criterion | Result | Observations |
|---|---|---|
| 1.1.1: Non-text Content | Entire sampleResult: Not checked |
1.2 Time-based Media
| Success Criterion | Result | Observations |
|---|---|---|
| 1.2.1: Audio-only and Video-only (Prerecorded) | Entire sampleResult: Not checked | |
| 1.2.2: Captions (Prerecorded) | Entire sampleResult: Not checked | |
| 1.2.3: Audio Description or Media Alternative (Prerecorded) | Entire sampleResult: Not checked | |
| 1.2.4: Captions (Live) | Entire sampleResult: Not checked | |
| 1.2.5: Audio Description (Prerecorded) | Entire sampleResult: Not checked |
1.3 Adaptable
| Success Criterion | Result | Observations |
|---|---|---|
| 1.3.1: Info and Relationships | Entire sampleResult: Not checked | |
| 1.3.2: Meaningful Sequence | Entire sampleResult: Not checked | |
| 1.3.3: Sensory Characteristics | Entire sampleResult: Not checked | |
| 1.3.4: Orientation | Entire sampleResult: Not checked | |
| 1.3.5: Identify Input Purpose | Entire sampleResult: Not checked |
1.4 Distinguishable
| Success Criterion | Result | Observations |
|---|---|---|
| 1.4.1: Use of Color | Entire sampleResult: Not checked | |
| 1.4.2: Audio Control | Entire sampleResult: Not checked | |
| 1.4.3: Contrast (Minimum) | Entire sampleResult: Not checked | |
| 1.4.4: Resize text | Entire sampleResult: Not checked | |
| 1.4.5: Images of Text | Entire sampleResult: Not checked | |
| 1.4.10: Reflow | Entire sampleResult: Not checked | |
| 1.4.11: Non-text Contrast | Entire sampleResult: Not checked | |
| 1.4.12: Text Spacing | Entire sampleResult: Not checked | |
| 1.4.13: Content on Hover or Focus | Entire sampleResult: Not checked |
2 Operable
2.1 Keyboard Accessible
| Success Criterion | Result | Observations |
|---|---|---|
| 2.1.1: Keyboard | Entire sampleResult: Failed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Failed | Entire sampleObservations: While the home page and article repository page are fully operable using keyboard-only input, the individual article page contains multiple interactive components that are not reachable or operable via keyboard, resulting in a failure of this criterion for the sample. Home PageAll interactive functionality on the home page can be operated using keyboard-only input. Article Repository pageAll core functionality, including browsing, filtering, and navigation, is operable using keyboard-only input. Individual Article PageMultiple visually interactive components (toolkit cards, questionnaires, checklists, and game elements) are not reachable or operable using keyboard-only input. |
| 2.1.2: No Keyboard Trap | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: Across all sampled pages, keyboard focus can move into and away from interactive components without trapping. Home PageKeyboard focus can move into and away from all components without trapping. Article Repository pageKeyboard focus can move into and away from all interactive components without trapping. Individual Article PageKeyboard focus can move into and away from all reachable components without trapping. |
| 2.1.4: Character Key Shortcuts | Entire sampleResult: Not present Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Not present | Entire sampleObservations: No sampled pages implement single-character keyboard shortcuts. Home PageNo single-character keyboard shortcuts are implemented on this page. Article Repository pageNo single-character keyboard shortcuts are implemented on this page. Individual Article PageNo single-character keyboard shortcuts are implemented on this page. |
2.2 Enough Time
| Success Criterion | Result | Observations |
|---|---|---|
| 2.2.1: Timing Adjustable | Entire sampleResult: Not present Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Not present | Entire sampleObservations: No time limits were present on any sampled pages that required user adjustment. Home PageNo time limits are present that require user adjustment. Article Repository pageNo time limits are present that require user adjustment. Individual Article PageNo time limits are present that require user adjustment. |
| 2.2.2: Pause, Stop, Hide | Entire sampleResult: Not present Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Not present | Entire sampleObservations: No sampled pages contain moving, blinking, or auto-updating content requiring user control. Home PageNo moving, blinking, or auto-updating content is present. Article Repository pageNo moving, blinking, or auto-updating content is present. Individual Article PageNo moving, blinking, or auto-updating content is present. |
2.3 Seizures and Physical Reactions
| Success Criterion | Result | Observations |
|---|---|---|
| 2.3.1: Three Flashes or Below Threshold | Entire sampleResult: Not checked |
2.4 Navigable
| Success Criterion | Result | Observations |
|---|---|---|
| 2.4.1: Bypass Blocks | Entire sampleResult: Failed Home PageResult: Failed Article Repository pageResult: Failed Individual Article PageResult: Failed | Entire sampleObservations: No sampled pages provide a mechanism to bypass repeated navigation content and move directly to the main content. Home PageNo mechanism is provided to bypass repeated navigation content and move directly to the main content. Article Repository pageNo mechanism is provided to bypass repeated page content and move directly to the main content. Individual Article PageNo mechanism is provided to bypass repeated page content and move directly to the main content. |
| 2.4.2: Page Titled | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: All sampled pages have descriptive and meaningful page titles. Home PageThe page has a descriptive and meaningful title. Article Repository pageThe page has a descriptive and meaningful title. Individual Article PageThe page has a descriptive and meaningful title. |
| 2.4.3: Focus Order | Entire sampleResult: Failed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Failed | Entire sampleObservations: The individual article page exhibits keyboard focus order issues where focus skips interactive sections, resulting in a failure for the overall sample. Home PageKeyboard focus moves in a logical and predictable order through the page. Article Repository pageKeyboard focus moves in a logical and predictable order through the page content and controls. Individual Article PageKeyboard focus skips multiple interactive sections, resulting in a navigation order that does not follow the visual or logical reading sequence. |
| 2.4.4: Link Purpose (In Context) | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: Links across all sampled pages clearly communicate their purpose through visible text or surrounding context. Home PageAll links clearly communicate their purpose using visible text or surrounding context. Article Repository pageLinks and controls clearly communicate their purpose using visible text and surrounding context. Individual Article PageLinks clearly communicate their purpose using visible text or surrounding context. |
| 2.4.5: Multiple Ways | Entire sampleResult: Not present Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Not present | Entire sampleObservations: Sampled pages do not provide multiple navigation methods beyond the primary interface structure. Home PageThe page does not provide multiple navigation paths beyond the primary interface structure. Article Repository pageThe page does not provide multiple navigation methods beyond the primary interface structure. Individual Article PageThe page does not provide multiple navigation paths beyond the primary interface structure. |
| 2.4.6: Headings and Labels | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: Headings and labels are descriptive and support efficient navigation across all sampled pages. Home PageHeadings and labels are descriptive and appropriately structured. Article Repository pageHeadings and labels are descriptive and support efficient scanning and navigation. Individual Article PageHeadings and labels are descriptive and support content scanning. |
| 2.4.7: Focus Visible | Entire sampleResult: Failed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Failed | Entire sampleObservations: On the individual article page, keyboard focus indicators become difficult to perceive within certain interactive components, resulting in a failure for the overall sample. Home PageKeyboard focus is clearly visible on all interactive elements. Article Repository pageKeyboard focus is clearly visible on all interactive elements. Individual Article PageFocus indicators become difficult to perceive within certain interactive components, reducing trackability during keyboard navigation. |
| 2.4.11: Focus Not Obscured (Minimum) | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: Focus indicators are not hidden or obscured by other content on any sampled pages. Home PageFocus indicators are not hidden or obscured by other content. Article Repository pageFocus indicators are not hidden or obscured by other interface elements. Individual Article PageFocus indicators are not hidden behind other content. |
2.5 Input Modalities
| Success Criterion | Result | Observations |
|---|---|---|
| 2.5.1: Pointer Gestures | Entire sampleResult: Not present Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Not present | Entire sampleObservations: No sampled pages require complex pointer gestures for interaction. Home PageNo complex pointer gestures are required for interaction. Article Repository pageNo complex pointer gestures are required to operate page functionality. Individual Article PageNo complex pointer gestures are required for interaction. |
| 2.5.2: Pointer Cancellation | Entire sampleResult: Not present Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Not present | Entire sampleObservations: No press-and-hold or irreversible pointer actions are present across the sample. Home PageNo press-and-hold or irreversible pointer actions are present. Article Repository pageNo press-and-hold or irreversible pointer actions are present. Individual Article PageNo press-and-hold or irreversible pointer actions are present. |
| 2.5.3: Label in Name | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: Visible labels for controls match their programmatic names across all sampled pages. Home PageVisible labels for controls match their programmatic names. Article Repository pageVisible labels for interactive controls match their programmatic names. Individual Article PageVisible labels match the programmatic names of controls. |
| 2.5.4: Motion Actuation | Entire sampleResult: Not present | Entire sampleObservations: No sampled pages require drag-and-drop interactions for core functionality. |
| 2.5.7: Dragging Movements | Entire sampleResult: Not checked Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Passed | Home PageNo drag-and-drop interactions are required. Article Repository pageNo drag-and-drop interactions are required to use the page. Individual Article PageNo drag-and-drop actions are required; slider and controls are operable via keyboard. |
| 2.5.8: Target Size (Minimum) | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: Interactive targets across the sample meet minimum size requirements and do not require fine motor precision. Home PageInteractive targets meet minimum size requirements and are sufficiently spaced. Article Repository pageInteractive targets meet minimum size requirements and are sufficiently spaced to reduce precision demands. Individual Article PageInteractive targets meet minimum size requirements and do not require fine precision. |
3 Understandable
3.1 Readable
| Success Criterion | Result | Observations |
|---|---|---|
| 3.1.1: Language of Page | Entire sampleResult: Not checked | |
| 3.1.2: Language of Parts | Entire sampleResult: Not checked |
3.2 Predictable
| Success Criterion | Result | Observations |
|---|---|---|
| 3.2.1: On Focus | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: No unexpected changes in context occur when elements receive focus across all sampled pages. Home PageNo unexpected context changes occur when elements receive focus. Article Repository pageNo unexpected context changes occur when elements receive focus. Individual Article PageNo unexpected changes in context occur when elements receive focus. |
| 3.2.2: On Input | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: User input does not trigger unexpected changes in context on any sampled pages. Home PageUser input does not trigger unexpected changes in context. Article Repository pageUser input does not trigger unexpected changes in context. Individual Article PageUser input does not trigger unexpected changes in context. |
| 3.2.3: Consistent Navigation | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: Navigation mechanisms are presented consistently across the sampled pages. Home PageNavigation mechanisms are presented consistently across the site. Article Repository pageNavigation mechanisms are presented consistently across the site. Individual Article PageNavigation mechanisms are presented consistently across the site. |
| 3.2.4: Consistent Identification | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: Components with the same functionality are identified consistently throughout the sample. Home PageComponents with the same functionality are identified consistently. Article Repository pageComponents with the same functionality are identified consistently throughout the page. Individual Article PageComponents with the same functionality are identified consistently. |
| 3.2.6: Consistent Help | Entire sampleResult: Not present Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Not present | Entire sampleObservations: No sampled pages provide contextual or task-based help mechanisms. Home PageNo contextual help mechanisms are provided on this page. Article Repository pageNo contextual or task-based help mechanisms are provided on this page. Individual Article PageNo contextual or task-based help mechanisms are provided. |
3.3 Input Assistance
| Success Criterion | Result | Observations |
|---|---|---|
| 3.3.1: Error Identification | Entire sampleResult: Cannot tell Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Cannot tell | Entire sampleObservations: No error conditions were encountered during testing that would allow evaluation of error identification across the sample. Home PageNo input errors are generated on this page. Article Repository pageNo input errors are generated on this page. Individual Article PageNo error conditions were encountered during testing that would allow evaluation of error identification. |
| 3.3.2: Labels or Instructions | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: Clear labels and instructions are provided wherever user input is required across all sampled pages. Home PageClear labels and instructions are provided where user input is required. Article Repository pageClear labels and instructions are provided where user input is required. Individual Article PageClear labels and instructions are provided where user input is required. |
| 3.3.3: Error Suggestion | Entire sampleResult: Cannot tell Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Cannot tell | Entire sampleObservations: No errors were triggered during testing that would allow assessment of error recovery suggestions. Home PageNo error recovery scenarios are present. Article Repository pageNo error recovery scenarios are present. Individual Article PageNo errors were triggered that would allow assessment of error suggestions. |
| 3.3.4: Error Prevention (Legal, Financial, Data) | Entire sampleResult: Not present Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Not present | Entire sampleObservations: No sampled pages involve legal, financial, or data-submission actions requiring error prevention mechanisms. Home PageNo legal, financial, or data-submission actions occur. Article Repository pageNo legal, financial, or data-submission actions occur. Individual Article PageNo legal, financial, or data-submission actions occur on this page. |
| 3.3.7: Redundant Entry | Entire sampleResult: Passed Home PageResult: Passed Article Repository pageResult: Passed Individual Article PageResult: Passed | Entire sampleObservations: Users are not required to re-enter the same information across any sampled pages. Home PageUsers are not required to re-enter information. Article Repository pageUsers are not required to re-enter the same information during interaction. Individual Article PageUsers are not required to re-enter information. |
| 3.3.8: Accessible Authentication (Minimum) | Entire sampleResult: Not present Home PageResult: Not present Article Repository pageResult: Not present Individual Article PageResult: Not present | Entire sampleObservations: No authentication mechanisms are present on any sampled pages. Home PageNo authentication mechanisms are present. Article Repository pageNo authentication mechanisms are present. Individual Article PageNo authentication mechanisms are present. |
4 Robust
4.1 Compatible
| Success Criterion | Result | Observations |
|---|---|---|
| 4.1.2: Name, Role, Value | Entire sampleResult: Not checked | |
| 4.1.3: Status Messages | Entire sampleResult: Not checked |
Sample of Audited Web Pages
- Home Page - https://delightful-island-079d50603.2.azurestaticapps.net/
- Article Repository page - https://delightful-island-079d50603.2.azurestaticapps.net/articles
- Individual Article Page - https://delightful-island-079d50603.2.azurestaticapps.net/articles/understandingyourownnoodle
Web Technology
HTML,CSS,WAI-ARIA,JavaScript
Recording of Evaluation Specifics
The evaluation focused on Success Criteria relevant to motor accessibility, including keyboard access, focus management, target size, and interaction predictability. Automated findings unrelated to motor impairment (e.g. semantic or screen reader–specific issues) were recorded but not prioritised for manual evaluation in line with the study scope.