Bug 157233 - A11y sidebar: Add option to ignore warnings
Summary: A11y sidebar: Add option to ignore warnings
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.2.0.0 alpha0+
Hardware: All All
: medium enhancement
Assignee: Balázs Varga (allotropia)
URL:
Whiteboard: target:25.2.0
Keywords:
Depends on:
Blocks: Accessibility-Check
  Show dependency treegraph
 
Reported: 2023-09-14 09:59 UTC by Samuel Mehrbrodt (allotropia)
Modified: 2024-07-26 06:41 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file with some accessibility warnings (10.14 KB, application/vnd.oasis.opendocument.text)
2024-06-27 15:25 UTC, Gabor Kelemen (allotropia)
Details
The example file exported as PDF/UA (24.25 KB, application/pdf)
2024-06-27 15:26 UTC, Gabor Kelemen (allotropia)
Details
Warnings in the side bar, but no warnings in PAC tool (52.38 KB, image/png)
2024-06-27 15:29 UTC, Gabor Kelemen (allotropia)
Details
The PDF Export dialog gives another warning about all these issues (26.38 KB, image/png)
2024-06-27 15:44 UTC, Gabor Kelemen (allotropia)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Samuel Mehrbrodt (allotropia) 2023-09-14 09:59:13 UTC
It should be possible to "Ignore" warnings in the a11y sidebar. Ignored warnings should be hidden in the list of a11y issues.
Also, there should be a way to show which warnings have been ignored.

Needs a way to store the list of ignored warnings in the document.
Comment 1 Gabor Kelemen (allotropia) 2024-06-27 15:22:42 UTC
I'd take this to a different direction. Some warnings we currently have in the sidebar do not result in an error being reported by the PAC tool (https://pac.pdf-accessibility.org/en ).

To help users prioritizing issues, I suggest to:

* introduce separate issue categories, Error and Warning, based on how the PAC tool reports them (which also has this sort of distinction)
* show warnings in a separate section below errors
* do not count warnings in the PDF Export dialogs confirmation popup, only the errors
* warnings usually do not have/need a Fix button, instead we could show an Explanation button ( (i) icon?) that would show on press/highligh/hover why is something considered incorrect and how to fix it.
Comment 2 Gabor Kelemen (allotropia) 2024-06-27 15:25:27 UTC
Created attachment 195019 [details]
Example file with some accessibility warnings
Comment 3 Gabor Kelemen (allotropia) 2024-06-27 15:26:11 UTC
Created attachment 195020 [details]
The example file exported as PDF/UA
Comment 4 Gabor Kelemen (allotropia) 2024-06-27 15:29:18 UTC
Created attachment 195021 [details]
Warnings in the side bar, but no warnings in PAC tool
Comment 5 Gabor Kelemen (allotropia) 2024-06-27 15:44:40 UTC
Created attachment 195022 [details]
The PDF Export dialog gives another warning about all these issues

Another angle when demoting A11Y issues to warnings could be the PDF export dialog, which gives a popup before exporting, if the PDF/UA box is enabled and there are some issues.

The number here can be scarily high, in a large document with lots of direct formatting (which is also fine, usually) this can be overwhelming. See also bug 159906.

So this popup should only count the real errors, and skip the less important warnings.
Comment 6 Gabor Kelemen (allotropia) 2024-06-27 18:04:42 UTC
Todo for me: check all the A11Y checks and decide exactly which ones can be considered warnings, and what would be their explanation text.
Comment 7 Commit Notification 2024-07-25 15:44:42 UTC
Balazs Varga committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/33ea719d6c6ad23dfca088853d95d5688782da2d

tdf#157233 - A11y: Add global Accessibility check options for

It will be available in 25.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.