—
"Instead of not being aware about the problematic approach the developer chose, they try to improve accessibility but – unbeknownst to them - create new barriers in the first place doing it." @marcus
I am either making friends or enemies with subject librarians at my university this week by requesting many purchases of books about queer and disabled community building/intimacy/materiality and arts.
Just rewatched Sweden’s Eurovision entry, which has a lot of strobing lights and flashing with i(Pad)OS’ Dim Flashing Lights setting turned on. It’s very interesting how this setting can compensate somewhat for the flashing but also clearly misses the mark sometimes.
(And of course it would be better if there were no strobing lights or flashes in the first place.)
I'm looking for benchmarks.
For @mucConf we want to provide accessibility information online.
Please send me links to events/conferences that did a good job communicating accessibility information!
>>
I, for one, am curious how allowing tables (et al) in <option> is going to work when the issue discussing it is deferring #accessibility to another issue — in which none of them are participating.
TalkBack does not expose the contents of the tabpanel in the first example (“Auto Tab Panel sans Interactive Child”). Looking for confirmation from another Chrome 124 / TalkBack 14.2 / Android user. Or prior experience.
Until JAWS (and TalkBack) fixes its heading level bug and unless Microsoft removes its heading level limit in Windows, heading depth will continue to have a limit.
This may become more obvious if headinglevelstart ever lands.
Granted, most content doesn’t (shouldn’t) need more than 6 levels, so it would (should) be an edge case.
I know there are some fediverse apps with features that make adding alt text easier, some using image detection, etc. Can anyone point me to any write-ups on these?