npub1wd…jcsk9 on Nostr: npub183n8f…wtahh ask if they have any plans for accessibility, contributing to ...
npub183n8fp0xavfvuejszsfzkf44af77j6xfgmk33k2whm7ktflcr4jqswtahh (npub183n…tahh) ask if they have any plans for accessibility, contributing to major desktop environments to add more, build tools with ui accessibility in mind, etc. Also, what does he think is the direction forward for wayland and assistive technology providers to work together? A wayland protocol extension to loosen the security model for accessibility dedicated applications, like magnifiers and screenreaders such as orca and odilia, or a simpler dbus api implemented by the compositor to do the same thing? Basically, should ATs connect to the compositor and talk the protocol, or use dbus and let the compositor gain a direct dbus dependency? Here are relevant links:
* my ideas on p2p accessibility in a post-wayland world
https://www.freedesktop.org/wiki/Accessibility/Accessibility/P2P/?updated
wayland accessibility issues, as of 2021:
https://www.freedesktop.org/wiki/Accessibility/Wayland/
* my ideas on p2p accessibility in a post-wayland world
https://www.freedesktop.org/wiki/Accessibility/Accessibility/P2P/?updated
wayland accessibility issues, as of 2021:
https://www.freedesktop.org/wiki/Accessibility/Wayland/