View profile

Internal tools, sites, and accessibility

Internal tools, sites, and accessibility
By Duncan Mackenzie • Issue #4 • View online
One reoccurring problem I see within companies is how internal tools are handled. Often, they aren’t treated like production systems, when in fact, they are.
This means they should be given the same level of attention around planning, security, accessibility, documentation and more.
If a system is being used to do work, then it is a production system and should be managed as such.

There's no such thing as a website or web app that doesn't need to be accessible
Maddie @ 🏠
Making a web-application accessible is not a matter of cost and should not be discussed with customers.

If you say, you're doing a good job and you're not doing the bare minimum for accessibility, you're a bad web dev.

There, I said it
The web performance of internal systems is important, so optimise them too
More on Accessibility
Legibility in User Interfaces
The Mobile Performance Inequality Gap
Stark’s Public Library of Accessibility Resources
Did you enjoy this issue?
Duncan Mackenzie

In each newsletter, I'll share a set of links related to web development and software engineering. As the editor, my opinions are going to influence the topics and tone of this material, so expect to see lots of information on web performance and general topics around working in a software engineering team! Check it out and let me know what you think at

In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue