Bug 147556 - Accessibility checker "Fake numbering '1. 2....'"
Summary: Accessibility checker "Fake numbering '1. 2....'"
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.0.0 alpha0+
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-20 19:14 UTC by raal
Modified: 2022-03-07 16:53 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
printscreen (53.67 KB, image/png)
2022-02-20 19:14 UTC, raal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description raal 2022-02-20 19:14:11 UTC
Description:
Feature info: https://tomazvajngerl.blogspot.com/2020/01/accessibility-checker-and-support-for.html
I'm not sure if it's bug or not, but I suppose it is.
Tested with Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 8942956e05f2208ffb666a2118f5db092c30ce6a
CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded Jumbo

Steps to Reproduce:
 - write 1. 2. 3. in new paragraphs/lines (This is fake numbering. When I run Accessibility checker it warns "Fake numbering '1. 2....'" and it's correct warning).
 - select three lines and press button Toggle ordered list (F12). Now we have correct list, see printscreen.
 - run Accessibility checker. 

Actual Results:
Warning still present.

Expected Results:
Without warning


Reproducible: Always


User Profile Reset: No



Additional Info:
.
Comment 1 raal 2022-02-20 19:14:45 UTC
Created attachment 178413 [details]
printscreen
Comment 2 Dieter 2022-03-07 16:53:31 UTC
I confirm the behaviour with

Version: 7.3.1.2 (x64) / LibreOffice Community
Build ID: 9fff0292474d6d0bf5df787b512c71d9ac4bc98e
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

But if you delete 1. 2. 3. from first step you don't get a fake numbering warning. So accessibility check doesn't treat corect numbering as fake numbering, but numbering from step 1 (There is also no warning, if you insert text before fake numbering

=> RESOLVED NOTABUG

Raal, feel free to change it back to UNCONFIRMED with a short reasoning, if you disagree.