Search results

Craig Abbott @craigabbott@a11y.info
Public

Finally hit publish on a blog post I've been writing for a while.

It's common to hear the term "fully accessible" used to describe products which have passed WCAG 2.2 level AA. But, are they really?

In this post, I explore 5 examples which highlight why WCAG, as awesome as it is, is not a measure of great usability or performance.

craigabbott.co.uk/blog/2025/5-

Craig Abbott presenting at a conference

5 reasons why WCAG AA compliance does not mean your website is accessible

5 reasons why WCAG compliance does not mean accessible accessible

craigabbott.co.uk · craigabbott.co.uk

0
0
0
Steve Faulkner @SteveFaulkner@mastodon.social
Public

👀 @w3cWorld Wide Web Consortium WAI invites you to comment on the updated:
W3C Accessibility Guidelines (WCAG) 3.0 Working Draft

w3.org/TR/wcag-3.0/

W3C Accessibility Guidelines (WCAG) 3.0

W3C Accessibility Guidelines (WCAG) 3.0 will provide a wide range of recommendations for making web content more accessible to users with disabilities. Following these guidelines will address many of the needs of users with blindness, low vision and other vision impairments; deafness and hearing loss; limited movement and dexterity; speech disabilities; sensory disorders; cognitive and learning disabilities; and combinations of any of these disabilities. These guidelines address the accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other Web of Things devices. The guidelines apply to various types of web content, including static, dynamic, interactive, and streaming content; audiovisual media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

www.w3.org

0
0
0
Hyunjin Cho @resistan@hackers.pub
Public

WCAG 3.0 WD가 나왔다니..

https://www.w3.org/TR/2024/WD-wcag-3.0-20241212/

W3C Accessibility Guidelines (WCAG) 3.0

W3C Accessibility Guidelines (WCAG) 3.0 will provide a wide range of recommendations for making web content more accessible to users with disabilities. Following these guidelines will address many of the needs of users with blindness, low vision and other vision impairments; deafness and hearing loss; limited movement and dexterity; speech disabilities; sensory disorders; cognitive and learning disabilities; and combinations of any of these disabilities. These guidelines address the accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other Web of Things devices. The guidelines apply to various types of web content, including static, dynamic, interactive, and streaming content; audiovisual media; virtual and augmented reality; and alternative access presentation and control. These guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.

www.w3.org

0
0
0
0
0
0
Patrick H. Lauke @patrick_h_lauke@mastodon.social
Public

not going to lie, one of the worst side effects of has been the obsession with reading the tea leaves of what a particular SC means (many of these written almost 20 years ago), which SC to fail things under, and generally an obsession (from industry/product owners) to satisfy WCAG ... rather than focusing on actual (which often goes beyond WCAG, or involves things that simply fall between SCs, or are just "best practice" rather than hard fails). but it is what it is...

0
0
0
Access42 @access42@social.a11y.fr
Public

Bonjour ! 🖖 Nous sommes Access42, une coopérative (Scop) française spécialisée en accessibilité numérique. L’équipe compte une vingtaine de personnes, dont la plupart télétravaillent à 100 %.

Nous proposons de l’audit, du conseil et de la formation en accessibilité numérique. access42.net/services

Nous publions chaque mois des articles de blog sur l’accessibilité : access42.net/blog

0
0
0