E-mail List Archives
Re: Internal tool accessibility justifications
From: Tim Harshbarger
Date: Sep 25, 2017 6:36AM
- Next message: Bourne, Sarah (MASSIT): "Re: Boston Accessibility Conference October 2nd"
- Previous message: Maurice Peret: "Re: visually impaired front end developer"
- Next message in Thread: mhysnm1964@gmail.com: "Re: Internal tool accessibility justifications"
- Previous message in Thread: mhysnm1964@gmail.com: "Internal tool accessibility justifications"
- View all messages in this Thread
If your friend does some searches on the archive of this forum, they should find plenty of past discussions of this topic.
When it comes to technical benefits of accessibility, those are the same for both external and internal applications.
The business benefits mostly boil down to being that accessible applications make it possible for employees with disabilities to contribute to and participate in the organization fully.
I will add that I think it is a lot easier to create accessible applications than it is to purchase them. When your organization is designing and developing an application, you have the ability to introduce the level of accessibility you want at every step. With purchased products, you are at the mercy of what that company may or may not know about accessibility. Also, there really isn't any simple way to evaluate a product's accessibility claims.
- Next message: Bourne, Sarah (MASSIT): "Re: Boston Accessibility Conference October 2nd"
- Previous message: Maurice Peret: "Re: visually impaired front end developer"
- Next message in Thread: mhysnm1964@gmail.com: "Re: Internal tool accessibility justifications"
- Previous message in Thread: mhysnm1964@gmail.com: "Internal tool accessibility justifications"
- View all messages in this Thread