-
Notifications
You must be signed in to change notification settings - Fork 89
Day 18: “Giving pages a clear shape by using headings” / Steve Barnett #203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: advent25
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thank you. That was a nice and easy read.
What do you think about adding a section with tools that help visualize heading structures? Like Wave, Accessibility Insights, etc.
hell/adventcalendar/2025/18/index.md
Outdated
| Some text. Some text. | ||
|
|
||
| ## Heading | ||
| We can make our pages easier to understand by using headings to give our pages a clear shape. Our users might visually scan the page, use an extension or bookmarklet, jump around using assistive technology like a screen reader, or ask AI for a summary of the page. High quality headings can make things better for everyone. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use an extension or bookmarklet
To do what?
jump around
For people not knowing how screen readers work that could be confusing. Can we say "navigate" instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated in 637b960.
| ## Text *should not* be a heading | ||
|
|
||
| Some text. | ||
| Ah, this one's a real classic! When we have some big and bold text, for Design Reasons, we sometimes take a bit of a shortcut and mark it up as a heading. Let's say an `<h2>`, because it seems about the right size, or that’s what it says in the design file. But here's the thing: this text doesn't introduce or describe the content that follows. It just "needs" to be big for the look of it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An example would be great, maybe in form of an outline!?
h1: Fruits
h2: Apples
h2: Pears
h2: [BAD HEADING] <-- you would have to come up with something. I'm not creative enough at the moment. :)
h2: Oranges
|
|
||
| This is an issue because when things that are headings aren't marked up as headings, it makes the page harder to understand. For example: screen readers won't announce it as a heading with its level, making it hard to understand the content and structure when listening to all the headings. Excellent. | ||
|
|
||
| ### How to fix it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, a before/after example would be great.
Co-authored-by: Manuel Matuzovic <[email protected]>
Co-authored-by: Manuel Matuzovic <[email protected]>
No description provided.