So I finally contacted Google disability support about the degrading accessibility of the youTube app for iOS. I'm fairly sure I was sent there from the youTube help site. I summarized a lot of the issues I and other Voiceover users have been having with the iOS app, particularly the hellish clutter of search results and recommended videos. The response I got today directed me to write to YouTube premium support, but the page they linked to is only for help with one-time purchases or ongoing subscriptions. As an alternative, I was told to post in the community. There was no acknowledgement of the issues and no offer to pass it along. It very clearly said "You've reached the wrong place."
My interpretation of this e-mail is simple: Google disability support can't file feedback about youTube. If there is a way to do so and reach an accessibility-aware person, I have not found it.
The youTube iOS app has now degraded to the point where it's painful to use. I think this is a good nudge to move the podcast feed generator in-house (literally) and start listening to videos in Overcast. It'll also make me less unfocused and dependent on the algorithm. #Accessibility#Google#YouTube#Enshittification
Say your site styles are responding to the prefers-contrast: less media query. Must they still conform to the relevant 4.5:1 and 3:1 contrast ratios when the media query is active?
TalkBack does not expose the contents of the tabpanel in the first example (“Auto Tab Panel sans Interactive Child”). Looking for confirmation from another Chrome 124 / TalkBack 14.2 / Android user. Or prior experience.
You should always be running the latest version of any software program.
…
…
Sure, until #accessibility for disabled users goes down the pisser and they're left feeling frustrated, upset, worried and confused as to how long it'll take for the shit they rely on every day to be usable again.
Dear @microsoft#MSExcel developers: has none of you printed a spreadsheet with #MSWindows set to its built-in #accessibility visual theme, high-contrast black? Because the latest version of #Microsoft365 apps for enterprise prints out black pages with light text. And when I switch the visual theme to the built-in high-contrast white, it prints white pages with black text. Same spreadsheet. That shouldn't happen. #usability
Until JAWS (and TalkBack) fixes its heading level bug and unless Microsoft removes its heading level limit in Windows, heading depth will continue to have a limit.
This may become more obvious if headinglevelstart ever lands.
Granted, most content doesn’t (shouldn’t) need more than 6 levels, so it would (should) be an edge case.
Check out this great segment from CBS. It features Jordyn Zimmerman who is nonspeaking, and uses Live Speech on iPad to communicate. Our team created this #accessibility feature to help give everyone a voice. https://www.youtube.com/watch?v=mTECNar9yG4
Blind Sonos users have an important and rare opportunity to make our presence felt and our displeasure heard about the massive #accessibility regression in the new mobile apps.
Next Tuesday 14 May between 2 and 5 PM US Eastern time, three senior Sonos staff are conducting an “ask me anything” (AMA) session in the Sonos community. In attendance will be Diane Roberts, Senior Director of Software Development, Kate Wojogbe, Senior Director of User Experience, and Tucker Severson, Director of Product Management.
These are the key people in the company who agreed to the app being released in the inaccessible state it’s in, and they are the key people who need to take fixing it seriously.
Many people want to take some action that makes a difference. This is something you can do.
You can bookmark the page for the AMA. It is, https://en.community.sonos.com/events/sonos-app-redesign-ama-6
Try to become familiar with the forum before Tuesday, because while it isn’t completely inaccessible, it’s not the best and a little quirky. You should be able to sign in with your Sonos ID.
Perhaps compose your question thoughtfully ahead of time and have it on your computer, so you can paste it into the AMA when it goes live. It will not hurt for Sonos to understand how upset and inconvenienced many of us are by what they have done. We can do that firmly while remaining polite.
They need to understand, the best way to make us go away is to fix what they broke. We won’t be quiet until we get back what they took from us.
Happy contributing.
Let’s all please keep in mind that #accessibility is all about who will and will not be included. It is nothing less and it is not just some sort of technical compliance issue. The key is impact.
On Monday, the #HadesII Early Access #game version dropped on #Steam. On Tuesday, some of the #accessibility mods were updated to support it. And on Wednesday, yours truly's streaming it. Come see what's up in an hour over at https;//twitch.tv/zersiax #selfPromo#twitch#goingLive#streamer
👩💻👨💻 Praxisnah und innovativ – unsere Kolleginnen und Kollegen aus dem Team Barrierefreiheit der IT des Bundesamts nehmen heute am German Testing Day 2024 teil, der größten unabhängigen Konferenz zu Software-Qualität im deutschsprachigen Raum. #GermanTestingDay#GermanTesting
🗨️ Während eines Vortrags zum Thema „Barrierefreiheit für alle — Digitalisierung ohne Hindernisse“ können die Teilnehmenden in einem innovativen Formatmix an verschiedenen Stationen mit Simulationsbrillen oder Tastsäckchen eigene Erfahrungen mit Barrieren sammeln. #Accessibility#GermanTesting
Hey if Sonos can just up and screw their UI then I can just up and decide to never use them for future speakers. Time to check the resale value of this garbage in case they can't fix the UI accessibility like yesterday.
@nick#Sonos has replaced its app not because they truly think the app is better. But because they can replace specialised Android, iOS, Windows, and macOS teams with one generic team who know how to use cross-platform tools.
It goes beyond that, though. Look at the ideas behind the new home screen, which essentially can be described as: "put what you want on it". Is that primarily a user-facing improvement? No.
Rather, it's a reason to not rely on designers who can carefully think through information architecture, viewport sizes, user flows, and the best ways to present information. Make it the user's problem so that they can fire the people whose responsibility it used to be, or move them to another team where they won't be able to do their best work and will eventually quit and not be replaced.
This update goes way beyond #accessibility. It's a fundamental shift in how they do business, and it will be shit for everyone. That, more than the lack of #VoiceOver support, is what will probably cause me to move away from their ecosystem.