Fedora: “The Fedora Quality Team is joining Week of Diversity with an Accessibility Test Week!
Much like other Test Days, the goal of this week is to put Fedora through its paces and catch as many accessibility related issues as we can for our disable users.”
Me: Fedora, your screen reader is broken.
Fedora guy: Patches welcome 👍
Me: reaches for block button
From the actually-what-you’re-referring-to-as-ableism-is-GNU/ableism department
Background: It’s not just Fedora. Every Linux distribution that ships with Wayland by default – and that’s almost every major Linux distribution – ships with a broken/unusable screen reader at the moment.
(Read that again until it really sinks in. Yep. I know. Uh-huh. Really.)
The Fedora Quality Team is joining Week of Diversity with an Accessibility Test Week!
Much like other Test Days, the goal of this week is to put Fedora through its paces and catch as many accessibility related issues as we can for our disable users. If you want to put your advocacy to action, consider participating!
The Accessibility Test Week runs from Jun 19-25, starting tomorrow.
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.
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!
@FediTips I'd love to see an article containing tips & tricks to improve #accessibility when using an instance's website and popular mobile clients. A couple of suggestions... stress how important describing media is for equal access & what options might be available in an instance's settings that could improve accessibility for a user. I know I'd certainly appreciate the tips, and imagine others with various disabilities would as well. #A11Y#EqualAccess
I'm looking for benchmarks.
For @mucConf we want to provide accessibility information online.
Please send me links to events/conferences that did a good job communicating accessibility information!
>>
Our mission is to ensure that machine learning masquerading as intelligence benefits us, the shareholders of exploiting your content, while the returns to you dwindle roughly in line with the degradation of habitability that we are accelerating.
…“Sorry, we couldn’t spend any of our ridiculous market over-valuation on a decent web designer, or on a developer who had any care or clue about keyboard accessibility, we were too busy stealing your content and screwing your future.
And by using Tailwind to implement crappy design patterns, we have even more time to do that. Another win for us”
A brief reminder that our Call for Presentations for the next #id24 (scheduled for 12 September 2024) is still open until 7 June https://inclusivedesign24.org/2024/
(and a small note: have an idea for a talk, but perhaps you're not comfortable doing a whole presentation in English? let us know anyway ... in the past we've had a few presentations in other languages, so it's not necessarily a hindrance)
I've been working on a subtitle editor plugin for #peertube !
It adds a extra button on the update video page, and can do most of what you find in other tools, like visualize audio, basic formatting, and makes it easy to switch language.
The goal is that it should be "good enough" for most who just want to add subtitles/captions, but don't want to spend time finding and downloading dedicated software for this.
Instance administrators can install it via the plugin page. #accessibility#a11y#foss
A Tumblr post by DracuDyke. I honestly do not know how applicable this is outside of Tumblr, particularly on the Mastodon/Misskey/Pleroma, etc. side of the Fediverse. I do know that most such instances don't provide the requisite character count to pull this off. Heck, I had to break up the screenshot because there wasn't enough room for all of the alt text if I left it intact. (Yes, I know the character count for toots vs alt text are entirely unrelated to each other. There's no way I could make this a single toot on my main account.)
Also, does anyone know what "PT" stands for in this context?
Is only Alt Text enough?
[PT: Is only Alt Text enough? End PT.]
If you post something and include an image description in the alt text, that's great! But it would be even better if you included a description in the body of the post as well. Alt text doesn't always work, especially on a platform as broken as Tumblr is. An image must also load fully before the [ALT] button shows up, so people with Internet issues won't be able to see it for a long time. It also requires pressing on the small [ALT] button, which may be difficult for people with motor issues. The point I'm trying to make here is that the ability to access and read alt text is conditional, not a given. Putting the image description in the text of the post helps it be accessible to everyone.
"Okay, well can I at least put it under a readmore?"
[PT: "Okay, well can I at least put it under a readmore?" End PT]
No! If your blog or the original post is deleted, that readmore is gone forever! It also presents an extra step, another thing to push. This can be difficult for a number of reasons! I have also heard that readmores are difficult for some screenreaders, but I can't remember for sure.
"Can I at least make it pretty?"
[PT: "Can I at least make it pretty?"]
No! If you write the image description in small text, italics, bold, colored text, or other fonts that makes the description harder to read! That defeats the purpose! It can also be hard for screenreaders to read certain kinds of text, especially unicode or other fonts.
TLDR: Please include your image descriptions in the body of the post as plain text. It's the best way to make sure your post is actually accessible to everyone!
Just rebooted and I’m up and running with Fedora Silverblue 40.
(Just tried reinstalling mozilla-openh264 – so videos work in Firefox – but it failed with the same error. Not a big deal, I’m using @Vivaldi as my main browser these days anyway and I guess the Fedora folks will fix this in time.)
More importantly, I wonder if the screen reader has been fixed yet. (Yes, Fedora ships with a broken screen reader.)
At least 3 things missing from UC's Global Accessibility Awareness Day event:
The idea that there's any accessibility issues beyond the type digital technology tools could potentially help with
and
Actual diversely disabled UC community leading the event.
Statement up front as to what accessible options are available for this event.
Keeping the emphasis on digital tools allows abled people to continue their hegemony by simply training to be "experts" on accessibility, keeping jobs & control in abled hands. It allows UC to keep refusing to hire human captioners, human notetakers, as well as keep NOT addressing making things as accessible as possible as the default at UC.
We're #hiring a remote, full-stack #Drupal developer! We build Drupal & WordPress websites for nonprofits, with a content strategy & #a11y focus. We have a 35-hour work week, 5 weeks+ paid time off annually to start, & an intentionally-small, sweet, collaborative team. We are woman- and queer*-owned and led.
Must be US-based b/c we're small don't @ me we are doing our best I assure you.
⌛ Good morning from sunny Nuremberg! We're excited to announce one last call for presentations for the #Accessibility Club #Summit in #Amsterdam. If you have a passion for #a11y and ideas you'd love to share, we invite you to submit your presentations before the deadline on Sunday, 14 April 2024, at midnight. Join us on 8 June at the Amsterdam University of Applied Sciences to inspire and be inspired. Your contributions are eagerly awaited!