Search

Items tagged with: accessibility






The maintainer of the Orca screen reader, Joanie Diggs, has made noteworthy enhancements in recent weeks. I mention them here for the benefit of those who are not following these developments or who are not regular Linux screen reader users.
Many of the improvements are performance-related, taking advantage of the cache of accessibility tree nodes maintained by the AT-SPI service. Table processing has received particular attention, and fundamental changes are underway in the code that handles users' keystrokes, some of which need to be interpreted as screen reader commands, with the remainder being passed through to the application.
I have been testing some of the changes along the way, as have other users active on the Orca mailing list. Rapid and precise bug reports continue to contribute to the development process. At this point, it is reasonable to expect these valuable improvements to appear in a release during the first half of 2024, presumably as part of GNOME 46.
#linux #orca #ScreenReader #AssistiveTechnology #accessibility #Gnome



"Most importantly, tooltips should only provide descriptive and non-essential text, giving slightly more detailed text for active elements such as links and form controls. Ultimately, they provide expendable text which is already on the web page."

htmhell.dev/adventcalendar/202…

Great in-depth article about #tooltips by Jan Hellbusch. He knows what he's talking about, had the pleasure to be in one of his workshops and he's an absolute pro. 🤯

#HTML #CSS #JavaScript #accessibility #a11y #HTMHell


Adobe has just added AltText & Extended Description to the IPTC fields supported by Lightroom Classic (I requested this feature in March 2022 & just got word that they've added it). This is potentially huge for anyone who uses LR to prep images for social media, e.g. Mastodon, or the Web.

@paul Could Ivory automatically read these fields & use them to populate the alt-text on image posts? (Read Ext. Desc. first, fallback to AltText?)

iptc.org/std/photometadata/spe…

#a11y #accessibility #photography


WTH @RocketChat why the hell are accessibility features like high contrast themes only available with "Enterprise"?! Do this with things that do not exclude people based on their disabilities.

What is being done there is straight up discrimination!

#accessibility


NVDA 2024.1 Beta 1 is now available for testing. Highlights include a new on-demand speech mode, the ability to drop speech modes from the NVDA+s command, a new "native selection" mode for Firefox, bulk actions in the add-on store & ability to review add-ons & more!

Note this release breaks add-on compatibility and only works on Windows 8.1 and newer.

Full info and Download from: nvaccess.org/post/nvda-2024-1b…

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



European Commission makes statement on accessibility overlays.

"Claims that a website can be made fully compliant without manual intervention are not realistic"

"overlay tools may make a website less accessible for some users"

commission.europa.eu/resources…

#eu #a11y #accessibility #overlays #fail




Call to the global accessibility community. An overlay company won a 26,000 Euro judgment against accessibility consultancy Koena, a woman-owned 7 person shop run by @armonyaltinier. Koena was sued for sharing its opinion, as part of the global public conversation about the overlay company's one-line-of-code product.

I'm supporting Koena's fundraising campaign to raise money to appeal the judgment. Learn how you can help: lflegal.com/2021/11/overlay-le… #accessibility #a11y



Say hello to our official Telegram channel. We're slowly but surely taking steps to get closer to you and make our content accessible to everyone. Our Telegram channel will keep you up to date with the latest news, tips, app insights and device reviews straight from our website. Subscribe to us for all things Android accessibility! t.me/AccessibleAndroid #Android #A11y #Accessibility #Telegram




For the past couple of months I've been working on Pied (pied.mikeasoft.com), an application that makes it easy to use modern, natural sounding, text-to-speech voices on Linux. It does this by integrating the Piper neural text-to-speech engine with speech-dispatcher, so most existing software will work with it out of the box.

The first beta version is now available in the snap store: snapcraft.io/pied

And available as a Flatpak from pied.mikeasoft.com

(Other package formats will follow)

I'd appreciate any feedback if you're able to test it, thanks!

#TTS #accessibility #ScreenReader #linux #TextToSpeech



I am just testing @Jami with a #screenreader on both linux desktop and android for #accessibility.
Initial setup is accessible on both the platforms.
Listing conversations I can't really say as I only have single contact.
Audio calling is working fine. I am impressed that the call setup took just a moment. On android controls like microphone toggle, speaker / earpiece toggle and hangup button are working fine.
I am unable to find out in call controls with the keyboard on linux.
On both desktop and android I can write messages.
On android I can read messages, find and execute additional actions in the popup menu.
On the desktop I can't read incoming and outgoing messages with a screen reader. I haven't discovered on how to copy them.

In conclusion comparing this to the tox chat the Jami is more accessible with a screen reader. Perhaps I will be able to figure out how to handle the calls with a keyboard shortcuts however the fact message text is not readable with a screen reader on desktop linux and perhaps other platforms sounds dissapointing. The idea and decentralized nature of this communication app sounds really amazing.


The universe has cried and Kostyantin, the dev behind Whatsapp+ and Unigram+ NVDA addons, has delivered: Github-Release-Downloader, a NVDA addon that will happily download the latest release of any Github repo you throw at it. It's quite rudimentary at the moment i.e. we need to enter the URL manually, it can't handle multiple asset files etc. but I was just able to download some NVDA addons just fine. It's definitely a start.
dropbox.com/scl/fi/n7xn2fsv70c…
If you like this one and would like to support the dev, all the info you need is at t.me/unigramplus. Thanks, Kostya, and greetings to Ukraine! #NVDASR #Accessibility #Blind



156th episode of the Blind Android Users podcast has landed on your favorite podcatcher of choice. This episode features Samsung OneUI lockscreen settings, managing and clicking links in messaging apps, new image recognition feature of Jieshuo Screen Reader, and Android journey of Amir Soleimani @amir accessibleandroid.com/podcast #Android #accessibility #podcast


In-Process is out! Featuring some more NVDA 2023.3 goodies, a few other things we've been up to, a sneak peek at something in NVDA 2024.1 AND a HUGE walkthrough of Object Navigation. If you're not familiar with how object navigation works after that, I'll give you a refund on the cost of your In-Process subscription! 🤑: nvaccess.org/post/in-process-4…

#NVAccess #NVDA #NVDAsr #ScreenReader #Blog #News #Tutorial #A11y #Accessibility



I have a question regarding a semantic HTML construct, and I'd like to know what the current consensus is (if there is one). So here goes:

Should navigation links be placed in an unordered list in a <nav>?

The spec doesn't recommend anything, but examples from MDN (developer.mozilla.org/en-US/do…) and WHATWG (html.spec.whatwg.org/multipage…) consistently use lists unless the contents are written in prose. Is this still the preference more broadly?

I have some other questions in this area. Safari removes list semantics if you remove the bullets (with exceptions, such as if the list is a child of "nav"), due to alleged "list-itis". At what point do lists become inappropriate? If I have a list of blog posts, and I format them as cards, with a heading, publish date, summary, and an image, is that too much content for each <li>?

Also, MDN and WHATWG point out not all links should be contained in navs (such as footer links), and "nav" should instead signal major blocks of navigation links. Would my prior example of a list of blog posts count as a major block? Should I enclose my list of blog posts in a nav? Does that extend to all section, category, and tag pages listing pages in that section/category/tag?

Feel free to respond if you have opinions, but keep it civil, and boosts are appreciated.

#HTML #semanticHTML #WebDev #website #accessibility #a11y


Are you involved in digital accessibility outside the United States? I welcome updates to my global law and policy page - and I'd especially like to hear how laws and policies are implemented outside the United States.

I'm getting ready for Part 2 of my digital #accessibility legal update coming up on December 7. Free and online. Global page is here: lflegal.com/global-law-and-pol… You can register for the webinar here: go.3playmedia.com/wbnr-11-30-2… #a11y




So I wrote a blog post for the first time in 5 years, warning about hcaptcha's accessibility account. Long story short, they banned me from the accessibility account because I'm not blind. I am blind, but well, they seem to think not. Please boost, share, etc since this seriously affects me, and it's not ok at all. You can read the full blog post here: 4mt.me/hcaptchastory

#blind #hcaptcha #a11y #accessibility #boost



I wonder if anyone here is using or has used Humanware’s StellarTrek device for actual heavy-duty travel? I am trying to read more about its features, but cannot find too many on this website: store.humanware.com/hus/stella…
Thx for any ideas!
#accessibility #travel