C
clifftyll
I consider this to be a serious application error. If the user has not
explicitly added semantic structure to at least one paragraph in a document,
Word guesses. It decides, in a rather inconsistent way, that some of the
short lines, formatted lines, lines in all caps, and so forth must be
headings and displays them as level 1 headings in the document map. This is
confusing, not helpful, and generally bad.
In one document I use to demonstrate how the document map works (and fails),
Word invariably decides that the first line in an address is body text, but
the second line -- the P.O. box number -- is a heading 1. And neither of
these lines has any formatting other than "Normal." How can such wild guesses
possibly be helpful?
Because of this behavior, I have found no one who intuitively grasps the
purpose and function of the document map. However, once a user is taught how
it is *supposed* to work, they immediately appreciate this tool for what it
offers:
- a quick check on the outline of their document
- a way to quickly navigate deeply into a document right after you've opened
it
- a way to discover what a screen reader or other form of assistive
technology will reveal to its users as the structure of the document
The problem is, this last point works only if at least one paragraph has
been made into a heading using a style with the appropriate outline level as
one of its properties. As I said above, whenever the user does not apply a
heading style to at least one paragraph, Word shows a document map based on
its own erratic evaluation of the document. Even if the document is only a
letter.
If Word would show nothing in the document map when there is no structure
encoded into the document map, more people would get how this tool works. And
it would be a simple and powerful quick check on the feature that for many --
perhaps most -- Word documents is the most significant issue with respect to
accessibility.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...8&dg=microsoft.public.word.application.errors
explicitly added semantic structure to at least one paragraph in a document,
Word guesses. It decides, in a rather inconsistent way, that some of the
short lines, formatted lines, lines in all caps, and so forth must be
headings and displays them as level 1 headings in the document map. This is
confusing, not helpful, and generally bad.
In one document I use to demonstrate how the document map works (and fails),
Word invariably decides that the first line in an address is body text, but
the second line -- the P.O. box number -- is a heading 1. And neither of
these lines has any formatting other than "Normal." How can such wild guesses
possibly be helpful?
Because of this behavior, I have found no one who intuitively grasps the
purpose and function of the document map. However, once a user is taught how
it is *supposed* to work, they immediately appreciate this tool for what it
offers:
- a quick check on the outline of their document
- a way to quickly navigate deeply into a document right after you've opened
it
- a way to discover what a screen reader or other form of assistive
technology will reveal to its users as the structure of the document
The problem is, this last point works only if at least one paragraph has
been made into a heading using a style with the appropriate outline level as
one of its properties. As I said above, whenever the user does not apply a
heading style to at least one paragraph, Word shows a document map based on
its own erratic evaluation of the document. Even if the document is only a
letter.
If Word would show nothing in the document map when there is no structure
encoded into the document map, more people would get how this tool works. And
it would be a simple and powerful quick check on the feature that for many --
perhaps most -- Word documents is the most significant issue with respect to
accessibility.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...8&dg=microsoft.public.word.application.errors