Luna Fox WintersThey're putting blue food coloring in everything.
A short story
https://blog.foxtrotluna.social/theyre-putting-blue-food-coloring-in-everything/
James Edwards
@siblingpastry@mastodon.world
- 283 Followers
- 94 Following
- 3K Posts
Technical consultant at TPGi, JavaScript accessibility specialist, writer, musician, neurodivergent (ADHD), vegetarian, socialist.
@heydon I totally agree, the association I’m making has no real basis, it’s just an impression, a feeling.
I get a similar feeling from the Black Country flag, which also makes me think of slavery. https://en.m.wikipedia.org/wiki/Flag_of_the_Black_Country
@schalkneethling Yeah it's always possible that your use case has identified a bug. I hope you can get it to work 🙂 @NVAccess
@heydon Not sure about this one, the fist gives off a bit of a neo-fash vibe, that could then be read as "pride in eliminating diversity"
Or is that kinda dissonance part of the point?
@fubsepude I can't directly answer your question, but I did find this thread that discusses the issue, you might find some useful tips in there -- https://www.applevis.com/forum/macos-mac-apps/how-can-you-even-use-terminal-daily-macos-voiceover-major-bugs-vim
@schalkneethling A couple of possibilities:
1. Are "Automatic Language switching" and "Automatic Dialect switching" enabled in the Speech NVDA Settings?
2. If that doesn't help or they're already enabled, maybe try a different TTS (not all of them have multi-lingual support). According to the NVDA docs, the "eSpeak NG" engine should work.
@SteveFaulkner OMFG how have I never encountered this brilliance before??
Steve FaulknerDo the WCAG
It’s a kick ass tune at any speed
https://html5accessibility.com/stuff/2024/08/01/do-the-wcag/
lloydiFriday bookmarklet time!
This is another one that I've been using myself for a long time, but not shared before. It's dead simple - it checks the page title (testing for SC 2.4.2 Page Titled (Level A)), but also looks at the page `<h1>` element (if it exists) and shows the two together.
Using ARIA
This document is a practical guide for developers on how to add accessibility information to HTML elements using the Accessible Rich Internet Applications specification [WAI-ARIA-1.1], which defines a way to make Web content and Web applications more accessible to people with disabilities. This document demonstrates how to use WAI-ARIA in [HTML51], which especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies.