Subject: Amendment v3.7.3: Consolidated UI Accessibility Extension Specification & Pre-Merge Evaluation (Target: vcl / desktop / officecfg) Dear LibreOffice ESC Maintainers and Accessibility Team, Following the submission of our baseline technical report yesterday (August 11, 2026, under Amendment v3.6), I am submitting the consolidated architectural specification for Amendment v3.7.3. This revision unifies our core requirements for a high-visibility, single-action installation workflow tailored for users with severe visual and mobility impairments, while incorporating critical runtime safety configurations. Please find the finalized engineering requirements below: 1. Core Goal & User Profile Context The target profile is a low-vision user with 1/10 visual acuity per eye (2/10 combined total vision) operating on a 23" 1080p display at 150% fractional scaling. The user utilizes the NVDA screen reader and exhibits mobility limitations, requiring absolute operational autonomy without mouse interaction. 2. Native Extension Manager Bypass & Dialog Geometry
- Subsystem: desktop / extensions / vcl (SilentInstallationJob API). - Mechanism: Opening the .oxt package bypasses the standard multi-tab Extension Manager user interface. It initializes a clean, high-contrast, single-action confirmation dialog. - UI Layout: Features a single, predictable action button anchored at the bottom edge. - Typography: The button label text is scaled up to 14pt-16pt Bold Sans-Serif to ensure geometric structural integrity under 150% fractional system scaling. 3. Strict Localization & Screen Reader Interoperability (UAA / NVDA) - Localization (l10n): Complete native implementation for the Greek (el-GR) locale. The installation trigger button must render natively as "[ Εγκατάσταση Νέου Θέματος ]". - Accessibility API Bridge: The custom dialog component must fully implement the UNO Accessibility API (UAA), bridging directly to IAccessible2 on Windows hosts. - Focus Handling: Keyboard tab-focus must programmatically anchor onto the action button immediately upon dialog initialization (AccessibleStateType::FOCUSED). This ensures NVDA reads out the button label instantly and allows deployment via a single keyboard interaction (Enter or Space key). 4. Toolbar Customization & Freeze-Protection Matrix (Add/Remove Capability) - The extension packages Tango icon assets, applies high-contrast Elementary styling variables, and patches layout structural overrides inside officecfg. - Integrates .uno:ToggleToolbarButtonVisibility directly into the customized layout. This provides an accessible, flat menu mapping for adding or removing toolbar buttons, eliminating nested navigation paths. - Execution Policy: The modification, addition, or removal of toolbar configuration metrics must be performed with absolutely no technical restrictions or interface locks. - Integrity Check: The application layer must undergo a meticulous runtime inspection to detect and prevent any hidden locks, structural blockages, or background thread freezes that could instantly lock down the application environment or corrupt the newly deployed profile immediately following the initial installation phase. 5. Pre-Merge Experiential Evaluation & Testing Pipeline - Prior to the final integration of these architectural changes into the master branch, a staged testing build (Daily/Nightly or specialized tdf-Gerrit build) must be generated. - As the experiential evaluator and end-user of this project, I require direct access to this pre-merge build to conduct manual verification using the NVDA screen reader under the 150% fractional scaling environment. Final approval for deployment will follow this live user-testing phase. We look forward to your engineering feedback and instructions for staging this deployment into the daily build pipeline for verification. Sincerely, Evangelos Vagias *Mechanic Experiential Evaluator & Accessibility End-User* *LibreOffice UI Accessibility Project* ------------------------------
