mastodon.ie

Frontend DogmaOn Dashes, AI, and Screen Readers, by <a href="https://aus.social/@onsman" class="u-url mention" rel="nofollow noopener" target="_blank">@onsman</a> (<a href="https://mstdn.social/@TPGi" class="u-url mention" rel="nofollow noopener" target="_blank">@TPGi</a>):<a href="https://www.tpgi.com/on-dashes-a-i-and-screen-readers/" rel="nofollow noopener" translate="no" target="_blank">https://www.tpgi.com/on-dashes-a-i-and-screen-readers/</a><a href="https://mas.to/tags/typography" class="mention hashtag" rel="nofollow noopener" target="_blank">#typography</a> <a href="https://mas.to/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a> <a href="https://mas.to/tags/screenreaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenreaders</a> <a href="https://mas.to/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a>

Sara Joy :happy_pepper:I'm updating our device lab computer and I see JAWS has a new major 2025 version!I may be very behind. Is this all fine? Or are people sticking largely with the 2024 one for good reasons?Thanks for any insight!<a href="https://front-end.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> <a href="https://front-end.social/tags/screenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenReaders</a>

Benrob0329Alright, I've managed to get text and HTML outputs working reasonably well tonight, and got an initial version of a text and Docx character sheet going.I'm not very good with a screen reader, but it seems to be reasonably navigable? I'm not sure what's normal and what's painful to someone using it on the daily.If anyone is interested in testing my stuff, I'd appreciate any and all feedback!<a href="https://uune.org/downloads.html" rel="nofollow noopener" translate="no" target="_blank">https://uune.org/downloads.html</a><a href="https://dice.camp/tags/ttrpg" class="mention hashtag" rel="nofollow noopener" target="_blank">#ttrpg</a> <a href="https://dice.camp/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> <a href="https://dice.camp/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a>

Benrob0329Anyone around who's into TTRPGs who uses accessibility tools like a screen reader? What's the best way to make RPG material available to low vision users? How do you approach character sheets, and how can they be designed to be more accessible?EDIT: Well this blew up-Thank you all! I have a starting point now, but I'd very much appreciate any and all feedback on what I have now if anyone's interested!<a href="https://uune.org/downloads.html" rel="nofollow noopener" translate="no" target="_blank">https://uune.org/downloads.html</a><a href="https://dice.camp/tags/ttrpg" class="mention hashtag" rel="nofollow noopener" target="_blank">#ttrpg</a> <a href="https://dice.camp/tags/accessibiliy" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibiliy</a> <a href="https://dice.camp/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a>

Matthew WhitakerFor those who use RIM (Remote Incident Manager), quick question: can you connect to an unattended computer while it’s asleep, or does it have to be on and awake the entire time?\<a href="https://dragonscave.space/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://dragonscave.space/tags/BlindTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlindTech</a> <a href="https://dragonscave.space/tags/RemoteAccess" class="mention hashtag" rel="nofollow noopener" target="_blank">#RemoteAccess</a> <a href="https://dragonscave.space/tags/RIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#RIM</a> <a href="https://dragonscave.space/tags/TechSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechSupport</a> <a href="https://dragonscave.space/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a>

Robert Thinks You’re GreatDearly beloved, add alt text to your images, especially if your post is just a reaction to something in a screenshot. That is all. <a href="https://toot.community/tags/AltText" class="mention hashtag" rel="nofollow noopener" target="_blank">#AltText</a> <a href="https://toot.community/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://toot.community/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a>

Steve FaulknerEvent handling in JAWS and NVDA by <a href="https://mastodon.world/@siblingpastry" class="u-url mention" rel="nofollow noopener" target="_blank">@siblingpastry</a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#a11y</a> <a href="https://mastodon.social/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> <a href="https://mastodon.social/tags/screenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenReaders</a><a href="https://www.tpgi.com/event-handling-in-jaws-and-nvda/" rel="nofollow noopener" translate="no" target="_blank">https://www.tpgi.com/event-handling-in-jaws-and-nvda/</a>

Dan GeroI heard people talk about how one of the down sides to <a href="https://vocalounge.cafe/tags/NVDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#NVDA</a> is not being able to use <a href="https://vocalounge.cafe/tags/Jaws" class="mention hashtag" rel="nofollow noopener" target="_blank">#Jaws</a> scripts. Never mind the addon echo system for NVDA being much larger, but I have a question. I don't know much about Jaws scripts. How feasible would it be to make a compatibility layer addon for NVDA that lets you use Jaws scripts with it? I ask because I'm not sure if scripts are compiled or not, but if they're not, a compatibility layer could fix that problem. <a href="https://vocalounge.cafe/tags/Blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#Blind</a> <a href="https://vocalounge.cafe/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://vocalounge.cafe/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a>

Mark Wyner Won’t Comply :vm:Question for accessibility folks and people who rely on screen readers.I code nav so there’s no link when you’re on a respective page. Like this:<dd>One</dd> <dd><a href="/two">Two</a></dd>But the aria-current attribute can be used with persistent links:<dd><a href="/one" aria-current="page">One</a></dd> <dd><a href="/two">Two</a></dd>Which of these, or using aria-current on a non-linked item, feels the most accessible?<a href="https://mas.to/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://mas.to/tags/A11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#A11y</a> <a href="https://mas.to/tags/UI" class="mention hashtag" rel="nofollow noopener" target="_blank">#UI</a> <a href="https://mas.to/tags/Development" class="mention hashtag" rel="nofollow noopener" target="_blank">#Development</a> <a href="https://mas.to/tags/Code" class="mention hashtag" rel="nofollow noopener" target="_blank">#Code</a> <a href="https://mas.to/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML</a> <a href="https://mas.to/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a>

Frontend DogmaFoundations: Types of Assistive Technology and Adaptive Strategies, by <a href="https://a11y.social/@TetraLogical" class="u-url mention" rel="nofollow noopener" target="_blank">@TetraLogical</a>:<a href="https://tetralogical.com/blog/2025/07/28/foundations-types-of-assistive-technology-and-adaptive-strategies/" rel="nofollow noopener" translate="no" target="_blank">https://tetralogical.com/blog/2025/07/28/foundations-types-of-assistive-technology-and-adaptive-strategies/</a><a href="https://mas.to/tags/fundamentals" class="mention hashtag" rel="nofollow noopener" target="_blank">#fundamentals</a> <a href="https://mas.to/tags/assistivetech" class="mention hashtag" rel="nofollow noopener" target="_blank">#assistivetech</a> <a href="https://mas.to/tags/screenreaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenreaders</a> <a href="https://mas.to/tags/screenmagnification" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenmagnification</a> <a href="https://mas.to/tags/keyboardnavigation" class="mention hashtag" rel="nofollow noopener" target="_blank">#keyboardnavigation</a> <a href="https://mas.to/tags/tooling" class="mention hashtag" rel="nofollow noopener" target="_blank">#tooling</a> <a href="https://mas.to/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a>

Georgiana BrummellBefore I begin, I am totally blind and have never seen. I agree with most of this, but not all of it. I simply use things that work. I never buy things without real dials or buttons, including all of my appliances. I don't need an app to turn on my microwave or use my toaster. I don't shop on inaccessible sites. Most restaurants have websites with menus, many of which are fully accessible. If I don't simply ask someone who is with me what's available, I use my computer before we get there and decide what I want, or if I absolutely had to, I would pull out my keyboard and check it on my phone. I see no issue with 3.5mm jacks, since I use them every day in my own devices. I usually just buy things online, negating the need for cash entirely, though I do usually keep some in my wallet. I have no problem asking for help when needed. I fail to see what dignity has to do with it. It's not my fault that idiots make idiotic technology.Having said all of that, on the whole, I do agree with this. Many sites are inaccessible, and in 2025, with WCAG (website accessibility guidelines) available to all, this shouldn't even be an issue. I can understand very small businesses not knowing much about these things, but some of these sites are owned by multi-billion dollar corporations (ahem, Facebook, Google for GMail and Youtube). They claim accessibility while destroying the versions of their sites that were actually accessible in the first place (Basic Mobile site, Basic HTML, and pre-2018 mobile site, respectively). The obsession with touchscreens and digital everything is also utterly ridiculous. Even cars aren't made normally anymore. I'm surprised people don't have computers to think for them! There do need to be more normal options available. Nowhere is this more obvious than with phones. Why can't we have a qwerty phone that runs the latest version of Android, works well, and receives updates in a decent amount of time? At the very least, why can't we have a phone that's a good size (around that of the iPhone SE 2016-20-22 or smaller), instead of being almost as large as a tablet! I have to carry that and my folding bluetooth keyboard around with me, and then, people wonder why I don't bring my phone everywhere and am not addicted to it? I already own one, but why can't there be more microwaves with dials sold alongside the annoying touchscreen ones? What about stoves which are completely flat and can literally kill or severely burn us? Since when did putting real burners on them become a problem? Why can't people actually say whether something such as a fan or heater uses a touchscreen or dials? Most of the time, they do, or it will say "digital controls" which is a dead giveaway, but that's not always the case. And why, in 2025, can't we have simple braille labels on products, or at least labels and bar codes that are easy to scan with ocr software?I don't work, but I also understand things from that perspective. I've heard a horror story of a woman who had a great job and did it well. One morning, she went to work and the updated software wouldn't work with her screen reader, so she lost her job. I've seen many applications for jobs that require vision, even when you think they wouldn't, or jobs that, by all rights should be doable, until, again, the software causes trouble.<a href="https://nimerblogs.blogspot.com/2025/08/congratulations-youve-unlocked-expert.html?m=1" rel="nofollow noopener" translate="no" target="_blank">https://nimerblogs.blogspot.com/2025/08/congratulations-youve-unlocked-expert.html?m=1</a><a href="https://someplace.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> <a href="https://someplace.social/tags/blindness" class="mention hashtag" rel="nofollow noopener" target="_blank">#blindness</a> <a href="https://someplace.social/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> <a href="https://someplace.social/tags/technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#technology</a>

🇨🇦Samuel Proulx🇨🇦 TIL: Google Gemini is significantly better at reading the kinds of colourful graphs you see on server monitoring dashboards than are any of the other leading <a href="https://fed.interfree.ca/tags/AI" rel="nofollow noopener" class="hashtag" target="_blank">#AI</a> models from <a href="https://fed.interfree.ca/tags/OpenAI" rel="nofollow noopener" class="hashtag" target="_blank">#OpenAI</a> and <a href="https://fed.interfree.ca/tags/Meta" rel="nofollow noopener" class="hashtag" target="_blank">#Meta</a>. Why yes, I do, in fact, resent that I had to learn this. Because <a href="https://fed.interfree.ca/tags/OpenSource" rel="nofollow noopener" class="hashtag" target="_blank">#OpenSource</a> tools don't make data visualizations <a href="https://fed.interfree.ca/tags/accessible" rel="nofollow noopener" class="hashtag" target="_blank">#accessible</a> to <a href="https://fed.interfree.ca/tags/screenreaders" rel="nofollow noopener" class="hashtag" target="_blank">#screenreaders</a> (even on the terminal) sometimes the things I <a href="https://fed.interfree.ca/tags/selfhost" rel="nofollow noopener" class="hashtag" target="_blank">#selfhost</a> to get rid of big tech just mean I have to use big tech anyway to fix them when they explode. But never the less, Google is the only AI that doesn't tell me about the menus and other Windows I captured by mistake in my screenshot, doesn't make unhelpful recommendations, and actually provides the data without cluttering it up with Emoji. But I did appreciate metta telling me "This graph shows CPU use on the X axis, RAM use on the Y axis, network use on the Z axis, and time on the fake axis." I mean, open source UI is famously terrible...but I don't think it's that terrible...yet! Shhh, don't give the data visualization people any ideas!

Frontend DogmaScreen Reader HTML Support Tables, by <a href="https://mastodon.social/@SteveFaulkner" class="u-url mention" rel="nofollow noopener" target="_blank">@SteveFaulkner</a> (<a href="https://a11y.social/@TetraLogical" class="u-url mention" rel="nofollow noopener" target="_blank">@TetraLogical</a>):<a href="https://tetralogical.com/blog/2025/07/10/html-support/" rel="nofollow noopener" translate="no" target="_blank">https://tetralogical.com/blog/2025/07/10/html-support/</a><a href="https://mas.to/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#html</a> <a href="https://mas.to/tags/support" class="mention hashtag" rel="nofollow noopener" target="_blank">#support</a> <a href="https://mas.to/tags/screenreaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenreaders</a> <a href="https://mas.to/tags/jaws" class="mention hashtag" rel="nofollow noopener" target="_blank">#jaws</a> <a href="https://mas.to/tags/nvda" class="mention hashtag" rel="nofollow noopener" target="_blank">#nvda</a>

FlorianWHY ARE drag-and-drop operations so hard for <a href="https://cupoftea.social/tags/screenreaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenreaders</a> to support? Does the drop-zone usually not include where the screen reader thinks the control is? Not a shit post, I actually am curious where this is coming from. We can suss out coordinates for left and right clicks relatively accurately, so why is left-clicking on the draggable and lifting on the drop-zone almost always going to fail? I'd get it if we go from window to window, or if the drop-zone is off-screen and needs to be visible first but even when both elements are within the viewport I don't think I've ever seen this work correctly bar maybe once, within a test where the two were literally right next to each other

ResearchBuzz: FirehoseUniversity of Wisconsin-Milwaukee: UWM professors are reimagining digital libraries for the visually impaired . “The problem is that most online platforms emphasize visuals, giving little consideration to the needs and primary senses of visually impaired users. That’s why Xie, a professor in the University of Wisconsin-Milwaukee’s School of Information Studies, is creating research-driven […]<a href="https://rbfirehose.com/2025/07/15/university-of-wisconsin-milwaukee-uwm-professors-are-reimagining-digital-libraries-for-the-visually-impaired/" class="" rel="nofollow noopener" target="_blank">https://rbfirehose.com/2025/07/15/university-of-wisconsin-milwaukee-uwm-professors-are-reimagining-digital-libraries-for-the-visually-impaired/</a>

RealZeroHeads-up if you who care about people that are blind or use screen readers (software tools that read text from the screen for you) in general:I occasionally see people use "fancy looking" text, here's a great example attached.To someone that can read it, this clearly reads "free art raffles" followed by a heart and some icons.Google's "Talkback" screen reader reads it as "Heart. Hermitian conjugate matrix."So: the heart and the name of the last icon. None of the text that is, actually, symbols, not text.Different screen readers handle this differently, but this can happen.So, if you want to treat people fairly, don't use "fancy" over "working".Sadly, the whole user profile looks like this.This is intended as well-meant info, no rant! ♥️<a href="https://social.tchncs.de/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://social.tchncs.de/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a>

ChronocideQuestion for those who use <a href="https://sunny.garden/tags/screenreaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenreaders</a> (specifically <a href="https://sunny.garden/tags/nvda" class="mention hashtag" rel="nofollow noopener" target="_blank">#nvda</a> with Firefox). How do you get the screenreader to announce the Firefox developer tools? All I seem to get is "Developer Tools frame, Inspector Panel frame, Markup View frame" and no announcement of the actual HTML displayed in the Inspector panel.Navigating with the keyboard (arrow keys) doesn't announce anything either, nor does NVDA + arrow keys.Retoots would be appreciated!<a href="https://sunny.garden/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> <a href="https://sunny.garden/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a>

davey<a href="https://mindly.social/tags/Usability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Usability</a> <a href="https://mindly.social/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://mindly.social/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> <a href="https://mindly.social/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSS</a> <a href="https://mindly.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML</a> <a href="https://mindly.social/tags/WAVE" class="mention hashtag" rel="nofollow noopener" target="_blank">#WAVE</a> Part 3 Fourth concern: skipped header levels. How disruptive is this for screen-readers? I've tried CSS-modifying header formatting, but discovered that cell phones ignore this. Example: Each page has a ~logo, consisting of a head and subhead. The subhead works best stepped two sizes down from the head. Thus, I've defined h2 as smaller than h3 . . . but my subhead looms on cell phones. Alternately, I could make the subhead h3, but then WAVE squawks because I've skipped a level. Thoughts? I'm happy to hear about standards, and I'm equally happy to hear what works for individual mastodoners.I don't know how many local visually impaired people will want my services, but regardless, it seems stinky to omit them from my potential customers.Many thanks.

davey<a href="https://mindly.social/tags/Usabililty" class="mention hashtag" rel="nofollow noopener" target="_blank">#Usabililty</a> <a href="https://mindly.social/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSS</a> <a href="https://mindly.social/tags/HTML" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML</a> <a href="https://mindly.social/tags/ScreenReaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScreenReaders</a> Part 2First, the WAVE analysis tells me my alt text often is too long. I've kept within limits someone suggested, so I wonder whether there is a variety of preferred lengths. Here are two related questions. Example 1: I show an image of a page that's relevant to what I've been nattering about. The alt text could say "Magazine page"; it could say, "Magazine column on subject XYZ published in the 1980s"; or something other. What would folks prefer? The image is shrunk so much that its content is not readable, aside from title, author, magazine, year, and callouts, so in the text just above the illo, I note that customers can request copies of pictured articles. Example 2: the pages generally are split into two columns, with significant content in the left column and context-setting eye candy in the right. Should I simply eliminate the right column for screen readers, alt=" ", or if not, how much description makes sense. I can say, "Park bench," or I can describe it--color, material, surroundings. Question 2: headers. The pages have a drop-down navigation bar, and below that H1 and H2 title/branding. Does all of this belong in the header> section, or just the <header>title/branding</header>? Question 3: The footer material is at the bottom of the left, substantive-material column. If I declare it a footer, I screw up the column layout. I could reconfigure the right column as an <aside>, but it doesn't really qualify.To Be Continued

Superdave!Still playing with GNOME 48, and notice that orca doesn't realize the items on the top bar, including time and battery state, Are not refreshed, in the screen reader, until orca is cycled off and on. I don't think this issue is particular to <a href="https://queer.cool/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a> but, maybe, someone running a different distro can confirm. <a href="https://queer.cool/tags/gnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnu</a> <a href="https://queer.cool/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://queer.cool/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#accessibility</a> <a href="https://queer.cool/tags/screenreaders" class="mention hashtag" rel="nofollow noopener" target="_blank">#screenreaders</a> <a href="https://queer.cool/tags/gnomedesktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnomedesktop</a>

Recent searches

Search options

Administered by:

Server stats:

#screenreaders