Accessibility Support

Jan 08, 2026
3 minutes to read

XAF UI for ASP.NET Core Blazor and WinForms platforms offers partial accessibility support at the same level as the corresponding DevExpress controls for the respective UI platforms:

DevExpress ASP.NET Core Blazor
DevExpress WinForms
DevExpress DevExtreme (DevExtreme UI controls are used in XAF ASP.NET Core Blazor UI.)

XAF includes its own UI components and elements. As of v24.1, XAF Blazor UI components have been assessed for accessibility conformance and updated to meet additional accessibility criteria (see Accessibility in XAF UI for ASP.NET Core Blazor).

Accessibility assessments and enhancements for WinForms UI components are scheduled for 2024.

Accessibility Standards and Guidelines

Many XAF Blazor UI components comply with WCAG 2.2 (Level AA), Section 508, and EN 301 549 standards. To learn more about how XAF Blazor UI components satisfy these requirements, refer to the DevExpress Accessibility Conformance Report (ACR).

Download: DevExpress XAF for ASP.NET Core Blazor ACR v24.1(based on VPAT®)

Accessibility in XAF UI for ASP.NET Core Blazor

Accessibility Conformance of Underlying UI Libraries

XAF UI for ASP.NET Core Blazor is built on top of Blazor-compatible DevExpress UI libraries. For information on compatibility conformance in these libraries, refer to their respective documentation sections:

Blazor Components - Accessibility
DevExpress DevExtreme - Accessibility (DevExtreme UI controls are used in XAF ASP.NET Core Blazor UI.)
Accessibility in Reporting for Web

Accessibility Conformance of XAF-Specific Features and Components

The table below lists XAF-specific features and components, along with their accessibility conformance status.

✅ - The feature or component fully conforms to related accessibility requirements.

⚠️ - The feature or component partially conforms to related accessibility requirements (exceptions are listed).

Feature / Component

Accessibility Support

Comments

| | --- | --- | --- | |

Header Buttons

✅

All buttons displayed in the page header have localizable labels and tooltips; buttons use focus frames that look consistent with the rest of the UI.

| |

Image Editor

⚠️

The Image Editor component supports accessibility on the following levels:

The displayed image has alternative text.
The editor’s “Change Image” button has a title and tooltip detectable by assistive technology.
The editor supports keyboard navigation with some exceptions (see the Keyboard Navigation section below).

| |

Keyboard Navigation

⚠️

XAF Blazor UI supports keyboard navigation with the following exceptions:

The Detail View layout customization window does not support keyboard navigation.
The Image Editor component loses focus after the displayed image is modified or removed.
It is impossible to focus and press the Customize button in the grid column chooser using a keyboard interface.
The vertical splitter displayed in master-detail mode cannot be operated (moved to the right or left) using a keyboard.

| |

Navigation

✅

The navigation pane fully supports keyboard navigation and assistive technology.

| |

Page Markup

✅

The main page markup includes the global lang attribute. The page title reflects the purpose of the active view. The page contains an initially hidden “Skip to main content” link, which is the first to be focused when a user presses the ‘Tab’ key.

| |

Popups

✅

Popups support keyboard navigation and assistive technology. Popups can be closed by the ‘Esc’ key press.

| |

Property Editors

✅

ARIA labels for property editors correctly reflect validation statuses and error messages.

| |

Settings Menu

✅

The “Settings” Menu supports accessibility on the following levels:

Each <nav> element in the menu’s layout has a label.
The Settings menu obtains a visibility: hidden style when collapsed to avoid unnecessary focusing.
The Settings menu can be closed by the ‘Esc’ key press.