Search

Items tagged with: accessibility


I'm calling you out, #ubuntu folks. Please bask with me in the irony of THIS happening when a screen reader user tries to read the accessibility screen of the installer, ALMOST the first screen you see after booting into it. I think we can safely say it ...pushed my buttons youtube.com/shorts/C_I3TCLvVpU #accessibility #linux


Tis done 🎉
My #youtube channel, formerly known as BlindlyCoding, is now named ViewpointUnseen. This allows me to broaden the content on that channel to include a lot more different types of content, from tutorials for the #blind from a #blindness perspective, tech reviews from that same perspective, #gaming streams as well as reaction content when I find sufficient things to react to.
I think there's a lot of value I can offer to the world at large with stuff that's currently locked inside my head and having a bit more time during the work week allows me to spend more time on #contentCreation. Screen reader tutorials? Hacking streams? Videogames? Reviewing pieces of tech and supplying #accessibility recommendations to users AND developers/creators? Yes, all of that and more. Stay tuned!


The weather's cloudy a lukewarm. Perfect for today's stream where I create a "yes, but no" resource for everyone who tells me to just switch to #linux :P
Nah but seriously we'll look at a number of first-time experiences (install, initial boot into the OS ec.) of various popular and less popular distros. I will comment on the #accessibility considerations primarily for #screenReader users and I'm sure other things'll come up. See you bright-eyed and bushy-tailed around 3 PM EST/8P BST/9pm CEST over at twitch.tv/ic_null or youtube.com/@blindlyCoding. My #peertube account is, unfortunately, not approved yet :) #selfPromo #tech #foss #selfHosting #homeLab #stream #ubuntu #debian #fedora #elementaryOs #kaliLinux #blind


Coooool! that's how you do #Accessibility (it's sarcasm of course).
There is a search input box on a site, and a search button of course. for those who doesn't speak French, "Rechercher" means "Search". When you step on this button with JAWS, you hear this:
"RECHERCHER • RECHERCHER • RECHERCHER • RECHERCHER • RECHERCHER • RECHERCHER • RECHERCHER • RECHERCHER • RECHERCHER • RECHERCHER •".
And here's the code copied from the dev tools:
```
<button class="pannel py-xxs font-regular mx-auto uppercase flex focus:outline-none mt-xl-alt text-xs leading-xs bg-white hover:bg-red text-red hover:text-white max-w-pannel overflow-hidden"><span class="flex-shrink-0 px-0">
Rechercher
<span class="inline-block font-sans-serif mx-1 text-xs">•</span></span><span class="flex-shrink-0 px-0">
Rechercher
<span class="inline-block font-sans-serif mx-1 text-xs">•</span></span><span class="flex-shrink-0 px-0">
Rechercher
<span class="inline-block font-sans-serif mx-1 text-xs">•</span></span><span class="flex-shrink-0 px-0">
Rechercher
<span class="inline-block font-sans-serif mx-1 text-xs">•</span></span><span class="flex-shrink-0 px-0">
Rechercher
<span class="inline-block font-sans-serif mx-1 text-xs">•</span></span><span class="flex-shrink-0 px-0">
Rechercher
<span class="inline-block font-sans-serif mx-1 text-xs">•</span></span><span class="flex-shrink-0 px-0">
Rechercher
<span class="inline-block font-sans-serif mx-1 text-xs">•</span></span><span class="flex-shrink-0 px-0">
Rechercher
<span class="inline-block font-sans-serif mx-1 text-xs">•</span></span><span class="flex-shrink-0 px-0">
Rechercher
<span class="inline-block font-sans-serif mx-1 text-xs">•</span></span><span class="flex-shrink-0 px-0">
Rechercher
<span class="inline-block font-sans-serif mx-1 text-xs">•</span></span></button>
```


I'm considering getting a Linnstrument (as I have been for years), and just came across this super freaking awesome comment w/ response by Roger Linn on one of his YouTube videos.

This is seriously so cool.

Update: I just bought one directly from rogerlinndesign.com because of how hard I support this way of doing business, and wrote him an email to let him know. Let's make it RAIN for people who are kind and empathetic!

#accessibility


We are excited to be a part of #NFB25 next week and to announce our new partnership with @nationsblind!

First time members can join Bookshare for 30% off our annual membership, and existing members can renew for 20% off. You can sign up and renew at our booth D14. See you at the convention next week!

#A11y #NFB #VI #Accessibility


Always fun to read #hackerNews and their rather ... let's call it ... qualitatively exceedingly disappointing mentality towards #accessibility (stroopwafel to the dutchies who see what i did there). But some points do make me think to what degree, say, #screenReaders could be innovating more.
One thing that stuck by me was a comment on an article regarding the use of "click here" that basically suggested some kind of heuristic for, say, reading the entire line of text when that's encountered, rather than the link text. Another one could be including the previous sibling's accessible name on unlabeled form fields which I ...think? JAWS might already be doing?
Like obviously these should be toggleable to not screw up audits but I think after 30 years we can safely say people often can't be forked to learn #HTML basics and it might make some things smoother?


Whether you're heading to #ACB2025, #nfB2025, a holiday family vacation, or nowhere at all, enjoy some free #RemoteIncidentManager on us! From now until the 18th, experience a first of its kind independence that is fully accessible remote desktop, free of charge! Experience just how satisfying being able to provide assistance to any computer - even ones without a screen-reader installed - can be! Download RIM to your Windows or Mac today!
getrim.app
#accessibility #inclusivity


I love this so much. It's pretty much a GUI for #tampermonkey, offering an easier way for #blind folks to find elements on a webpage and do things to them. Yes, you could do the same things directly by just writing JavaScript yourself. But this is much, much faster, and requires a bit less knowledge. It took me less than 30 seconds to turn all the story titles on fanfiction.net into headings. Labeling a button, or making other small changes would be just as fast. The typos and slightly incorrect English put me off at first; especially the word "blinds" for blind people felt weird and derogatory. apparently the author is from #Cameroon, though, so maybe that's standard there. stsolution2.org/WebAccessibilizer/#a11y#accessibility#screenreader


Does anybody know if debugging functionality is accessible with #VSCode? And if so, am I right you need to switch back and forth between virtual cursor and forms mode (#JAWS terminology), or browse mode and focus mode (#NVDA terminology)? #Accessibility


#Frage bzgl. #accessibility #screenreader
Wenn jemand eine Website per Screenreader benutzt (Desktop), wird dann (eher) die Tastatur oder die Maus benutzt, um die einzelnen Textblöcke vorlesen zu lassen? Habe gerade das Problem, dass #nvda beim Testen unterschiedlich reagiert.




Boosts and tips appreciated for a crisis I'm going through right now, (more info in the replies). I'm likely about to be kicked out of my home for reasons that I currently cannot disclose. I will have to move back in with my mother, which is a very bad idea. What should I do? #Accessibility #Blind #housing


As a community that includes folks with a range of disabilities ourselves, we’re deeply invested in improving access to Open Source software. We succeed at our mission when we build open computing experiences that are available regardless of ability and fail when accessibility is considered an afterthought or a nice-to-have. This month and always, Inclusive Design is at the core of what we do and we will continue to strive towards that ideal

#Accessibility #DisabilityPrideMonth #InclusiveDesign


Since the release of OS 8 we’ve been working on things like improving contrast, Dark Mode screenshots and brand colors in AppCenter, turning on or snoozing Dark Mode without canceling your schedule, expanding the “Reduce Motion” setting, and more options to reduce distracting notifications. Plus, thanks to feedback from @fireborn—who you may know from his blog series on Linux accessibility—Notifications and the Shortcut Overlay both got releases that add screen reader support

#accessibility



#GitHub, issue labels: On my request the default colors are labeled with meaningful names, not only with hex codes.
I.e., you want to create several labels for your GitHub-powered workflow: bug, Enhancement, Dependency Updates, and so on.
It's very nifty if you mark all those labels with different colors: red for bug, yellow for dependency, blue for enhancement and so on.
But what if you are blind? Before you had only hex codes randomly thrown at you, and you had to be a CSS guru to know that those six hexits represent, say, teal or dark green.
Now it's fixed, and you can select one of the default colors with a press of a button, and those colors have meaningful English names in front of their hex codes.
Well done, GitHub! #Accessibility #Microsoft cc @cariefisher


Does anyone here have any visual impairments? I’m after some accessibility advice about apps.

Boosts appreciated for reach

#Accessibility


Continuing our volunteer effort to make GNOME Calendar fully accessible with a keyboard (see thread for context), we fixed a major bug that was causing the focus to disappear into the abyss when the user tried to tab into the month view in merge request !576. This means, as of this commit, events should now be completely functional and accessible within the month view. Additionally, the merge request changes the keyboard and focus behavior within the month view: Events can only be cycled using arrow buttons, the focus can't escape the month view with arrow buttons, and entering/exiting the month view can only be done with tab. These improvements will be available on GNOME 49.

#GNOME #Accessibility #a11y #GNOMECalendar #Calendar #FOSS #FreeSoftware #Linux


Happy Disability Pride Month everybody :)

During the past few weeks, there's been an overwhelming amount of progress with accessibility on GNOME Calendar:

Event widgets/popovers will convey to screen readers that they are toggle buttons. They will also convey of their states (whether they're pressed or not) and that they have a popover.

Calendar rows will convey to screen readers that they are check boxes, along with their states (whether they're checked or not). Additionally, they will no longer require a second press of a tab to get to the next row; one tab will be sufficient.

Month and year spin buttons are now capable of being interacted with using arrow up/down buttons. They will also convey to screen readers that they are spin buttons, along with their properties (current, minimum, and maximum values). The month spin button will also wrap, where going back a month from January will jump to December, and going to the next month from December will jump to January.

Events in the agenda view will convey to screen readers of their respective titles and descriptions.

Accessibility on Calendar has progressed to the point where I believe it's safe to say that, as of GNOME 49, Calendar will be usable exclusively with a keyboard, without significant usability friction!

There's still a lot of work to be done in regards to screen readers, for example conveying time appropriately and event descriptions. But really, just 6 months ago, we went from having absolutely no idea where to even begin with accessibility in Calendar — which has been an ongoing issue for literally a decade — to having something workable exclusively with a keyboard and screen reader! :3

Huge thanks to @nekohayo for coordinating the accessibility initiative, especially with keeping the accessibility meta issue updated; Georges Stavracas for single-handedly maintaining GNOME Calendar and reviewing all my merge requests; and @tyrylu for sharing feedback in regards to usability.

All my work so far has been unpaid and voluntary; hundreds of hours were put into developing and testing all the accessibility-related merge requests. I would really appreciate if you could spare a little bit of money to support my work, thank you 🩷

ko-fi.com/theevilskeleton
github.com/sponsors/TheEvilSke…

#Accessibility #a11y #DisabilityPrideMonth #GNOME #GNOMECalendar #GTK #GTK4 #Libadwaita #FreeSoftware #FOSS #OpenSource



From the Debian mailing list: Proposal: Debian-AI — A Free and Open-Source AI Operating System

So people think of AI before accessibility. I'm not surprised, but still, just another reminder. And I know it's just a proposal, nothing concrete, but we don't see proposals for accessibility, like, at all. So yeah foss, keep going with that End of Ten evangelism, keep showing disabled users how y'all are. I hope governments in Europe have to return to Windows due to accessibility issues in Linux, and that it hits the news hard. Maybe then you'll wake up.

#accessibility #foss #debian #linux


Serious #accessibility question:

If I want to mark positive and negative outcomes in color, the "obvious" choice is of course to do that in green and red and have some form of textual fallback.

Now, Im of couse not getting rid of that fallback, but since there is usually a reason to mark things in color (it's much more obvious if you can see it!), so it would be nice to have a combination that is accessible to at least more people (nothing will work for everyone, it's about reaching 95% or 99%[1]), while still being intuitive for everyone else.

I've played around with green and orange before (yellow doesn't work, because it is super bright and I want to support both light and dark mode.)

Anyone any good ideas?

#a11y


To #Blind and #LowVision Linux users:

Which #Linux or #BSD distributions are you able to install without assistance? Are there any that work better with screenreaders and other assistive technologies out of the box?

I'm trying to understand how much of the problem is specific to distributions, their installers or differences in windowing system such as Wayland breaking screenreaders vs X11.

#accessibility


Dear apple.
Please comply with the EU so I can continue to use your amazing products and serveces, and not be forced to switch to inferior products and services from companies like google and microsoft.
#accessibility #apple #android #blind #google #microsoft #windows



@fireborn @kde @gnome They are, a simple policy change would prevent #accessibility from regressing and being a second class citizen on new features. It's not a code problem, never has been.



Does the feature meet the standards for #accessibility? Is the documentation complete? No? THEN DON’T RELEASE THE FEATURE. Make these things release blockers, it’s literally that simple.

#linux #a11y


Disabled people and allies: We want accessibility in our software!

Developers: It's too hard, too expensive, *whine* (repeat for decades)

Most people I know: We don't want AI in our software!

Developers: We've gone to record lengths to shove AI into everything in less than a year. #a11y #Accessibility #AISucks


We've recently made many tweaks to improve accessibility of our settings pages for keyboard users, screen reader users, and users who have JavaScript disabled. Ensuring Kagi is accessible is a priority for us.

Anything we can do better? Let us know: kagifeedback.org/

#Kagi #Search #Accessibility


Day 3 of running Windows XP in 2025 is up.
I opened Enafore to check my Mastodon replies. It worked—for a few seconds. Then the notifications started. And they didn’t stop. Ping. Ping. Ping. I couldn’t reply. I could barely move the cursor. I watched the system buckle in real time.
So I tore XP apart.
I disabled over thirty services, deleted Windows File Protection, nuked the prefetch cache, rewrote shutdown behavior, and killed every background process that wasn’t strictly mine. If it touched the network, tried to log something, or ran without permission, it’s dead.
And you know what? Enafore runs fine now. JAWS doesn’t read new posts live, but I don’t care. I can read. I can reply. XP obeys.
Discord, though? Wouldn’t even load in the browser. Just a blank page. So tomorrow, I’m pulling in what channels I can through IRC. It’s not over.
Read the full post:
fireborn.mataroa.blog/blog/dea…
#WindowsXP #Retrocomputing #BlindComputing #Accessibility #IRC #Mastodon #DeadOSWalking


Day 3 of running Windows XP in 2025 is up.
I opened Enafore to check my Mastodon replies. It worked—for a few seconds. Then the notifications started. And they didn’t stop. Ping. Ping. Ping. I couldn’t reply. I could barely move the cursor. I watched the system buckle in real time.
So I tore XP apart.
I disabled over thirty services, deleted Windows File Protection, nuked the prefetch cache, rewrote shutdown behavior, and killed every background process that wasn’t strictly mine. If it touched the network, tried to log something, or ran without permission, it’s dead.
And you know what? Enafore runs fine now. JAWS doesn’t read new posts live, but I don’t care. I can read. I can reply. XP obeys.
Discord, though? Wouldn’t even load in the browser. Just a blank page. So tomorrow, I’m pulling in what channels I can through IRC. It’s not over.
Read the full post:
fireborn.mataroa.blog/blog/dea…
#WindowsXP #Retrocomputing #BlindComputing #Accessibility #IRC #Mastodon #DeadOSWalking