Accessibility

Making a UI usable with a screen reader, with a keyboard alone and without seeing the layout: accessible names on controls, a heading order, landmarks, focus handling and announcements. Target size for a finger is touch operation.

Overview

SAP SHIPS
Freestyle →

@openui5/sap.ui.core The OpenUI5 core: the module loader, the MVC runtime, data binding, routing, theming and the test stack, which is everything a UI5 app does before a single community package is added.

Not covered: At the single control. SAP's documentation places labels, titles, heading levels and landmarks with the app that combines the controls, because they depend on the app's context.

The one repository answering this in the batch is a UI5con 2026 hands-on from SAP-samples, which demonstrates rather than provides, so core-only reads what the framework ships. UI5 Web Components agent skills carry accessibility guidance for agents and are placed under agent guidance, not here.

THE COMMUNITY ADDS

UI5X adds composite controls of its own that state the same contracts for what they render: aria-busy on loading containers, skeleton content kept out of the accessibility tree, and animation stopped when the system asks for reduced motion.

Artifacts2

2 of 2 artifacts
ArtifactSignals
Packages2
@openui5/sap.ui.coreFramework core: module loader, MVC runtime, binding, routing, theming
Signals
none
UI5XUI5 library of eight composite controls under the ui5x namespace
Signals
Functional boundary

Seen working1

ArtifactSignals
Samples1
ui5con-2026-a11y-hands-onUI5con 2026 workshop fixing accessibility defects in a UI5 app
none

Details

Coverage
statecore and community, UI5
assessed
relationshipunassessed
For your agent
Ref
capability:accessibility
JSON
/capabilities/accessibility.json
MCP
Connecting an agent