Please remember that WCAG itself is the bare minimum of #accessibility. Conforming to WCAG does not guarantee something is accessible. It does not even guarantee something is usable. All WCAG does is provide you with a starting point. Lots of WCAG failures suggest the page has not even made it to the starting line.
Is there a clickable, 2-level, responsive #hamburger#menu with minimal javascript, simple design, header and #navigation only, separate, free to use, #webdev up to date, modern browser.
@aardrian the same devices that can run Safari 17.3.1 can run 17.4 and 17.5 if you just install the latest iOS updates. Both of those Safari versions list multiple VoiceOver fixes. In short, I’d suggest there’s no point submitting a bug report unless the issue can be replicated on the current version of Safari… because it seems maybe it’s already been fixed?
Kudos to Quezon City government for making their website more accessible. According to this article, the website is now passing the #WCAG 2.1 at AA level.
I visited the website and, well, it is accessible I guess. But like other Philippine government websites, the UX is passable but still terrible lol. And it seems that they're using an overlay for the screen reader feature? Big ick for me. #accessibility#a11y
I think there's a growing misconception in the Philippine government that equipping your website with a bring-your-own screen reader is a good way to promote accessibility. It isn't. But this is not the first time I encountered such, because BIR's website also sports its own screen reader for its chatbot Revie.
[Nouvelle BD rendue accessible] Baisse de « charges »
Une BD très courte mais qui résume bien la situation. Je précise pour les plus jeunes qu'à l'époque où je l'ai publiée, un événement de ce genre était encore relativement exceptionnel. Évidemment, aujourd'hui, bon…
"it is important to highlight that Full Keyboard Access (FKA) on Flutter does not exist. If you are planning on building an app using Flutter, FKA users will not be able to use your app"
I noticed that #Obsidian is barely useable with keyboard navigation on iOS/iPadOS. The UI herarchy does not translate into accessible tab navigation. The deepest reachable UI element is the vault switcher menu. There is room for improvement.
@kepano Thanks for reaching out! Appreciate that.
So, there is actually nothing I could rank because tab navigation simply does not function at all. All I can reach with a keyboard is the vault switch menu. It is not possible to navigate the UI via tab/shift-tab keys and arrow keys.
Different areas of UI but also quite important: Scaling fonts, scaling font size of reader separately from UI, scaling horizontal margins of notes quickly and something like a focus-reading mode.