Single-user Windows 10/11
Multi-user Windows Server 2025
Real-World Applications
Discover Our Mission.
Get in touch.
Compliance & VPAT.
Get Answers Here.
We believe everyone deserves a seamless desktop experience.
In April 2026 an independent firm audited flexidesktop against WCAG 2.2 Level AA and Section 508. Here are the results — and the full report.
Every applicable Level A and AA success criterion is fully supported. Zero failures.
Alt text on all meaningful imagery, a logical reading order, AA-level contrast, resizable text and full reflow at 320px.
Full keyboard operation with no traps, visible focus, descriptive titles and links, and 24px minimum target sizes.
Consistent navigation and help, clearly labelled fields, error identification and suggestions, and accessible authentication.
Valid, semantic markup with correct name, role and value exposed to assistive tech, and live status messages announced.
| Success criterion | Level | Conformance | Remarks |
|---|---|---|---|
| Perceivable | |||
| 1.1.1 Non-text Content | A | Supports | Meaningful images carry text alternatives; decorative images are hidden from assistive tech. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Not applicable | The product contains no pre-recorded audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded) | A | Not applicable | No pre-recorded video with audio is present in the interface. |
| 1.2.3 Audio Description or Media Alternative | A | Not applicable | No synchronised media is present. |
| 1.2.4 Captions (Live) | AA | Not applicable | No live media is present. |
| 1.2.5 Audio Description (Prerecorded) | AA | Not applicable | No pre-recorded video content is present. |
| 1.3.1 Info and Relationships | A | Supports | Structure is conveyed with semantic markup — headings, lists, labels and table semantics. |
| 1.3.2 Meaningful Sequence | A | Supports | Reading and navigation order is logical and preserved without CSS. |
| 1.3.3 Sensory Characteristics | A | Supports | Instructions don't rely on shape, size or location alone. |
| 1.3.4 Orientation | AA | Supports | Content is not locked to a single display orientation. |
| 1.3.5 Identify Input Purpose | AA | Supports | Common form fields use appropriate autocomplete attributes. |
| 1.4.1 Use of Color | A | Supports | Colour is never the only means of conveying information. |
| 1.4.2 Audio Control | A | Not applicable | No auto-playing audio longer than three seconds is present. |
| 1.4.3 Contrast (Minimum) | AA | Supports | Text and essential graphics meet AA contrast ratios. |
| 1.4.4 Resize Text | AA | Supports | Text scales to 200% without loss of content or function. |
| 1.4.5 Images of Text | AA | Supports | Real text is used instead of images of text. |
| 1.4.10 Reflow | AA | Supports | Content reflows to a 320px-wide viewport without two-dimensional scrolling. |
| 1.4.11 Non-text Contrast | AA | Supports | UI components and graphical objects meet the 3:1 contrast minimum. |
| 1.4.12 Text Spacing | AA | Supports | No loss of content when users override text spacing. |
| 1.4.13 Content on Hover or Focus | AA | Not applicable | No additional content appears on hover or focus that requires this handling. |
| Operable | |||
| 2.1.1 Keyboard | A | Supports | All functionality is operable through a keyboard interface. |
| 2.1.2 No Keyboard Trap | A | Supports | Keyboard focus can always move away from any component. |
| 2.1.4 Character Key Shortcuts | A | Not applicable | No single-character key shortcuts are implemented. |
| 2.2.1 Timing Adjustable | A | Supports | No essential time limits are imposed on the user. |
| 2.2.2 Pause, Stop, Hide | A | Not applicable | No moving, blinking or auto-updating content is present. |
| 2.3.1 Three Flashes or Below Threshold | A | Supports | Nothing flashes more than three times per second. |
| 2.4.1 Bypass Blocks | A | Supports | Landmarks and headings let users bypass repeated blocks of content. |
| 2.4.2 Page Titled | A | Supports | Pages have descriptive, unique titles. |
| 2.4.3 Focus Order | A | Supports | Focus order preserves meaning and operability. |
| 2.4.4 Link Purpose (In Context) | A | Supports | The purpose of each link is clear from its text or context. |
| 2.4.5 Multiple Ways | AA | Supports | More than one way is available to locate pages within the app. |
| 2.4.6 Headings and Labels | AA | Supports | Headings and labels describe topic or purpose. |
| 2.4.7 Focus Visible | AA | Supports | A visible focus indicator is present for all interactive elements. |
| 2.4.11 Focus Not Obscured (Minimum) | AA | Supports | The focused element is not entirely hidden by author-created content. |
| 2.5.1 Pointer Gestures | A | Supports | All functionality works with single-pointer actions; no path-based gestures required. |
| 2.5.2 Pointer Cancellation | A | Supports | Actions complete on the up-event, allowing cancellation. |
| 2.5.3 Label in Name | A | Supports | Accessible names include the visible label text. |
| 2.5.4 Motion Actuation | A | Not applicable | No functionality is triggered by device or user motion. |
| 2.5.7 Dragging Movements | AA | Not applicable | No functionality relies on dragging movements. |
| 2.5.8 Target Size (Minimum) | AA | Supports | Interactive targets meet the 24×24 CSS-pixel minimum. |
| Understandable | |||
| 3.1.1 Language of Page | A | Supports | The default human language of each page is set programmatically. |
| 3.1.2 Language of Parts | AA | Supports | Passages in another language are marked up where they occur. |
| 3.2.1 On Focus | A | Supports | Receiving focus does not trigger an unexpected change of context. |
| 3.2.2 On Input | A | Supports | Changing a setting does not automatically change context without warning. |
| 3.2.3 Consistent Navigation | AA | Supports | Navigation is consistent across the application. |
| 3.2.4 Consistent Identification | AA | Supports | Components with the same function are identified consistently. |
| 3.2.6 Consistent Help | A | Supports | Help mechanisms appear in a consistent location across pages. |
| 3.3.1 Error Identification | A | Supports | Input errors are identified and described to the user in text. |
| 3.3.2 Labels or Instructions | A | Supports | Labels and instructions are provided where input is required. |
| 3.3.3 Error Suggestion | AA | Supports | When an error is detected, a correction suggestion is offered. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Supports | Submissions are reversible, checked or confirmable. |
| 3.3.7 Redundant Entry | A | Supports | Previously entered information is auto-populated or available to select. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Supports | Authentication does not rely on a cognitive function test. |
| Robust | |||
| 4.1.1 Parsing | A | Not applicable | Obsolete and removed in WCAG 2.2; no longer evaluated. |
| 4.1.2 Name, Role, Value | A | Supports | Name, role and value are exposed for all UI components. |
| 4.1.3 Status Messages | AA | Supports | Status messages are announced by assistive technology without focus change. |
Tested with axe DevTools, Lighthouse, NVDA and manual keyboard review across the web app and admin dashboard. Scope covers flexidesktop's own surfaces; the Windows OS and third-party apps you run inside your desktop are out of scope.
The complete, unedited Accessibility Conformance Report — every criterion, conformance level and the auditor's remarks.
Voluntary Product Accessibility Template — WCAG 2.2 & Section 508 edition.
We're committed to resolving accessibility barriers promptly. If something doesn't work as expected with your assistive technology, contact us and we'll investigate.
Download the full VPAT or get in touch with questions about conformance, procurement or assistive technology compatibility.





