It’s a huge issue that many industries (including my own) built communities in these closed walled gardens. Twitter will change extremely, and small communities will lose out because there isn’t enough value for Twitter. What happens when accounts like…
… the one from @UncannyMagazine are restricted in who they can reach until they pay? Or when every conversion on Kickstarter needs to pay 20% to Twitter because the transaction is WeChat style happening in Twitter.
The economical Damocles’ sword hanging over a lot of communities is real. And no matter how well Twitter has worked for you, the chances that it keeps working are much lower than two weeks ago.
I hope Uncanny makes it, through whatever comes. I am supporting the Kickstarter every year despite almost never reading it (I’m a bad reader!) – but I know what it means to the people writing for it. Support indy publications!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Too bad that @AccessiBe’s overlay does not make this organization’s website accessible. Text with 1.31:1 contrast ratio (minimum for text this size/weight is 3:1) while having the “Vision Impaired Profile” switched on.
And if a person with low-vision is also using a screen reader, the “vision impaired profile” is switched off. You really have to decide to which bucket of disabled person you belong to.
And in this example, the “Vision Impaired Profile” does nothing to make the text that overlays the image more readable (which can be done, see Windows High Contrast Mode). It instead increases the photo’s saturation in a way that makes everyone look sunburned.
1. The Web Content Accessibility Guidelines are a Web Standard. 2. If you want to make websites you need to follow them as much as you follow other Standards like HTML or CSS. 3. They are an integral part of the Web.
I know “Guidelines” is a bit easy to misunderstand as non-binding, but it is not. The guidelines are in place to help you keep track but it also has Success Criteria that tells you exactly when you have left those guardrails and made something inaccessible.
WCAG has a double functionality:
1. It can guide you (as Design Principles) to an accessible, usable user experience and tells you what the minimum requirements are.
2. It can tell you when you have failed to provide accessibility.