[libreoffice-accessibility] MASTER TECHNICAL ACCESSIBILITY REPORT markdown

* MASTER TECHNICAL ACCESSIBILITY REPORT *

*markdown*

### **MASTER TECHNICAL ACCESSIBILITY REPORT**


**To:** LibreOffice Development Team / UI-UX Advisory Group

**From:** Evangelos Vagias (LibreOffice Accessibility End-User Advocate)

**Date:** July 28, 2026

**Subject:** Re-inclusion of Tango Icon Theme, Structural UI Design,
Toolbar Flexibility, and Safe Defaults


---


#### **1. Introduction & Critical Accessibility Blocker**

The removal of the Tango icon theme from the core installation of recent
LibreOffice versions (including 24.x/26.x) has created severe,
insurmountable accessibility barriers for users who strictly rely on
high-contrast, classically defined, and color-distinct iconography.


For the applicant and other users operating with concurrent severe visual
and motor impairments (such as limb spasticity), maintaining a core of
stability and continuity in the interface layout is not a matter of
aesthetic preference. It is a strict medical, functional, and professional
requirement [Office 97]. Sudden overhauls in icon styles disrupt muscle
memory and visual recognition, causing heavy cognitive strain and
completely halting daily workflows.


The core philosophy of Free and Open Source Software (FOSS) supports true
freedom of choice and customization, ensuring that the software remains
inclusive and adaptable to diverse human needs rather than forcing generic
interface designs upon vulnerable user groups.


---


#### **2. FIRST FOUNDATIONAL PILLAR: Re-Inclusion of the Tango Icon Theme**

To restore true accessibility, the re-bundling of a distinct, well-defined,
and legacy-inspired theme like Tango is a scientifically and empirically
backed requirement to restore necessary visual anchors that modern flat UI
design has systematically stripped away. We formally request that the
LibreOffice QA and development team either:

1. **Re-include the Tango icon theme** in the standard Windows installation
package under the optional components wizard.

2. **Provide a direct, foolproof, and fully accessible installation
method** through the internal Extension Manager, bypassing broken web links.


---


#### **3. SECOND FOUNDATIONAL PILLAR: Theoretical Rationale & The Scaling
Fallacy of Modern Flat UI**

The necessity for classic icon themes like Tango is empirically validated
by the lived experience of the author, who operates with a functional
visual acuity of 1/10 in each eye (totaling 2/10). Early-generation office
suites—specifically **Office 97** running on Windows 98—clandestinely
excelled at accessibility due to technical constraints that modern flat
designs have entirely abandoned:


* **High-Contrast Rasterization:** Legacy 16-bit bitmap (raster) icons
relied on distinct, dark 1-pixel borders. When scaled up via legacy OS
magnification, these icons underwent raw pixel-doubling (pixelation). This
geometric sharpness and hard-edged contrast acted as a vital visual
roadmap, preventing icons from blending into a blur.

* **Skeuomorphic Affordance:** The pseudo-3D design of the **Office 97** UI
utilized strict light-and-shadow cues (white top/left borders, dark gray
bottom/right borders). This tactile, "clickable" aesthetic provided
essential cognitive markers, allowing low-vision users to instantly
distinguish an interactive button from static backgrounds.

* **Dark Mode Visibility Collapse & Missing Focus States:** Modern
minimalist flat icons present an absolute visibility collapse when Dark
Mode is enabled, submerging into the dark background due to their thin
strokes and lack of vibrant colorization. Conversely, the Tango suite, with
its solid, vibrant primary colors, remains highly visible against dark
themes. Furthermore, legacy environments utilized robust visual focus
states; hovering over a toolbar button instantly enclosed the icon in a
highly defined bounding box with a solid fill highlight. Modern flat
interfaces lack these resting anchors for the eye, leaving the user
guessing where the cursor is focused.

* **The Scaling Fallacy:** Even though LibreOffice currently offers an
option for "Very Large" toolbar icons, and development points toward future
environment-variable-based percentage scaling (via the Qt toolkit), these
features remain ineffective on their own. Scaling a fundamentally flawed,
contrast-deficient visual asset simply magnifies the visual blur ("empty
magnification"). Without rigid, high-contrast borders, linear enlargement
merely scales up the cognitive strain. True accessibility requires a
perfect synergy between spatial scaling and structural, hard-edged
iconography.

* **An Industry-Wide Regression:** This critical assessment is an objective
critique of a flawed industry-wide design trend. Regrettably, modern
iterations of Microsoft Office have undergone the exact same accessibility
collapse. By abandoning the robust visual architecture of Office 97 and
moving toward minimalist flat designs, modern Microsoft Office suites have
introduced identical barriers—replacing clear, structural, and bounded
iconography with washed-out, borderless elements that cause severe visual
strain.


---


#### **4. Technical Requests & UI/UX Proposals**

In addition to the core icon architecture, true interface accessibility
requires absolute toolbar flexibility and layout clarity:


1. **Streamlined Toolbar Customization:** Currently, adding or removing a
button forces the user to navigate the complex "Tools -> Customization"
menu, which requires high visual acuity and precise mouse control. We
propose a permanent, highly visible shortcut (such as a large right-click
context menu or a prominent drop-down arrow) *directly on the docked
toolbar itself*, bypassing overwhelming configuration windows.

2. **Custom Graphics Parameter:** Introduce a parameter allowing users to
easily load and apply their own custom icons/graphics directly to specific
toolbar buttons.

3. **Deduplication of Clipboard Actions:** Implement an automated layout
rule to detect and easily remove duplicate Clipboard buttons (Cut, Copy,
Paste) across overlapping toolbars, as redundant icons create severe visual
clutter and disorientation.

4. **The Need for Safe Defaults:**

* **Disable Background Auto-Save by default (currently every 10 seconds):**
The constant generation of temporary or duplicate-looking files on the
screen causes immediate visual disorientation for low-vision users.

* **Smart Default File Naming:** The software should automatically suggest
the first line of text as the default filename during a "Save As" action,
instead of the generic number "1", drastically reducing the physical strain
of manual typing during dictation sessions.


---


#### **5. Technical Notes, Website Regressions & Core Compatibility Audits
(From User Testing)**

* **Critical Core Compatibility Check (Pre-Installation Regression
Prevention):** Beyond the mere re-inclusion of the assets, the development
team must thoroughly audit the core framework of the current versions
(24.x/26.x). We must proactively ensure that no hardcoded internal blocks,
rendering engine conflicts, or layout constraints exist within the core
application that would instantly lock down, misrender, or destabilize the
Tango theme upon installation. A deep code-level check is required to
guarantee that the application's core logic fully supports and safely
executes the classic iconography package without triggering immediate
system regressions or interface freezes.

* **Menu Bar Font Scaling Core Audit:** When implementing independent text
scaling for the Menu Bar, the development team must thoroughly audit the
core layout engine to ensure no hardcoded environment locks exist. The
rendering logic must be verified to guarantee that internal font-size
parameters for menu items can be scaled independently without being
overridden or blocked by OS-level window managers or global desktop theme
constraints [Office 97].

* **Version Conflict:** In LibreOffice 24.x/26.x, the Windows installation
wizard no longer contains Tango, forcing an unguided manual `.oxt`
extension installation.

* **Extension Website Bug:** The "Download Now" button on the official
extension page currently points to source script files (such as `.nsi`)
instead of the actual `.oxt` package, breaking the workflow for standard
users.

* **OS & Browser Restrictions:** Modern browsers on Windows 10/11
frequently flag the raw `.oxt` link or misinterpret it as a text webpage,
causing immediate download failures.

* **Configuration Reset Bug:** After software updates, LibreOffice
frequently resets user configurations (e.g., reappearance of the `.docx`
warning prompt, or native Windows save dialogs switching back to
empty/blank LibreOffice dialogs).


---


#### **6. Developer Feedback Integration & Hybrid Tracking Note**

Following constructive initial feedback from LibreOffice developer Michael
Weghorn, this master report serves as the philosophical and theoretical
foundation for these interconnected accessibility needs.


* **UX Evaluation Request:** We request the activation of the
**`needsUXEval`** keyword to involve the UI/UX design team (`
libreoffice-ux-advise@lists.freedesktop.org`).

* **Future Toolkit Architecture:** We welcome the potential future
migration to the **Qt UI toolkit** on Windows, as mentioned by development,
which may inherently provide environment-variable-based percentage scaling
for the UI.

* **Tracking Note:** For triaging efficiency, while this document holds the
complete architectural context, individual sub-tickets will be
cross-referenced in Bugzilla to track specific engineering tasks (e.g., the
Auto-Save default behavior, the Extension website download bug, and the
configuration reset bug).


**Submitted by:**

**Evangelos Vagias**

LibreOffice Accessibility End-User Advocate

-- 
To unsubscribe e-mail to: accessibility+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/accessibility/
Privacy Policy: https://www.documentfoundation.org/privacy