https://bugs.documentfoundation.org/show_bug.cgi?id=159906
V Stuart Foote <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from V Stuart Foote <[email protected]> --- Given that the 'accessibility check' feature resident in the SB is to *assist* the author with preparing accessible text, organizing it to do so efficiently makes sense. It is really not performing validation--rather it just indicates some text span that may need consideration. Currently each instance of "Text formatting conveys additional meaning" flag is picked up for *each* DF the author has assigned. Grouping by Paragraph would certainly help the author proceed through the document. But if the author does not want to consider each instance, they can already collapse the 'Formatting' exposure arrow. And doing so "by paragraph" or "by section" would be reasonable improvement and, suited to task of checking document accessibility. However would note that currently assigning a defined 'Character style' (e.g. Emphasis, Strong Emphasis) unlike the DF does not trigger the same additional meaning flag. Why not? -1 for an action button, stripping out the DF in bulk doesn't encourage the author to review the DF impact on accessible content. Beyond that, it is up to the users chosen Assistive Technology tool to consume and respond to document formatting--fonts, attributes, super/subscript, emphasis, highlight/marking, styling and color. Such DF and styling within a document are not incorrect, rather the author should be made aware where they have applied them--and the potential impact their formatting choices can have. Viewed in that context, +1 to organize by Paragraph, -1 to strip out ALL DF in a single pass, but fine to review/process at paragraph or section. And need to consider handling of applied Character styling in an accessible text context. -- You are receiving this mail because: You are the assignee for the bug.
