src/java.xml.bind/share/classes/javax/xml/bind/JAXBPermission.java

@@ -39,19 +39,23 @@
  * <P>
  * The following table lists all the possible {@code JAXBPermission} target names,
  * and for each provides a description of what the permission allows
  * and a discussion of the risks of granting code the permission.
  *
- * <table border=1 cellpadding=5 summary="Permission target name, what the permission allows, and associated risks">
+ * <table class="striped">
+ * <caption style="display:none">Permission target name, what the permission allows, and associated risks"</caption>
+ * <thead>
  * <tr>
- * <th>Permission Target Name</th>
- * <th>What the Permission Allows</th>
- * <th>Risks of Allowing this Permission</th>
+ * <th scope="col">Permission Target Name</th>
+ * <th scope="col">What the Permission Allows</th>
+ * <th scope="col">Risks of Allowing this Permission</th>
  * </tr>
+ * </thead>
  *
+ * <tbody style="text-align:left">
  * <tr>
- *   <td>setDatatypeConverter</td>
+ *   <th scope="row">setDatatypeConverter</th>
  *   <td>
  *     Allows the code to set VM-wide {@link DatatypeConverterInterface}
  *     via {@link DatatypeConverter#setDatatypeConverter(DatatypeConverterInterface) the setDatatypeConverter method}
  *     that all the methods on {@link DatatypeConverter} uses.
  *   </td>

@@ -61,10 +65,11 @@
  *     This allows malicious code to gain access to objects that it may otherwise
  *     not have access to, such as {@link java.awt.Frame#getFrames()} that belongs to
  *     another application running in the same JVM.
  *   </td>
  * </tr>
+ * </tbody>
  * </table>
  *
  * @see java.security.BasicPermission
  * @see java.security.Permission
  * @see java.security.Permissions