Recent datepicker experience:
1. Control is presented as three separate spin controls, supporting the Up/Down Arrow keys to increment and decrement the value as well as manual typing. But because they're not text inputs, I can't use the Left/Right Arrow keys to review what each separate one contains, only to move between day, month, and year.
2. I tab to year.
3. I press Down Arrow, and the value is set to 2075. I'm unclear how many use cases require the year to be frequently set to 2075, but I can't imagine it's many so this seems like a fairly ridiculous starting point.
4. I press Up Arrow, and the value gets set to 0001. The number of applications for which 0001 is a valid year is likewise vanishingly small.
5. I delete the 0001, at which point my #screenReader reports that the current value is "0". Also not a valid year.
6. Out of curiosity, I inspect the element to see which third-party component is being used to create this mess... only to find that it's a native `<input>` with `type="date"` and this is just how Google Chrome presents it.

A good reminder that #HTML is not always the most #accessible or user-friendly.

So an update on Guide: I've exchanged some long emails with Andrew, the lead developer. He's open to dialogue, and moving the project in the right direction: well-scoped single tasks, more granular controls and permissions, etc. He doesn't strike me as an #AI maximalist can and should do everything all the time kind of guy. He's also investigating deeper screen reader interaction, to let AI just do the things we can't do that it's best at. I stand by my thoughts that the project isn't yet ready for prime time. But as someone else in the thread said, I don't think it should be written off entirely as yet another "AI will save us from inaccessibility" hype train. There is, in fact, something here if it gets polished and scoped a bit more. #blind #screenreader #a11y

Any fellow screen reader users successfully using @Vivaldi web browser? So far I’ve just tried it on iOS but am having some challenges. #Accessibility #A11y #Blind #ScreenReader #VoiceOver #Fediverse

Looked at the pull request interface of #Forgejo. With a #screenReader and keyboard, there's no way to jump between PRs in the list without reading the info for each one, and the diffs are even less #accessible than on #GitHub. #accessibility

This is why littering your post with emojis is stupid.

Can you guess what I'm reading about from this nonsensical #screenReader output? I loaded the webpage myself and not even I understand. #accessibility

"
heading level 2 How it Works
Slides carousel 1 / 3 slide
out of slide 2 / 3 slide graphic How it works
out of slide 3 / 3 slide
out of slide 1 / 3 slide
out of slide 2 / 3 slide graphic How it works
out of slide 3 / 3 slide
out of slide 1 / 3 slide
out of slide 2 / 3 slide graphic How it works
out of slide 3 / 3 slide
out of slide button Previous slide
button Next slide
button current Go to slide 1
button Go to slide 2
button Go to slide 3
out of carousel link app-tutorial
link App Tutorial
heading level 2 No One Does it Alone...
"

After wondering why the screen reader wasn't working with Flatpak versions of Chromium and GNOME Web, I figured I should document this somewhere

https://axel.leroy.sh/blog/how-to-fix-screen-reader-chromium-gnome-web

When I started the IC_Null channel the idea was to cover topics primarily about #cybersecurity, #hacking, #pentesting etc. from a #blind perspective. Blind as in #screenReader user, that is. But an overarching topic is showing off what jobs are (up to a point) doable for this demographic and where the obstacles are. Today's stream leans that way: we'll be looking at the premier #translation and #localization tool, Trados Studio. Supposedly they have upped their #accessibility as of late. I'll be the judge of that
I'll see you all on #youtube and #twitch just under 1.5 hours from now. https://twitch.tvic_null https://youtube.com/@blindlyCoding #selfPromo #stream #trados

#Development #Guidelines
Navigation for keyboard users · How to build a keyboard-friendly navigation https://ilo.im/162xlc

_____
#Accessibility #Keyboard #ScreenReader #WebDev #Frontend #ARIA #HTML

In-Process is now available, featuring all the info on CSUN ATC 2025, Thorium Reader, how the NVDA 2025.1 Update is going, Open-Source software and a new RH Voice Update! Read it all here: https://www.nvaccess.org/post/in-process-25th-march-2025/ and don't forget to subscribe via email: https://eepurl.com/iuVyjo

#Design #Findings
Can AI write contextual alt text? · Putting the 5 most popular AI models to the test https://ilo.im/162yi6

_____
#AI #AltText #Image #Content #Accessibility #ScreenReader #WebDesign #Development #WebDev #Frontend

Hello #Blind and #VisuallyImpaired community!
I'm having trouble signing PDF documents with a digital certificate using my #screenreader (NVDA on Windows). I can do it in Adobe Reader but it's quite cumbersome and requires sighted assistance.
Does anyone have a more accessible workflow or software recommendation for signing PDFs with a digital certificate using the keyboard and a screen reader? Any tips or advice would be greatly appreciated!
Could you please #Boost this so it reaches more people? Thank you in advance! #Accessibility #NVDA #PDF #DigitalSignature #AssistiveTechnology @NVAccess

#Chromium does not seem to "talk" to my screen reader on #Linux, is it expected behavior (they say Orca "may work" here https://www.chromium.org/user-experience/assistive-technology-support/), misconfiguration or a bug?
#a11y #ScreenReader #WebDev #Chromium

#Development #Techniques
HTML button groups for keyboard users · Keyboard-friendly ‘menu’, ‘menubar’, ‘toolbar’, and ‘tablist’ https://ilo.im/162rp7

_____
#Accessibility #ScreenReader #Keyboard #WebDev #Frontend #ARIA #HTML #JavaScript

To people who use #HomeAssistant, do you need #NodeRed to get the most out of it? Found this guide to setting up HomeAssistant in #Docker that helped me get both installed, but Node-Red's interface is pretty much unusable with a #ScreenReader, and I'm thinking of uninstalling it.
#SelfHosting #SelfHosted #RaspberryPi #RaspberryPi500 #RPi #RPi500 #Linux #Stormux #ArchLinuxARM
@selfhosting @selfhost @selfhosted

Webinar: Learn how to Create #PowerPoint Presentations as a #ScreenReader user
March 25, 2025, from 2:00 p.m. - 3:30 p.m. eastern via #Zoom. Register at: https://nfb.org/programs-services/center-excellence-nonvisual-access/events/accessibility-boutique-reg
#blind #A11Y #NFB