Search

Items tagged with: a11y


#a11y







Hey. Turns out #AudioEye might be just as immoral as we all suspect:

“Lawsuit Accuses NASDAQ-listed AudioEye CEO and its Executive Chairman of Stock Manipulation”
prnewswire.com/news-releases/l…

I pulled out its CEO’s threats against the whistleblower so they are easier to read:
adrianroselli.com/2023/02/audi…

#accessibility #a11y #overlay




#a11y


NV Access are very pleased to announce the release of NVDA 2024.2! Please download from: nvaccess.org/post/nvda-2024-2/

Highlights include Sound Split, numerous new keystrokes, new Braille mode & other features, updates to eSpeak, LibLouis & other dependencies & programs.

#NVDA #NVDAsr #ScreenReader #A11y #Accessibility #New #Release #FOSS #Update #NewVersion



Do any screen reader users have tricks for locating a Youtube video's description? I was viewing this one on the web. He talks about specific audio cables he's ordering from Amazon, and there's a link to them in the description. I've tried with both JAWS and NVDA, but can't find a fool proof way to jump to a video's description, or for that matter, even get to the comments. #a11y youtube.com/watch?v=I0yFQi4b5c…
#a11y



Freedom isn’t freedom if it’s only for abled people.

Then again, there’s a reason you don’t see the word “freedom” in “open source.”

And there’s a reason “share alike” is just one of the principles of Small Technology, alongside a non-colonial approach, inclusivity, and others. (small-tech.org/about/#small-te…)

#openSource #ableism #foss #freedom #accessibility #a11y #inclusivity #SmallTech


For eight years Fedora has been shipping GNOME with a broken screen reader!

EIGHT YEARS!

(Wayland has been default on Fedora for eight years – since Fedora 25, released in 2016.)

And a hundred-billion-dollar corporation like IBM ships operating systems today based on it with a broken screen reader.

What is an ableist culture? One in which the people who call this out get ostracised.

#ableism #fedora #redHat #IBM #gnome #cosmic #wayland #a11y #system76 #linux fosstodon.org/@soller/11264637…



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.

Learn more: fedoramagazine.org/announcing-…

#Fedora #FedoraA11yTestWeek #FWD #Accessibility #a11y #Linux #OpenSource


Here's my latest update on Newton, the #Wayland-native, #Flatpak-friendly #accessibility project for the modern #FreeDesktop ecosystem, developed as part of @gnome and funded by @sovtechfund. It's not ready for production yet, but this blog post includes a demo video and links to GNOME OS and Flatpak runtime builds you can try. As a bonus, because I'm integrating #AccessKit into #GTK, GTK apps will finally have #a11y on Windows and macOS. blogs.gnome.org/a11y/2024/06/1…


@Matt Campbell @Sonny The most accessible @The Matrix.org Foundation client is now @Element. However this is either an electron app or a web app on windows and linux. Secont best matrix client when it comes to #a11y is fractal. At least I am seeing it that way. Since fractal is a native desktop app it will have its fans for sure. The fact it's very accessible is very good. Additionally I don't know but I haven't seen matrix client targetting windows that is up to date with matrix development. It's why I think fractal is closest to become one once accesskit is merged into GTK4 and fractal is built against it on windows.




Chrome / TalkBack bug I first reported in 2020, and which was fixed for a time (?) appears to be back. Looking for confirmation before I file yet another one.

A named region with a `tabindex` does not expose its contents. Chrome / TalkBack only announces its accName and role.

I think I have an ugly workaround (“Shawarma” heading).

Test case:
codepen.io/aardrian/pen/Exzyad…

Similar to issue I filed earlier this month, which I limited to APG tab panels.

#accessibility #a11y



Images without text alternatives is a huge problem. The issue is magnified when the image is a link. Realize that screen reader users receive no valuable information when the image wrapped with a link is missing a text alternative.

Ensure that all images, including those that act as link, provide appropriate text alternatives.

#DigitalAccessibility #Accessibility #A11y #UXDesign #WebDev #WebDevelopment


Oh GitHub.

@sclower filed a discussion item (with @jscholes confirming) and since I was bumping into it during a call today I also made a video:
github.com/orgs/community/disc…

A lot going on here:
• Verbose.
• The instructions sometimes lie.
• Some triggers are a problem.
• Fake-dialog has issues.
• Those are links, not disclosure triggers.
• Verbose.
• Also, verbose.

#a11y #accessibility



Congratulations to Oko for winning the Apple Design Award in the inclusion category. Oko uses your phone’s camera and some machine learning to let blind and visually impaired travelers know the status of traffic signals. #a11y

applevis.com/blog/oko-accessib…

#a11y


I am not the only one to say this:

Please remember that WCAG itself is the bare minimum of #accessibility. Conforming to WCAG does not guarantee something is accessible. It does not even guarantee something is usable. All WCAG does is provide you with a starting point. Lots of WCAG failures suggest the page has not even made it to the starting line.

Which I say at the end of this post comparing free automated WCAG testing with manual testing:
adrianroselli.com/2023/01/comp…

#a11y



All these discussions about captcha and #accessibility are the demonstration of how reality is infected by inclusion-washing and performative activism. Everyone to talk about #PrideMonth in June, disability day in December, #a11y day #gaad in May, but then facts are always where they've always been: in 1999 or before. With illusions to solve it all with some out-of-box solution. (1/2)


For blind people like me, if AI solves a captcha it's a miracle, not a problem. Companies should rethink client-based human verification; captcha is a discriminatory message. If you -company- experience fraud, it's not my responsibility to tell you I'm a human. It's your responsibility to protect me SERVER side, not placing a guardian with the gun at the door who kicks me out if I'm blind, deaf or cognitive impaired, because I can't solve the quiz you implemented. #accessibility #a11y


In this 5000+ word tome, I walk you through every button, toggle, and slider in Overcast. I’m hoping that @marcoarment checks my work and tells me if I made any egregious errors (and doesn’t mind my editorializing as I do the walkthrough.) Also - it's accessible with VoiceOver!

How to Use Overcast as Your Podcatcher of Choice podfeet.com/blog/2024/05/overc…

#a11y


This generative model allows you to sketch out a scene with a few words, it then leverages an LLM to flesh out the details, with the ultimate goal of feeding those details to a downstream visual image generation model.
It is almost, but not quite, entirely the inverse of image captioning models.
This offers the closest experience to an image generation tool that's usable by people with visual impairments.

huggingface.co/spaces/lllyasvi…

#a11y #genai #llm



NVDA 2024.2 Beta 3 is now available. As well as all the amazing things already announced, changes in Beta 3:
- Disable style navigation in Microsoft Word
- Add section on Add-on Store to Quick Start Guide
- Fixes for using Poedit with all plural forms
- Minor fixes for sound split
- Minor documentation fixes
- Updates to translations

Read the full what's new and download from: nvaccess.org/post/nvda-2024-2b…

#NVDA #NVDAsr #ScreenReader #News #FOSS #Update #Accessibility #A11y #Beta


I've just pushed a bunch of #accessibility changes for screen readers to the main branch of FediThready. ( It makes long texts into post sized chunks)

I've run through it with #VoiceOver and it _seems_ ok. HOWEVER it all feels like it's "usable" instead of "good".

If there's a #a11y geek out there who uses screen readers regularly I would REALLY appreciate some suggestions on how to make this actually feel good for folks who rely on screen readers.

github.com/masukomi/fedithread…


Three tips for reporting inaccessibility to companies.
1. Be as specific as you can and provide solutions if possible.
2. Provide resources for developers to learn more about accessibility. In most cases, companies are just unaware of the needs of disabled users.
3. Include how to replicate the accessibility issue and what you think should be happening if the issue is not present.
Learn more in our self-advocacy toolkit. nfb.org/programs-services/cent…
#Accessibility #a11y