Stéphane Deschamps @accessiblestef@framapiaf.org

Was working in dozen-screen SPA this morning, shifted in seat, accidentially two-finger swiped right, which triggers ’Back’ in Chrome. Lost all my work because dev did not consider managing history object.

Quick note on CSS focus: I never understood the energy spent to remote it all the time. It is as important as your cursor.
Wanna be an OK human being? Next release please restore it & make the Web a better place than it was before #accessibility #abstractionscon @abstractionscon@twitter.com

How #accessibility trees inform assistive tech // #a11y #HTML #CSS #JS https://hacks.mozilla.org/2019/06/how-accessibility-trees-inform-assistive-tech/

RT @hannahwarmbier@twitter.com
With the recent trend/return to static sites, I'm noticing a lot of people are not including RSS feeds. Please, if you post articles regularly or have anything resembling a blog, provide a feed. Yes, RSS is *still* a thing!

In short, add-on accessibility is always worse (technically, in effort, in cost, in user experience) than just building it correctly from the start.

#accessibiity #content
"Accessibility Strategies for Your Content Team" read this, share it with anyone who need to put content in a site at some point, we need to educate our content writers about simple heading semantics, alt texts, etc! https://www.deque.com/blog/accessibility-strategies-for-your-content-team/

RT @knowbility@twitter.com
Happy Monday everyone. A good exploration of accessibility issues of tooltips from @codingchaos@twitter.com . Enjoy! #a11y https://sarahmhigley.com/writing/tooltips-in-wcag-21/

Last year at at Mozilla Hackathon I volunteered to tackle tool-tips. After an intervention I gave up. Sarah nicely summarizes why tool-tips are such a mess.

---
RT @codingchaos@twitter.com
Tooltips: a study in why something so basic is also somehow so difficult.

(I'm trying out this whole blog thing, I hope it goes well!)

https://sarahmhigley.com/writing/tooltips-in-wcag-21/
https://twitter.com/codingchaos/status/1163177492414287872

Using Progressive Enhancement to Design for Accessibility, interesting article even if it's quite hard on designers https://www.sitepen.com/blog/using-progressive-enhancement-to-design-for-accessibility/

I failed to include the W3C Custom Control Accessible Development Checklist (https://w3c.github.io/using-aria/#checklist) in my post from last night (http://adrianroselli.com/2019/08/basic-custom-control-requirements.html) though it is shared on http://DoesMySiteDeserveRecognition.com.

RT @aardrian@twitter.com
Every day I work with teams building custom widgets. They almost always fail to spec them well. An effort: http://adrianroselli.com/2019/08/basic-custom-control-requirements.html

Hey and welcome to all #mastoart #artist newbies! I hope you find your way around mastodon and the fediverse, feel free to ask any questions that arise!

Here's a general hint to get started: We value #accessibility very much over here, so please make sure to add image descriptions as well as content warnings to your #art where applicable. A lot of people only boost ("RT") images with descriptions, so this will likely increase your reach!

Thanks and happy artsing!

I think all bikes and scooters need a qr code/number so that the companies can be informed centrally and punish/charge their customers for behavior like this. Otherwise they will never learn to park their bikes/scooters properly.
---
RT @OnALighter_Note@twitter.com
I'm a wheelchair user and I'm so fucking tired of people leaving these bikes and scooters wherever they want. For able bodied folx it's an inconvenience but for me it me…
https://twitter.com/OnALighter_Note/status/1156340116446687234

* bump *

---
RT @webaim@twitter.com
New WebAIM Screen Reader User Survey #8 is now available - https://webaim.org/projects/screenreadersurvey8/ If you use a screen reader, please complete and share. Your responses provide valuable data and promote better accessibility.
https://twitter.com/webaim/status/1156218119523688449