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?
TL;DR: Avoid setting heading levels greater than six (6). This applies whether using aria-level or the proposed headingstart HTML attribute. Use HTML <h#> elements whenever possible.
Le site #Korii de #Slate propose de temps en temps des articles intéressants, mais son design arrache la rétine (par pitié, Slate, virez le designer qui a cru bon de baser tout le design sur le jaune et le blanc >.<).
J'ai créé un userscript qui améliore le contraste général du site : https://greasyfork.org/fr/scripts/494381-fix-korii-s-redability