#screenreader
Any Logeion user around here who regularly uses a screenreader?
November 10, 2026 at 3:03 PM
Ich mach die Antworten mal zu, weil der Post gleich die Bubble verlassen wird und dann kommen wieder Leute, die nicht wissen, wie das Suchfeld funktioniert oder über Screenreader diskutieren wollen.
November 7, 2026 at 10:15 AM
Thank you! I don't use a #ScreenReader, but know people that do. This is super helpful.
November 5, 2026 at 10:30 PM
November 9, 2026 at 2:31 AM
I'm determined that even if you need a screenreader you still get to know what the image is and you still get a laugh out of it.
November 6, 2026 at 3:00 PM
Alle Jahre wieder
November 6, 2026 at 7:58 AM
Soweit ich weiss, klingt beides nicht gut, weil nach dem Zeichen dann ne Pause kommt.
Auch AFAIK gibt es inzwischen auch Screenreader, die du in die Richtung etwas konfigurieren kannst.
November 7, 2026 at 3:43 PM
they do HTML great, actually, but alt itself doesn't support it. (There's a fascinating & gnarly bit of W3C politics history about that.) Whether or not a screenreader announces uppercase or reads it differently depends on screenreader and user config, but by default they generally don't.
November 11, 2026 at 6:13 AM
That's a very good point, I imagine a screenreader probably makes it a big ass run-on sentence otherwise?
November 10, 2026 at 5:18 PM
Ich hatte mal eine Umfrage und das * war für Screenreader etc nie ein Problem. Und da Betroffene das Sternchen bevorzugen, nutze ich das.
Gab kürzlich mal einen Faden dazu. Mal schauen, ob ich den noch finde.
November 9, 2026 at 11:18 AM
BFSG-Tipp für Shops: Icon-Buttons wie Warenkorb, Suche oder Menü brauchen einen zugänglichen Namen. Sonst hört man im Screenreader nur „Schaltfläche“. Prüfen Sie per Tab-Taste und Screenreader, ob jeder Button sagt, was er tut (WCAG 4.1.2). Abhilfe: sichtbarer Text oder aria-label. #BFSG #a11y
November 10, 2026 at 10:09 AM
🧵 Wondering if any other screenreader users or #a11y folks have better ideas for a journalist who wants to do right & is confronted with the reality of a medium where we convey complex legal text through screenshot but image alternatives lack semantic markup so #accessibility is inherently limited.
So, alt text people, how are you supposed to deal with highlighting in a long screenshot with alt text?

Sometimes I UPEPRCASE THE HIGHLIGHT but also sometimes I wonder if it would be better to only include the highlight in the alt text. cf. bsky.app/profile/john...
Is it bad that when I saw this, my first thought was, "did they not read the docket???" about which case to file into?

« But I suppose *technically* a motion is not a "pleading," merely a paper (but FRCP 7(b)(2) "The rules governing…matters of form in pleadings apply to motions and other papers." »
November 11, 2026 at 4:04 PM
Screenreader erkennen Alttext und lesen diesen dann ebenfalls vor.
November 4, 2026 at 1:11 PM
I think it's one of those deals where the more tasks a thing does, the less good it is at each one. Could we make a screenreader do that? Probably? But I can think of several reasons to just not do that and let it be perfect at reading actual text.
November 8, 2026 at 6:13 AM
We have all this AI and yet we don’t use it to automatically generate Alt text? I mean, human generated will clearly be better, but if we must have AI, at least help the screenreader peoples.
November 8, 2026 at 11:28 AM
In our latest #ScreenReader Survey, JAWS remains the primary desktop screen reader at 55%, followed by NVDA (32.9%) and VoiceOver (6.5%). Reliance on JAWS increased, while NVDA and VoiceOver declined. Do these results surprise you? What are your thoughts? #a11y #WebDev webaim.org/projects/scr...
November 10, 2026 at 3:09 PM
This was the point when I realised MS were not fully committed to accessibility as they previously claimed. the menu key is used frequently by screenreader software.
November 9, 2026 at 8:42 AM
Könnte ich. Aber für Leute mit Screenreader steht dann da:

RotesHerz RotesHerz RotesHerz RotesHerz

Und das etwa 20 Mal. Das will ich denen nicht antun :D
November 5, 2026 at 6:39 PM
WordPress verbessert Fokusmarkierungen, Screenreader-Links und Touch-Zielgrößen. Gut so. Aber Accessibility entsteht nicht durch ein Update allein: Komponenten, Formulare und Inhalte müssen im Projekt getestet werden. Wann habt ihr eure Website zuletzt nur mit Tastatur genutzt?
November 10, 2026 at 8:30 AM
WordPress verbessert Fokusmarkierungen, Screenreader-Links und Touch-Zielgrößen. Gut so. Aber Accessibility entsteht nicht durch ein Update allein: Komponenten, Formulare und Inhalte müssen im Projekt getestet werden. Wann habt ihr eure Website zuletzt nur mit Tastatur genutzt?
November 10, 2026 at 8:30 AM
I didn't know you could drag images out of Bluesky; didn't try before. Thanks! I don't know if it would work for anyone who uses a screenreader; the dragged image doesn't have copy/pasteable text as such.
November 5, 2026 at 9:33 PM
For JS SPA/SSR frameworks, move focus to the h1 on route changes for keyboard and screenreader a11y. Exclude back navigation to preserve scroll restoration
www.a11yflow.dev/blog/focus-m...
November 5, 2026 at 7:10 PM
Tipp für Shop-Betreiber: Prüfen Sie, ob jedes Formularfeld im Checkout eine sichtbare Beschriftung hat – nicht nur Platzhalter. Screenreader und Nutzer brauchen dauerhafte Labels (WCAG 1.3.1 / 3.3.2). Platzhalter verschwinden beim Tippen und reichen nicht.

#BFSG #Barrierefreiheit #a11y
November 6, 2026 at 10:24 AM
Reusing "Read more" as the link text for each news item makes our code and content management simpler, but it provides bad usability for screenreader users. Hidde de Vries
November 8, 2026 at 1:27 AM