Accessibility (A11Y) is an essential part of creating apps and web pages, and not one that should be left up to chance or post-development. Let's dive into what it takes to create accessible apps in the .NET ecosystem.

But first, you should be aware of what it means to achieve accessibility, and a good reference is here.

In short, A11y is the study of improving how disabled persons access or benefit from a site, system, or app.

Also, if you are creating apps for the Government sector, A11y is non-optional, as per an update to US and other governments' laws around 2018. (You can read about the US version of the law here: https://www.hhs.gov/web/section-508/index.html)

A bit first step toward A11y can be achieved by making your app or site mobile-friendly. Congratulations! Most modern UI frameworks do this work for you. Just verify that your app works great on mobile screens.

To get to the next step, you should use the Web Accessibility Checker to look for issues in your site automatically, or if you're developing an app, use the [LINK=
https://devblogs.microsoft.com/visualstudio/developing-accessible-apps-with-visual-studio/
]Accessibility Checker for XAML-based apps.

Want to go further? The W3 maintains a list of tools that can check for A11y violations here: https://www.w3.org/WAI/ER/tools/

Happy accessibilitizing!