Search

Items tagged with: a11y



#Blind users, users that rely heavily on #keyboardNavigation or anyone else with a preference on that matter (please indicate what applies in the comments):

Do you have a preference for or comments on the format of URLs? During user research, we have learned that URLs that are easy to handle are a good thing.

We are currently considering to introduce URLs that do not need more reserved usernames in #Forgejo, such as codeberg.org/-/something/ or codeberg.org/_something/.

#a11y #accessibility



New POUR tees just dropped!

The four principles of WCAG, plus more. You can pay money for them (3 day sale)!

Available in black or white, set in Neue Helvetica Heavy or Atkinson Hyperlegible. You can choose shirt colors.

Black Helvetica:
teepublic.com/t-shirt/73535251…

#a11y #accessibility


📣 Sei #A11y und unterstütze den Zugang zum !@metalab für Menschen mit Sehbehinderung oder Blindheit! Komm zum Do-It-Blind (DIB) Treffen 🛠️ am Montag, 24. März, Treffpunkt Ring-Passage, U3-Station Volkstheater um 16:00; Ende 20:00 metalab.at/calendar/event/7914… #make #blind #inklusion
Verbesserung: März statt Februar


Ever seen fancy italics, bold text, or even gothic letters in a slick marketing post on social media?

These platforms do not offer text formatting, so people use weird mathematical characters from the fringes of the Unicode spectrum. And because they aren't really letters screen reader software will announce them as silence or incomprehensible garbage.

@aardrian has the lodown in "Don’t Use Fake Bold or Italic in Social Media"
adrianroselli.com/2025/03/dont…

#a11y
#accessibility




You can’t say ”it’s not worth making it accessible for only 1% of our users”. That’s a logical fallacy. And reveals a lot about your understanding of the subject area, and your value system.

If you had made it accessible to begin with, people with disabilities could’ve been 20% of your user base.

And it would have been better for 100% of your users.

#a11y #accessibility


While I'm talking about games: #stardew Access is so, so close to being actually fun, with a good time freeze and autofishing addon. Unfortunately, I just can't get past the way pathfinding fails sometimes, and the way crops that are watered randomly don't update to show they're watered, and the way NPCs run around like pixies when you want to talk to them, so by the time pathfinding finishes they're already gone, and the way getting into bed is still a matter of trial and error. It makes things that would otherwise be fun into a chore. But, like, the mod itself is done well enough that it makes Stardew feel like a native #audiogame, if it wasn't for the weird bugs and issues. And the game is fully playable, from what I can tell. I just can't get into the relaxing cozy vibe when I'm trying to figure out the exact direction to approach my bed at night, or wondering why the plants aren't getting watered when I'm using my watering can right on the tile, or chasing an NPC across the map who keeps walking away from me when I wanna talk to them. github.com/stardew-access/stardew-access#a11y


Sensitive content


Navigating iOS WhatsApp message threads is becoming very difficult with VoiceOver. Management of focus position, especially after performing an action is atrocious, it jumps largely back up the thread losing your position, this happens a lot especially on a busy thread. How can we get Meta to take heed of these issues #WhatsApp #VoiceOver #Accessibility #A11Y #iOS



Saying "No-one using our service has accessibility needs" is a bit like saying "We don't need a ramp, no-one in a wheelchair has ever come up the stairs".

#accessibility #A11y



The next OZeWAI panel topic is Accessibility for Content Management Systems featuring Amber Hinds (Equalize Digital), @mgifford, CPWA (CivicActions) and Ricky Blacker (WPEngine), moderated by Brigitta Norton.

Register for the Ask the Professionals on 21 March 2025 – 12-1.30pm AEDT (UTC+11). events.humanitix.com/ozewai-on…

#Accessibility #A11y #CMS #Drupal #Wordpress


The app for the TP-Link Deco mesh system is nice and #screenreader#accessible if you're in the market for a router. More than can be said for Linksys Velop. Amplifi was okay, but the TP-Link app is actually better, at least on #IOS with #voiceover. I haven't had the system for long enough to give a review, other than that setup was quick and all the apps joined without issue. Also the default DHCP settings are weird. Who wants to start at 192.168.68.1? Changing it isn't obvious. First you have to change the lan address. Then it will change the gateway for you as part of that. Only then can you change the DHCP allocation. And even then it wants to start allocating at 192.168.0.1. That's too weird for me when the router lives at 192.168.1.1. And even after fiddling, it's still randomly assigning devices in 192.168.2. and 192.168.3.. But at least it let me reserve the devices that I need to be static. I probably have to go somewhere and do something incomprehensible with netmasks, but whatever. It's fine. #a11y




Does anyone have the #eloquence 6.1 dlls with Korean and Japanese support? I can't use 6.6 in this context because it needs to be portable and so I can't register the dll files. #nvda#screenreader#a11y Maybe @Tamasg perhaps?



Hey, #MechanicalKeyboard people! I just got myself a #Ducky One X wireless mechanical keyboard. As a #screenreader user who finds myself constantly running out of keyboard shortcuts, multi-level actuation sounded really exciting to me. Unfortunately, the browser-based programmer at duckyhub.io is entirely inaccessible. Apparently it uses a standard called #QMK or something? I don't build mechanical keyboards; I use them because I love the feedback, so I'm not deep enough into the hobby to know much about this. A browser-based programmer gave me hope that programming would be #accessible, but at least with the official website, that hope turned out to be false. So before I return this thing, do these standards mean there might be other software I can try to program the keyboard, to see if it's more accessible for me? #a11y#keyboard


Does anyone know if #LibreWolf or any other privacy focused #firefox forks keep #screenreader and other #accessibility features? Sadly, most of these projects seem to consider accessibility an unneeded feature that ads bloat and security issues and just strip it out completely, so I don't have high hopes. This just seems to be the latest one getting popular after the recent #firefox issues. #a11y




What's the state of #matrix, #xmpp and #IRC as far as #screenReader -accessible clients are concerned? Desktop (Windows, Mac) and mobile (iOS, Android).

Hoping for some input, please feel free to boost. As far as I know:

Matrix does not have a lightweight, fully accessible client for desktop, but one could be modified, such as #gomuks. On mobile, Element has scrolling issues, which is unacceptable for large rooms.

XMPP has accessible desktop clients (I used to run #Adium on the Mac), also #WeeChat. No idea about mobile.

IRC is perhaps the one which everything supports on desktop, from #MirandaIM through Weechat to the old Freedom Chat, which I could probably rewrite if I had to. Also not sure about mobile, but it would definitely need push notifications, because we can't expect people to stay constantly online on the go. #a11y #accessibility


To be clear, I don't just mean the output chooser dropdown. I literally mean every dropdown on that screen--input, output, configuration for choosing whether something is stereo/5.1/7.1. I'm glad there's an alternative for this specific case but a whole widget class not working feels like kind of a big deal. Also, the output chooser dropdown only lets you select outputs AFAIK. If I plug in a headset that isn't detected, I'll need to switch inputs too. And it was tricky configuring my media PC because I couldn't figure out how to indicate that the system I was connecting to was 5.1.

I plan to do a bit more formal digging next week to figure out whether it's just this specific screen or this widget class entirely, but I do want to fix these things. Is #a11y:gnome.org the best place to go with any questions improving the GNOME apps/widgets?

#a11y


I have a work trip next week, and my coworker sent me some simplified floor plans for the building we'll be meeting in. I printed them out with ink, then ran those through my embosser to place raised lines and shapes exactly where the ink was on the maps. I can now both feel my way around the tactile surface while using Be My AI or Meta Glasses to describe what I'm pointing at. This is pretty slick! Meta does take some extra coaxing to get useful description, though, so be warned. #A11y
#a11y


If the extent of your WCAG testing is running axe / ARC / WAVE / EAAC and that’s it, not only are you only testing ~30% of WCAG, but my own 2023 testing shows those tools catch under 15% of issues:
adrianroselli.com/2023/01/comp…

Manual testing is still a thing.

Which you need to know how to do, especially if bumping into `<canvas>`.

#accessibility #a11y


Top Tech Tidbits for Thursday, February 27, 2025 - Volume 1004 ♿️
toptechtidbits.com/tidbits2025…

The Week's News in Access Technology
A Mind Vault Solutions, Ltd. Publication
#news #technology #accessibility #a11y #disability #blind #deaf #deafblind #toptechtidbits

Top Tech Tidbits. The world's #1 online resource for current news and trends in access technology.

Subscribers: 36,455 🔢️ subscribers were sent this issue via email.