Very pleased and a little nervous to announce that I got to write a bumper post for @csstricks!

https://css-tricks.com/come-to-the-light-dark-side

#CSS #darkMode #lightMode #contrast #accessibility

In just over 8 days (12 September) you can watch the twelfth edition of @inclusivedesign24 #id24, a free online event that requires no payment, no sign-up, and no wading through overt product pitches:
https://inclusivedesign24.org/2024/schedule/

Just look at that schedule and those great topics and speakers.

Set up a viewing party. Binge watch them again over the weekend. Participate in real-time to ask questions.

I like that this 1.4.11 breakdown addresses how adjacency works and how many adjacent colors count. This is a regular point of confusion and I have dedicated many Zoom calls to explaining it.
https://yatil.net/blog/non-text-contrast-in-detail-ui-components

#a11y #accessibility

Worth grepping your source code for "polyfill.io" and taking urgent measures to remove that code if you're linking it into your site - the domain name apparently now intermittently serves malicious JavaScript

My notes here: https://simonwillison.net/2024/Jun/25/polyfill-supply-chain-attack/ - or read this article https://sansec.io/research/polyfill-supply-chain-attack

Oh hey, it’s #GAAD.

Be on the lookout for the (mostly corporate) performative A11yship of #GAAD which is about to fill your timelines.

A couple years ago I demonstrated #overlay companies as the worst offenders:
https://adrianroselli.com/2022/05/the-performative-a11yship-of-gaad.html

#accessiBe #AudioEye #FACILiti #LevelAccess #UserWay #accessibility #a11y

It's #GAAD, so time to re-share this. https://ericwbailey.website/published/global-accessibility-anger-day/

WCAG 3 Working Draft is updated and ready for your input.

This draft includes potential outcomes that we are exploring. The purpose of this draft is to:
* better understand the scope of user needs and how they could be addressed in an accessibility standard,
* request assistance in identifying possible gaps, and
* request assistance locating and conducting research to validate or invalidate the outcomes listed.

Find out more about WCAG 3 and how you can comment from https://w3.org/WAI/wcag3

Why do we need Global Accessibility Awareness Day? A quarter of a century later and we still don't have enough awareness, support, knowledge, buy-in for accessibility. It is improving, but slowly, we need even more advocates.

https://buff.ly/3UEu1qj

#GAAD #A11y #Accessibility #DigitalAccessibility

GitHub produced a great mini documentary about my work with @michaeldcurran, @Scott and others to create both #NVDASR and #OSARA.
With audio description: https://www.youtube.com/watch?v=N-y3yomLLSk
Without audio description: https://www.youtube.com/watch?v=L076ngGbBRc&t=0s
#accessibility #a11y

Live regions have a reputation for being inconsistent.

While this can be partly attributed to shortcomings in current implementations, the problem can also be caused by developers misunderstanding how live regions are intended to work.

In this blog post written by @patrick_h_lauke, we look at common pitfalls, and how to avoid them.

https://tetralogical.com/blog/2024/05/01/why-are-my-live-regions-not-working/

#Accessibility #A11y #Aria

@aardrian @weirdwriter on the bright side, the official app (which I'm using right now) underlines links, so at least the app developers didn't agree 😝

I'm back at #CSUNATC24 this year and decided to bring back the Great Big List where anyone can add links or other notes about any of their accessibility sessions at https://bit.ly/csunatc24. Please share and add your information! Feedback and other contributors welcome!

@aardrian finally! Firefox has had this functionality for so long and I'm kinda surprised it's taken so long for Chrome to follow suit. Not at all surprised by Safari given that it defaults to having keyboard support turned off.

People, listen… you can’t censor subtitles, alt text, or accessibility labels that are not also censored audibly or visually.

Deaf and Blind people are just as capable of handling a profanity as a someone who can see or hear.

IMO this goes against the ideals of accessibility and is a form of ableism.

#a11y #accessibility

Surprise surprise. Story by Paresh Dave.

https://www.wired.com/story/google-black-deaf-worker-diversity-suing-discrimination/

Jakob Nielsen thinks accessibility has failed.

Jakob Nielsen thinks that generative AI will make my experience better.

I think Nielsen needs to think again.
https://tink.uk/nielsen-needs-to-think-again/

#accessibility #a11y #AI

In “Techniques to Break Words” I quickly review:
`word-break`
`overflow-wrap`
`hyphens`
`<wbr>`
`&shy;`
https://adrianroselli.com/2024/02/techniques-to-break-words.html

You can play around with the demo directly:
https://cdpn.io/aardrian/debug/eYoOdrX

#HTML #CSS

@alan42 In practice, having duplicate ids that contain the same text content for something like an aria-labelledby reference wouldn't be problematic. There are cases where duplicate ids would cause a problem, like if the content is different or for something like an aria-controls reference. In those cases, you can usually find a more meaningful SC to apply that points more to the problem.

@yatil @aardrian @notabene @pixelate I feel like I remember the folks at WebAIM encouraging people to take it as long as they use a screen reader for any purpose, even if it's not for a disability. I guess in some cases it's kinda interesting to see the comparisons, but I'd also prefer if they filtered people out of the survey if they only use it for testing purposes.