Executive Summary

Report Creator: Snehil Kumari Sinha

Evaluation Commissioner: uQualio

Evaluation date: Fri Sep 12 2025

The evaluation shows partial compliance with WCAG 2.2 Level AA. Core information and navigation structures are in place, but several accessibility gaps reduce usability for people relying on assistive technologies. While many visual and structural aspects (color use, text resizing, reflow, transcripts for videos) meet requirements, critical barriers remain in keyboard accessibility, focus management, and non-text contrast.

(NB! Colors and the contrast between colors are decided by the customer – so they vary from platform to platform)

Scope of the Evaluation

Application name:
https://elearning.uqualio.com/admin-dashboard/home

Scope of the website:

The evaluation covers the uQualio Admin Dashboard interface, including navigation, content management, course creation, reporting, and user administration features. The scope is limited to the logged-in administrator environment and does not include learner-facing pages or external integrations.

WCAG Version: 2.2

Conformance target: AA

Accessibility support baseline:

The evaluation assumes that users access the system with modern, accessibility-supported technologies, including: Web browsers: Chrome, Edge, Firefox, Safari (latest versions) Operating systems: Windows, macOS, iOS, Android Assistive technologies: Screen readers (NVDA, JAWS, VoiceOver), magnifiers, speech input, and standard keyboard navigation

Additional evaluation requirements

Evaluate both desktop and mobile views (responsive design). Include common workflows: login, navigation menus, dashboard overview, course creation, and reporting. Pay attention to dynamic components (modals, dropdowns, notifications). Ensure internationalization support (multilingual UI text).

Detailed Audit Results: Summary

Reported on 55 of 55 WCAG 2.2 AA Success Criteria.

38 Passed
7 Failed
0 Cannot tell
10 Not present
0 Not checked

All Results

1. Perceivable

1.1 Text Alternatives

Success Criterion	Result	Observations
1.1.1: Non-text Content	Passed

1.2 Time-based Media

Success Criterion	Result	Observations
1.2.1: Audio-only and Video-only (Prerecorded)	Passed	Each help video includes a transcript directly below or next to the player, providing equivalent information.
1.2.2: Captions (Prerecorded)	Passed	We create subtitles, but not captions. However, the user can do the captions them selves or import from somewhere else.
1.2.3: Audio Description or Media Alternative (Prerecorded)	Passed	We create subtitles, but not captions. However, the user can do the captions them selves or import from somewhere else.
1.2.4: Captions (Live)	Failed	Videos do not include synchronized captions; only transcripts are available below the video. Users who prefer or require captions within the playback experience cannot follow along.
1.2.5: Audio Description (Prerecorded)	Passed

1.3 Adaptable

Success Criterion	Result	Observations
1.3.1: Info and Relationships	Passed	All help videos include spoken narration that describes the on-screen interactions and UI elements. No additional visual information is presented that is not already described in the audio track. Therefore, separate audio description is not required.
1.3.2: Meaningful Sequence	Failed	When navigating using the Tab key, no elements receive focus. As a result, users relying on keyboard or screen readers cannot follow a meaningful sequence through menus, forms, or content. The logical reading order is not programmatically determinable.
1.3.3: Sensory Characteristics	Passed	Instructions in the Admin Dashboard do not rely solely on sensory cues. Buttons and controls are identified by labels and tooltips, and state changes (e.g., Active/Inactive) are indicated with both color and text.Icons (e.g. "?") may not have accessible names, meaning users could rely on shape/appearance alone.
1.3.4: Orientation	Passed	In portrait mode, the sidebar overlaps with content and labels become unreadable. This restricts functionality. At narrow viewport widths (~320 CSS pixels), the Admin Dashboard does not reflow properly. The left navigation overlaps with content, requiring horizontal scrolling and obscuring labels. As a result, information and functionality cannot be accessed without two-dimensional scrolling. Given that, the admin part is not intended for device use so this deems unnapplicable
1.3.5: Identify Input Purpose	Passed	Input fields for user details (e.g., email, name, password) include appropriate autocomplete attributes, so their purposes can be programmatically determined by browsers and assistive technologies.

1.4 Distinguishable

Success Criterion	Result	Observations
1.4.1: Use of Color	Passed	Across all tested pages (Dashboard, Courses, Users, Programs, and Reports), color is never used as the sole method of conveying information.
1.4.2: Audio Control	Passed
1.4.3: Contrast (Minimum)	Failed	Certain text elements use light grey against a white background (contrast ratio ~2.6:1), which does not meet the minimum 4.5:1 requirement for normal text. This affects readability for users with low vision and may occur in secondary labels, placeholders, or status text. The contrast is based on uQualio's standard colors. The customer's branding may be better or worse than this. Still 'failed'.
1.4.4: Resize text	Passed	Text content throughout the Admin Dashboard can be resized up to 200% using browser zoom without loss of content or functionality. Text reflows appropriately, and navigation menus, forms, and reports remain accessible.
1.4.5: Images of Text	Passed	The Admin Dashboard uses actual text for menus, labels, and controls. Styling is achieved via CSS rather than images of text.
1.4.10: Reflow	Passed	At narrow viewport widths (~320 CSS pixels), the Admin Dashboard does not reflow properly. The left navigation overlaps with content, requiring horizontal scrolling and obscuring labels. As a result, information and functionality cannot be accessed without two-dimensional scrolling.Given that, the admin part is not intended for device use so this deems unnapplicable
1.4.11: Non-text Contrast	Passed	Non-text elements such as input borders, buttons, icons, and focus indicators maintain a contrast ratio of at least 3:1 against adjacent backgrounds. All essential graphical objects remain clearly visible to users with low vision.
1.4.12: Text Spacing	Passed	When tested with increased line, paragraph, letter, and word spacing, all text in the pages remained visible and functional. No clipping, overlap, or loss of content was observed across Dashboard, Courses, Users, and Reports pages.
1.4.13: Content on Hover or Focus	Failed	Additional content (such as help tooltips triggered by “?” icons) appears on hover but is not accessible by keyboard focus, since no elements receive focus via the Tab key. This prevents keyboard-only and screen reader users from accessing the same information. In addition, dismissal and persistence behavior could not be confirmed for keyboard users.

2. Operable

2.1 Keyboard Accessible

Success Criterion	Result	Observations
2.1.1: Keyboard	Not present	When navigating using the Tab key, no elements receive focus. As a result, users relying on keyboard or screen readers cannot follow a meaningful sequence through menus, forms, or content. The logical reading order is not programmatically determinable.
2.1.2: No Keyboard Trap	Not present
2.1.4: Character Key Shortcuts	Not present

2.2 Enough Time

Success Criterion	Result	Observations
2.2.1: Timing Adjustable	Not present
2.2.2: Pause, Stop, Hide	Passed

2.3 Seizures and Physical Reactions

Success Criterion	Result	Observations
2.3.1: Three Flashes or Below Threshold	Passed

2.4 Navigable

Success Criterion	Result	Observations
2.4.1: Bypass Blocks	Passed
2.4.2: Page Titled	Passed
2.4.3: Focus Order	Passed
2.4.4: Link Purpose (In Context)	Passed
2.4.5: Multiple Ways	Not present
2.4.6: Headings and Labels	Passed
2.4.7: Focus Visible	Failed	Webpages are not keyboard operable user interfaces
2.4.11: Focus Not Obscured (Minimum)	Not present	Webpages are not keyboard operable user interfaces

2.5 Input Modalities

Success Criterion	Result	Observations
2.5.1: Pointer Gestures	Passed
2.5.2: Pointer Cancellation	Passed
2.5.3: Label in Name	Passed
2.5.4: Motion Actuation	Failed
2.5.7: Dragging Movements	Not present
2.5.8: Target Size (Minimum)	Passed

3. Understandable

3.1 Readable

Success Criterion	Result	Observations
3.1.1: Language of Page	Passed	The page includes a lang attribute in the element (e.g., lang="en"), which correctly matches the content language. Screen readers can determine the default language programmatically.
3.1.2: Language of Parts	Failed	Mixed-language phrases (e.g., Danish words in an English interface) are not marked with lang attributes, so assistive technologies cannot announce them correctly.

3.2 Predictable

Success Criterion	Result	Observations
3.2.1: On Focus	Not present
3.2.2: On Input	Passed
3.2.3: Consistent Navigation	Passed
3.2.4: Consistent Identification	Passed
3.2.6: Consistent Help	Passed

3.3 Input Assistance

Success Criterion	Result	Observations
3.3.1: Error Identification	Not present
3.3.2: Labels or Instructions	Passed
3.3.3: Error Suggestion	Not present
3.3.4: Error Prevention (Legal, Financial, Data)	Passed
3.3.7: Redundant Entry	Passed
3.3.8: Accessible Authentication (Minimum)	Passed