Accessibility with Canvas Apps

[Hjaf]

Ensure that the documentation encourage and enable citizen developers to follow company requirements for accessibility.

• EDS Custom components should continue to produce accessibility warnings in power apps studio when company requirements are not met.

• EDS Template documentation should highlight accessibility requirements and how to fulfill them, especially where power apps studio accessibility requirements are insufficient or incompatible with company requirements.

• [ ] Review how Power Apps studio produce accessibility warnings and identify incompatibilities or insufficiencies with company requirements.

• [ ] Review template and components to limit caveats and ensure they do not resolve issues regarding accessibility with re-use by citizen developers.

[Hjaf]

The convention citizen developers use for naming the screens in canvas apps is important because this name is used by screen readers. This is not so obvious perhaps one of many examples of how accessibility is handled in power apps studio.

Documentation on screen naming and screen reader support