Search

Items tagged with: Accessibility

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
#Accessibility #VSCode #nvda #jaws

#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.
#Accessibility #screenreader #Frage #nvda

#Accessibility #blind

#Accessibility #free #screenreader #nvdasr #community #nvda #welcome #Users

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
#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

The elementary logo in the colors of the disability pride flag
#Accessibility #inclusivedesign #DisabilityPrideMonth

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

#Accessibility @aaron

#a11y #Accessibility #html #UX

#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
#Accessibility #github #microsoft @cariefisher

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

Boosts appreciated for reach

#Accessibility

#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


Improve accessibility with event widgets in the month view (!576) · Merge requests · GNOME / gnome-calendar · GitLab

Calendar application for GNOME
GitLab
#FreeSoftware #a11y #Accessibility #linux #foss #gnome #calendar #gnomecalendar

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


Sponsor @TheEvilSkeleton on GitHub Sponsors

Support TheEvilSkeleton's open source work
GitHub
#FreeSoftware #a11y #Accessibility #foss #opensource #gnome #gtk #libadwaita #GTK4 #DisabilityPrideMonth #gnomecalendar @Jeff Fortin T. (風の庭園のNekohayo) @Lukáš Tyrychtr

#Accessibility #foss #blog #floss #screenreader #nvdasr #News #nvda #beta #newversion #prerelease

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

#Accessibility #linux #foss #debian

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

#a11y #Accessibility

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

#Accessibility #linux #blind #bsd #lowvision

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
#Accessibility #android #apple #google #blind #Windows #microsoft

#Accessibility #blind #ham #amateurfunk #ibfd #hamradio2025 #midi2hamlib

@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.
#Accessibility @GNOME @aaron @KDE

#Accessibility #europeanaccessibilityact

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

#a11y #Accessibility #linux

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

#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

#Accessibility #search #kagi

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

Dead OS Walking: 30 Days on Windows XP in 2025 Day 3 – I Don’t Patch. I Burn. — fireborn

fireborn.mataroa.blog
#Accessibility #Mastodon #irc #retrocomputing #windowsxp #blindcomputing #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

Dead OS Walking: 30 Days on Windows XP in 2025 – — fireborn

fireborn.mataroa.blog
#Accessibility #Mastodon #irc #retrocomputing #windowsxp #blindcomputing #deadoswalking

#Accessibility #Sweden #europe #digitalgov #swedish #govtech #WebAlmanac

#Accessibility #europe #finland #digitalgov #govtech #WebAlmanac

#Accessibility #europe #slovakia #digitalgov #govtech #WebAlmanac #slovakian

#Accessibility #europe #digitalgov #slovenia #govtech #WebAlmanac #slovenian

#Accessibility #europe #digitalgov #norway #govtech #WebAlmanac #norwegian

#Accessibility #dutch #europe #digitalgov #netherlands #thenetherlands #govtech #WebAlmanac #nl

#Accessibility #europe #digitalgov #govtech #WebAlmanac #lithuania

#Accessibility #europe #digitalgov #govtech #WebAlmanac #cyprus

#Accessibility #europe #digitalgov #croatia #govtech #WebAlmanac #croatian

#Accessibility #europe #ireland #irish #digitalgov #govtech #WebAlmanac

#Accessibility #europe #digitalgov #Estonia #govtech #WebAlmanac

#Accessibility #Germany #europe #digitalgov #govtech #WebAlmanac

#Accessibility #europe #digitalgov #denmark #govtech #WebAlmanac

Example of something that might be technically #accessible with a keyboard, but in reality is probably unusable: 141 consecutive checkboxes in the tab order. #accessibility
#Accessibility #accessible

You Don’t Own the Word “Freedom”: A Full-Burn Response to the GNU/Linux Comment That Tried to Gatekeep Me Off My Own Machine, 20250625,
by @fireborn,
fireborn.mataroa.blog/blog/you…

… via lobste.rs/s/nwvary/you_don_t_o…

> Freedom is also not telling disabled users to go fuck themselves because they asked for a working login prompt […]

>> GNU/Linux is about you owning your machine.

> Then why do I have to reassert that ownership every time a package breaks accessibility?

#linux #accessibility #gatekeeping


You Don’t Own the Word “Freedom”: A Full-Burn Response to the GNU/Linux Comment That Tried to Gatekeep Me Off My Own Machine

53 comments
lobste.rs
#Accessibility #linux #gatekeeping @aaron

⇧