Accessibility limitations in canvas apps

You can design and build accessible canvas apps with built-in controls. Sometimes, the combination of app design, use of various controls, and the configured control properties may result in an app to have an inaccessible user interface.

In this article, you'll learn about these accessibility limitations in canvas apps, and how can you improve the app interface to make it more accessible.

Dialogs and overlays

Dialogs and user interfaces that appear on top of other content are not supported. These overlays require focus management, hiding background content from screen readers, and appropriate control roles.

Consider the following:

Tabbed interfaces

A tabbed interface is made up of a list of tabs and a panel that shows content associated with the selected tab.

The only built-in control that supports tabbed interfaces is the Tab list. Avoid using Galleries to create tabs. The list of tabs should be navigable with arrow keys. Appropriate control roles and states are required.

Consider the following:

Custom tables

The only built-in control that supports two-dimensional data is the Data Table. Avoid using Galleries to present data in rows and columns. Rows and columns have to be annotated so that screen reader users can understand their structure and navigate cells.

Consider the following:

Custom combo boxes

It is possible to emulate a combo box by combining a Text Input and a Gallery. However, combo boxes assembled from built-in controls are not accessible. Combo boxes must handle arrow keys and set appropriate roles and states on its components.

Consider the following:

Scrollable content

Keyboard users can't scroll Forms, Scrollable screens, and Containers if there are no interactive controls inside them.

For Galleries with no interactive content, you can set TabIndex on the Gallery itself so that keyboard users can focus on it and use arrow keys to scroll it.

For Labels, setting TabIndex will make them focusable for keyboard scrolling. However, it will also turn them into buttons. Don't making labels scrollable if they're not meant to be buttons. Ensure the Label is large enough to fit text. The AutoHeight property can be used to automatically adjust the control's size when it is inside a Form, Scrollable screen, or Gallery.

Expandable sections

Expandable sections, also known as disclosures, contain content that is hidden until the user presses a button. There is no built-in support for these elements but there is a workaround.

Mention the expanded state in the AccessibleLabel of the button. For example, “Show more details. Collapsed.”.

Update the AccessibleLabel when the expanded state changes. Position the expanded content immediately after the button so that screen reader users can logically navigate to it. Push other content down when the section expands.


You can create headings with Label controls. Navigation, banner, and other landmarks are not supported. Power Apps automatically sets the main landmark to the app screen.

For other landmarks, use a heading as a workaround.

Custom roles and states

There is no built-in support for custom roles and states. Hence, it's not recommended to create composite check boxes, sliders, and toggles from built-in controls.

Consider the following:

Custom keyboard handling

It is not possible to react to specific key presses. For example, you can't have custom behavior for arrow keys or the Escape key. Hence, it is not possible to compose list-like controls like radio buttons from built-in controls. Nor can you create overlays that can be dismissed with the Escape key.

Enter or Space key handling is supported with OnSelect. However, this property is also triggered by other input methods like mouse clicks. There is no way to distinguish the source of the event.

Focus management

SetFocus function can be used to change focus but it only works in limited scenarios.

It is not possible to detect when controls receive or lose focus.

Hide content from screen reader users only

There is no aria-hidden equivalent to show content to sighted users but hide it for screen reader users. Only a few scenarios are supported.

Next steps

Accessibility properties

See also