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)

Hi @robert , thanks for #ReCast. It is great to see a tool for audio/video #transcription. We'd like to include it in the Awesome #GTK4 #GTK3 applications list [2]. Which category would ReCast best fit? The best category seems to be #SocialSciences as transcription is used in qualitative research [1], but the examples on the recast website suggest more general purpose. Which category would you choose?

[1] https://github.com/valpackett/awesome-gtk/pull/330/commits/6efe8a83c01fb63ba8a8df7ce6fd85cf90c19fcf
[2] https://github.com/valpackett/awesome-gtk

@alvaroburns #Gnome #SocialScience

GTK 4.18 drops old GL renderer, breaking Megapixels camera app (and potentially some other apps) on PinePhones with Arch Linux (ARM), Alpine/postmarketOS edge, Fedora 42, Alpine 3.22/postmarketOS 25.06, NixOS 25.05, and Debian 13 "Trixie" systems, some workarounds include installing the Flatpak version of Megapixels, or running it in an Alpine 3.21 Distrobox container:
https://linmob.net/gtk-418-the-pinephone-and-megapixels/
(PinePhone's camera isn't the best anyways, but regardless it's sad to see it aging, it's basically the only affordable Linux phone on the market (unless you're a rich guy). Luckily I don't use a lot of apps on my phone as I prefer desktop for 99% of things, but since Google made some steps towards killing off custom roms (by restricting public access to smaller AOSP updates, and giving app devs the option to block sideloading), Linux phones have a crutial role in smartphone privacy, and it shouldn't be only for the rich. Of course, some Android phones are supported by UBports and postmarketOS but most mobile distros don't support many Android devices, users are left with less options.)
(With that being said, PinePhone has the most supported distros (20+) but ironically all of them are either unstable or has missing support for features like Bluetooth or GPS, with this dropped GL renderer, there might be even more issues in the future.)

(more Linux news in original post)
(FOSS news in comment)

Intelligent grammar & style checks
Instant publishing to WordPress, Medium, Ghost, DUDA & more
Smooth, responsive interface
Built-in goal tracking to boost your productivity
Extensive formatting options for your text.
Extensive support for importing and exporting to your favorite formats (yes, you can most likely import your project from commercial-editor-X)
and i'm not ready for a release until three other features have been implemented.

Hi @robert , Verb looks great. Is it already in a repository?

I wonder if you have thought of using #LibreOfficeKit as backend? A simple GTK4-based word processor on top of libreofficekit as backend would be great. A simple app that can display any #LibreOffice document with basic text-editing features. Together with a minimal clutter-free UI would be great. I'd use it everyday.

See (incl. prototype): https://dev.blog.documentfoundation.org/2024/06/27/libreofficekit-api-in-action/

@gnome @libreoffice #gnome #wordprocessor @gtk #gtk4 #libadwaita