JDK-8199892 : Missing landmarks when generating docs using html sources
  • Type: Enhancement
  • Component: tools
  • Sub-Component: javadoc(tool)
  • Affected Version: 11
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-03-20
  • Updated: 2019-01-17
  • Resolved: 2019-01-14
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 13
13 b04Fixed
Related Reports
Relates :  
JDK-8199176 - Accessibility issues in java.base docs
Description
When the javadoc tool generates a page from a html source such as net-properties.html (see below), it takes the content from the source and adds a header (navbar) and footer (bottom navbar). While doing so, it failed to add landmarks as it did when compiling other sources such as package-info.java. This includes the <header> and <main> tags.

As a result, the following docs are missing landmarks:

docs/api/java.base/java/net/doc-files/net-properties.html
docs/api/java.base/java/util/doc-files/coll-overview.html
docs/api/java.base/java/util/doc-files/coll-reference.html
docs/api/java.base/java/util/doc-files/coll-index.html
docs/api/java.base/java/util/doc-files/coll-designfaq.html
docs/api/java.base/java/lang/doc-files/threadPrimitiveDeprecation.html
docs/api/java.base/java/lang/doc-files/ValueBased.html
Comments
It could reasonably be said that these landmarks are the responsibility of the author of the corresponding HTML pages. This is significantly different from the quoted precedent of javadoc generating the entire html file from a source file like package-info.java. That being said, if the page _did_ include the landmarks in the underlying html file, then the doclet would have to work harder to edit the navbar into the correct place in the file ... and for that reason (only) I think this issue should remain open.
18-04-2018