https://bugs.documentfoundation.org/show_bug.cgi?id=127201
V Stuart Foote <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |accessibility,
| |implementationError
Blocks| |101912
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
CC| |[email protected],
| |[email protected]
--- Comment #2 from V Stuart Foote <[email protected]> ---
Confimred on Windows 10 Home with NVDA 2019.1 and recent master 6.4.0alpha1
build
Version: 6.3.0.4 (x64)
Build ID: 057fc023c990d676a43019934386b85b21a9ee99
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win;
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
Though the Extension Manager's dialog controls are assigned accessible events
and all sound in AT, the list box of extensions is not being assigned
accessible events when built. And, unfortunately the list entries are also not
exposed to NVDA's object navigation. Suspect it will be the same for ORCA use.
Claiming implementation error in that we are omitting accessible events where
they are clearly needed for AT.
@Caolán, seems similar to the tree view of expert config stanzas (bug
99609)--and of equal impact on UX when dependent on AT. Is there an efficient
way to expose elements of these list items to AT?
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=101912
[Bug 101912] [META] Accessibility (a11y) bugs and enhancements
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs