Hello everyone,
_*Feature suggestion:*_
When a user changes the background color or the actual color of a text
element that results in a low contrast, show a notification that
provides additional information regarding either to
a) technical correct blackening out of text or
b) notes on accessibility guidelines
probably including a link to relevant help articles
I would suggest to provide a suiting notification for either (a) or (b),
depending on the contrast factor.
*
_Reasoning:_*
This feature request is based on observed user errors in the political
and accessibility context (part of my profession).
*Regarding (a): *I've observed several instances where users from a
political context intended to redact/blacken out text (to hide
confidential information), but were unaware that just changing the
background color, won't result in an actual blackening out of the text,
when e.g. exporting a document as a PDF.
Personally observed instances where this happened:
* in the US in the past days with the release of certain documents from
the Epstein files
<https://www.nytimes.com/2025/12/23/us/politics/epstein-files-redactions-doj.html>
* in several instances in the US, which resulted in a article by the NSA
on proper redaction
<https://www.cnet.com/news/privacy/editing-tips-from-the-nsa/> in 2006
* in a Swiss cantonal school commission (which I've been a member of;
but I can't disclose details)
I've come to realize that a majority of users may never be properly
trained on proper redaction.
*Regarding (b): *Ensuring accessibility for all users is an increasingly
important factor, partially due to demographic changes in most
populations (i.e. an increasing number of users with age-related issues).
e.g. consider the European Accessibility Act
<https://en.wikipedia.org/wiki/European_Accessibility_Act>, which
intends that an increasing number companies are fullfilling WCAG
guidelines
<https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines>.
A common problem concerns ensuring accurate contrast between foreground
and background. In the current WCAG 2 guidelines there are distinctions
concerning AA (e.g. related to EAA regulation for companies) and AAA
levels (mostly related to digital governmental services). There's also a
novel contrast calculation called APCA, which uses a more complicated
formula to calculate a contrast ratio than in WCAG 2, but provides a
better rule of thumb for human contrast perception, based on scientific
research and might be part of an upcoming WCAG 3 standard. I suggest to
check out contrast checkers on the web <https://colorcontrast.app/>, in
case you're not familiar with these topics yet.
*_
Additional notes:_*
I'm sorry in case my suggestion ended up on the wrong place and would be
more than happy - given that was the case - that someone would forward
this suggestion to the proper mailing list.
I'm well aware that (a) and (b) are unrelated on a technical level.
best & thanks in advance for any consideration
- Pat Mächler
UX and Accessibility specialist
--
To unsubscribe e-mail to: design+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/design/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
- [libreoffice-design] UX feature request: trigger a notification if users do low contrast formatting · Pat Mächler
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.