I'm looking for benchmarks.
For @mucConf we want to provide accessibility information online.
Please send me links to events/conferences that did a good job communicating accessibility information!
>>
I have been testing low visibility accessibility on websites I visit, just to see what the experience is like.
Voice over is very easy to enable on a Mac with a magic keyboard. Clicking your touch id button quickly 3 times turns voice over on, and 3 times again turns it back off. Excellent shortcut that makes it easy to include in your development process.
First was an interesting talk by David Gissen on the architecture of disability at the Global Disability Innovation Hub (GDI Hub). Architecture has engaged with accessibility well before HCI, and the insight Gissen brings here is widely applicable https://www.youtube.com/watch?v=6uV0hxeChgY (2/9) #architecture#accessibility
I, for one, am curious how allowing tables (et al) in <option> is going to work when the issue discussing it is deferring #accessibility to another issue — in which none of them are participating.
Delighted to see the tech press taking an interest in the Sonos #accessibility debacle. We need this to keep the pressure on. New Sonos app breaks accessibility for visually impaired users, here’s what this advocate recommends
Tired of coming home with a case of "conference crud"? Want to enjoy great talks about science and accessibility? SciAccess is an accessible conference that started among astronomers, but also has talks that are of interest to folks in STEM in general as well.
And you can still register for it and attend despite it kicking off tomorrow!
Anyone ever had to OCR a webpage to find a link? I did today. On a supposedly accessible college site, with nice fluffy captions on tables telling us poor simpleton blink blinks what the table will contain. Well it didn't contain the one link we were looking for! So yeah, thank goodness for OCR.
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
Just spent today at work with Linux. Fedora's Mate spin still works well generally, and Orca is much more stable. And, according to Orca, the system never even ran over about 3 of the 16 GB of RAM on that Intel NUC. I set up Emacs and Emacspeak, Firefox, Bitwarden, VS Code, and never even took my laptop out of the bag. Of course, I really miss a lot of NVDA addons, like the OpenAI one, sounds for entering browse and focus modes, and the Thunderbird addon most of all. But I was able to log into, and use, Salesforce and Google Sheets. So now when I get a good workflow with Markdown and such, I think I'll just about, maybe, be able to start using it more. Packages are all up-to-date, Orca will alwasy be current, and hopefully I can one day move to a desktop environment with a proper notification center! Oh, and I'll have to see if Pidgin still takes up more RAM the more I use it.
Note that I still wouldn't expect a regular computer user to get into Linux, as far as setting it up. But, honestly, having the #BTSpeak out on the market makes me hope that more power users and programmers will hammer Linux into more of a shape that blind people can be at home with.
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.