Title descriptive expectation is vague[c4a8a4]

[WilcoFiers]

The expectation of this rule is as follows:

The target element describes the topic or purpose of the overall content of the document.

The term "overall content" is somewhat vague and undefined. Does that for example include content that is inside an iframe? We need to spend some time refining what exactly we mean here I think.

[dan-tripp-siteimprove]

Would it help if we change the expectation to use 'web page' instead of 'document'? Like the Applicability does.

[WilcoFiers]

Some common challenges for this rule:

• Single-page apps, and are title changes required when the purpose of the page changes
• Pages who's main content is an iframe -- commonly this is done with forms
• What about describing repeated content
• Dynamic content in the page, such as tab panels

Possible improvements:

1. Web page (HTML) is better than document, so that this applies to iframe content too
2. Instead of "overall content" maybe use visible content and content in the accessibility tree?
3. If the purpose of the page changes, regardless of navigation, the title has to change
4. Purpose includes the main section, possibly the site name / section name, but probably not repeated content like the navbar and footer