Comment 1 by James Teh <jamie@... on 2015-02-02 06:04
In [df32b04]:

User Guide: Clarifications regarding browse mode for Microsoft Word/Outlook.

Fixes #4863.

Changes:
State: closed

Comment 2 by jteh on 2015-02-02 06:06
Changes:
Milestone changed from None to 2015.1

Comment 3 by JamaicanUser (in reply to comment 2) on 2015-02-06 10:35
the user guide still gives the impression that one can skip past links and tables in Word. Also, the user guide states that the Elements list provides a list of headings, links and landmarks. In Microsoft Word, however, annotations replace landmarks. Could you point out what an annotation is?

Comment 4 by jteh (in reply to comment 3) on 2015-02-06 11:27
Replying to JamaicanUser:

the user guide still gives the impression that one can skip past links and tables in Word.

The User Guide now notes that not all of these commands are supported in all cases and NVDA itself clearly indicates when a command is not supported.

Also, the user guide states that the Elements list provides a list of headings, links and landmarks.

Hmm. Yes, that needs to be fixed. It's too late now to fix this for 2015.1, though.

Could you point out what an annotation is?

An annotation is a footnote, endnote, comment, etc. It's not part of the main text but complements it.
Changes:
Milestone changed from 2015.1 to 2015.2
State: reopened

Comment 5 by JamaicanUser (in reply to comment 4) on 2015-02-06 18:11
why is it too late. Don't you think it will cause a bit of confusion if you implement this feature if the user guide doesn't properly state this? Waiting until May is only haphazard. You could say
"The elements list shows headings, links and landmarks. For Microsoft Word, landmarks are substituted for annotations such as endnotes, footnotes and comments.

Comment 6 by jteh (in reply to comment 5) on 2015-02-07 04:05
Replying to JamaicanUser:

why is it too late.

Because we're now in translation freeze; i.e. we avoid any critical changes to English text so that translators have a stable target to translate.

Don't you think it will cause a bit of confusion if you implement this feature if the user guide doesn't properly state this?

Yes, but the actual impact of this particular confusion is minimal.

Comment 7 by jteh on 2015-02-07 04:09
We actually need to rethink this section a little. More applications will probably start supporting browse mode and it's going to get very unreadable to say "for app 1, the dialog will show this; for app 2, the dialog will show this; and for app 3, the dialog will show this". To complicate matters, it's difficult to explain to a user which type of browse mode they're using in some cases; e.g. an embedded browser control versus an embedded Microsoft Word document. I think it may be better to simply state that the Elements List will list the elements appropriate to the application.

Comment 8 by James Teh <jamie@... on 2015-04-13 07:26
In [54e9c7d]:

Change User Guide and command documentation for the browse mode Elements List to reflect the fact that the types of elements listed depends on the application, rather than always being links, headings and landmarks (as was previously the case).

Fixes #4863.

Changes:
State: closed

Comment 9 by James Teh <jamie@... on 2015-04-13 07:26
In [6816ad8]:

User Guide: With respect to single letter navigation, document what an annotation is.

Re #4863.

Comment 10 by JamaicanUser on 2015-04-15 14:35
what about section 8.1.12, in the list of settings that can be configured for document formatting, clickable elements are not part of the list.

Comment 11 by James Teh <jamie@... on 2015-04-20 06:51
In [9072a5b]:

User Guide: Document ability to configure whether clickable content is reported.

Re #4863.