The state of web accessibility is pretty depressing.

- Standards have been around 20+ years, but 97% of the top 1mil sites fail to meet them.
- Standards are hard to learn but automating accessibility is terrible and makes it worse.
- Standards are still the bare minimum. (cont)
- Standards are the best way to make consistent experiences but this makes non-standard or novel experiences even harder to design for.
- We still largely have a "market driven" approach to accessibility, which means justifying human rights in terms of a business case.
- Veteran folks burn out all the time and new folks have a pretty hard time getting started.
- The veterans who don't burn out are often pretty grumpy and are not kind when they spot the same mistakes happening they've been seeing for 20+ years.
- Accessibility specialization can HURT your pay (Consultant a11y engineer/analyst: 100/hr. Consultant engineer with a different, deep specialty: 200-300/hr).
- Accessibility isn't woven into jobs and therefore the work is often on a contract basis.
- Browsers don't strictly enforce valid semantics
- HTML/JavaScript doesn't require accessible patterns or defaults
- Laws don't strictly enforce standards
- Guidelines have to be discovered and implemented by one's own initiative
- Litigation is slow and favors those in power
- Self-advocacy becomes an exhausting chore with folks often going unheard and given little agency
- Community members making the technology around them (such as open-source projects) more accessible without compensation isn't sustainable
- New tools coming out every day which make it even easier to make new things faster... massively increasing the problem of scale without addressing the decades old accessibility issues that still exist
- Older tools relying on voting, grants, and volunteers to fix issues
Anyway. I'm tired but still here. I hope y'all are too. We certainly need you.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Frank ⌁

Frank ⌁ Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @FrankElavsky

24 May
Okay, gonna start a thread where I compare "cool concept stairs"/DIY stair fails to data visualization.

You make fancy custom charts? Guess what? They are probably an accessibility liability. Use standards.

See Fig. A (the alt on each image will be a bonus roast explanation): A set of stairs where each step is a glowing, translucent, g
If you're using a low contrast/minimalist design, many users won't be able to see what is important! There is a minimum ink you should use in your data to ink ratio:

4.5:1 contrast ratio for text and 3:1 contrast ratio for geometries (non-text). A stairway with a carpet pattern similar to white noise. It
Speaking of contrast, make important elements even higher contrast. Create a hierarchy using size, boldness, or color contrast to guide the user through each step in your graphic.

Test and validate the whole graphic and all its little components work in harmony. A stairway with a carpet pattern that not only makes each st
Read 8 tweets
24 May
"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.
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!
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.
Read 5 tweets
5 May
Exhausting. While this might be a cause for celebration for some, my preliminary audit shows that this is yet again another tool for easily creating inaccessible data experiences.

No SR or keyboard access, no semantic control of marks or their relationship to one another, etc
As just naked DOM stuff, this means that yet again the onus is not on the creator of the library but the consumer to do accessibility. Why do we continue to make it easy to make inaccessible things?

Disappointed because this solves technical barriers for some, but produces many.
Why do big names/groups/companies in this space continue to innovate exclusionary tools, libraries, and resources?

These fast and easy solutions create more accessibility problems than they solve. We are long overdue for accessibility and inclusion in the wide field of data.
Read 15 tweets
4 May
Oh you're a "small team" with "limited resources" that "can't afford accessibility?"

Well at least 25% of people have some form of disability. So at least 25% of any team OR solo dev should have accessibility expertise.

If not, the problem isn't team size but hiring priorities.
Even teams of only ONE person should devote 25% of your time to this LEGALLY REQUIRED activity.

If you're not building something to be accessible, you are cutting corners and building garbage.
If you have shipped an MVP (minimum viable product) that isn't accessible, I have bad news:

It *isn't* minimally viable.

You've been shipping deficient prototypes and still do.
Read 4 tweets
3 May
After hearing I do accessibility in data science, it is always weird when a researcher or data practitioner says, "how interesting, very cool work."

As if human rights is some kind of curious little subject they hadn't considered? This is projected by law?? They need to do it??
Designers and web engineers tend to know this is important, so the comments are rarely off-putting after I give a talk. They usually attend because they need the skills.

From them I often get, "wow, this is exactly what I was looking for and knew I needed! Thank you!"
But many academics and analysts are so used to compartmentalizing info and literally deleting human consideration from their work that they do not know they are neglecting significant legal precedence.

"Oh how curious that someone would need this 'access' you speak of. Strange!"
Read 6 tweets
21 Mar
Unlearning ableism also includes unlearning self-deprecation.

I used to really loathe myself, but trying to come up with words and terms that weren't ableist made me realize that I actually did not know myself very well at all.
I would catch myself wanting to insult myself after a mistake. The only reasonable thing I could replace an ableist slur with was the truth (which is frustratingly unsatisfying).
*ableist slur towards myself*

Which was replaced by

"I hate myself for messing up because I am not good enough" (still ableist)

Then replaced by

"I am mad at myself for making a mistake and I don't like how it feels to make mistakes" (still not good)

Then

"That felt bad"
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(