Open position! #W3C#WAI is seeking a full-time Accessibility Specialist to work on digital accessibility standards and supporting materials. This is a unique opportunity to contribute to the vision of an accessible digital future.
I'm hosting a meetup of frontend webdevelopers in my company (8 teams, 20-25 ppl). We've been working with #WCAG & accessibility this year. Very old & new applications, so the challenges are diverse.
i'm hoping to find a blind / visually impaired person who could talk (30min?) about what it's like to use the web.
No complicated tech, just how it works, & how you experience it.
.@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.
An attempt to make the process of checking 2.5.8 Target Size (Minimum) as painless and swift as is possible.
👉🏽 Check it out, tear it apart, call me a no good punk, pour scorn, make it better, even better; make something else that works better! AND share it publicly without a restrictive licence
Open position! #W3C#WAI is seeking a full-time #Accessibility Specialist to work on digital accessibility standards and supporting materials. This is a unique opportunity to contribute to the vision of an accessible digital future.
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.
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...
#a11y question: For this new #Mastadon#WordPress plugin I am working on that displays your Mastodon feed , would you like all the posts as headings or just a list? #accessibility#WCAG
Orange est une entreprise tellement fière de faire des sites inaccessibles qu'elle a même enregistré un sous-domaine captcha.orange.fr pour proposer ce magnifique CAPTCHA totalement inaccessible lorsqu'on s'identifie sur ses sites !!!!
On vous dérange pas trop, Orange, ça va ???
Je vous propose de remplacer la phrase "Vérifions ensemble que vous n'êtes pas un robot" par "Vérifions ensemble que vous n'êtes surtout pas une personne aveugle ou malvoyante".
🤨
"We expect to publish Web Content Accessibility Guidelines (WCAG) 2.2 as a “W3C Recommendation” web standard in 2023.
We are addressing new comments that we received in August 2023. Depending how that goes, the final publication could be in September or later in 2023."
Are there freelance #accessibility people or those who have time to work on a possible audit? If you're a beginner in the field and haven't done this kind of work, let me know as well. I'm willing to mentor. Please DM.
"Regularly people link to or quote from some outdated version of a specification. This can be confusing and detrimental to understanding, if the information is no longer correct or relevant."
"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."