Tait Hoyem
Tait Hoyem
> There is a general problem with "nag" like permissions, which is that the user sooner or later "gives up" or doesn't care if there is a yes/no permission. In...
Thanks you, @jadahl ! This is a great encapsulation of what we discussed. I'm going to create a simple set of calls for the portal here, and see if there...
> As for accessing the accessibility bus, if that means accessing private information, then the user should be aware of that. Yes. The user would be aware of that by...
I suppose that would technically be possible, @Mikenux
> I imagine A-Z, delete, backspace and enter could perhaps be "shortcuts" that the portal backend can disallow even for an AT This will not be possible. I can't say...
> the possibility that an app disguising itself as an AT can use an a11y portal to do really terrible things is a real problem and hard to solve. Right...
> It would be better to warn the user when shortcuts are assigned to delete/destructive actions. What exactly do you mean by destructive actions?
> I think this is likely the only method needed regarding shortcuts, if the intention is for a11y shortcuts to always take precedence without any user interaction. It also means...
> the system screen reader must read them instead of the app's screen reader (or at least give a hint). What is your meaning here? I'm not sure I understand...
> If it's already communicated, that's fine. Yes, so in this case focusing a button labeled "delete", or "remove", would speak the label of the button. So the user would...