Search
Items tagged with: Accessibility
📢 *AI-generated podcasts aren't here to replace human creativity* 🎙️—they're enhancing accessibility, especially for people like me who learn best by listening. As a blind student, tools like NotebookLM turning PDFs into podcasts help me absorb material more effectively. 🎧 It’s about *learning in a way that works for you*, not replacing the personal touch of traditional podcasts. 🧠💡
#Accessibility #AI #AIforAccessibility #Podcasts #Blind #AIAccessibility #LearningTools #NotebookLM
Where web #accessibility, digital #sustainability, #contentManagement, open-source software, and web standards intersect, you'll find @mgifford always advocating for content, people, and the planet.
In his practice, Mike ensures that the content systems they deliver are built as sustainably as possible, deliver accessible experiences to citizens, and work well for authors and others who use the system.
ellessmedia.com/csi/mike-giffo…
A complex and challenging case in accommodations, accessibility and creating healthy, respectful and effective inclusive workplaces.
For all of interested and engaged in accessibility and disability inclusion rights, it will be important and to follow this one through the legal processes.
I'm telling y'all, if sighted people had to deal with the kind of senseless bullcrap that blind people *have* to deal with, daily, there would be very widespread protests. Public ones. Miles of people.
So, imagine this. You go to Google. Or Kagi. Whatever you like. The text box has "search" as a placeholder text. When you type into the field, the "search" is supposed to be replaced with what you're typing. So you go to search one day, and find that when you search for "cat food", you get "csatf aroochd". No matter what you do, that "search" is there, messing up all your searches. If you backspace everything out and try again, you get the same thing. No matter what. Now, you can click outside of the box, and type and press Enter and it works, but you don't see what's in the search box. You can paste your search in from notepad, but do you *really* want to do that? And this has been a problem for weeks now. You start to wonder if anyone at Google, uses Google.
And while this isn't entirely comparable with what's happening with the iOS Facebook app right now, it's the closest I can get. Truth be told, I don't post on Facebook. I haven't posted on there in like a year or two. So I, personally, don't have to deal with this. But for some people, Facebook is their lifeline. And no, that's not some stupid cliche like it sometimes is when overused by marketing teams. No. For some people, Facebook is how they communicate with their communities. And you had better not come in the replies all "well they should use Mastodon." No. Humble yourself. So this issue is a huge problem for them. And when you have elderly people who just want to talk to the people they care about involved, who know how to do it one way, and just stick to that because technology is so vast that one can easily get lost in their view? Things need to change. People need to understand these things. And while bugs suck and new frameworks are cool and Facebook loves to move fast and break things, if you want to do that, you'd better have a testing team that includes blind people, Braille users, dictation users, as wide a net as you can cast. And you know what? Maybe that'd cut down on that damn blind employment problem too. Fucking listen damn it! And I could go on and post on Facebook about this, using my computer because I'm privileged enough to have one and know how to work around accessibility issues, while I could even grab my Android phone, or dictate into my iPhone, I'm not the general blind person. And this isn't even just about Facebook, or just about this one situation. Developers of anything of any size should take this kind of thing to heart. And I know people are tired of me all on here dampening the party mood with all this anti-fun accessibility talk since like 2017, but at some point, we need to take things seriously. Because devs' "fun", building, developing, trying new frameworks and new updates sparkle sparkle, effects other people.
I work at a public administration with an obligation to keep its software and systems #accessible for its civil servants, who like me might be disabled, as well as for citizens who use its systems from the outside.
Recently, #Firefox stopped working with my screen reader, after it was updated to version 115. After some investigation, requiring the aid of a coworker and far more knowledge about computers and #accessibility than should be expected from a civil service end user, I worked out what was happening. Can you guess?
Someone had the brilliant idea to set, as group policy, the following Firefox directive: accessibility.forced_disabled: 1.
Yes, that does what you think it does. It disallows accessibility providers such as screen readers to connect to Firefox and use the APIs. Who thought this was a good idea and why?
Well y'all, I broke something. I was using Emacs, and was committing a change to a repo like always, when my audio started to studder a bit. I'd noticed that Emacspeak sounds were a big sluggish, but I thought that was Sox being sox or Pipewire messing with something as usual. So I unplugged my Dell docking station, plugged it in again, and things returned to normal until the next time I committed. This time, audio stopped, and, well, never came back. I plugged the dock into my iPhone, and it worked. Windows, worked. Linux though? Nope. Not sure what's going on, but goodness I'm tired of technology. So tired of everything changing and breaking. Google Drive changed, so I'm having to redo the whole course on Google Docs/Drive. And this was not something I was expecting and definitely not something I needed today. So I'm gonna have to look for a way to reset the dock or something.
#linux #foss #accessibility #blind
🦈 JAWS (only) NO MORE
"In 2017 I embarked on a journey to improve and open the reporting of issues with JAWS support for Web Standards.
I continued to work on this after leaving TPGi, until now…"
W3C Web Accessibility Initiative (WAI) invites you to review the draft French translation of Web Content Accessibility Guidelines (WCAG) 2.2:
🇫🇷 Règles pour l’accessibilité des contenus Web (WCAG) 2.2
The @thunderbird team just released the first beta of their email client for Android. I've filed two accessibility bugs on GitHub, and within hours one is addressed and will be in the next beta release (with a pleasant thank you note to boot).
If you feel so inclined, please consider downloading the app and reporting accessibility problems. Especially if you're a native TalkBack user.
#a11y #Accessibility #AndroidAccessibility #Android #TalkBack #ScreenReader #Thunderbird
There are two solutions to ARIA Live Region issues:
1. Don’t use ARIA Live Regions (but use focus, dialogs, or other managing of what’s going on)
2. Put the live region in the DOM at page load (They cost nothing. If you need an alert and a status, put two divs in with both roles.)
See more in these slides:
🤖 XR Accessibility: for people with hearing disabilities by @JoeLamyman
"Extended Reality (XR) experiences tend to focus on providing immersive sounds and directional audio to convey information. But we need to consider how we convey the information in these experiences to people who can’t hear them."
#XR #VR #accessibility
✍🏽 drugs button popover - updated October 1 2024
"Several people have questioned my reasoning for writing about the use case of popover as a tooltip, no I was not on drugs, at the time of writing I noticed that GitHub was using popover as a tooltip"
I am glad `<datalist>` saw some fixes in Safari, as spotted by @adactio adactio.com/journal/21445
However, other bugs (such as the ones I link from JAWS and Firefox) are still open as well as voice control challenges and text size issues:
adrianroselli.com/2023/06/unde… (anchor link)
So nothing likely changes in your support landscape. Yes, this still makes me sad.
"I say that NVDA changed my life, because only we know how difficult it is to get a job, and companies rarely want to pay for software licenses." - Mykael, Brazil.
Read Mykael's full testimonial at: nvaccess.org/post/mykael-makes…
Helping people achieve independence is our passion at NV Access. Thank you Mykael!
#Independence #Empowerment #Accessibility #NVDA #ScreenReader #NVDAsr
Benutzt du einen #Screenreader oder Ähnliches?
Vermute ich richtig, dass eine einfache HTML-Seite (ohne JavaScript oder kompliziertes Layout) bei gleichem Inhalt grundsätzlich barrierefreier ist als eine PDF-Datei? Wie ist es mit ePub?
Wertet dein Screenreader PDF-Tagging und Alternativtexte aus, oder liest er nur vor, was an der Oberfläche zu sehen ist?
#blind #sehbehindert #Barrierefreiheit #accessibility #TaggedPDF
Okay y'all, I need to understand this. So someone said that a Pixel 8 is faster than an iPhone 15. Can someone help me understand why someone would say such a thing? The iPhone 15 has a much better SOC than even the Pixel 9, and Google has said that they aren't pushing for benchmarks. This person is using a screen reader, TalkBack and VoiceOver. Meanwhile, to me, the Pixel 8 feels even slower than my iPhone SE 2020, and the Samsung Galaxy S20 FE. Like I guess it could be their way of coping with Android, but I mean there are people who genuinely like it. And yes, it has LLM image descriptions now, so I mean there are people that will put up with it just for that feature. But, meh, sometimes people are unknowable.
#Android #iOS #accessibility #blind
What I now want is a set of predefined style sheets that will take care of the visual layout, conforming to all of the applicable accessibility guidance (font selection, layout for mobile and desktop environments, reflow, etc.). The plan would be to write correct HTML, and for the presentation to be handled automatically - in the first instance, for static content.
What are others using and recommending nowadays? There are various CSS collections on GitHub, for example.
#CSS #WebAccessibility #Accessibility
- Yes, I'm in! (32%, 33 votes)
- I'd consider, but it's too expensive or too little storage for me (16%, 17 votes)
- Not interested (15%, 16 votes)
- I'm self-hosting it already for my needs (32%, 33 votes)
- What is NextCloud? (Please reply if you selected this!) (2%, 2 votes)
Does anyone who does #GUI programming and uses or has users who use a #ScreenReader or #BrailleTerminal have the scoop on how well Tk (the GUI toolkit of Tcl, accessed via Tkinter in Python) integrates with these tools?
I saw some references to #accessibility as an area of focus in the 8.5 roadmap, and with 9.0 out now, I'd really like to use it - but I need to be able to support screen reader users.
#Accessibility #Instagram #Android #TalkBack #Jieshuo
The amount of much-needed work going into Firefox bug 1590215 for forced-colors support in DevTools is incredible to watch.
People on StackOverflow telling people to screw up #accessibility with the HTML dialog element defeats the purpose of using that element in the first place IMO. Please upvote my answer that corrects the numerous wrong answers, including the accepted answer, to this question if you have an SO account.
stackoverflow.com/a/79028606/2…
#webDev #a11y #html #css #javaScript
Nutzung einer externen Tastatur mit VoiceOver am iPhone: Ein Paar Gedanken
#VoiceOver #blind #iPhone #Accessibility
Die Kombination einer Bluetooth-Tastatur mit dem iPhone und der VoiceOver-Funktion kann ein echter Gamechanger sein. Ich nutze meine nun schon seit einigen Jahren und habe eine echte Workflow-Optimierung festgestellt. Es ist eine tolle Alternative zur Braille-Bildschirmeingabe oder zum herkömmlichen Touch Typing und bringt viele Vorteile mit sich. (1/7)
Reminder: To celebrate our 100th follower on Mastodon we are slashing our prices in half! 50% off all of our courses, just enter code 100-masto-pals on checkout! This code is Mastodon only. Valid until end of September. a11y-collective.com/courses-ov…
(But I can't keep you from sharing this code with anyone who needs a solid foundation in all things Web Accessibility.)
#a11y
#accessibility