Post

Power Apps accessible forms: structure, labels and tests for keyboard and screen-reader users

Diesen Beitrag auf Deutsch lesen

How to structure Power Apps canvas forms for keyboard and screen-reader users: logical tab order, clear AccessibleLabel values, visible focus, specific errors and real testing.

TL;DR

Accessible Power Apps canvas forms need a logical field order, a clear AccessibleLabel on every input and a visible focus indicator. Keep decorative controls out of the tab sequence, pair color cues with text, make validation errors specific, and verify with the Accessibility checker, keyboard-only testing and screen readers such as Narrator with Edge or NVDA.

Original by Softchief, on Softchief Blog. Read the original

This is our own summary, not a republication or full translation.

Governance takeaway

  • Makers: Set a meaningful AccessibleLabel on every input, keep decorative controls out of the tab sequence and run the Accessibility checker before treating the form as done.
  • Admins/CoE: Add keyboard-only runs and screen-reader tests, such as Narrator with Edge or NVDA with Chrome, to your app review checklist so gaps surface before release.
  • Security/Compliance: Require text cues for required fields, visible focus and specific error messages, because color or icons alone exclude keyboard and screen-reader users.

Frequently asked questions

How do I set the AccessibleLabel property in Power Apps canvas apps?

Describe each input's purpose in the AccessibleLabel property, for example work email address instead of enter here, then check what the screen reader announces in the running app.

Which screen readers does Microsoft verify for canvas apps?

Narrator with Microsoft Edge and NVDA with Chrome or Firefox are among the verified combinations for canvas apps; test with the tools your audience uses.

What does the Power Apps Accessibility checker flag in canvas forms?

It flags missing labels, hidden or zero-thickness focus borders and screen names that need more meaning; treat the results as a starting point, not a guarantee.

Summary by KMUpower, licensed under CC BY 4.0 . Rights to the original article remain with its author.

Privacy Policy · Legal notice

Microsoft and the Power Platform product names (for example Power Apps, Power Automate, Copilot Studio) are trademarks of the Microsoft group of companies. This is an independent website. It is not operated, sponsored or endorsed by Microsoft.