"We are a small team of 3 devs, we don't have time for accessibility" is the same as "we are a small team of 3 devs, we don't have time for CSS."
Accessibility in practice is literally just:
1. Knowledge
2. Techniques
Anyone who does it knows that it is just part of the job.
Accessibility in practice is literally just:
1. Knowledge
2. Techniques
Anyone who does it knows that it is just part of the job.
Standards for accessibility exist! Techniques, suggestions, and examples exist!
Learning it is the same as any other job.
Buying a house that wasn't built to standard code is a huge liability. But the standards exist for a reason. Same with software.
Use standards!
Learning it is the same as any other job.
Buying a house that wasn't built to standard code is a huge liability. But the standards exist for a reason. Same with software.
Use standards!
My field (data visualization) is especially bloated by wild DIY stuff. We celebrate it, in fact.
A consistent experience between two bar charts is unheard of!
But buttons and other UI components have standards that make consistent experience across environments and authors.
A consistent experience between two bar charts is unheard of!
But buttons and other UI components have standards that make consistent experience across environments and authors.
It's time for our field to grow up and work towards collective standards of access.
Now that I can announce it, just here to say that our team for our chart library IS 3 dedicated devs (manager not included). This work is possible if companies hire with this in mind.
https://twitter.com/FrankElavsky/status/1397222372764229641?s=20
• • •
Missing some Tweet in this thread? You can try to
force a refresh
