@Sirs0ri@corteximplant.comHey #webdev bubble - can any of y'all recommend resources to learn about accessibility?
I'm aware of the WCAG guidelines as the "golden standard", but I'm looking for something more bite sized / approachable than 75 pages of raw paragraphs and rules
Boosts welcome! 
W3C Editor's Draft 17 February 2025
for review/feedback
WCAG2Mobile, describes how WCAG 2.2 principles, guidelines, and success criteria can be applied to Mobile Applications
this video was going to be made public at some point ... but as this seems to have stalled (and there's really no financial incentive anymore that the conf can gain from keeping this 16 month old video under lock and key) ... here's the recording of my (then) updated talk "These (still) aren't the SCs you're looking for..." from 19 October 2023 / #a11yTO / Toronto https://www.youtube.com/watch?v=ADIgU53Y2Rg #a11y #wcag #barrierefreiheit #accessibility
A beginner-friendly accessibility check list for my new Gen-Z colleagues? An A4 printable PDF or the like would be great.
I need something to help them get started without the complete and somewhat intimidating WCAG recommendations website.
Reach out to me for advice and guidance on digital accessibility.
With over twenty years of experience in design and development, I am dedicated to improving user experiences for a diverse audience, particularly for individuals with disabilities.
Die Web Content Accessibility Guidelines 2.1 (WCAG) - der internationale Standard zur barrierefreien Gestaltung von Online-Angeboten - sind für öffentliche Stellen in Deutschland seit einigen Jahren rechtlich verbindlich. Es gibt aber bis heute keine offizielle deutschsprachige Fassung dieser Richtlinien.
Mit anderen Worten: Die Vorgaben zur Barrierefreiheit sind selbst nicht barrierefrei.
Please consider commenting to FTC about the case against AccessiBe for misleading advertising. Deadline Feb. 5.
One of the #Accessibility specialists at work shared this gem of an article with me, which I hadn't seen before:
It is not uncommon that I raise an accessibility or usability issue with a client’s design or implementation and am met with either “But #Google does this,” or “But #Apple does this.” Mostly it is the default response to any issue I raise, but it is far worse when it is a reaction to a genuine technical failure or problem real users have identified.
That response does not address the problem I may have raised. It avoids. It offloads responsibility. It declines to even try.
This is followed by a litany of #WCAG and other accessibility violations by the two behemoths.
https://adrianroselli.com/2020/03/i-dont-care-what-google-or-apple-or-whomever-did.html
If you use your voice to navigate websites, the @w3c Accessibility Conformance Testing (ACT) Rules Community Group and Task Force would like your help to test 27 different controls:
https://docs.google.com/forms/d/e/1FAIpQLSetBabmHgRYXFHxbUjPu3eVoHwwquy7FFI6wIRx0uOWLSPgQg/viewform
It'll help them understand which patterns work (and which don't) for #WCAG 2.5.3 Label in Name
Appreciating this mechanism for closing multiple status messages at once.
One of the methods of ensuring that toast messages (conform to Enough Time) is by making them visible until dismissed, this can result in multiple messages being present and users having to dismiss them individually. So not an example of conforming to WCAG 2.2 Guideline 2.2 Enough Time, but an example of a way to mitigate an unwanted side effect of conforming. 
WCAG’s A and AA distinction is mostly academic https://yatil.net/blog/wcags-a-and-aa-distinction-is-mostly-academic by @yatil #wcag #a11y
W3C Web Accessibility Initiative (WAI) invites you to review the draft French translation of Web Content Accessibility Guidelines (WCAG) 2.2:
Getting To The Bottom Of Minimum WCAG-Conformant Interactive Element Size
There are many rumors and misconceptions about conforming to WCAG criteria for the minimum sizing of interactive elements. I’d like to use this post to demystify what is needed for baseline compliance and to point out an approach for making successful and inclusive interactive experiences using ample target sizes.
Is orange the forbidden colour in accessibility? 
Stack Overflow made an exception during its accessibility-focused redesign and chose to measure #colour #contrast using the Accessible Perceptual Contrast Algorithm (#APCA). Although they initially considered the #WCAG colour contrast algorithm, they decided against it because it struggles to accurately assess colour contrast when using orange, which is a significant issue when orange is a brands primary colour.
"There does not appear to be any clear definition of what parameters a success criteria must meet in order to qualify for any particular conformance level."
I just stumbled across this blog post from 2019 about #colour #contrast in relation to the colour orange. In their case study, they found that white text on orange is mostly preferred over black text, despite this being a #WCAG violation.
What are your thoughts on this?
"Orange You Accessible? A Mini Case Study on Color Ratio" by Ericka O'Connor: https://www.bounteous.com/insights/2019/03/22/orange-you-accessible-mini-case-study-color-ratio/
I built a little #a11y link list for folks to use if they are interested in getting into #WebAccessibility. Education resources, #WCAG breakdowns, #Coding tutorials, people to follow, organizations and companies, all put together into one simple site. I made this for a talk I gave last night for #Blind and Low-vision people interested in breaking into this industry, and will continuously add more to it for my own continuum of knowledge and for everyone else. https://marconius.com/a11yLinks/
WebAIM’s interpretation of the difference between “change of context” and “change of content”:
https://webaim.org/blog/decoding-wcag-change-of-context/
Thanks David MacDonald, hope you are doing OK
#WCAG #accessibility #sharky #W3C
"Sharky raps at 250 words a minute
I'm a cool DJ, Sharky, WCAG. I like techno geek music. How's that David, am I a cool rapper now?
David: Sharky, I couldn't understand a word you said.
Sharky: Most of my blind friends understand everything when I speak at that speed
(slowly) Would you like me to speak really slow for you David?"
https://html5accessibility.com/stuff/2024/08/01/do-the-wcag/
of course, these musings are nothing new. if you've followed me, you probably know of my little "these aren't the SCs you're looking for..." talk. i'm actually really happy about the last iteration of this presentation at last year's #a11yTO conference...which is why it really shits me that that conf decided NOT to release the video recordings of the talks publicly, and seem to have no intention to in future... but at least my slides are here https://patrickhlauke.github.io/wcag-interpretation/ #a11y #wcag #accessibility
