Accessibility · VPAT 2026

flexidesktop Accessibility & VPAT 2026

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.

Audited April 2026 WCAG 2.2 Level AA Section 508
Accessibility Conformance Report
flexidesktop
VPAT® 2.5
Voluntary Product Accessibility Template
WCAG 2.2 AA Section 508 WCAG 2.0 / 2.1
Report dateApril 8, 2026
Audited byAccessmeter
Criteria evaluated56 success criteria
Result0 failures
View the full report (PDF)
2.2 AA
WCAG conformance level
508
Section 508 aligned
44
Criteria fully supported
0
Failures found
56
Success criteria audited
Apr '26
Independent audit
Conformance results

How flexidesktop measures up

Every applicable Level A and AA success criterion is fully supported. Zero failures.

Perceivable

13 supported · 7 not applicable

Alt text on all meaningful imagery, a logical reading order, AA-level contrast, resizable text and full reflow at 320px.

Fully supports

Operable

16 supported · 4 not applicable

Full keyboard operation with no traps, visible focus, descriptive titles and links, and 24px minimum target sizes.

Fully supports

Understandable

13 supported · 0 not applicable

Consistent navigation and help, clearly labelled fields, error identification and suggestions, and accessible authentication.

Fully supports

Robust

2 supported · 1 not applicable

Valid, semantic markup with correct name, role and value exposed to assistive tech, and live status messages announced.

Fully supports
View the full WCAG 2.2 criteria table — all 56 success criteria
Success criterion Level Conformance Remarks
Perceivable
1.1.1 Non-text ContentASupportsMeaningful images carry text alternatives; decorative images are hidden from assistive tech.
1.2.1 Audio-only and Video-only (Prerecorded)ANot applicableThe product contains no pre-recorded audio-only or video-only content.
1.2.2 Captions (Prerecorded)ANot applicableNo pre-recorded video with audio is present in the interface.
1.2.3 Audio Description or Media AlternativeANot applicableNo synchronised media is present.
1.2.4 Captions (Live)AANot applicableNo live media is present.
1.2.5 Audio Description (Prerecorded)AANot applicableNo pre-recorded video content is present.
1.3.1 Info and RelationshipsASupportsStructure is conveyed with semantic markup — headings, lists, labels and table semantics.
1.3.2 Meaningful SequenceASupportsReading and navigation order is logical and preserved without CSS.
1.3.3 Sensory CharacteristicsASupportsInstructions don't rely on shape, size or location alone.
1.3.4 OrientationAASupportsContent is not locked to a single display orientation.
1.3.5 Identify Input PurposeAASupportsCommon form fields use appropriate autocomplete attributes.
1.4.1 Use of ColorASupportsColour is never the only means of conveying information.
1.4.2 Audio ControlANot applicableNo auto-playing audio longer than three seconds is present.
1.4.3 Contrast (Minimum)AASupportsText and essential graphics meet AA contrast ratios.
1.4.4 Resize TextAASupportsText scales to 200% without loss of content or function.
1.4.5 Images of TextAASupportsReal text is used instead of images of text.
1.4.10 ReflowAASupportsContent reflows to a 320px-wide viewport without two-dimensional scrolling.
1.4.11 Non-text ContrastAASupportsUI components and graphical objects meet the 3:1 contrast minimum.
1.4.12 Text SpacingAASupportsNo loss of content when users override text spacing.
1.4.13 Content on Hover or FocusAANot applicableNo additional content appears on hover or focus that requires this handling.
Operable
2.1.1 KeyboardASupportsAll functionality is operable through a keyboard interface.
2.1.2 No Keyboard TrapASupportsKeyboard focus can always move away from any component.
2.1.4 Character Key ShortcutsANot applicableNo single-character key shortcuts are implemented.
2.2.1 Timing AdjustableASupportsNo essential time limits are imposed on the user.
2.2.2 Pause, Stop, HideANot applicableNo moving, blinking or auto-updating content is present.
2.3.1 Three Flashes or Below ThresholdASupportsNothing flashes more than three times per second.
2.4.1 Bypass BlocksASupportsLandmarks and headings let users bypass repeated blocks of content.
2.4.2 Page TitledASupportsPages have descriptive, unique titles.
2.4.3 Focus OrderASupportsFocus order preserves meaning and operability.
2.4.4 Link Purpose (In Context)ASupportsThe purpose of each link is clear from its text or context.
2.4.5 Multiple WaysAASupportsMore than one way is available to locate pages within the app.
2.4.6 Headings and LabelsAASupportsHeadings and labels describe topic or purpose.
2.4.7 Focus VisibleAASupportsA visible focus indicator is present for all interactive elements.
2.4.11 Focus Not Obscured (Minimum)AASupportsThe focused element is not entirely hidden by author-created content.
2.5.1 Pointer GesturesASupportsAll functionality works with single-pointer actions; no path-based gestures required.
2.5.2 Pointer CancellationASupportsActions complete on the up-event, allowing cancellation.
2.5.3 Label in NameASupportsAccessible names include the visible label text.
2.5.4 Motion ActuationANot applicableNo functionality is triggered by device or user motion.
2.5.7 Dragging MovementsAANot applicableNo functionality relies on dragging movements.
2.5.8 Target Size (Minimum)AASupportsInteractive targets meet the 24×24 CSS-pixel minimum.
Understandable
3.1.1 Language of PageASupportsThe default human language of each page is set programmatically.
3.1.2 Language of PartsAASupportsPassages in another language are marked up where they occur.
3.2.1 On FocusASupportsReceiving focus does not trigger an unexpected change of context.
3.2.2 On InputASupportsChanging a setting does not automatically change context without warning.
3.2.3 Consistent NavigationAASupportsNavigation is consistent across the application.
3.2.4 Consistent IdentificationAASupportsComponents with the same function are identified consistently.
3.2.6 Consistent HelpASupportsHelp mechanisms appear in a consistent location across pages.
3.3.1 Error IdentificationASupportsInput errors are identified and described to the user in text.
3.3.2 Labels or InstructionsASupportsLabels and instructions are provided where input is required.
3.3.3 Error SuggestionAASupportsWhen an error is detected, a correction suggestion is offered.
3.3.4 Error Prevention (Legal, Financial, Data)AASupportsSubmissions are reversible, checked or confirmable.
3.3.7 Redundant EntryASupportsPreviously entered information is auto-populated or available to select.
3.3.8 Accessible Authentication (Minimum)AASupportsAuthentication does not rely on a cognitive function test.
Robust
4.1.1 ParsingANot applicableObsolete and removed in WCAG 2.2; no longer evaluated.
4.1.2 Name, Role, ValueASupportsName, role and value are exposed for all UI components.
4.1.3 Status MessagesAASupportsStatus messages are announced by assistive technology without focus change.
"Supports" means the criterion is fully met. "Not applicable" means the criterion does not apply to flexidesktop's interface (for example, pre-recorded media criteria on a product with no video content).

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 full report

Download the VPAT 2026

The complete, unedited Accessibility Conformance Report — every criterion, conformance level and the auditor's remarks.

flexidesktop VPAT® 2.5

Voluntary Product Accessibility Template — WCAG 2.2 & Section 508 edition.

PublishedApril 2026
AuditorAccessmeter
FormatPDF

What's inside

  • Full WCAG 2.0, 2.1 and 2.2 conformance tables (Level A & AA)
  • Section 508 functional performance criteria
  • Per-criterion conformance level and the auditor's remarks
  • Evaluation methods, tools and scope

Found an accessibility barrier?

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.

Accessibility team [email protected]

When you write in, please include

  • The page or screen where it happened
  • Your browser, OS and assistive technology
  • What you expected versus what happened

Need the full report or have questions?

Download the full VPAT or get in touch with questions about conformance, procurement or assistive technology compatibility.

WCAG 2.2 AA Section 508 Independently audited