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”:
I'm training someone to do #WCAG audits. Reading the definitions we came across this (SC 4.1.2):
"programmatically determined: determined by software from author-supplied data provided in a way that different user agents, including assistive technologies, can extract and present this information to users in different modalities."
This is such inaccessible language! Especially is English isn't your first language. I managed to explain it in Dutch, but it was NOT easy.
Currently supporting an effort to localize thousands of B2C websites + a native app across 20+ languages using machine translation.
Anyone have experience with handling Language of Parts (WCAG 2.0 AA 3.1.2.) at scale through machine translation? Let me buy you a virtual cup o' coffee for your thoughts! :) #a11y#wcag
🇺🇸 I think today was one of the most important updates of my website. It's a bit of a shame that (especially as a disabled person) I didn't take care of it sooner, but simply, like many other people, I didn't know it was bad. So I've been improving accessibility for people with disabilities, including the blind and visually impaired (increased contrast in the dark theme, alternate text in all my graphics), and rearranging buttons so that my site can be operated entirely from a keyboard. The goal is to get the site to the AAA level of accessibility, the highest according to WCAG 2.1 guidelines.
🇵🇱 Myślę, że dzisiaj nastąpiła jedna z ważniejszych aktualizacji mojej strony internetowej. Trochę wstyd, że (zwłaszcza jako osoba niepełnosprawna) nie zająłem się tym wcześniej, ale zwyczajnie, tak jak wiele innych osób, nie wiedziałem, że jest źle. Więc udoskonalałem ją poprawiając przede wszystkim dostępność dla osób niepełnosprawnych, w tym osób niewidomych i niedowidzących (zwiększony kontrast w ciemnym motywie, tekst alternatywny we wszystkich moich grafikach) oraz zmieniając układ przycisków, dzięki czemu moją stronę można obsługiwać całkowicie z poziomu klawiatury. Celem jest osiągnięcie dostępności strony do poziomu AAA, czyli największego według wytycznych WCAG 2.1.
♿ Finally we are continuing to improve #accessibility across CryptPad. In this release the toolbar becomes much more navigable with the keyboard and (most) menus can be used with arrow keys. We will keep pushing on this until full #WCAG compliance. #a11y
What an absolute joke of a product this is. YouAccess, the accessibility overlay that isn't accessible. You can't even open it with a keyboard. https://youaccess.site/#accessibility
@mattobee "Run a fully accessible website" is a bold claim I have to say, curious what this means.
Fully #WCAG compliant? Or a different requirement? Fully accessible to #screenreader users? Fully accessible to a certain degree?
No matter how complex and broken my website is, I just add their product and never have to worry about accessibility again? Amazing, they solved one of the biggest issues with one plugin
"Appt.org empowers developers and organizations to build accessible apps for everyone. On this website you will find current statistics about the use of accessibility features on mobile phones, code documentation for iOS, Android and other platforms, official guidelines, in-depth articles and tips."
Linee guida per l'accessibilità dei contenuti Web (WCAG) 2.2 -- Italian Authorized Translation of Web Content Accessibility Guidelines WCAG 2.2 -- is now published at: https://www.w3.org/Translations/WCAG22-it/
“Multi-step processes can be mentally tiring, and this is exacerbated when the process requires the user to recall or transcribe information. Users with learning or cognitive disabilities are particularly susceptible to mental fatigue, since they generally have reduced working memory or increased cognitive load to begin with.”
Can anyone help me. There was a thread on here (relatively recently) that had really good advice for tools and resources to help build websites for accessibility (or at least posters preferred tools).
I thought I had retooted, or bookmarked (or interacted with the thread in some other way) but cannot seem to find it now.
⌨️ Keyboard accessibility myths and WCAG by @graeme
“Supporting keyboard-only interaction is one of the most important principles of web accessibility. However, the scope of the Web Content Accessibility Guidelines (WCAG) in relation to keyboard accessibility is often misunderstood.”