Accessibility in Dynamics 365 products
Typically, project requirements are full of feature requests, some screen layouts, and occasional performance metrics to strive toward. However, requirements for accessibility aren't often included in the project scope. Even if the expected users don't request accommodation, it's important to incorporate accessible features as often as possible. For example, following color contrast ratio guidelines can make the difference between a user needing an adaptive device to do their job or not needing the device. A team member might need accommodation but be reluctant to request it. Conversely, a new team member might join who needs accommodation and the system doesn't support it.
With a highly customizable platform, such as Microsoft Dynamics 365, consultants need to be mindful of not removing accessible features as they customize and build business applications. As you build business applications, keep in mind the following considerations:
As you add elements, such as new columns of data to forms and views to your Dynamics 365 apps, continue using tool tips as provided.
Test with accessibility in mind by using no mouse/tabbing through the screens and screen readers to understand how the end user hears their experience.
When adding custom theming or custom apps from Microsoft Power Apps, be aware of color standards and ratios.
Visual elements are easier to see with borders around them.
Don't crowd screens with too many elements. It might be better to add another screen or scroll to the next page to make visual separation of elements easier to see.
Include icons with text labels where you can.
Review industry standards regularly to ensure that the user experience remains accessible.