@… is wondering how much trouble a skipped heading level is for screen reader users. Three users have replied but it'd be great to see more feedback. Anyone else willing to reply to Manuel's post? Here is the link:
h…
Two years ago at #CSUN I learned about what became my favorite browser extension, BeeLine Reader. I've been a subscriber ever since.
It's easy to set up on desktop, but has been some struggle to get working on Android. But this week I discovered it works with Microsoft's Edge Canary mobile browser, which has experimental support for extensions. Instructions are here:
"Simultaneously to Steve Jobs’s introduction of the iPhone in January 2007, Google started publishing a series of blog posts called “Testing on the Toilet”. On May 15th, 2008, this series featured a famous issue: “TotT: Using Dependancy Injection to Avoid Singletons.” The writing was literally on the wall of toilets worldwide: Singletons are bad™®©. Sadly, the much more exciting idea of dependency injection contained in the article got lost in the minds of most readers."
https://deprogrammaticaipsum.com/the-hype-cycle-of-oop/
For 5 years now I've been learning about web accessibility and reviewing websites. But I'm not a native screen reader user, and my mobile app experience is lacking.
This month I learned about "Accessibility Actions" or "actions available" for VoiceOver and TalkBack. I shoulda known about it for years-- it makes navigation by swiping potentially much quicker.
Would you be willing to share your thoughts and experiences with this feature?