JDK-6786028 : Javadoc HTML WCAG 2.0 accessibility issues in standard doclet - Bold tags should be strong.
  • Type: Bug
  • Component: tools
  • Sub-Component: javadoc(tool)
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2008-12-17
  • Updated: 2014-05-05
  • Resolved: 2011-07-15
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 7
7 b44Fixed
Related Reports
Relates :  
JDK-6702376 - Javadoc HTML accessibility issues in generated HTML by standard doclet (including WCAG 2.0 issues)
Relates :  
JDK-6790217 - Javadoc HTML WCAG 2.0 accessibility issues in jdk docs makefile - Bold tags should be strong.
Description
This bug is to track specific issues specified in bug 6702376.

Licensee observes the HTML generated by the Javadoc tool does not meet the
requirements of the Web Content Accessibility Guidelines 2.0 standard:

   http://www.w3.org/TR/WCAG20/

Here are some accessibility problems believed to be found so far.  Note that
this is not an exhaustive list - there are likely to be more problems.

1. Bold characters should be <strong>
Comments
SUGGESTED FIX New functions to generate <strong> and </strong> tags. Function to accept a string parameter enclosed between the strong tags. Replace all function calls to bold by all function calls to strong. Update existing regression tests which check for strings containing <B> tags to check for <STRONG> tag in the strings.
02-01-2009
EVALUATION The Javadoc standard doclet generates <B> tags. Source files need to be updated to generate <STRONG> tag instead of <B>.
02-01-2009