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

            Bug ID: 159906
           Summary: A11Y sidebar: Too many issue reports about direct
                    character formatting
           Product: LibreOffice
           Version: 7.1.0.3 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]
            Blocks: 154929

Created attachment 192786
  --> https://bugs.documentfoundation.org/attachment.cgi?id=192786&action=edit
Example file from Writer with many character DF in a paragraph

If there is some character direct formatting applied to the text of a document,
there is one entry in the sidebar for all of the instances. In a larger
document this can become annoying to oversee (let alone fix), and possibly can
cause fatigue of the user.

One idea to make this better would be to group these issues by paragraph (or
even by document?): one entry in the sidebar, and highlight all of the affected
characters, or even the whole paragraph if this is not possible.

Another idea is to provide a Fix button to this warning, which would call
uno:ResetAttributes (Clear Direct Formatting) on the text belonging to the
warning.

1. Open attached document
2. Open the Accessibility sidebar
-> Several entries about direct character formatting. Imagine this density of
DF in a 100 page long document...

Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 74185b8edf7f046a3372319da86a1d8ca0024c87
CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: default

Started in 7.1 with the first implementation of accessibility check.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=154929
[Bug 154929] [META] Accessibility Check sidebar deck, Automatic Accessibility
Checking
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to