"Your goal as a feedback giver is to help the document’s author" - great thought from lethain.com/providing-feed…

Spend more time watching loading bars When I switch to something else while waiting, I waste way more time than if I just watched it load

📱 New blog post: WCAG2Mobile is a step in the right direction for mobile accessibility, but there's room for growth. I share my thoughts on how it could evolve from simple terminology updates to become a comprehensive mobile accessibility resource. colinmarsch.ca//2025/06/14/wc…

🚨 There’s a lot of horrific news out of Washington right now—but you might have missed this: Senate Republicans just introduced a plan to sell off 120 million acres of our public lands. Let me break down what’s in the bill and why it’s a full-scale land grab. 🧵

For some reason posting my blog posts does way better on LinkedIn (??) than here?

Happy Canada day! 🇨🇦

I wrote a blog post re-introducing Paparazzi's accessibility snapshots, highlighting the many recent updates they have gone through! code.cash.app/paparazzi-acce…

Accessibility labels in mobile apps should describe purpose, not implementation details. “Send message,” not “paper plane icon.”

Being concise matters in all writing, especially mobile accessibility labels. Long announcements are overwhelming and likely do not communicate a controls purpose clearly.

Testing your Android app with the Accessibility Scanner app by Google is an easy way to check for tap target size, colour contrast and missing label issues! While satisfying these pass/fail checks doesn't guarantee your app is accessible, it's not accessible if you fail them.

One of the simplest ways of resolving large font scale related accessibility issues is to ensure your apps screens are scrollable, even if the content on them doesn't exceed the screen height in the default font scale. This is also a good practice to support small screen devices.

Manually test with TalkBack before shipping, not after. It catches 90%+ of accessibility issues.

One of the most common font scaling problems comes from elements laid our horizontally beside each other running out space (e.g. two buttons). The best way to fix this is to relayout them to be vertically on top of each other instead, if they run out of horizontal space.

Null contentDescriptions are valid—for purely decorative images. Don’t mislabel them or add uneccessary confusion for your customers.

Mobile app error messages must be spoken/announced, not just shown visually. Otherwise, they’re invisible to screen reader users. This is a super common problem.

TalkBack users on Android swipe to navigate, not tap randomly. Every control needs to be in the correct order in the accessibility hierarchy and have a clear label.

Don’t make swipe gestures the only way to do something in a mobile app. Always give an alternative like a button or at the least a custom accessibility action.

Supporting dynamic text scaling isn’t optional. If your app breaks at 200% font size, it’s not accessible.

Add large font scale snapshot test cases to your apps UI test suite. These will help catch bugs and prevent regressions to your font scale handling.