More links

source

@@ -3787,6 +3787,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
     attributes are defined in <cite>ARIA</cite>: <ref spec=ARIA></p>
 
     <ul class="brief">
+     <li><dfn data-x-href="https://w3c.github.io/aria/#aria-checked"><code data-x="attr-aria-checked">aria-checked</code></dfn></li>
      <li><dfn data-x-href="https://w3c.github.io/aria/#aria-describedby"><code data-x="attr-aria-describedby">aria-describedby</code></dfn></li>
      <li><dfn data-x-href="https://w3c.github.io/aria/#aria-disabled"><code data-x="attr-aria-disabled">aria-disabled</code></dfn></li>
      <li><dfn data-x-href="https://w3c.github.io/aria/#aria-label"><code data-x="attr-aria-label">aria-label</code></dfn></li>
@@ -65670,8 +65671,9 @@ customElements.define('my-checkbox', MyCheckbox);</code></pre>
 
   <p>Custom element authors are encouraged to state what aspects of their accessibility semantics
   are strong native semantics, i.e., should not be overriden by users of the custom element. In our
-  example, the author of the <code data-x="">my-checkbox</code> element would state that its role
-  and aria-checked values are strong native semantics, thus discouraging code such as the above.</p>
+  example, the author of the <code data-x="">my-checkbox</code> element would state that its
+  <span>role</span> and <code data-x="attr-aria-checked">aria-checked</code> values are strong
+  native semantics, thus discouraging code such as the above.</p>
 
   <h5 id="custom-elements-customized-builtin-example">Creating a customized built-in element</h5>