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
Currently studying for the #cpacc exam and I found the #legal part surprisingly interesting. This topic was also relevant in a workshop I gave, so here's a couple of law suits that are #accessibility related:
Our mission is to ensure that machine learning masquerading as intelligence benefits us, the shareholders of exploiting your content, while the returns to you dwindle roughly in line with the degradation of habitability that we are accelerating.
…“Sorry, we couldn’t spend any of our ridiculous market over-valuation on a decent web designer, or on a developer who had any care or clue about keyboard accessibility, we were too busy stealing your content and screwing your future.
And by using Tailwind to implement crappy design patterns, we have even more time to do that. Another win for us”
With the popover API available in all browsers for a while now, we can easily build entirely accessible, even animated popovers for all use cases just with HTML and CSS. As an example I have created a codepen with a simple search button that opens a search field. #HTML#CSS#A11Y#accessibility https://codepen.io/philliproth/pen/OJYLyMp