diff options
| author | sthibaul <sthibaul@web> | 2020-01-27 02:20:24 +0000 |
|---|---|---|
| committer | IkiWiki <ikiwiki.info> | 2020-01-27 02:20:24 +0000 |
| commit | e8faf339aca1a6e32dd1a617b50f1f77d6ddf08f (patch) | |
| tree | f265dfa6a7737797bcfacfe863856fd04c8e41dc /Accessibility | |
| parent | 757bf6764dc777ded01d83eaf1b7cab996d0a2fd (diff) | |
Diffstat (limited to 'Accessibility')
| -rw-r--r-- | Accessibility/GTK-a11y-revamp.mdwn | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Accessibility/GTK-a11y-revamp.mdwn b/Accessibility/GTK-a11y-revamp.mdwn index aec77645..f413e853 100644 --- a/Accessibility/GTK-a11y-revamp.mdwn +++ b/Accessibility/GTK-a11y-revamp.mdwn @@ -109,11 +109,6 @@ Just ideas randomly thrown here, no particular order/priority/applicability inte * key press notification can be asynchronous, thus not slowing desktop down * only keyboard shortcut would have to go through the screen reader -* Implement accessibility support (such as "read current line") within the toolkit itself - * There are a *lot* of such things that would need to be implemented to make working with speech feedback workable, and not shared with other toolkits - * The screen reader has its own state (e.g. feedback verbosity level) - * That makes integration with other screen reader behavior extremely difficult (We need to have it interrupted by e.g. desktop notifications, focus change, etc.) - * key press/shortcut transmission * through XInput? (Requires a window, but at-spi2-core could create one ; wayland needs something else) * through AT-SPI or another protocol? We want authorization to avoid arbitrary key snooping, if we add authorization over the whole AT-SPI that should be fine @@ -127,6 +122,11 @@ Just ideas randomly thrown here, no particular order/priority/applicability inte * But also input method expansions * make IM emit an at-spi event to notify of this? +* Implement accessibility support (such as "read current line") within the toolkit itself + * There are a *lot* of such things that would need to be implemented to make working with speech feedback workable, and not shared with other toolkits + * The screen reader has its own state (e.g. feedback verbosity level) + * That makes integration with other screen reader behavior extremely difficult (We need to have it interrupted by e.g. desktop notifications, focus change, etc.) + * Involve the compositor * for keypresses / shortcuts? * for getting absolute window position |