https://bugs.documentfoundation.org/show_bug.cgi?id=165002

            Bug ID: 165002
           Summary: gtk3: Buttons to switch between styles categories in
                    sidebar don't have an accessible name
           Product: LibreOffice
           Version: 25.8.0.0 alpha0+
          Hardware: All
                OS: Linux (All)
            Status: UNCONFIRMED
          Keywords: accessibility
          Severity: normal
          Priority: medium
         Component: UI
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
            Blocks: 36549

Steps to reproduce (on Linux):

1) start the Orca screen reader
2) start LO Writer with the gtk3 VCL plugin (SAL_USE_VCLPLUGIN=gtk3)
3) make sure the sidebar is active and the "Styles" deck is active
4) press F6 until focus is in the sidebar
5) press Tab key until focus is on the "Paragraph Styles" button
6) press right arrow key to move between to the other styles categories
("Character Styles", "Frame Styles",...)

Actual result:

In step 5, Orca just says "Toggle button, pressed", giving the user no clue
what this button is about.
Similarly, in step 6, Orca just says "Toggle button, not pressed" for the other
buttons.

Expected result:

Orca should announce what these buttons are for, so the user knows what they're
for and how to switch to the style category of interest. It should e.g. say
"Paragraph Styles, Toggle button, pressed" in step 5.

The problem is that no accessible name is set for those buttons when using the
gtk3 VCL plugin.

Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 08e40accb3fabe676746c40797efc20eaa218801
CPU threads: 32; OS: Linux 6.12; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=36549
[Bug 36549] [META] ACCESSIBILITY: Tracking bug for issues affecting a11y ATK
and GNOME Orca screen reader support
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to