André Polykanine

@ruemaleficent I'm not autistic, but I cringe every time I have to listen to them talking with loud speaker on. I don't know where that fashion came from, but it's horrible.

For anyone who uses 1Password, and who has read about Universal Sign In. I've just been offered it and it does seem to be accessible. I certainly cannot see any issues using it with Windows and JAWS.
As I understand it, when you arrive at a website’s login page, 1Password displays one prompt near the top of it. That prompt gathers together the different ways you might be able to sign in:

A username and password
A passkey
A password followed by a one-time verification code
“Sign in with Google,” Microsoft, Apple or another provider
A company’s single sign-on system

You choose the appropriate account, and 1Password attempts to complete the whole login process—including moving through multi-page login forms and submitting the information.

Suppose you visit a website where you originally registered using “Sign in with Google.”

Previously, you might have needed to remember that you used Google, find the relevant button and then choose the correct Google account.

With Universal Sign-In, 1Password can present that saved method in its own prompt. You select the account and it presses the appropriate website button and handles the subsequent steps.

For an ordinary password-based account, the difference is less dramatic: 1Password fills and submits the username and password much as it did before, but presents the process through the same Universal Sign-In prompt.

What is genuinely new?

There are three principal improvements:

One consistent interface: passwords, passkeys and third-party sign-in methods are presented together.
Better recognition of login pages: 1Password has improved the way its browser extension identifies username fields, password fields and buttons such as “Sign in with Google.”
Better login addresses: if your saved item contains only a website’s homepage, 1Password may now know the address of its actual login page. It currently has this information for more than a thousand popular websites.

If you generally use conventional usernames and passwords and are already comfortable activating 1Password from the keyboard, this is chiefly a change to the interface rather than a major new capability.

It will matter more to people who:

Use several accounts on the same site
Frequently use passkeys
Cannot remember whether they selected Google, Microsoft or Apple when registering
Encounter complicated login forms spread across several pages
Want 1Password to locate the correct login page automatically

Your existing vault items do not need converting or resaving. The feature is included in the latest 1Password browser extension for Chrome, Edge, Firefox and Safari.

Socialism and Christianity are completely incompatible.

We only need to do a quick search of Socialism’s history. For example, the word ‘Nazi’ is an abbreviation of the German term "Nationalsozialist. The term refers specifically to the National Socialist German Workers' Party, which was led by Adolf Hitler.

And let us not forget the USSR – the abbreviation of the Union of Soviet Socialist Republics.

I want to be clear about this: Voting for politicians who call themselves Socialists is like signing your own death warrant and the death warrants of everyone you know and love who faithfully serves Christ.

Prove me wrong.

If you have come across a black cat. Pet it. If it will let you. It’s not bad luck

So today I worked on an interesting project.
One of our customers is a Dragon and J-Say user and is completely reliant on using her voice as she cannot use the keyboard.
She needs to work a great deal with custom applications which are complex in layout and also Outlook Classic to find messages within specific date ranges, and then respond to them.
So I set up the ChatGPT app for her and we worked with the Computer Use element of it which I detailed here on Sunday.
Now, she can ask ChatGPT to do a lot of this work for her. J-Say works well in the ChatGPT app, so she can ask it to do things like:
Create a task in this application with the subject of, followed by the subject.
Summarise the details of all messages received within the past three days.
Open the third of those messages and reply to it, saying I will send a full response within 48 hours,
Etc.
There's still a lot of work to do but it's a fun project and is going to be of great value.

@jpoesen For me it doesn't work. I won't mention its accessibility is suboptimal, to say the least, but they have been verifying my account for half a year instead of one day. "We'll contact you if any additional information is needed". #Mollie

Hallelujah! #Google fixed password autofill #Accessibility in #Chrome! Coooool!

Just submitted this to Google accessibility support. What the actual hell is this timeline?

If you use TalkBack and navigate by exploring by touch rather than swiping, when you drag your finger over the player controls while a video is playing in the YouTube Android app, within seconds the entire app dies with a `StackOverflowError`. Over 4,500 frames of pure recursion before the 8 MB stack runs out.

Naturally, the app restarts, immediately reloads the exact same video and player state, and the second you touch the screen again to find the pause or seek controls, it blows up again.

I pulled `adb logcat -b crash` and it's a ridiculous infinite loop between Android's framework and Litho:

`View.dispatchTouchExplorationHoverEvent`.
-> `TouchDelegate.onTouchExplorationHoverEvent` (framework forwards hover event to delegate).
-> `ComponentHost.dispatchHoverEvent` (Litho forwards back to host).
-> `hdu.onTouchExplorationHoverEvent` (obfuscated TouchDelegate subclass.)
-> and back around forever.

From the looks of it, a `TouchDelegate`, presumably meant to enlarge the tap target for one of the smaller player controls, was given a delegate view that points right back to the `ComponentHost` that owns the delegate in the first place.

The best part? Normal touches don't hit `dispatchTouchExplorationHoverEvent`. Sighted users will never encounter this, and even blind users swiping through elements one at a time won't trigger it because linear navigation doesn't emit hover events. It strictly breaks explore by touch. Conveniently, the exact interaction model a huge chunk of us rely on to quickly locate controls.

I handed them the exact cycle, device specs, and the obfuscated frame name for build 21.34.243. Now taking bets on whether an engineer actually sees and fixes the root cause or if support tells me to reinstall the app and clear my cache.

N’importe qui peut prétendre faire un audit d’accessibilité numérique, alors comment faire confiance ?

Eh oui, l’expertise-conseil en accessibilité numérique n’est pas une profession réglementée.

Je vous donne des pistes de réflexion : formations et certifications, expérience, façon de faire un audit, possibilité de demander un exemple de grille/rapport d’audit, tests à réaliser sur le site du prestataire…

#accessibilité #RGAA #a11y

https://www.copsae.fr/nimporte-qui-peut-pretendre-faire-audit-accessibilite-numerique/

Think of AI as a brilliant, eager intern who just walked in. Knows a staggering amount about the world, and absolutely nothing about you.

Every single thing it needs, you GET to hand it. That is not a limitation. That is power. Use it.

No Sight Required.
#AI #Accessibility #Blind

@daltobr claude, definitely. A huge code helper, and not only in code, btw.

SharpLouis, my #LibLouis #DotNet wrapper, is updated to version 3.0.0.
Main changes:
* Updated to LibLouis 3.39.0 that was released yesterday.
* Now the Braille translation table metadata is fully handled. for example, some tables have several languages, like Israeli Braille table has Hebrew, Arabic and English, and now `FindByLanguage()` will return those. Also, missing fields like region, grade, system, version, unicode-range, variant are handled by the wrapper.
NuGet: https://www.nuget.org/packages/AccessMind.SharpLouis
gitHub: https://github.com/accessmind/sharp-louis
Do you like my work? Please donate. https://oire.org/donate/. Thanks!
#Braille #BrailleTranslation #Wrapper

Currently working on improving the accessibility of PitchNet, an open source alternative to plug-ins like Melodyne. Thanks to CodeX got a preliminary version working in about an hour or so, but I'm not sure if I like my implementation. I'll probably end up releasing the code on GitHub anyways after I do a little more work, but here's the original repo in case anyone who actually knows what they're doing wants to take a crack at it: https://github.com/SessionLoops/PitchNet

I wonder whether it's accessible. I'm reconsidering #1password for my family anyway.

What about blind children who will want or need to use smart glasses for navigation throughout the building? If a teacher distributes a print handout, will a blind child be allowed to use a cell phone's scanning app to read it? These full bans on some of these technologies really concern me.

Many have pointed out that Aaron Swartz was driven to suicide by the prosecution for his copyright infringements, while the LLM companies can violate copyright with impunity. The proper resolution to that isn't to say that those companies shouldn't be able to do what they do, let alone that we shouldn't use the models that they create. The proper resolution is that information should be as freely accessible as Swartz wanted, and the legal system shouldn't have driven him to suicide over that.