Re: [libreoffice-accessibility] Write documents read only.

2024-04-11 Thread Michael Weghorn
Hi, On 2024-04-11 10:25, Gabriele Battaglia wrote: Is is normal that I can't read a document which is in read only mode? Do you mean that navigation using the text cursor/caret isn't possible? If so, please see this reply from an earlier question asked here which describes how to enable it:

Re: [libreoffice-accessibility] issue for missing alt text copy and paste

2024-04-11 Thread Michael Weghorn
On 2024-04-11 08:42, Roberto Scano wrote: Sorry i don't explain well. If I copy and paste image from a browser that has alt text, during copy it miss alt text. Thanks for the explanation. I've tested that. For that to work, the corresponding data needs to be present in the clipboard after

Re: [libreoffice-accessibility] issue for missing alt text copy and paste

2024-04-11 Thread Michael Weghorn
On 2024-04-10 11:22, Roberto Scano wrote: Another issue for images. When copy / paste and image, system shall copy also the accessibility attribute "alt". I just tested the following: 1) start Writer 2) insert an image (via menu: Insert -> Image) 3) press F4 to open dialog to edit details 4)

Re: [libreoffice-accessibility] Notes on LibreOffice 24.2 under Linux with Orca, GNOME 45.7

2024-02-26 Thread Michael Weghorn
On 2024-02-24 01:06, Jason J.G. White wrote: On 23/2/24 11:25, Jason J.G. White wrote: Yes, I'll submit a bug report. There's no screen reader output or any other indication after issuing Ctrl-Shift-Pgdn. I've created https://bugs.documentfoundation.org/show_bug.cgi?id=159863 Thanks! For

Re: [libreoffice-accessibility] Notes on LibreOffice 24.2 under Linux with Orca, GNOME 45.7

2024-02-23 Thread Michael Weghorn
On 2024-02-21 18:58, Jason J.G. White wrote: I noticed a few issues that may be Orca or LibreOffice-related - I don't know which is responsible. Orca is undergoing extensive development at the moment, which I'm testing by running the latest code from the main branch. By the way, do you know

Re: [libreoffice-accessibility] Notes on LibreOffice 24.2 under Linux with Orca, GNOME 45.7

2024-02-23 Thread Michael Weghorn
On 2024-02-21 18:58, Jason J.G. White wrote: I noticed a few issues that may be Orca or LibreOffice-related - I don't know which is responsible. Orca is undergoing extensive development at the moment, which I'm testing by running the latest code from the main branch. Thank you for reporting

Re: [libreoffice-accessibility] Saving to any particular location and grammar checker addon

2023-12-17 Thread Michael Weghorn
On 2023-12-18 07:52, Michael Weghorn wrote: There are 4 radio buttons: 1) Restore from backup 2) Configure 3) Extensions 4) Reset to Factory Settings PS: To navigate between the radio buttons, use the up/down arrow key when one of the radio buttons has focus. -- To unsubscribe e-mail

Re: [libreoffice-accessibility] Saving to any particular location and grammar checker addon

2023-12-17 Thread Michael Weghorn
On 2023-12-17 18:52, FARHAN ISHRAK Fahim wrote: Thank you. If I open libre office in safe mode, it shows four radio boxes. If I select any of them and press continue, it takes me to the home page or window of libre office. The radio boxes are Restore from backup radio button checked f 1

Re: [libreoffice-accessibility] Saving to any particular location and grammar checker addon

2023-12-16 Thread Michael Weghorn
On 2023-12-16 19:04, FARHAN ISHRAK Fahim wrote: Thank you. How can I reset libre office and update it? You can reset settings (or the complete profile) by starting LibreOffice in Safe Mode, then selecting the "Reset to factory settings" radio button. Then, enable the "Reset settings

Re: [libreoffice-accessibility] Saving to any particular location and grammar checker addon

2023-12-15 Thread Michael Weghorn
On 2023-12-15 18:23, FARHAN ISHRAK Fahim wrote: I am using LibreOffice 7.5.4.2. I can save to other location in other applications such as notepad. However, I am unable to do it in libre office. I can save to other location, if I open in safe mode. This suggests that the problem is likely

Re: [libreoffice-accessibility] Saving to any particular location and grammar checker addon

2023-12-14 Thread Michael Weghorn
On 2023-12-14 18:59, FARHAN ISHRAK Fahim wrote: No, it is not happening on windows. I can write the name of the file. However, I cannot change the location or directory. It worked just fine in a quick test of mine with LibreOffice 7.6 and NVDA 2023.3. When using "File" -> "Save As" (or the

Re: [libreoffice-accessibility] Writer: Problem with Voiceover auf macOS Ventura

2023-11-01 Thread Michael Weghorn
Hello Frank, On 2023-10-24 10:56, Michael Weghorn wrote: How exactly VoiceOver announces things is not fully under LibreOffice's control, but from what you write, this sounds like this might actually be related to the role (or specific other properties) that LibreOffice sets

Re: [libreoffice-accessibility] LibreOffice Writer's read-only mode and screen readers

2023-10-27 Thread Michael Weghorn
On 2023-10-27 14:55, Jason J.G. White wrote: Using LibreOffice Writer with Orca under Linux, I recently found that I couldn't navigate a read-only document with the usual cursor movement keys. Thus, I couldn't read it without using Ctrl-Shift-M to exit read-only mode. The scenario was

Re: [libreoffice-accessibility] some issues with screen reader accessibility

2023-10-24 Thread Michael Weghorn
On 2023-10-24 19:36, Dave Grossoehme wrote: How does the spell checker work with Narrator? In a quick test of mine, Narrator did not announce anything in LibreOffice, except for the title of windows. I don't know much about Narrator, but it might be that it only supports UIA (User

Re: [libreoffice-accessibility] Writer: Problem with Voiceover auf macOS Ventura

2023-10-24 Thread Michael Weghorn
Hello Frank, thanks for the additional information you've provided. How exactly VoiceOver announces things is not fully under LibreOffice's control, but from what you write, this sounds like this might actually be related to the role (or specific other properties) that LibreOffice sets on the

Re: [libreoffice-accessibility] Writer: Problem with Voiceover auf macOS Ventura

2023-10-24 Thread Michael Weghorn
Hi Frank, On 2023-10-23 10:59, Frank Becker wrote: When I go through a text in Writer, on each line Voiceover says: Reduced, edit text, insertion point at the beginning of the text. This is extremely annoying. How can I turn this off? I don't have this problem in Microsoft Word or Pages.

Re: [libreoffice-accessibility] some issues with screen reader accessibility

2023-10-23 Thread Michael Weghorn
On 2023-10-23 08:51, Michael Weghorn wrote: If you rely on the feature of announcing formatting information, I'd recommend to update NDVA to 2024.1 next year before updating to LibreOffice 2024.2. (Announcement for text formatting will not work with NVDA 2023.x and LibreOffice 2024.2 and above

Re: [libreoffice-accessibility] some issues with screen reader accessibility

2023-10-23 Thread Michael Weghorn
Hi, On 2023-10-12 14:02, Michael Weghorn wrote: I think the best way forward is to switch to adhere to the IAccessible2 specification and report the "invalid:spelling" attribute for spelling errors. That also needs a modification in NVDA to longer expect the custom attributes. O

Re: [libreoffice-accessibility] some issues with screen reader accessibility

2023-10-13 Thread Michael Weghorn
On 2023-10-12 20:27, Jason White wrote: I just confirmed that spelling errors are being reported by Orca under Linux as expected. Thanks! That matches what I see with Orca and the gtk3 VCL plugin (interface variant) on Linux. (The Qt-based VCL plugins don't expose that information yet. I

Re: [libreoffice-accessibility] some issues with screen reader accessibility

2023-10-12 Thread Michael Weghorn
Hi, On 2023-10-07 23:25, Michael Weghorn wrote: That sounds plausible. As mentioned in my previous email, I'm planning to take a closer look at this. Since it works with other applications (like Word or Thunderbird) and NVDA is free and open source, too, I'm optimistic that it'll be possible

Re: [libreoffice-accessibility] some issues with screen reader accessibility

2023-10-09 Thread Michael Weghorn
Hi Jean-Phillipe and Joanmarie, On 2023-10-08 00:07, Jean-Philippe MENGUAL wrote: Yes, COlomban is working for this. I gave him my nputs, he now tries to give a better technical base and reproduction scenarios. (...) Great, knowing the exact steps to reproduce will be very helpful. Or would

Re: [libreoffice-accessibility] some issues with screen reader accessibility

2023-10-07 Thread Michael Weghorn
Hi Jean-Philippe, On 2023-10-07 06:19, Jean-Philippe MENGUAL wrote: Nice to start chatting with you, I heard of you at Libocon via COlomban you met there and worling with my organization. I am glad if I can help you working on LO accessibility given the high needed job. For your info, as a

Re: [libreoffice-accessibility] some issues with screen reader accessibility

2023-10-06 Thread Michael Weghorn
Hi Daniel and Jason, thanks a lot for your email mentioning these points and the further input! Some notes/questions on the individual points follow below. On 2023-10-05 00:01, Jason White wrote: On 4/10/23 17:22, Daniel McGrath wrote: Firstly, when bringing up a word count, it's very

Re: [libreoffice-accessibility] Libre Inpress

2023-09-26 Thread Michael Weghorn
=96471  * https://bugs.documentfoundation.org/show_bug.cgi?id=101005  * https://bugs.documentfoundation.org/show_bug.cgi?id=149488 Thanks for pointing to these. I've at least linked them with each other for now (via the "See also" field in Bugzilla). Michael Weghorn might be able to

Re: [libreoffice-accessibility] Accessibility Requirement for LibreOffice Adoption at National Governmental Levels, etc.

2023-07-25 Thread Michael Weghorn
Hi Marc, there was a discussion around VPAT in 2020 already, s. the mailing list thread starting here: https://listarchives.libreoffice.org/global/accessibility/msg00926.html To summarize: Your below suggestion is something that this list cannot deal with, but that would have to be addressed

Re: [libreoffice-accessibility] LibreOffice Calc 7.5.4.2 and NVDA 2023.1: NVDA Not Consistently Announcing Cell Coordinates When Navigating Using Arrow Keys

2023-07-04 Thread Michael Weghorn
On 2023-06-30 07:04, David Goldfield wrote: Michael wrote: At first I was baffled as I was encountering this behavior rather consistently. However, I now understand why you weren't seeing the problem as well as how to correct it. In NVDA's Document Settings I had the "Cell Coordinates" option

Re: [libreoffice-accessibility] LibreOffice Calc 7.5.4.2 and NVDA 2023.1: NVDA Not Consistently Announcing Cell Coordinates When Navigating Using Arrow Keys

2023-06-26 Thread Michael Weghorn
Hello, On 25/06/2023 19.50, David Goldfield wrote: Hello. I wanted to report this in case it's not a known issue. When using arrow keys such as right or left arrow to navigate in a Calc spreadsheet NVDA consistently announces the incorrect cell coordinates. This does not happen with JAWS

Re: [libreoffice-accessibility] Accessibility Regressions Observed With Writer 7.5.1 and JAWS 2023

2023-06-21 Thread Michael Weghorn
Hello, On 21/06/2023 14.34, David Goldfield wrote: Hello. As of yesterday JAWS 2023 is now reading text in the manner expected when navigating a Writer document using arrow key navigation. From the changelog: Resolved an issue with JAWS not reading text entered into a document in LibreOffice

Re: [libreoffice-accessibility] Accessibility Regressions Observed With Writer 7.5.1 and JAWS 2023

2023-05-07 Thread Michael Weghorn
On 2023-05-07 05:23, David Goldfield wrote: Michael Weghorn wrote: (I'd suggest to either query for the toolkit name, which is "VCL" or support not just "LibreOffice" as app name, but also "LibreOfficeDev", which is the name that the development version uses, and

Re: [libreoffice-accessibility] Accessibility Regressions Observed With Writer 7.5.1 and JAWS 2023

2023-03-21 Thread Michael Weghorn
On 21/03/2023 09.28, Michael Weghorn wrote: 2.    When navigating in a pull-down menu JAWS is silent and no longer reads the item that has focus. Example: press alt+T for the Tools menu and press down arrow to navigate in this menu. JAWS is now silent when moving from one item to the next

Re: [libreoffice-accessibility] Accessibility Regressions Observed With Writer 7.5.1 and JAWS 2023

2023-03-21 Thread Michael Weghorn
Hi David, On 21/03/2023 03.30, David Goldfield wrote: I just upgraded from LO 7.4 to 7.5.1 and I have noticed two accessibility regressions with Writer and JAWS which make using Writer a total blocker for JAWS users. I can reproduce both issues (more details below). 1. JAWS no longer

[libreoffice-accessibility] Re: high contrast accessibility application guidelines?

2022-10-11 Thread Michael Weghorn
[Adding the accessibility mailing list, somebody on that list might have more insights] On 10/10/2022 22.02, Caolán McNamara wrote: Is there a set of guidelines as to the intent of high contrast within documents? Not sure I grasp the context of this question (s. below), but from a quick

Re: [libreoffice-accessibility] jaws screen reader is not reading word count

2022-10-11 Thread Michael Weghorn
On 28/09/2022 19.59, Jason White wrote: I tested this with the Orca screen reader under Linux. I am able to use the screen reader's review mode to read the dialogue, including the word and character counts. Have you tried to review it with the JAWS cursor? As I'm testing under Linux and

Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26 [IAccessible2 support in JAWS]

2022-06-24 Thread Michael Weghorn
On 22/06/2022 14.44, Jason White wrote: Note also that GTK 4 implements its own accessibility API, which, under Linux, connects directly to the running AT-SPI 2 demon. This approach may be an option in the future when the GTK 4 accessibility support matures. In other words, GTK is migrating

Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26 [IAccessible2 support in JAWS]

2022-06-09 Thread Michael Weghorn
Hi Marco, all, On 09/06/2022 09.39, Marco Zehe wrote: AFAIK, QT exposes accessibility information to UIA on Windows. They switched over from an MSAA implementation to UIA some time in the QT5 time frame: https://www.qt.io/blog/2018/02/20/qt-5-11-brings-new-accessibility-backend-windows.

Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26

2022-06-09 Thread Michael Weghorn
7/6/22 06:07, Michael Weghorn wrote: I tried again with just a single screen instead of two, and then NVDA announces "Slide 1", then reads out the slide content, and when moving further: "Slide 2" and its content, etc. Is that what you think Impress should do as well? (It di

Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26 [IAccessible2 support in JAWS]

2022-06-09 Thread Michael Weghorn
Hi Marco, On 08/06/2022 13.09, Marco Zehe wrote: JAWS does support IAccessible2, but only if it needs to, like in Firefox, and some parts of Chromium-based browsers. However, with the UI Automation implementation for the latter becoming stronger, there might be a time when JAWS moves to UIA

Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26

2022-06-08 Thread Michael Weghorn
On 07/06/2022 21.34, Jason White wrote: Yes. If I recall correctly, under MS-Windows/PowerPoint, NVDA and JAWS both support arrow key navigation in the slide contents when the slides are being presented (i.e., after F5 is used to start a presentation). Ideally, one should be able to do the

Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26 [IAccessible2 support in JAWS]

2022-06-07 Thread Michael Weghorn
Hi Christophe, On 07/06/2022 12.14, Christophe Strobbe wrote: After some online searching, it seems that JAWS at least used to support IAccessible2, originally mainly for IBM Lotus Symphony. According to a tweet by Marco Zehe from December last year, JAWS handles Chromium and Edge via

Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26

2022-06-07 Thread Michael Weghorn
On 07/06/2022 11.54, Michael Weghorn wrote: Could you please explain what the expected (and actual) behavior would be when showing an Impress presentation? I think it makes sense to create a bug report to keep track of this (and I'd be happy to do so, but don't know what to write

Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26

2022-06-07 Thread Michael Weghorn
On 31/05/2022 22.13, Jason White wrote: On 31/5/22 14:11, David P Á wrote: Other problem with accessibility is comments and tracked changes on Writer. The issues with these systems make using Writer problematic in professional settings. I agree, and in particular, the screen

Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26

2022-06-07 Thread Michael Weghorn
On 31/05/2022 14.20, Jason White wrote: It seems to be very much a matter of unaddressed bugs and regressions. The Document Foundation advertised a contract (presumably fulfilled by now) to rewrite the accessibility regression testing infrastructure in C++. FWIW, that conversion to C++ is

Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26

2022-06-07 Thread Michael Weghorn
On 31/05/2022 16.24, Christophe Strobbe wrote: I don't have a comprehensive overview of LibreOffice UI accessibility either, unfortunately. However, if you are looking for ways to prioritise issues, one way may be based on the accessibility requirements in the ETSI standard EN 301 549, which

[libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26

2022-06-07 Thread Michael Weghorn
On 31/05/2022 12.36, Caolán McNamara wrote: If the overview is there are a thousand little things and not a small set of large scale specific projects then that's still a useful overview. We could still sweep them into some general themes. Indeed. Thanks for adding the subtopics that came up

[libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26

2022-06-07 Thread Michael Weghorn
On 31/05/2022 12.01, Colomban Wendling wrote: * Only on-screen elements of the document are exposed to ATs.  This is on purpose probably for performance (not sure if we have any numbers to base it on?) so elements are lazy-loaded and destroyed, but it has non-trivial impact on various AT

[libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26

2022-05-30 Thread Michael Weghorn
On 30/05/2022 11.08, Caolán McNamara wrote: For a11y I don't know what is seen as the major problems, is there some fundamentally missing pieces (like in the past not having direct windows IAccessible2 support and needing a java access bridge). Or are the fundamentals ok and its a matter of a

Re: [libreoffice-accessibility] Using Calc with NVDA screen reader

2022-01-12 Thread Michael Weghorn
Hi Chris, welcome to this list and thanks for sharing your experience from using LibreOffice with NVDA. My comments on the aspects you mention are inline below. On 10/01/2022 18.27, Christopher Mullins wrote: In Excel, the cell in focus is always selected (highlighted) and if I use

Re: [libreoffice-accessibility] Calc navigation bug fixed

2022-01-07 Thread Michael Weghorn
Hi Simon, thanks for testing! Best regards, Michael On 07/01/2022 09.30, Simon Eigeldinger wrote: Hi all, Just want to report that in the latest daily build the calc navigation bug has been fixed. Now you can move around with the arrow keys as much as you want. Focus is always tracked

Re: [libreoffice-accessibility] Sluggishness with NVDA and Calc

2022-01-06 Thread Michael Weghorn
Hi Simon and Richard, On 17/12/2021 16.11, Michael Weghorn wrote: out of interest: How are you navigating through the sheet? Are you using the arrow keys (left, right, up, down) on a keyboard? It would definitely be interesting to hear whether the issue is still present once the problem

[libreoffice-accessibility] Re: Sluggishness with NVDA and Calc

2021-12-19 Thread Michael Weghorn
Subject: Re: [libreoffice-accessibility] Sluggishness with NVDA and Calc Hi Michael, I am navigating using the arrow keys. Thinking of it i am still using LibreOffice 7.1.5. So at the moment i am not sure if this bug is still present. Greetings, Simon Am 17.12.2021 um 16:11 schrieb Michael Weg

Re: [libreoffice-accessibility] Sluggishness with NVDA and Calc

2021-12-17 Thread Michael Weghorn
navigating to the next cell you have the same tracking/focus issues again. The problem is a pretty old one i guess. Greetings, Simon Am 17.12.2021 um 15:05 schrieb Michael Weghorn: Hi Richard, I can reproduce the behavior you describe, though the lag is only about 4-5 seconds in my case. I'd

Re: [libreoffice-accessibility] Sluggishness with NVDA and Calc

2021-12-17 Thread Michael Weghorn
Hi Richard, I can reproduce the behavior you describe, though the lag is only about 4-5 seconds in my case. I'd suggest to create 2 bug reports in Bugzilla to keep track of this: * one bug report for the slowness (the first two aspects you mention) * one bug report for the full

Re: [libreoffice-accessibility] Problems with Base Form and Screenreader

2021-09-17 Thread Michael Weghorn
Hello Frank, this sounds like LibreOffice might not be really accessible for the scenario you describe at this point. I suggest to create a bug report in LibreOffice Bugzilla, which allows to keep track of this issue: https://bugs.documentfoundation.org/ I recommend attaching an easy

Re: [libreoffice-accessibility] How to activate and expected functionality of a "Drop Down Button"

2021-03-02 Thread Michael Weghorn
work-around solution! Thanks! Richard -----Original Message- From: Michael Weghorn Sent: Monday, March 01, 2021 1:00 AM To: Richard B. McDonald ; accessibility@global.libreoffice.org Subject: Re: [libreoffice-accessibility] How to activate and expected functionality of a "Drop Down Button

Re: [libreoffice-accessibility] How to activate and expected functionality of a "Drop Down Button"

2021-03-01 Thread Michael Weghorn
Hi Richard, On 26/02/2021 14.55, Richard B. McDonald wrote: I am using Windows 10, NVDA 2020.4 and LO 7.1. In several places, like in Calc's formatting toolbar, there are things called a "drop down button." How do you activate them, and what is the expected functionality? To further, on this

Re: [libreoffice-accessibility] Spin Boxes Do Not Seem to Work Correctly

2021-02-22 Thread Michael Weghorn
Hi Richard, I quickly tried with the current development version of LibreOffice and can reproduce the behavior you describe using the NVDA screen reader on Windows. The value is changed when pressing the up or down key, but the screen reader does not say the new value, so that looks like an

Re: [libreoffice-accessibility] Arch Linux: LibreOffice 7 unable to read documents in Writer with Orca

2021-02-17 Thread Michael Weghorn
Hi Devin, I'm not an expert here, but quickly tried this: enabled Orca, started LibreOffice Writer, typed some text, moved between the different paragraphs using the up and down keys and the text of those paragraphs was read out as expected, so that seemed to work just fine in my case. Is

Re: [libreoffice-accessibility] Can LibreOffice be defaulted to save documents in MS Office formats?

2021-02-17 Thread Michael Weghorn
Hi Richard, yes, you can configure that in the options under "Tools" -> "Options" -> "Load/Save" -> "General". There, select "Text document" as document type and set "Always save as" to "Word 2007 - 365 (*.docx)". And select "Spreadsheet" as document type and set "Always save as" to "Excel

Re: [libreoffice-accessibility] accessibility LibreOffice Writer?

2020-10-26 Thread Michael Weghorn
Hello Keith, it's best to report LibreOffice bugs in the Bugzilla issue tracker at https://bugs.documentfoundation.org/ . This page contains some more information on reporting bugs: https://wiki.documentfoundation.org/QA/BugReport (After creating the bug report, you can add the keyword