Jonas Ådahl

Could you reopen this on https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/? Further development on the screen casting portal will happen there.

@stransky, can you "move" this to https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues ? The dialog for this has moved there.

> The user must be asked once whether the application should be allowed as an assistive technology. The "never", "just this time", and "always" options seem appropriate here (remember what...

> it may want to zoom in Zooming in can only practically be implemented by the compositor itself. In GNOME there is possible via the a11y menu, but could perhaps...

> This shouldn't need to make a screen reader your default to have it usable. I don't mind a combination of these features where: Correct me if I'm wrong, but...

> Agreed..... but this makes my situation (where I switch back and forth between two screen readers for testing) an absolute nightmare. I agree from a normal users' perspective this...

> EDIT: As long as it is possible for a distribution to ship with a default screen reader, then automatically run that without user interaction, that's fine by me. I'm...

This is an attempt to summarize a rough proposal that was discussed on the GNOME a11y Matrix room yesterday: ## Assistive Technology Assistive Technology (AT) are rather special when it...

> Methods > ``` > // set all possible shortcuts this assistive technology will use; > // all shortcuts are disabled by default > SetShortcuts (IN o session_handle, > IN...

> As for accessing the accessibility bus, if that means accessing private information, then the user should be aware of that. Yes, it'd be a tricky design task to some...