Search
Items tagged with: Orca
#accessibility question:
Does anyone know if a HTML support for Orca screen-reader exist?
(like @SteveFaulkner's tests on github.com/stevefaulkner/scree…)
#Orca #screenReader #a11y #Linux
GitHub - stevefaulkner/screen-reader-HTML-support
Contribute to stevefaulkner/screen-reader-HTML-support development by creating an account on GitHub.GitHub
From a Mailing List:
As some of you may already know, System76 is working on their new Linux graphical interface, the COSMIC desktop. They have created a form with some questions related to accessibility. If anyone is interested in participating in the survey, please access the address below:
docs.google.com/forms/d/e/1FAI…
#accessibility #Linux #foss #orca #blind
The release of #GNOME47 is imminent and our #translators have done their usual amazing work! There was a lot of #Accessibility work this cycle and #translations are a big part of that.
With a few days left, this is a great cycle to improve the user experience for non-English #ScreenReader and #Braille users.
Oh, thank goodness not having a fully functional screen reader isn’t a blocker for Fedora 41. We wouldn’t want them to miss their 10th anniversary of shipping an operating system without a fully functional screen reader, after all.
ar.al/2024/06/23/fedora-has-be…
#Fedora #RedHat #IBM #a11y #accessibility #screenReader #orca #linux #openSource #FOSS #ableism masto.ai/@phoronix/11307885166…
For Linux developers, here's a page describing some of how to make your package accessible to the Orca screen reader.
gitlab.gnome.org/GNOME/orca/-/…
#accessibility #Linux #foss #Orca #blind
README-APPLICATION-DEVELOPERS.md · main · GNOME / orca · GitLab
Screen reader for graphical applications that use the atspi protocol, via speech or Braille.GitLab
The state of Unix/Linux accessibility is even worse then I feared 🙈 . Fedora has been shipping with a broken screen reader for NINE YEARS?
Orca doesn't work on any distribution that ships with Wayland by default? 😭 (thanks @aral for bringing it my attention)
Do all the distributions and such know that next year they should be accessible?
I can't code and I am not familiar with testing desktop apps, but I would really like to know how I can help to fix this.
(allthough it shows a bigger problem in open source and it's culture)
Read more: ar.al/2024/06/23/fedora-has-be…
Luckily the Newton Project should fix this blogs.gnome.org/a11y/2024/06/1…, but still: it shows accessiiblity is often an afterthought.
#accessibility #opensource #orca #gnome #wayland #screenreader
Fedora has been shipping with a broken screen reader for nine years but the real problem is me
Fedora has an ableism problem but woe to you if you point it out.Aral Balkan
@nah @fvsch @sonny @matt But here’s the thing: Wayland would never have been made the default if, say, fonts didn’t render correctly. Not having a functional screen reader is as big an issue for people who rely on screen readers. So at some point, someone at Canonical decided that it didn’t matter that people who use screen readers would be excluded. And so they should be ashamed.
#a11y #canonical #wayland #orca #screenReaders #accessibility
So @gnome is removing the x11 session, leaving just the Wayland one.
If this goes out before Orca, the GNOME screen reader, is fixed to work on Wayland, it will mean that people who rely on screen readers will have no way to use one on GNOME. And thus on the major Linux distributions.
So I’m hoping the plan is that this change will not land until GNOME has a working screen reader.
#accessibility #a11y #gnome #linux #openSource #foss #wayland #x11 #orca peoplemaking.games/@ailepet/11…
ailepet (@ailepet@peoplemaking.games)
@noracodes@tenforward.social @aral@mastodon.ar.al @zeorin@indieweb.social For now: https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/99People Making Games
I am not yet sure, perhaps you can give me an advice regarding this however now when scrolling the map we are getting distance and the direction from the navigation point to the map center spoken along with three closest features on the map. Have we lost the ability to hear distance from the map center to those close map features?
I'm thinking the way it's working now might be usefull when used on a mobile device with the current location updated as I move around.
And ability to hear distance from the center to the map features might be usefull when browsing the map on a computer. In this scenario I'm thinking I would use the map center as a replacement for the navigation point finding out what I should do in order to move to a certain map feature.
Or perhaps this is already possible and I just haven't discovered it all. Can you please try to describe how you think it's best used?
Many of the improvements are performance-related, taking advantage of the cache of accessibility tree nodes maintained by the AT-SPI service. Table processing has received particular attention, and fundamental changes are underway in the code that handles users' keystrokes, some of which need to be interpreted as screen reader commands, with the remainder being passed through to the application.
I have been testing some of the changes along the way, as have other users active on the Orca mailing list. Rapid and precise bug reports continue to contribute to the development process. At this point, it is reasonable to expect these valuable improvements to appear in a release during the first half of 2024, presumably as part of GNOME 46.
#linux #orca #ScreenReader #AssistiveTechnology #accessibility #Gnome
Hey devs around here: how do you test accessibility?
I've been testing #mapcomplete with the #Orca #screenreader today, and fixing some issues but I feel quite unsure about it, so I'p interested in your approaches.
Or if someone who's using a screenreader could help me test (in #ghent or at #CCC), that would be appreciated
¿Pero que es esto?
Pensaba que en mis primeras horas aquí iba a tener cero interacciones y está siendo la bienvenida a una red social más chuli que he tenido 😭🩵
Os dejo por aquí a nuestra amiga la orca Gladis, reconocida atacadora de yates, y me voy a seguir dando saltitos de gratitud 🌱🩵
#GLADIS #art #MastoArt #amigurumi #orca #whale
Dear @Thunderbird ,
I know you are changing for the better. However while testing Thunderbird 111 daily I would like to see some gradual improvements so it becomes ready for most userf of Thunderbird 115 in terms of #screenreader #accessibility once it's declared stable.
Positive things I have noticed:
We have brand new message list that no longer renders all the messages in selected folder at once but only those that are visible on the screen and ready for the user interaction. From my point of view it looks similar to infinite lists on mobile platforms. Most importantly it almost fully elliminates enormous lag when browsing huge message lists on linux with #orca #screenreader running. I was curious enough and I have tested imap folder with up to 75000 messages inside.
It is still possible to use F6 and shift+F6 to move the keyboard focus from the folder tree to the message list and back.
Message list has headers that are used for sorting and a popup menu for setting up visible columns almost from the begining of Thunderbird existence. From now on these controls are finally accessible to screenreader users. And we are now able to configure sorting and show / hide individual columns.
We can still use ctrl+shift+k to show / hide the filter entry. Also there are accessible buttons alongside the filter entry that allow quick filtering the list such as labelled messages, messages with attachments, starred messages, messages from addressbook contacts, unread messages, even ability to keep the filter active when changing folders. Some of these features were already there earlier but now these are accessible to keyboard users including screenreader users.
Now features that need some polishing:
It appears we can now open individual message folders on a new tab / in a new window however this feature needs some fixes. For example when navigating using up and down arrow keys in the folder tree, pressing shift+F10 first moves focus to the parent folder and displays popup menu for that parent item instead of currently selected one.
When navigating in huge list new selection is not properly reported to assistive technologies while scrolling. For example press end to move to the last message. Now press up arrow key several times to navigate back a message and notice how screenreader is reporting new selection as it happens. Now press the page up key to move the selection by the larger increment. New message is highlighted but the selection changed event is not fired properly or it's getting mixed with some spurious focus event on an unlabelled pannel. Some screen readers are able to filter out these but I think it would be nice to address it at the source rather than working it around.
Now the main window has a lot of focusable controls and it is no longer comfortable to use tab and shift+tab to navigate. It would be nice if buttons were grouped in a toolbar like controls implementing toolbar pattern the way it's explained at
w3.org/WAI/ARIA/apg/patterns/t…
It's nice that ability to reconfigure message list columns is now fully accessible to keyboard and screen reader users however accessible name of each item in the message list does not yet respect these settings. Subject is the only content that is communicated to assistive tools when navigating in the list using arrow keys. This is major issue and will likely be considered as a regression if it won't be addressed before releasing the stable version.
When navigating in the list of messages it is possible to select multiple messages for executing actions on them. I am afraid the fact multiple messages are selected or not selected is not properly communicated to assistive tools. This is major issue for screenreader users.
It is no longer possible to use applications key / shift+f10 to inwoke a popup menu in the message list.