Search

Items tagged with: accessibility


@Elena Brescacin For me there are multiple reasons why to prefer @Delta Chat over other similar apps and platforms.

It's free, open-source, self-hostable, respecting privacy, giving control to users rather than to someone else who might have the whole platform under his control.

However most prominent reason why it's so appealing to me is that screen reader #accessibility is being taken so seriously and actionably from the dev team. They have no contracts, no investors, no one time opportunities pushing for accessibility features and they are working on these features from the bottom of their hearts.

Do you think so called gate keepers would care to implement some of their accessibility if they have not been pushed to do so? Why do you think it takes so long to fix some accessibility related discrepancies in the most popular messaging apps?

I think this invisible message should be warmly understood by the blindness community and other communities where it makes such a significant impact.

Aren't you happy you do have verry accessible messaging app at your disposal you can freely use to its maximum?

XMPP is good however it's not yet screen reader accessible on the major platforms.
Matrix is also good it's even fully accessible technically however it still can be improved in this regard and it's more difficult to adopt. Further accessibility improvements are more difficult to get implemented when I am comparing to delta chat.

There were other attempts at a messaging app such as tox in the past that were verry promising however screen reader accessibility has never been recognized like this.




I am looking forward to going to the @w3c 's #TPAC in Kobe Japan. I will be hosting a breakout group on #ARRM — Accessibility Roles and Responsibilities Mapping — November 12th, 16:15 JST w3.org/events/meetings/76eeff8…

More about ARRM here:
w3.org/WAI/planning/arrm/

#W3C #accessibility #roles




Speaking on my behalf only, here are my two cents:

I’ve heard screen readers go at an astonishing number of words a second, much faster than I could read myself or process audibly.

To me, this indicates that it’s easier for a screen reader user to read larger texts than a “regular” reader, and thus can dive into longer threads in the same amount of time.

I have also noticed on Fedi that blind folks do not divide their texts into paragraphs.

While a screen reader needs no paragraphs, it is hard for (some, most?) visual readers to process a big blob of text without newlines.

As an ADHD person with information processing issues, I rarely even begin reading such walls of text.

Sighted users might also be less focused on retrieving information from text alone, but that is speculation on my part.

Perhaps it comes down to different ways of processing information, leading to various types of threads on Fedi.

#accessibility


#Accessibility research study wants "to engage a diverse pool of participants." Great!

The same study is limited to "Native English speakers residing in the United States." Not so good.



How is the state of PDF #accessibility on macOS for #screenReader users? If I gave someone a PDF that was prepared in a fully #accessible way, what would they use to read it with #VoiceOver, and to what extent would the accessibility be retained?

Note that I'm specifically not interested in applications that strip out all of the text to essentially make a plain version. Those can be useful when you just need to read something and don't care how, but the degree to which accessible semantics like headings, tables, lists, etc. are kept at that point is usually zero.

I'm also not asking about applications that reinvent the accessibility for PDFs and ignore what's already there, as many browsers do.




RE: mastodon.social/@ebassi/115429…

Got nerdsniped around lunchtime yesterday, and ended up implementing a shared "reduced motion" setting for GNOME and the rest of the xdg stack:

- gitlab.gnome.org/GNOME/gtk/-/m…
- gitlab.gnome.org/GNOME/gsettin…
- github.com/flatpak/xdg-desktop…
- gitlab.gnome.org/GNOME/xdg-des…
- gitlab.gnome.org/GNOME/gnome-c…

#a11y #accessibility #gnome #gtk #xdg #portals


Time for plumbing a whole new accessibility setting from desktop to toolkit: 3 hours

Time for knowing what to plumb: 20 years

Time for bikeshedding on the type of the setting: Positive infinity



Interesting, when a modal dialog (nested within a `<main>` element or some sectioning content) opens in Chrome it seems to disregard its context, so elements like `<header>` and `<footer>` will have `banner` and `contentinfo` roles as if they were scoped to `<body>`. When opened non-modally, they have `sectionheader` and `sectionfooter` (new ARIA roles + mapping) which means that it is computing the roles based on the dialog’s context.

Safari and Firefox keep the context is both scenarios (i.e. modal and non-modal). I have no idea what is correct. Need to read more.

Anyway, here’s a playground for the bug: knowler.dev/demos/MR4JmQW

#HTML #ARIA #accessibility


#Zed editor on #Windows is, as expected, absolutely, one hundred percent inaccessible. I created an issue but, honestly, I'm quite pessimistic. Splendors and miseries of #OpenSource.
github.com/zed-industries/zed/…
#Accessibility


I've been using IndentNav for a while to write Python. Recently I installed BrowserNav and now get way more positional info about HTML elements. It took some getting used to, but now the beeps and tones help me get an idea of the physical layout of a site or electron interface.
It's similar to IndentNav, but it has more rules and works with web browsers instead of being focused on code in a text editor. Positioning is one of the pieces of information that I forgot how much I miss from my sighted days. It's especially helpful with API reference docs that rely on positional encoding. Since there's more info in the browser, I only have beeps instead of precise indentation levels to get a general idea of the structure
#blind #nvda #nvaccess #browsernav #indentnav #accessibility #code




One reason I really really love running Gemini in Chrome is that it helps me to deal with many of these pesky dashboards. A press of a shortcut key, a quick prompt, and an accessible easy-to-follow summary. How is that not #accessibility? :)


Our In-Process blog is out! This time featuring:

- NVDA 2025.3.1 Release Candidate
- See Differently Tech Fest
- Typing Tutors
- Single Key Navigation Poll
- Featured Add-on: Screen Wrapping for NVDA

All this and more available to read now: nvaccess.org/post/in-process-2…

Don't follow us on social media and never saw this post? Then sign up to receive the blog via email! nvaccess.org/newsletter

#NVDA #NVAccess #Newsletter #Blog #News #ScreenReader #Accessibility #PreRelease #Typing #Poll


To #blind people with experience with #PowerPoint, I need help! My school wants me to create a #presentation with speaker notes and graphics, and I'm having extreme trouble even getting started. My info text box with my name, school, and date covers everything up, and I can't figure out moving it or how to get to speaker notes. I normally create assignments with #LaTeX, but I kept running into issues making a presentation that way. I'm on #Windows using #NVDA. Disability services made this sound doable and even easy, but so far that doesn't seem to be the case.
#accessibility #MicrosoftPowerPoint #BlindStudent @mastoblind @main


I know there is even a group about 3D printing as a blind person, but I don't know the address, unfortunately. #Accessibility


I just published a new piece: “Why Can’t Everything Be Accessible?”
Accessibility isn’t complicated—it’s ignored. We’ve failed to teach, enforce, and value inclusion in tech.
Developers, educators, governments, and companies all have a role to play.
Read and share if you believe accessibility should be for everyone:
taylorarndt.substack.com/p/why…
#Accessibility #Inclusion #A11y #DigitalAccessibility #DisabilityRights #TechForGood #AI #InclusiveDesign


"The #Orca screen reader now announces caps lock state changes, and screen readers will now describe the Shortcuts and Autostart pages more optimally. A new grayscale color filter for people sensitive to colors, developers have done a full pass to eliminate bright flashes in the UI, and the desktop zoom feature will now follow the text insertion point. Keyboard navigation has been improved, and a few other small changes have been to improve #accessibility."

mstdn.social/@osnews/115413333…

#KDE #Linux



I've just read: "Orca screen reader now announces CapsLock state changes". So... hm... emmmm.... it didn't before? till 2025? I mean... #Accessibility #Linux



I tested OpenAI’s new ChatGPT Atlas browser for Mac with VoiceOver. The built-in AI is impressive—especially Gmail prompts like “Summarize unread emails.” But major accessibility issues remain, from unlabeled buttons to missing feedback when typing.
I believe in Atlas’s potential and want to help make it better.
Read my review: taylorarndt.substack.com/p/acc…
#Accessibility #A11y #OpenAI #ChatGPTAtlas #BlindTech #InclusiveDesign


This is a perfect example of how nebulous #screenReader #accessibility is, and why it confuses so many laymen. I am looking at a web page right now that has a "Download" button. The button is an a (anchor) tag, with a div inside of it with the CSS class for a download button.
Obviously this is awful HTML, but it works fine, if you can see. There's a big fat button with "DOWNLOAD!" in all caps on the screen. Clicking this button starts the download. Seems good, no?
Well, no. This div has no actual textual content, and the anchor tag has no href or text either. So this huge honking button is entirely invisible to screen readers. How do I even begin to explain this to, say, a customer support rep? :)


Interesting. So the latest Mastodon web UI is not as accessible as previous versions. I can't turn off brows mode with NVDA and read posts with just the arrow keys anymore. #accessibility #NVDASR


Now #YouTube stopped sending emails even for comment replies. Given that the new notification experience is a mess ("Important" vs. "other"), finding new replies became an #Accessibility problem.



The Zed code editor is now available for Windows. To save anybody else wasting their time trying it with a #screenReader, it isn't #accessible so don't bother. #accessibility



Many people still misunderstand screen readers — who uses them, how they work, and what inclusive design really means.

Ela Gorla has unpacked the most common myths and what they reveal about digital accessibility on the TetraLogical blog:

tetralogical.com/blog/2025/10/…

#Accessibility #InclusiveDesign #ScreenReaders


I don't know who of you posted this theory but thanks to you and my colleague who helped me test this, I know for sure no that you can use the sound split feature of your screen reader to send just the sound of your other apps, without the TTS, while screen-sharing on meeting platforms. I tested this with NVDA and Jitsi running inside Chrome. When NVDA is on the left and everything else right, only a faint echo of my TTS could be heard most likely owing to how my headset and the jack of my Thinkpad is wired. This must mean that probably Chrome or Windows take the right channel as the mix in case of doubt and when everything has to be mono, but then I might be wrong on all of that so let's goooo! I'll have to test with other platforms. #Accessibility #A11y #Blind


There’s an accessibility bug on Mastodon: you cannot add custom alt text to your profile or header image. This means people using screen readers can’t know what these images show, so important info is missing for visually impaired users. ♿

Please help by upvoting and commenting on the issue so it gets more attention from developers 👇

github.com/mastodon/mastodon/i…

Let’s make Mastodon more inclusive for everyone! 🤗

CC @Mastodon

#Accessibility #Mastodon #Inclusion #OpenSource


OK #Blind #Linux people, is it really worthwhile to consider dual booting @elementary or at least testing it out in a VM? I’m probably not going to be able to give up windows completely, correct? What can I do natively under Lennox and what can’t I do? How is word processing, spreadsheets, making presentations? How about editing music notation? what works, what doesn’t, and what am I going to be giving up in terms of time and efficiency? Boosts appreciated and input very much welcome. #BlindMasto #BlindMastodon #BlindFedi @mastoblind @blind #OpenSource #ElementaryOS #ScreenReader #Accessibility #A11Y