Mark Steadman
banner
steady5063.bsky.social
Mark Steadman
@steady5063.bsky.social
Squad Leader, Accessibility Squad
at Fidelity Investments

Accessibility automation, Mobile iOS/Android A11y

Check out my articles: http://dev.to/steady5063
So if you use a hint to associate an error message and a user has the preference shut off… welp, no error message will be announced
October 5, 2025 at 2:09 PM
4) Focus management.

My goodness. If I have Talkback or Voice over on, view to view I’d be lucky to find apps that have consistent focus placement.

But when trays/modals appear, focus becomes a nightmare, and makes a lot of apps so difficult to understand
October 4, 2025 at 9:47 PM
3) Icon buttons like down arrows, X for close buttons, and profile icons not having proper description and therefore making the buttons purpose not clear at all

This issue persists EVERYWHERE and it alarming.

An example today: “down arrow sprite 2, button”. COME ON
October 4, 2025 at 9:45 PM
2) Adding the word “button” and “heading” to #Accessibility labels. Instead of using proper semantics to make them identifiable.

Headings especially will not work with screen readers in iOS and Android if you add them as a label
October 4, 2025 at 9:40 PM
1) Social media apps grouping content, but not allowing assistive tech users to access specific functionality like:

* comments
* likes
* reposts

Grouping content helps a TON but when it’s done incorrectly it can actually hurt more!
October 4, 2025 at 9:39 PM