Search

Items tagged with: WCAG


Great talk by @mrchrisadams at @fosdem this year. Loved how he explored #WCAG's #POUR in the context of older devices. Not everyone can update their devices every 2 years, but absolutely nobody should!

#FOSDEM #A11y #WSG #WCAG




Beware of AI Accessibility Promises: US Federal Agency Fines an Overlay Company One Million Dollars

Public can submit comments until February 5th in case against AccessiBe for misleading advertising

lflegal.com/2025/01/ftc-access…

by @LFLegal
#accessibility #a11y #wcag #accessiBe #accessiBeNot #ftc



FTC Order Requires accessiBe to Pay $1 Million for Deceptive Claims that its AI Product Could Make Websites Compliant with Accessibility Guidelines

ftc.gov/news-events/news/press…

#law #a11y #wcag #accessiBe #accessiBeNot #ftc







👉 Success Criterion Applying SC 2.4.2 Page Titled to Non-Web Documents and Software

🤔 Should SC 2.4.2 Page Titled be applied to individual screens of an app 🤔

#WCAG #apps #accessibility

github.com/w3c/wcag2ict/issues…




Happy 25 years of WCAG!

On this day in 1999, the Web Content Accessibility Guidelines 1.0 were published. WCAG 2.2 is still one of the most important standards on the web, ensuring a base level of access for everyone.

1.0 – May 5, 1999 w3.org/TR/WCAG10/
2.0 – Dec 11, 2008 w3.org/TR/WCAG20/
2.1 – Jun 5, 2018 w3.org/TR/WCAG21/
2.2 – Oct 5, 2023 w3.org/TR/WCAG22/

#wcag #a11y #accessibility











WCAG 2.2 removed SC 4.1.1, Parsing (Level A). I maintain that valid markup has important benefits despite no longer being required. We may find it possible to write good software without static analysis, construct a building without blueprints, or make an accessible website without validation. They remain good practices.

WCAG’s normative text describes outcomes, not how to achieve them. Validation is but one part of the process of achieving the necessary outcomes.

Let’s not interpret the removal of SC 4.1.1 as permission to ship known errors.


Originally posted on seirdy.one/notes/2023/10/06/wc… (POSSE). #accessibility #WCAG


WCAG 2.2 is now published as a Web Standard (“W3C Recommendation”)!

For an introduction to WCAG and a link to WCAG 2.2, see the WCAG 2 Overview
w3.org/WAI/standards-guideline…

There are a few updates in the WCAG 2 FAQ
w3.org/WAI/standards-guideline…

See new "In briefs" in
What's New in WCAG 2.2

w3.org/WAI/standards-guideline…

#WCAG #WCAG2 #a11y


.@w3c WCAG should not be developed/designed for the benefit of #accessibility testing vendors. It is there to improve the user experience of disabled people.

#web #a11y #politics #WCAG