News for hackers. Stuff that matters.
Re:Cally: Accessibility Statement by Eduard on Thursday April 04, 2024 @02:52AM (#39927319)
from my experience, testing on smartphones and tablets - Chrome on Android and Safari on iOS - reveal additional barriers.
Re:Cally: Accessibility Statement by lynx23 on Thursday April 04, 2024 @02:58AM (#39927351)
Andoid itself is a barrier. They are trying to catch up to iOS accessibility since what, 15 years now? And after all that time, its still 80/20 iOS/Android when it comes to users requiring a screen reader.

BTW, what barriers did you find?

Re:Cally: Accessibility Statement by Eduard on Thursday April 04, 2024 @03:32AM (#39927545)
when it comes to browsers, I found Android way better with respect to accessibility due to Safari lacking recent web standards support, though my perspective is of someone testing a11y, not depending on it.

for mobile browsers, I noticed tab order, tab focus-active paeudostate, and focus fallback (eg what gets focused when a menu closes) to behave differently /incorrectly compared to desktop browser. Also aria-live often does not work on mobile.