Bug 137268 - Accessibility: Text boxes for entering distances don't expose value to screen reader
Summary: Accessibility: Text boxes for entering distances don't expose value to screen...
Status: RESOLVED DUPLICATE of bug 140594
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks: a11y, Accessibility
  Show dependency treegraph
 
Reported: 2020-10-05 13:18 UTC by Tim in 't Veld
Modified: 2022-06-02 08:57 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim in 't Veld 2020-10-05 13:18:48 UTC
Description:
 Many dialogs in Writer contain text fields for entering distances (e.g. heighth / width / margins)
Those text fields don't seem to expose their value to screen readers so I need to copy the value to the clipboard and paste it into some other place to read it. 


Steps to Reproduce:
Open E.G. the "position and size" dialog for an object.1.
2.
3.

Actual Results:
NVDA reads the first field which gets focus as "width: spin button editable alt + w". It does not read the value (E.G. 1.00 cm).   

Expected Results:
NVDA should read the value of this text field. 


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 7.0.1.2 (x64)
Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: threaded
I am using the NVDA 2020.2 screen reader. The problem also occurs with my JAWS 2020 screen reader so it is probably screen reader independent.
Comment 1 spv999.vernier 2021-02-27 01:26:55 UTC
Able to replicate with current release build, also with NVDA and JAWS. 

On further testing, I believe the problem is with the ‘numerical + arrow’ component. Any numerical box that has an up/down arrow fails to read the value. Boxes that do not have this feature are able to be read the value correctly. 

Though these components are used throughout the software, the easiest one is in the Properties menu
Steps to reproduce:
1. CTRL+F5 to open the properties pane on the right side. 
2. Several offending components here, including Spacing, Indent, Width, Height  

I’ve also checked Microsoft Word and Google Writer as oracles. In both of these programs, screen readers are able to read numerical settings boxes of the same and similar type. 

The ability to read these values is required for the most basic Level A accessibility, specifically ATAG 1.2. 

Version: 7.1.0.3 (x64) / LibreOffice Community
Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c
CPU threads: 16; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL
Comment 2 Dieter 2022-02-16 18:18:53 UTC
(In reply to spv999.vernier from comment #1)
> Able to replicate with current release build, also with NVDA and JAWS. 

If you can reproduce it, you are allowed to change status to NEW

=> NEW
Comment 3 Michael Weghorn 2022-02-17 07:06:51 UTC
I cannot reproduce. This sounds like bug 140594 which was fixed in LibreOffice 7.1.5 and later, while the initial description and comment 1 mention older versions.

Can you please retest with LibreOffice 7.3 (or at least 7.2)?

Version: 7.2.5.2 (x64) / LibreOffice Community
Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 4 Caolán McNamara 2022-06-02 08:57:12 UTC
I hear the value+cm read out with ndva when I check under windows with latest version

*** This bug has been marked as a duplicate of bug 140594 ***