It was probably a screen reader like TalkBack on Android or VoiceOver on iOS.

There are some built-in AI tools that can help with accessibility (can do OCR and guess at unlabelled buttons, images, and content) but at the cost of privacy and reliability.

Ideally, the meaningful text content should be exposed to respective accessibility APIs in a manner that is understandable by the user. This simply means following some guidelines by the W3C to ensure that content is always exposed properly and in the correct reading order.

Unfortunately, it seems to still be the case, but have seen some interest and beginning progress in this area. Most designers and devs really want to do the right thing, but just need to be guided on what works best for all users.

Thanks! I will probably keep it up for at least a month. It can sometimes be hard to get data on users that may have been left behind.

Both options should be available but pure self-custody should be the ideal standard. No 2 users are identical in their needs. Most bip-39 seed based hardware wallets are inaccessible to screen reader users for example.

This was a long article outlining the history of design thinking and how it has been commoditized over time by corporate market dynamics. Interesting thoughts on the use of AI tools in design at the end. Designers will become ethical curators defining precise purpose within a wider context.

My boss at AT&T Labs actually read this to us on our first meeting in the office as new hires. We were founding the Corporate Accessibility Technology Office and trying to make our products accessible to people with disabilities. Great cautionary tale!

I would add that providing text labels will also help screen reader and voice dictation users identify and navigate the interface.

When providing text labels adjacent to forms and controls, they should also be programmatically defined as the primary accessible name for these controls and any adjacent image icons should be hidden from being announced by screen readers (usually through the use of alt="" or aria-hidden).

For voice dictation users, that accessible name should also match or at least include the visual text present on screen so that when voicing commands like "click update form", the software recognizes exactly which control they are attempting to activate.

The accessible name should contain the visible text, but not re-order it. For example:

Very nice to see! Thanks for posting

Interesting tool I saw demoed at CSUN AT Conference last week. Physical cards that represent JavaScript components which are arranged to iterate on the interaction design for specific features.

Thanks for the updates! Lots of exciting stuff happening in bitcoin.design

Have you looked into Stakwork.com?

Same here. One of my past colleagues getting told to sell their house for a loss and move to another city (where they will likely be laid off in the next round of cuts). They applied for 3 positions at my fiat job 2 they were qualified for and one they were overqualified for. Put in the time to write a nice cover letter, sent my recommendations to HR only to wait 4 weeks to be told they do not have anything to offer this person with 20 years experience in HW and Software engineering.

@Design_r Sorry it took me a bit to get around to this. Created a GH Issue here with a recommended usage table for color contrast accessibility of existing brand colors: https://github.com/stackernews/stacker.news/issues/1922

Feel free to comment or ask questions on the issue directly. Hoping to open the conversation on what voluntary standards or guidelines we can use to make the content more readable and usable for all.

This is a great idea!