https://bz.apache.org/ooo/show_bug.cgi?id=127291

Quentin <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|NOT_AN_ISSUE                |---
             Status|RESOLVED                    |UNCONFIRMED

--- Comment #2 from Quentin <[email protected]> ---
Dear user without a name,

Thank you so much for your considered and thoughtful questions in response to
my issue in order to better understand the issue.

Let me rephrase the issue:

Start your chosen screen reader.  I used NVDA as I happen to work for the
company who make it, and as it is freely available, you can try it to in order
to verify this issue: http://www.nvaccess.org/download/

This problem is also reproducible in Narrator, the screen reader that comes
with Windows.

So to reproduce:

1. Be in a document with spelling errors.
2. Press F7.
3. Navigate to the suggestions field (TAB or press alt+s).  The screen reader
correctly reads the first item as expected.
4. Press the down arrow to move through the suggestions.  The screen reader
does not read the suggestions so the user does not know what is there.  This is
a bug.  The correct behaviour is for Open Office Writer (hint: that's YOUR
program) to disclose the current suggestion to the screen reader, so that the
screen reader can then read it.

If you are in any doubt, feel free to repeat the same steps in LibreOffice,
Microsoft Word, or pretty much any other program with a spell check feature.

I admit I could have been clearer in my question, but you need to ask when you
don't know something.  NVDA+numpad 4 and NVDA+numpad 6 (the NVDA key is usually
insert, but may be caps lock if the user has set that) are used to navigate
between items when the regular navigation keys don't work.  It's not
recommended for most things, particularly something as mundane as spell check. 
What I was really trying to say was that I can half get to them, but Open
Office just needs to make a little more info discoverable by a screen reader
when the user is navigating through that part of the dialog.

I'm more than happy to provide more information if you require, and I can even
do it without the snarky attitude, if you are actually willing to investigate
bugs that are filed on your system, instead of just saying they don't exist
when you don't understand what was written.  In fact, I would be very
interested in having more of a discussion with you on how we can BOTH work
together to make our two programs work better for both our user groups.

Kind regards

Quentin (quentin at NV Access dot org if you'd like to discuss more general
accessibility)

-- 
You are receiving this mail because:
You are the assignee for the issue.

Reply via email to