Frontend DogmaSlouching Towards WCAG 2.1, by @mnit-services.bsky.social:
Scottish LassFucking WCAG
Finally translated into Glaswegian 👏 👏
Access42Ne sous-estimez pas la balise <title> de vos pages web !
Des titres de page clairs et contextuels améliorent l’UX. C’est un repère important au sein d’un parcours utilisateur.
Dans cet article en anglais, @katrin_k explique comment elle évalue cette balise lors d’un audit d'accessibilité :
Patrick H. Laukei love when somebody asks "surely this normative definition/wording doesn't mean what it says on the surface?"
and you go in and try to give the original writers the benefit of the doubt and say "nah, it's probably just awkwardly phrased...the logical interpretation is this" ...
and then one of the original writers comes in and says "nope, we meant it exactly like that, even though it's illogical" ...
every. single. time.
Need a clarification of color requirements for images *with* text · w3c wcag · Discussion #5012
Hello, I have always considered "standard" text in images as being covered by SC 1.4.5, but I think I might be wrong... The definition of "images of text" is: "text that has been rendered in a non-...
Jeff LangeAdvanced Mode comes to https://contrast.jefftml.com which lets you separate out dark-mode specific colors, and/or Text vs. Buttons vs. background colors. #accessibility #wcag #a11y
Jessica Tegner 👩🏻🦰I'm blind. I use a screen reader every day — to write code, to ship software, to navigate the internet.
Automated tools catch ~30% of accessibility issues. I catch the rest.
Now taking on 3-4 accessibility consulting clients for Q2. EAA is in effect — compliance isn't optional.
https://jessicategner.com/consulting
#accessibility #EAA #WCAG #a11y #ScreenReader #WebAccessibility #EN301549 #OpenSource #blind
EvolveumAccessibility in #IGA matters! ⚙️ New #midPoint 4.10.2 brings an important milestone: improved accessibility of the self-service user interface with #WCAG 2.2 AA compliance.
👉 Read about the release:
https://docs.evolveum.com/midpoint/release/4.10.2/
👉 Accessibility Conformance Report:
https://docs.evolveum.com/midpoint/compliance/wcag/wcag-vpat/
Participez à la relecture des nouvelles traductions en français des WCAG 2.1 et 2.2 ! 📣
L’appel à commentaires est ouvert à tout le monde : il vous suffit d’envoyer vos remarques par e-mail jusqu'au 6 avril 2026 !
Besoin d’aide pour participer ? On vous explique la marche à suivre ici :
Commentez les nouvelles traductions candidates en français des WCAG 2.1 et 2.2 jusqu’au 6 avril 2026 – Access42
Après plusieurs mois de travail avec le comité de traduction, le W3C lance l’appel à commentaires publics sur les nouvelles traductions candidates en français des WCAG 2.1 et 2.2. Vous pouvez relire et commenter ces documents jusqu’au 6 avril 2026 inclus. Cet appel à commentaires est ouvert à tout le…
Adrian Roselli, pH0Last month I was trying to unstick a WCAG issue on contrast for disabled controls,where I was fine with disabled buttons passing 1.4.3:
https://github.com/w3c/wcag/issues/4874#issuecomment-3929263408
Today, someone is trying to unstick low-contrast disabled buttons being ok (via @SteveFaulkner):
https://github.com/w3c/wcag/issues/922
Does the SC 1.4.3 Contrast minium exception apply to text outside a disabled control? · Issue #4874 · w3c/wcag
For the "Text or images of text that are part of an inactive user interface component" exception for WCAG 1.4.3 Contrast (Minimum), does the exception apply to the label for a control when it is ou...
Steve Faulkner👀 Greyed out submit buttons (conditional upon successful form completion)
Greyed out submit buttons (conditional upon successful form completion) · Issue #922 · w3c/wcag
I think we need a position on submit buttons that remain inactive until the user successfully completes the form. It is typically greyed out below the contrast standards, and is not tabbable until ...