I didn't think UIA was quite mature, but I am also old enough to forget Windows’ prior but somehow also current #accessibility APIs. So I may simply be wrong.
Web Platform Baseline does not track browser support for #accessibility features built into the web platform. If you need to understand whether browsers support accessibility features as your own base level set of requirements, for legal or other compliance reasons, then Web Platform Baseline does not represent a baseline.
We maken ons grote zorgen. Natuurlijk over de effecten van de inzet van gezichtsherkenningstechnologie op onze fundamentele rechten en vrije samenleving. Maar ook over de positie van het interne toezicht bij de politie. Het is tijd dat er wordt opgekomen voor de rechten en vrijheden van burgers en het interne toezicht op niveau wordt gebracht.
If you are a web developer who is not hugely familiar with the topic of web accessibility, your first encounter with it may be confusing. I’ve been there. It sucks to be presented with a list of changes to make your finely-crafted code more accessible, it can feel like scope creep, “someone else’s job”, or a critique of your work. The goal of this article is to give you tools – not more work.
This is great but can we please also have Fedora (& Ubuntu, etc.) acknowledge they started shipping operating systems without a functional screen reader when they switched to Wayland and that that’s still the case?
This is not to name and shame. Unless we acknowledge this as an error on par with shipping without monitor support and unless the culture is altered to make accessibility a showstopper, it’ll happen again.
This Should be *a huge conversation in the #Fediverse - really.
@jupiter_rowland certainly paraphrases much of the sentiment here in the Fediverse where many conversations are taking place, albeit briefly, and then dismissed, but why? Are people too busy to care? Are people too apathetic to take seriously anything that begins with the letters, masto...? Do those 5 letters really invoke such categorical dismissiveness that cuts into topics that would otherwise likely gain immediate traction were it not for mention of that corporate monolithic silo brand?
Probably; likely; perhaps - take your pick. There is indeed a general apathy amongst especially long term Fedizens and also Lemmy users who are refugees from Reddit, but it's okay to dismiss masto as the neo-corporate EEE platform conceivably threatening the UX for millions of Fedizens. And like it or not, there does need to be a viable shitposting platform, which is exactly what masto is, inhabited in very large ways by people who, as Jupiter raises the question, "are incapable of actually engaging in textual conversation. There's something to that.
Well, #A11Y is a very real concern, perhaps for the FEPs, considering there are projects that are very close in architecture to completely ignoring anything that isn't part of the W3's official specification, and that's okay.
It is, however, a misnomer that one must insert alt-text into media on the masto platform, at least at this juncture. Forcing the hand of refugees from the deprecated, #Privacy_Mining, monolithic silos is yet another complication that those poor souls need to be gently nudged into accepting - but even more importantly, ... "Why".
Some popular Android clients will complain if you try to post media without also including alt-text, some have no facilities at all for doing so. This is an adoption phenomenon, slowly being rolled out, as awareness increases (awareness of the WHY - not the HowTO) with respect to the reasons it is an important design consideration.
Do people actually get unceremoniously banned for not including alt-text for attached media on masto? Yes, On some instances they do, as if it will have any affect at all on the wider Fediverse - I have heard on several occasions that this does indeed happen - there aren't many things that piss people off more than having something that is important to them getting yanked out from underneath them in rug-pull fashion than that of an #instabanhammer, and yet childish, juvenile moderators and admins on several masto instances are truly guilty of such dystopian tyranny and abuse of privilege.
Those types of adversarial, clickish masto instances are much of the reason Fediverse gets a bad rap in some silo social networking circles, and it isn't a fair characterization, but the offensive behavior persists. More than an impetus for the deployment of #smolweb, single-user instances, it is indeed primarily a masto phenomenon.
Not a pretty thing, but masto always has been a caustic cauldron of cacophony of enmity and active vitriol, and that's just one more reason to expedite the outreach programs popping up all over the place to entice the good folks to ditch it in favor of many other good social networking platforms mentioned by Jupiter in his cw-LONG article (I wish he wouldn't bother catering to those mastoblasters with that sentiment, they should at least be smart enough to see that it's more substantive than their shitposting personas are capable of parsing).
Brilliant and overdue. So many people will be able to benefit from this #a11y work.
As a result, the IATP (Illinois Assistive Technology Program) created the Adaptive Chef’s Knife. Unlike existing offerings, it has a high-quality blade and is ergonomically designed so that the user can leverage their forearm while maintaining control.
A day meant to foster communication, education, and awareness about digital access and inclusion.
There's a huge community posting about accessibility daily. These people keep me informed and motivated to do my best every day.
GAAD is great, but it's just one day. Do what you can to keep accessibility awareness front of mind all year round. Check out the feeds below, start following some.
Happy GAAD Day, everyone! We have officially launched the crowdfunding campaign for Eventably. The world's first fully accessible events management and ticketing platform:
For Global Accessibility Awareness Day, we want to recognize the work being done on accessibility by @matt as part of the @gnome Foundation. He is the lead for @accesskit and is currently working on Newton, a Wayland-oriented solution for assistive technologies that can modernize accessibility on the Linux desktop!
The Fedora Accessibility Working Group is looking to work closer with upstream as we aim to improve accessibility on Fedora. If you are interested in joining, participating, collaborating, or sharing your experience, please reach out with the Fedora DEI tag on our forum.
Je découvre, un peu surpris, que le point médian est mal transcrit par les lecteurs de texte (notamment grâce à des posts linkedin qui remontent les travaux de @juliemoynat )
En poussant mes recherches je tombe sur “le point d’hyphénation” qui serait plus lisible par les logiciels de synthèse vocale que le point médian (puisqu’ignoré par lesdits lecteurs)
le caractère ‧ ressemble TRÈS fortement au point que j’appelais médian généré par le shortcut Cmd + Maj + F sur mon mac : · et pourtant ça n’est bel et bien pas un point médian (U+00B7) mais donc un point d’hyphénation (U+2027).
Du coup j’aimerais bien trouver le raccourci clavier pour ce point, s’il est mieux !
“Apple today announced new accessibility features coming later this year, including Eye Tracking, a way for users with physical disabilities to control iPad or iPhone with their eyes. Additionally, Music Haptics will offer a new way for users who are deaf or hard of hearing to experience music using the Taptic Engine in iPhone” #a11yhttps://www.apple.com/newsroom/2024/05/apple-announces-new-accessibility-features-including-eye-tracking/