for this episode of my series, the new #zrythm release brings some accessibility fixes, of course, more to come soon

* the splashscreen is now accessible.
* the tracks now have context menus accessible with the application key and they are named after what they contain
* some more controls have been labeled as far as I could see
#IHelpedMakeAccessible

* many buttons are labeled now. Those that aren't, will be soon
* discovered and fixed a bug in libadwaita which could cause focus to get trapped in a button
* fixed libpannel issues which cause unlabeled buttons
* add labels and a11y roles to some custom widgets, switch unnecesary custom widgets to gtk native ones

https://flathub.org/apps/org.zrythm.Zrythm

#IHelpedMakeAccessible

next in the list, #zrythm
Zrythm(zrythm.org) is a linux native daw, written in gtk. Currently, you can't yet compose music with it, but we're getting there. Here's what's been fixed since I went on board with it:
#IHelpedMakeAccessible

let's begin. I'm not putting this one in a separate thread, because it's the first one
the first app in this segment is #pipeline this is a youtube and peertube frontend, written in gtk. It's currently almost entirely accessible, except that the list isn't working very well, as in some controls are skipped, but if you go back, they're there. This issue will not be relevant soon, as the dev will switch to a context menu approach from what I heard.
https://flathub.org/apps/de.schmidhuberj.tubefeeder
#IHelpedMakeAccessible

So then, here's the convention I'm gonna follow:

1. All posts about this should be easily discoverable, so I'm making a hashtag which is distinguishable from the noise, one y'all can subscribe to and boost what you find for more coverage if you want. I thought about #IHelpedMakeAccessible, ideas welcome