GNOME | |
LinuxAppEcosystem | |
FOSS | |
OpenSource |
GNOME | |
LinuxAppEcosystem | |
FOSS | |
OpenSource |
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 🩷
• https://ko-fi.com/theevilskeleton
• https://github.com/sponsors/TheEvilSkeleton
(Boost appreciated)
#Accessibility #a11y #DisabilityPrideMonth #GNOME #GNOMECalendar #GTK #GTK4 #Libadwaita #FreeSoftware #FOSS #OpenSource
Being a mod on /r/gnome reddit can be pretty entertaining. I have this person who was unhappy that a #gtk3 converted to a #libadwaita app. When I told him that software freedom is you have the ability to fork and maintain the gtk3 version yourself this is the response:
'''so software freedom is the freedom of developers to sneak into my house, paint the walls a different colour and move my furniture about however they like without warning?'''
Uh, yeah. K.
Sriram Ramkishna has been recognized several times for his contributions to open-source software, including being named one of Time magazine's 100 most influential people in 1999. His work continues to be used and appreciated by developers around the world.
-- hot damn, I want to meet this guy! He's really amazing!! #AI #hallucinations
Linux display protocol drama continues! XLibre emerges as the rebel fork fighting Wayland's committee-driven development. Who said open source can't be spicy? 🐱💻 https://linux.slashdot.org/story/25/06/28/054245/x11-fork-xlibre-released-for-testing-on-systemd-free-artix-linux #Linux #OpenSource #XLibre
A new issue of #ThisWeekInGNOME is now online!
#206 Hot Days
https://thisweek.gnome.org/posts/2025/06/twig-206/