While checking my available updates in the App Store, I was initially impressed that the Libby app was only 3.1 MB.
Then I remembered my experience of actually using it and realised that a 31 or even 310 MB native app would probably be preferable to their overly verbose web container thing.
This entry was edited (6 days ago)
James Scholes
in reply to James Scholes • • •In some web platform circles, there's a push for a move away from walled garden distribution methods like the App Store and native apps in general.
Broadly, I think progressive web apps (PWAs) should be easier to distribute and install. And Apple should definitely do more to make those a viable option on iOS.
Unfortunately, purely web-based apps are currently not able to take advantage of several important #accessibility features, primary among them the ability to add actions to elements (e.g. for the VoiceOver rotor).
reshared this
Zach Bennoui and Borris reshared this.
Pitermach
in reply to James Scholes • • •miki
in reply to Pitermach • • •Jamie Teh
in reply to Pitermach • • •James Scholes
in reply to Jamie Teh • • •@jcsteh @pitermach It's a start. It's not quite the same, given that for privacy reasons it can only invoke concrete controls in the DOM rather than arbitrary event handlers, and it's not clear how those controls can be adequately hidden from SR users without disadvantaging other audiences.
When I most recently discussed it with a member of the ARIA WG and a screen reader engineer (in October), it seemed there were quite a few open questions about the relevant side effects too, like focus movement and restoration for e.g. actions that are toggles or open a piece of UI that can later be closed.
But as I say, it's a start and I'm hopeful it will make a difference. I like web apps, both as a developer and a user.
Jamie Teh
in reply to James Scholes • • •James Scholes
in reply to Jamie Teh • • •Pitermach
in reply to Jamie Teh • • •