Looking for people who regularly use screen readers to browse the web.
A dev version of #keyoxide  currently has 100% #accessibility score by #lighthouse  and 0 errors according to WAVE  but still I'd hope to receive some real-world feedback and ensure what I develop can truly be used by all.
@keyoxide Awesome to see more people paying attention to this! ☺️ I had a look at the 2 sites, and 2 things stood out. The minor one is that the top navigation menu really doesn't need to be so verbose, just saying "About" instead of "Go to the about page" is totally fine, like the links in the footer do even now.
The more serious issue is, on the first page, the group radio buttons to set the protocol are correctly spoken as a "radio group", but the actual buttons themself are just announced as text, without the screen reader saying it's a radio button and more importantly whether it's checked or not. I checked this both in Safari and Brave on a Mac and Chrome with NVDA on Windows.
@pitermach Thanks a bunch for the feedback!
- I'll fix nav (shorter labels)
- Ow, that is interesting because they are actually inpup[type=radio] elements. So I should fix that with a role=radio maybe? I'll try this later this evening
@pitermach This is soo nice! I'm following @keyoxide for a few months already. Recently I've created my profile at keyoxide.org/8df9b61a17bf88354842ecc5144312f3eb650a2d @marcozehe will have clearer suggestions but I can say that you don't need aria-label for controls that already have text content inside e.g. links in the navigation at the top.
Mastodon je sociálna sieť založená na otvorených webových protokoloch a na slobodnom softvéri. Je decentralizovaná, podobne ako email.