Key highlights from the WebAIM Million 2023 report show that of the 1 million home pages tested, 96.3% of home pages had detected WCAG failures. We should be ashamed of ourselves.
Mal ehrlich, über #WCAG hatte ich mich noch zu wenig auseinandergesetzt aber auch grosse #WebDev so wie #WebDesign Firmen setzten dies selten um. Ich sehe sehr selten Seiten im #Web, die dies in ihrem #Design berücksichtigen oder täusche ich mich?
Klar es benötigt ua einen gewissen Aufwand aber evt kann mensch es kaum logisch verrechnen, wie von #Kunden erwünscht nehme ich mal an.
SC 2.4.6 Headings and Labels (Level AA) does not require headings or labels. It just requires that headings and labels that are present describe the content.
This catches so many testers off-guard, and the Understanding’s “in brief” section does also a bad job of clarifying this.
How do you get people to sign up for paid stuff on your site? You write a so called simplified version of the Web Content Accessibility Guidelines (WCAG), which at best is so simplistic it misses out crucial information, to worst being completely wrong. And say it’s FREE. #wcag#accessibility
The Web Content Accessibility Guidelines (WCAG) officially evolved from 2.1 to 2.2 late last year, introducing crucial updates and nine new success criteria.
We run instructor-led training tailored for teams of all sizes and backgrounds to help your organisation integrate these updates into your workflow:
a timely reminder to put things into context: annoyed that a particular #WCAG success criterion, glossary definition, technique etc doesn't cover your specific situation you're facing? keep in mind that the majority of WCAG 2.x was written almost 25 years ago (!)
you're trying to apply thinking and rules to your work today that were dreamt up a quarter of a century ago...
"It is important to make users aware of required fields upfront. This should prevent them from making submission errors and having to backtrack through a form to fix such errors. But what is the best and most accessible way to indicate required fields? This article aims to explain exactly what’s required."
Here's a question for my web accessibility folks: are label elements without associated controls harmful? Say they're paired with static content (text in a div). Should the static content have an aria-labeledby attribute or just leave it be?
"California is considering adopting a new law (AB-1757) that adopts Web Content Accessibility Guidelines (WCAG) 2.1 level AA ...it also expands liability to third-party developers and gives people with disabilities and businesses the ability to sue web developers for creating websites that do not conform"
In WCAG 2.2, I found a term "encloses" in Glossary section, with no links from anywhere in WCAG success criteria. I wonder what does this term means. The description only says "solidly bounds or surrounds".
Anyway, the #WAI understanding conformance page has links to fragment identifiers that do not exist because those parts are copied and pasted (but maybe a technology with a fancier name than that was relied upon) verbatim from the #WCAG recommendation.
Hire fucking #actuallyAutistic people to do your fucking proofreading.
We really need to do away with this type of authentication.
The tests are often ambiguous. More importantly, they don’t meet accessibility requirements noted in WCAG 2.2. Specifically section 3.3.8 on “cognitive function tests”: