@Sagaliciouzzz @StingrayBadger I'm not so experienced with content discovery because I followed a large community here. But one tip I saw and never forgot: Don't tell them to sign up to Mastodon, tell them to sign up for fribygda.no, or whatever other server you think is good. Find them an instance. Even tech people agonize over this detail.
Don't worry about telling them how the fediverse works until they've signed up and started to discover people. Keep it basic, compare the username@domain format to email providers.

Me: I forgot my password.
Email: Okay, here's a link to reset it.
Me: Click.
Website: This link has expired. Try generating a new one.
Me: What? You literally just sent this to me. Ok, fine, give me another.
Website: You just generated a link. Try using that.
Me: Click.
Website: This link has expired. Please generate another.
Me: ...
Website: ...
Me: 🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯🤯

An e-mail I just wrote to Amazon's accessibility support--which has fixed approximately 0 of the issues I've reported so far, but I can dream, right?

Hello,

As of a recent update to the amazon.ca website, I am no longer able to read the price of products on search results pages. I'm using the NVDA screen reader but I suspect this issue will affect all screen readers.

1. Go to amazon.ca (NOT .COM) and search for anything.

2. Navigate to the first search result and read through the information following the name of the item.

3. Notice the link called "Price, product page". This is--for some reason--a link that has been re-labeled for screen reader users. In doing so, the actual price of the item has been removed.

I now need to open the page for each individual product and find the price there. This adds an unimaginable amount of page loads and time onto the process of shopping for multiple items.

I do not need support; I know how to find the prices of items. This just needs to be fixed.

(It's worth noting that I can actually use object navigation to drill down into the link and find the actual text label with the price. Some moron has just obscured it with an aria- label.)

@silverleaf57 @jscholes @pitermach @BorrisInABox Yes. Throw a screen reader at a sighted developer who is on too much of a time crunch to read the manual enough to even figure out basic navigation, and suddenly that developer is throwing tab stops on static text and trying to turn the whole sight into a narrated experience instead of thinking about efficiency.

@jscholes @BorrisInABox I see your point in theory, but I'm curious if you can think of examples of when a longer/different speech label might be useful. Most of the time it seems like the standard label could just be modified for conciseness.

@BorrisInABox I've been noticing this too, and even before I saw it in Braille I realized it would be horrible on Braille displays. I wish people would stop overthinking TTS and remember that Braille users exist. I don't understand this trend at all. I also have punctuation customized to report hyphens, so it's extremely obvious now. Definitely send a note to them. You could always ask if there's a reason they decided to do that.