1. Introduction

This accessibility statement applies to our deployment of the Pouta web interface. We are committed to providing a digital service that is accessible and usable for as many people as possible, including users with disabilities. Our assessment is based on automated accessibility testing carried out using axe DevTools on 10 March 2026, supplemented by known upstream accessibility constraints documented for Horizon.

2. Compliance Status

The Horizon dashboard is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. This means that some elements of the interface meet accessibility standards, but there are significant areas that do not yet achieve full compliance.

3. Non-Accessible Content

3.1 Current Accessibility Issues Identified

A. Form Fields Without Accessible Labels

Several input fields including date range selectors and table filter fields are missing visible or programmatic labels. These fields lack <label> elements, aria-label, or aria-labelled by attributes. This makes them inaccessible for screen-reader users and others relying on assistive technology. (WCAG 1.3.1, 4.1.2)

B. Buttons Without Discernible Text or Accessible Names

Multiple button controls across the interface, particularly in table action columns and transfer lists, contain only icons and provide no accessible name. These controls lack visible text, aria-label, or a descriptive title. This prevents assistive technologies from communicating the purpose of these buttons. (WCAG 4.1.2)

C. Invalid or Disallowed ARIA Attributes

Some interactive elements include ARIA attributes such as aria-expanded that are not permitted for the element’s role or are missing required roles. These issues occur in:

• Magic Search components
• Collapsible sidebar navigation
• Transfer table filters

Such incorrect ARIA usage may cause misleading or inconsistent announcements in assistive technologies. (WCAG 4.1.2)

3.2 Disproportionate Burden

Because OpenStack is a large open-source project actively evolving across many upstream contributors, some accessibility issues cannot be immediately resolved. We continuously monitor upstream fixes and apply local improvements where feasible.

4. Measures Taken to Improve Accessibility

We are actively working to improve accessibility by:

• Applying local UI enhancements where technically feasible.
• Tracking accessibility issues in future OpenStack releases.