Hashtag

#Gtk

9 posts tagged with this hashtag.

Everyone, rejoice 🙌

Georges livestreamed himself reviewing and merging accessibility contributions in GNOME Calendar again, specifically the entirety of merge request !564, which introduces keyboard-navigable month cells. This means, as of GNOME 50, GNOME Calendar's month view will be fully navigable with a keyboard for the first time in its history! The only high-level goal that needs work now is conveying these information with assistive technologies properly.

Do note that the screen recording attached won't have any alt text, to avoid redundancy. Everything written below is a detailed explanation of the experience, and the recording is essentially a visual demonstration:

- When tabbing between events, focus moves chronologically. This means that focus continues to move down until there are no event widgets overlaying the current cell. Then, focus moves to the topmost event widget in the next cell or row. Tabbing backwards with Shift+Tab moves in the opposite direction.
- On the last event widget, pressing Tab moves the focus to the adjacent month cell. Conversely, pressing Ctrl+Tab on any event widget has the same effect.
- Pressing an activation button (such as Enter or Space) displays the popover for creating an event. Additionally, pressing and holding the Shift key while pressing the arrow keys selects every cell between the start and end positions until the Shift key is released, which displays the popover with the selected range.

Both merge requests !564 and !598 took us almost an entire year to explore various approaches and finally settle on the best one for our use case. Everything was done voluntarily, relying solely on support from donors and those who share these posts, without any financial backing from other entities. In contrast, most, if not all, calendar apps backed by trillion-dollar companies still don't offer proper keyboard navigation across their views. In many cases, they haven't even reached feature parity. If it is not too much trouble, please consider funding my accessibility work on GNOME. Thank you! ♥️

@Brett_E_Carlock@mastodon.online

Anyone I know good with Python/GTK, and familiar with Exaile media player?

I would like to see some changes, either as core PRs, or plugins, and can't code well enough to make them happen.

Curious to see what a napkin-math quote would be to have them coded, , natch.

1) Moodbar background and highlight theme-aware, adjustable height, faster cursor update, increased samples/track

2) Custom columns (any field, including moodbars)

3) Desktop album art size/position

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

tesk.page

GNOME Calendar: A New Era of Accessibility Achieved in 90 Days

There is no calendaring app that I love more than GNOME Calendar. The design is slick, it works extremely well, it is touchpad friendly, and best of all, the community around it is just full of wonderful developers, designers, and contributors worth collaborating with, especially with the recent community growth and engagement over the past few years. Georges Stavracas and Jeff Fortin Tam are some of the best maintainers I have ever worked with. I cannot express how thankful I am of Jeff’s underappreciated superhuman capabilities to voluntarily coordinate huge initiatives and issue trackers. One of Jeff’s many initiatives is gnome-calendar#1036: the accessibility initiative, which is a big and detailed list of issues related to accessibility. In my opinion, GNOME Calendar’s biggest problem was the lack of accessibility support, which made the app completely unusable for people exclusively using a keyboard, or people relying on assistive technologies. This article will explain in details about the fundamental issues that held back accessibility in GNOME Calendar since the very beginning of its existence (12 years at a minimum), the progress we have made with accessibility as well as our thought process in achieving it, and the now and future of accessibility in GNOME Calendar.

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

(Boost appreciated)

github.com

Sponsor @TheEvilSkeleton on GitHub Sponsors

Support TheEvilSkeleton's open source work

@TheEvilSkeleton@treehouse.systems

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

gitlab.gnome.org

Make month cells keyboard-navigable (!564) · Merge requests · GNOME / gnome-calendar · GitLab

@YaLTeR@mastodon.online

Let's do an updated ! :ablobcatattention:

In my free time I work on a mix of video-game-related projects (#speedrun and tools for ) and stack (Mutter, Shell, ). is my favorite language and ecosystem.

I like , especially Quaver (7K LN) and Chunithm. :ablobcatbongo: I also enjoyed Celeste, The Witness, The Talos Principle.

By day I'm doing a PhD in computer vision and deep learning.

Kirin are the best Equestrian creatures :blobcat: