We want the suggestions and we want the pain points. Whatever feedback that folks want to share, we want to know what you think.Īnd this is only the start.
If you found something harder while recovering from a broken arm, we’d love to hear from you too. We’re not prioritizing folks with any particular type of disability, so if you identify as neurodiverse, we’d love to hear from you. We want to spend more time talking with folks who have disabilities. The only way we’re going to find the next round of features is through engagement with our community. Visual Studio shouldn’t merely “work” with a screen reader, but it should deliver an experience that feels fluid and natural. We want to find the features and innovations that help our users do the most amazing things they can. Today, my day-to-day is less about compliance issues and more about wanting to move beyond “good enough”. Inclusive design makes Visual Studio an amazing product for all users. I’m very proud of the work we’ve done, but I also know that there’s more we can do. The magnitude of the work it would mean for us as well as the impact of what that would mean has really helped many of us realize how important our mission of empowering everybody on the planet really is. From temporary disabilities, like an injury that will heal to neurodiversity, the idea of inclusive design is a great deal more than I had any idea of. In all honesty, I hadn’t really thought about accessibility as more than keyboard and screen reader, but we’ve come to learn that it’s a lot more than that. When I started leading the drive for accessibility in Visual Studio five years ago, I really didn’t understand the magnitude of what that meant.
0 kommentar(er)
