You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the tutorials page the heading levels skip from <h2> to <h4>.
Why it matters
People using assistive technology rely on proper headings structure to navigate effectively. By skipping levels people can get lost or miss entire sections of content using assistive tech.
Suggested fix
Two options here: first is to change the <h4> on each card to a <h3>.
However there is also a <h2> called "client" which is not currently needed / is redundant. A better option may be to remove this <h2> and promote the current cards' <h4>s to <h2>s as this will be a more logical structure for the page.
May I be assigned to this please?
Lol, I was just about to volunteer. :) Can I work on this? :) Accessibility is my jam and I love @GrahamTheDevRel! :) Hehe, that rhymed! :)
💭 Description
Issue
On the tutorials page the heading levels skip from
<h2>
to<h4>
.Why it matters
People using assistive technology rely on proper headings structure to navigate effectively. By skipping levels people can get lost or miss entire sections of content using assistive tech.
Suggested fix
Two options here: first is to change the
<h4>
on each card to a<h3>
.However there is also a
<h2>
called "client" which is not currently needed / is redundant. A better option may be to remove this<h2>
and promote the current cards'<h4>
s to<h2>
s as this will be a more logical structure for the page.Relevant Success Criterion WCAG
Info and Relationships in WCAG
Technique using heading levels
Additional Notes
Good first issue, but needs input from Appwrite to which solution they would prefer.
Found on stream on 2023-10-25
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: