Observed behavior
Links to sub-documents are implemented using <span type="button"> elements. These elements are neither rendered by screen readers nor accessible via keyboard. The type="button" attribute is invalid on a <span>. This error is present in the Docs.
Expected behavior
Links to sub-docs must be marked up with the <a href="url"> element to be rendered by assistive technologies, focusable via keyboard, and activatable with the Enter key.
Steps to reproduce
- Open one of the affected pages
- Locate a link to a sub-document
- Attempt to reach it via keyboard using the Tab key
- Notice that the element is not focusable
- Navigate with a screen reader in link navigation mode
- Notice that the element is absent from the links list
Possible solution
<!-- Before -->
<span type="button">Sub-document name</span>
<!-- After -->
<a href="/url/of/sub-document">Sub-document name</a>
Additional context / Screenshots
The type attribute is invalid on a <span> element. Only the <a href> element natively guarantees keyboard focusability, rendering in screen reader link lists, and activation via the Enter key. Adding role="link" and tabindex="0" to a <span> would be an insufficient and not recommended workaround.
RGAA criteria
Critère 6.1 : Chaque lien est-il explicite ?
Impact
A blind user navigating with a screen reader or a user navigating via keyboard cannot access the linked sub-documents. The functionality is entirely inaccessible without a mouse on the four affected pages.
Priority
P0
Observed behavior
Links to sub-documents are implemented using
<span type="button">elements. These elements are neither rendered by screen readers nor accessible via keyboard. Thetype="button"attribute is invalid on a<span>. This error is present in the Docs.Expected behavior
Links to sub-docs must be marked up with the
<a href="url">element to be rendered by assistive technologies, focusable via keyboard, and activatable with the Enter key.Steps to reproduce
Possible solution
Additional context / Screenshots
The
typeattribute is invalid on a<span>element. Only the<a href>element natively guarantees keyboard focusability, rendering in screen reader link lists, and activation via the Enter key. Addingrole="link"andtabindex="0"to a<span>would be an insufficient and not recommended workaround.RGAA criteria
Critère 6.1 : Chaque lien est-il explicite ?
Impact
A blind user navigating with a screen reader or a user navigating via keyboard cannot access the linked sub-documents. The functionality is entirely inaccessible without a mouse on the four affected pages.
Priority
P0