CIRCLE WITH A DOT

Seeing how many new things we can date with an improved accessibility mod https://twitch.tv/object_inspace

RE: https://flipboard.com/@pbsnewshour/headlines-81am25uuz/-/a-i9g2MRarSMqYHeRBwmbQQg%3Aa%3A2651838374-%2F0

LOL

I've spent entirely too much thought on the optimal contact sharing device.

Business cards suck. I have stacks of them, I never remember why or how I got them, I have to transfer them into my contact list by hand and never get around to it. I'm sure others feel the same. NFC cards are better but the providers are all vultures who want to lock you into a subscription, put their branding on your stuff, or both. Plus if you give someone a card, they think they should keep it. That's no good! Them keeping your card is afailure state, you want it in their address book. Shrinking it down makes it cheaper and means there's no space for any branding.

The tag and the QR code both simply open a URL. Tiny URL, tiny QR code. Dub makes 14-character URLs, which can be clicked up to 1000 times a month on the fre plan. I'm hosting it on github pages, which I already have and is also free.

The site has four things: my bio, a button to download my VCard, a mailto link that launches their email client, and an SMS fallback. From the email, they can attach their vcard, fill in their own contact information, or send it as-is and get the name, email address, plus whatever might be in the email signature. An SMS is a bit shakier but has much the same idea.

This interaction should take twenty seconds max, cost me nothing beyond the tags (which are super cheap) and the data only gets stored in my email, where I want it. A privacy win and I'm not relying on third parties I can't easily replace.

@indivisibleteam NYT called that "standing up to Trump" clowns

@RossMinor Someone has a huge list of accessible games on github, of all the playce. Not sure why they are doing it this way. But probably a good resource to spin up, you know, which games shoud have pages, and then someone can fill them in later or something like that. https://github.com/Molitvan/blind-accessible-games-list/

@RossMinor Welcome to the fediverse, slowpoke!

@vick21 In my future, the government will provide all interview participants with drones to silently hover a Hile PR40 between 2-4 inches from their faces.

@Rosalyn @kirch @WeirdWriter https://www.youtube.com/watch?v=Yrst8gmd9Cw

@RnDanger @zersiax @WeirdWriter YW! One of the many valuable services I provide the fediverse.

@zersiax @WeirdWriter And he's not an accessibility advocate, he knows nothing about it. He is a "human interface consultant," which is a fancy way of saying substack blogger. Totally different gig.

@zersiax @WeirdWriter Please don't. He gets enough attention as it is.

@kirch @WeirdWriter Devs/laws move too slowly! I need my access now. NOW NOW NOW NOW NOW NOW NOW!

@SaraSoueidan @murtaugh They won't. They'll just tell the Google machine, because that's how people get information now. Learn the Google. Love the Google.

@WeirdWriter https://www.uxtigers.com/post/accessibility-generative-ui (CW: stupid)

@Scott @stevo399 I believe there is a verbocity setting to turn off the clickable announcements. Not this excuses them.

RE: https://tomkahe.com/@GiftArticles/116613432671595981

mad King Jeoffry

@fastfinge NVDA publishes in-process updates every month and a roadmap at least once a year, describing their plans for future work. In fact they just posted the most recent one this month https://www.nvaccess.org/post/nvda-roadmap/

@cachondo @NVAccess @MostlyBlindGamer

@fastfinge How-ever, if I understand correctly, you want them to be more proactive about solicitting community feedback. Frankly there are pros and cons to this approach: it slows down development and leads to fiascos like when they tried adding a sound pack, everyone faffed around for months without settling on something they liked, and ultimately it got closed with no action taken. Maybe you liked that outcome because it's better suited for an add-on. In any case.

As I said earlier, public communications can be a job in itself. Considering the size of the team and the various tasks they have before them, what level of reach-out do you consider appropriate?

@cachondo @NVAccess @MostlyBlindGamer

@fastfinge The "magnifier" (which mostly extends the windows magnifier and then calls it, as I understand) got into core because people asked for it. Image descriptions were taken out of core, because people didn't like them. All of which happened in public.

I do take your point about it being hard to predict the outcome of decisions made about what is or isn't accepted. But there is also the roadmap, product vision, and contributor guide, which seems like a reasonable place to frame any future discussions on what should or should not go into core, which you are of course free to start whenever you feel the need. 1/2

@cachondo @NVAccess @MostlyBlindGamer

@fastfinge Again, the reason no discussion is happening is because you keep circling back to "no discussion can happen" after being pointed you to the discussion that happened, and being invited to ingage further on said discussions. You don't like that the magnifier is in core? Okay. I don't like that the magnifier is in core. So leave an issue comment. A response will be forethcoming. If the nature of that response is unsatisfactory, then you write the blog post.

I don't think you are being intentionally disingenuous, I'm sorry I said you made up the stuff in your post. I should not have. But imagine if someone, out of nowhere, wrote up a huge essay about something you did a year and a half ago, didn't ask you about it first, and signed off with "ultimately, the problem is trust." You would feel attacked by that, especially if it was your livelyhood. An open letter format comes off very aggressive to me, as an observer. I'm clearly not the only one who took it that way.

@cachondo @NVAccess @MostlyBlindGamer