The Wolfe Pack

@fu Yes, it did work for about a week several months ago, but then it broke again, and hasn't worked sense.

I keep hearing that Steam💩 is accessible again, so I tried it, and nope. The menu comes up but there is no screen reader feedback at all.

@rimu After talking to @sektor the tree view sounds like a neat option. Also @anguskola@stormux.org is interested in testing that too when it is available.

@rimu The table of communities is awesome now, thanks for that. I have joined a few communities.

Would it be possible to start each comment with a heading level? It would make it easy to skim through the comments or jump to the next one if desired. Also, I tried up voting a couple of things, and I can't tell if the button has been pressed or not. In this case, an aria live region to provide a status message would be good. Also, once voted, the selected button should report itself as disabled, (Orca says "grayed"). I'm not sure if the button turns gray visually or not.

This is getting more and more awesome. ☺️

@rimu If you are on Windows NVDA is the best screen reader for testing. It is free and open source. On Linux, you could use Orca. Orca comes with most distros or is installable through the package manager. For Mac, the screen reader is called Voiceover. I don't really know any more than the name for that one, but a lot of people complain about web navigation with Voiceover. Voiceover is also the screen reader for IOS devices like the iPhone. For Android the screen reader is called Talkback. If you ddcide to test with either of those, they do change how your device operates, for example, on Android you have to double tap items to activate them.

Link text should be enough to convey the link's purpose. Aria label is only needed when non standard elements are used, so for your typical a href="stuf", so long as you have accurate text before /a, you don't need to do anything else.

Thanks for being so awesome, and working hard on accessibility. It is very much appreciated. :)

@rimu I was wondering about the table on the "Explore Communities" link. All of them just say "View Community". Is this what is shown visually as well, or is the community name/topic missing for screen readers? I'm having difficulty looking through to find things to follow, but I'm not sure if that's accessibility, or user error lol.

For anyone using Talking Clock, I have updated the weather part. It no longer uses a service with an api key.