Search results

0
0
0
0
0
0

Dear Lovely Peeps:

An (re?) might be in order. I have decided it is time to stop wandering & settle down in a nice sunny garden. 😊

I've been around since 2016, and wherever I am, I try to create a wee gentle eddy of peace & whimsy in my corner of the Fediverse. 😇

I have a -full perspective. Am strongly influenced by . 😄 Believe in a / future. Manage to find small good things to celebrate every day. 🎉

Am interested in , , , , , , , being , / solutions, and a whole lot more.

(I have a neuro-spicy brain so 'a whole lot more' really is a LOT! 😄 )

Come in, have a scroll, and maybe breathe a little easier. I hope you enjoy your time here. 💛

0
0
0

Hello World! I'm a , , , sight-impaired (aka ) person. Working as a professional and since the late 1990s, with since 2004. Founding Committee member. Native speaker, near-native .

Our passions include , , , , , , , , , , , , ,

0
0
0

The X52 train in has ONE entry fit for people in wheelchairs, large strollers etc.

Just after the entrance there's stairs (on both sides). The extremely slow elevator lifts the entire floor and then swivels.

It's an awesome technical solution (for a created problem) but only fits one item. If two wheelchair users enter together they're stuck. If one enters and one leaves it's chaos.

The lift stays up between stations, blocking access for all others.

Rotating round column of technical excellence and practical shitshowiness.
0
0
0
0

Hello !

This is < polycule > - a geeky and efficient [matrix] client for power users.

We finally made it to the Fediverse. We focus on a geeky and accessible user interface written in Flutter aiming to target Linux mobile and Android.

If you're curious on past toots, check out @braidThe one with the Вовк 🐺's toots on !

@matrixThe Matrix.org Foundation

A square graphic with a figure and text. The figure is a cute, small shark in pink lurking behind a wall of stones. Below the figure, the text shows in huge letters "< polycule > and in smaller font size "- a geeky and efficient [matrix] client". The background is deep black.
0
0
0
0

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. (See !587)

• 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. (See !588)

• 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. (See !603)

• Events in the agenda view will convey to screen readers of their respective titles and descriptions. (See !606)

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 @nekohayoJeff Fortin T. 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 @tyryluLukáš Tyrychtr 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

(Boost appreciated)

After two weeks of writing, revising, and trying to make everything as digestible as possible, I finally published "GNOME Calendar: A New Era of Accessibility Achieved in 90 Days", where I explain in detail the steps we took to turn GNOME Calendar from an app that was literally unusable with a keyboard and screen reader to an app that is (finally) accessible to keyboard and screen reader users as of GNOME 49!

tesk.page/2025/07/25/gnome-cal

0

*Please only add me if you're over twenty-one.
Since the Bio field has such a short character limit, consider this to be my profile/biography.
I don't write about American politics, race, anticapitalism, world affairs (wars, poverty, oppression, etc.), loneliness, bad self-esteem, or anxiety/depression, and will not add those who do so often. The same is true of those who feel it necessary to use obscenities constantly. I am not a modern programmer or gamer, I do not use Linux, and I don't care what social network you use.*
Hello. You may have seen me on Friendica.world or blob.cat. Both had accessibility issues, so I am now here, but my other accounts are still open (dandylover1 on both). Also, if you wish to add me to MSN/Windows Live Messenger via Escargot, I am dandylover1@escargot.chat.
Georgiana Brummell is not my legal name, but it is what I use. I chose it in honour of Beau Brummell. I live in New Jersey and am forty-one years old. Some of my interests include studying dandyism, nineteenth-century English grammar, Upper Received Pronunciation, the Italian language, British history, the Regency, opera, and MS-DOS and its current varients. I like coffee, tea, wine, cooking, classic literature, nature and historical documentaries, old BBC radio shows, gardening, hot weather, and playing cards and dice. I love opera, particularly singers from the 1940's and earlier, with Tito Schipa, Beniamino Gigli, Ferruccio Tagliavini, and Mattia Battistini being my favourite singers. I also enjoy English and Viennese operettas. In classical music, I like Baroque through early Romantic. I prefer antique menswear (usually Edwardian) and accessories. I love wit, wordplay, and dry humour without vulgarity, though I do enjoy adult fun. I am happily childfree and am not religious. I have been totally blind since I was two months old, due to Retinopathy of Prematurity.
I am also single and searching. If you are a single, childfree, intelligent, well-dressed man over sixty, please write to me. I will accept platonic friends twenty-one and older.
This is my journal. Anyone can read or comment, whether or not he is a member.

dreamwidth.org

Interests

0

Today is a great day!
The first article I ever wrote has been published in a professional magazine. "Software includes diversity" can be read in the "Testing Experience" magazine.

You can download it here: testingexperience.media/ (email address must be supplied)

I'm stoked to share this topic, which is so dear to my heart, with my professional community.

This wouldn't have been possible without the input, support and feedback from many people and I'm very grateful to everyone of them.

I'd greatly appreciate it if you'd share this far and wide. Many more people need to be aware of the issues in the article, because being aware of them means that change becomes possible.

0
0
0

Just wrapped up high school and exploring what's next! You probably know me from Altbot (the accessibility bot that helps make Fedi more inclusive), but I also build terminal tools, AI integrations, and love working on anything that improves user experience.

Looking for opportunities in full-stack dev, UI/UX, or accessibility-focused roles. Strong in Go, Python, C#, Web, 7+ years Linux experience, and passionate about open source. My projects have thousands of users and I'm always thinking about how to make tech more accessible, inclusive, and user friendly for everyone.

Portfolio: micr0.dev

Boosts appreciated!

0
0
0

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.

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. (See !587)

• 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. (See !588)

• 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. (See !603)

• Events in the agenda view will convey to screen readers of their respective titles and descriptions. (See !606)

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 @nekohayoJeff Fortin T. 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 @tyryluLukáš Tyrychtr 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

(Boost appreciated)

0

As part of our volunteer-driven accessibility initiative in GNOME Calendar, and for the first time in the 10+ years of Calendar's existence, we finally completed and merged the first step needed to have a working calendar app for people who rely on keyboard navigation. This merge request in particular makes the event widgets focusable with navigation keys (arrow left/up/right/down) and activatable with space/enter. This will be available in GNOME 49.

Most of GNOME Calendar's layout and widgets consist of custom widgets and complex calculations, both independently and according to other factors (window size, height and width of each cell, number of events, positioning, etc.), so these widgets need to be minimal to have as little overhead as possible. This means that these widgets also need to have the necessary accessibility features reimplemented or even rethought, including and starting with the event widgets.

We also hope to get other parts of GNOME Calendar accessible before GNOME 49, but I can't promise anything at the moment. We did start working with making the month view accessible: gitlab.gnome.org/GNOME/gnome-c

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.

0
0

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!

YouTube commenter @Parisxniko says that they're a producer born with one hand and have been looking for an instrument they could learn to play instead of being stuck with using piano roll in their DAW.

Roger Linn replies and lets the person know that he gives a 20% discount for musicians with a physical disability that impedes their ability to play a traditional instrument.
0
0
0

🌍 Accessibility matters for everyone.

Whether permanent or temporary, disability can affect us all at some point in our lives. That’s why accessibility isn’t a bonus feature: it’s a necessity.

At Jami, we’re committed to making private communication truly inclusive. From screen reader support to keyboard navigation, here’s where we stand and where we’re going: jami.net/how-accessible-is-jam

Smiling woman in a wheelchair, dressed in a black outfit and headscarf, sitting outdoors in front of green foliage. Text on image reads: 'Discovery – How accessible is Jami?' with the Jami logo in the top right.
0
0
0
0
0
0

Hi. It is . You wouldn't know it from looking at me, but I'm disabled in at least four different ways.

Statistics tells us most people experience disability at some point on their lives. And I don't just mean old age. A bad injury, an accident, a neurological problem – even if, by luck, temporary, they'll disable a person for months or years.

is for all of us. Whether in physical space or in IT: deserve to join in, hassle-free.

0
0
0
0
0
0

So far I’ve learned:

The seat appears pretty comfortable even for my fat ass.

She’s got quite the torque. Like a Go Kart. I’m sure I’ll get used to it.

She will go through the downstairs doors. This is a plus!

Speaking of go karts, her lowest power setting is FAST. The highest setting is pure madness.
But I’m hoping this translates into being able to get deal with hills ok.

Steering… will take practice.

Remote control is hilarious but scares cats.

0

So far I’ve learned:

The seat appears pretty comfortable even for my fat ass.

She’s got quite the torque. Like a Go Kart. I’m sure I’ll get used to it.

She will go through the downstairs doors. This is a plus!

Speaking of go karts, her lowest power setting is FAST. The highest setting is pure madness.
But I’m hoping this translates into being able to get deal with hills ok.

Steering… will take practice.

Remote control is hilarious but scares cats.

0

Hello Universe!

Moved to new server.

Re-introduction--Been on here for a while and should write an intro. I'm deaf, I'm a fan of open-source projects, so this will be short and sweet.

Post random ramblings, news, techie stuffs, boost mostly cat pics. I just like computers and hang around here.
Hashtags of interests:












|
|
|

|


Howdy! 👋 Boost for visibility 🙌

Energy = Milk x Coffee²
0
0
0

Special shoutout to the group that chose to map the “I need to go to the toilets” journey. Because yes, that’s also, a real and important part of the library experience.
The tool still needs some refinement, and I want to explore how it might be adapted beyond libraries, maybe for public spaces like museums or theaters too.

The team challenge during the conference was a great way to bond and create something tangible together.

I had a lot of fun, and I also loved the craft table filled with stickers, shiny gems, and all things stickable to decorate our badges. Every conference should have this.
A massive thank you to Andy Priestner, @DrBryonyRamsdenBryony Ramsden, Marisa Priestner, Julie Willems, and Andrew Alexander for the incredible organisation. To Amy Theobald for the most entertaining housekeeping announcements ever. And to my panel partner in crimes, Venessa Bennett and Joel McGeorge!

0

provides the Ports Collection, a convenient way to install applications. Some ports allow users to configure options before building and installing. By default, this configuration is done through an interactive menu in the terminal.

To improve readability and especially for users with low vision or color blindness, it's important to offer simple and customizable color options. These features have recently been implemented and documented in the preview version of the FreeBSD Accessibility Handbook:
freebsd-accessibility-9d667f.g

The next step is to extend these features to all terminal-based graphical components.

I'd love to hear from you:
Do you use any accessibility features in the terminal?
Which color-related assistive technologies make the biggest difference in your daily workflow?

Together, we can make FreeBSD more accessible for everyone.

Screenshot showing four different terminal windows running the FreeBSD Ports Collection configuration menu for Vim. Each window demonstrates a different color scheme, illustrating the newly implemented color customization options for improved accessibility. The configurations include toggles for language support and ctags options, with varying background and text colors to enhance readability for users with different visual needs.
0

I didn’t plan to write about Wayland yet. But Xorg is dying — not eventually, but now. GNOME’s dropping X11 support. RHEL already removed it. Ubuntu and Fedora are next. And if you rely on accessibility, you don’t get to wait this one out.
So here’s Post 4 of I Want to Love Linux. It Doesn’t Love Me Back.
I’m using Wayland now. Primarily. Not because I love it. Because the fallback is disappearing, and I want to be there helping fix what comes next. GNOME with Orca actually works. KDE and COSMIC are making progress. I’ve talked to the people involved. They care.
But a lot is broken.
MATE — the desktop most blind users preferred — isn’t on Wayland.
ocrdesktop doesn’t work. xdotool is gone.
wlroots compositors still don’t reliably support Orca’s keybindings, especially on laptops.
This isn’t GNOME’s fault. They’re the only reason accessibility on Wayland works at all.
But the old excuses are gone. “Just use Xorg” isn’t going to be an option much longer.
So yeah. I’m a Wayland shill now. Because I’m using it. Because I have to.
And I want to make sure we’re not excluded from what comes next.
fireborn.mataroa.blog/blog/i-w

0
0
0

Steam just added screen reader support in the latest Big Picture Mode beta. On the Deck. On SteamOS. On Linux.
Not hacked in. Not community-patched. Built-in. From Valve.
There's an accessibility tab. There's a screen reader. There's high-contrast mode, UI scaling, color filters, reduced motion, and more.
I can’t believe I’m saying this but: I need a Steam Deck now.
Accessibility isn’t just coming to gaming — it’s here, and it’s official.
Let’s make some noise so they keep going.
🔗 theverge.com/games/689922/stea

0
0
0
0

Seeing carousels being promoted as accessible again, so here is a periodic reminder:

carousels are not "accessible by default" sarasoueidan.com/blog/css-caro

They are still highly experimental and there are still many open questions & issues being discussed.

+The browser will not do everything for you—you'll still have work to do, too.

0
0
0
0