Bug 112665

Summary:	NSAccessibility - accessibility failures when Starting Writer from StartCenter
Product:	LibreOffice	Reporter:	Alex Thurgood <iplaw67>
Component:	LibreOffice	Assignee:	Not Assigned <libreoffice-bugs>
Status:	NEW ---
Severity:	normal	CC:	buzea.bogdan, vsfoote
Priority:	medium
Version:	6.0.0.0.alpha0+
Hardware:	x86-64 (AMD64)
OS:	macOS (All)
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=49576
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	42082, 61914
Attachments:	Apple accessibility audit report

Description Alex Thurgood 2017-09-26 13:59:18 UTC

Description:
The enclosed report details the lack of, or incorrect accessibility feature implementation when starting a new Writer document from the StartCenter.

Steps to Reproduce:
1.Start LibreOfficeDev master
2. Start Accessibility Inspector (Xcode developer tool)
3. Attach Inspector to running LibreOfficeDev process
4. Click on StartCenter window.
5. Click on the New Writer Document button
5. Run Audit from Inspector tools


Actual Results:  
See enclosed output frm audit tool, exported as HTML file (only export option) - the tool is supposed to also export as thumbnails the parts of the screen window that are affected to aid in tracking down each individual problem - unfortunately, this doesn't seem to work properly. When I load the HTML in Firefox, the thumbnails aren't displayed, merely their placeholders.

Expected Results:
The UI should correctly implement accessibility features in accordance with Apple guidelines.


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Firefox/55.0

Comment 1 Alex Thurgood 2017-09-26 14:00:11 UTC

Created attachment 136544 [details]
Apple accessibility audit report

Comment 2 QA Administrators 2018-10-10 03:05:07 UTC Comment hidden (obsolete)

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

Comment 3 Timur 2020-09-21 14:08:31 UTC

*** Bug 112666 has been marked as a duplicate of this bug. ***

Comment 4 Timur 2020-09-21 14:09:07 UTC

*** Bug 112667 has been marked as a duplicate of this bug. ***