Skip to content
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

Add an <h> element to replace <h1-n>. #10835

Closed
RokeJulianLockhart opened this issue Dec 7, 2024 · 1 comment
Closed

Add an <h> element to replace <h1-n>. #10835

RokeJulianLockhart opened this issue Dec 7, 2024 · 1 comment
Labels
addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest

Comments

@RokeJulianLockhart
Copy link

What problem are you trying to solve?

As aforerequested in an archived repository:

The <h> element is desired for situations where the “ranking” context changes for a heading, either before or after the source is sent to the browser. The current process of figuring out the appropriate “rank” of a heading is as unnecessary as requiring <li> to be <l1-n>.

Which also brings up a secondary point; there are not only 6 levels of headings.

What solutions exist today?

To my knowledge, a CSS3-styled tag (like h2) is frequently utilized in place of its counterparts. This isn't brilliant for accessibility.

How would you solve it?

So, please, please thoughtfully consider a single heading element like <h>, which would represent the heading for its section. The “rank” of such elements would be determined by outline depth.

Anything else?

Interest (outside those who visit these repositories) exists, per https://stackoverflow.com/a/14184815/9731176. That citation is even evidence of someone implementing the aforeproposed solution themselves.

@RokeJulianLockhart RokeJulianLockhart added addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest labels Dec 7, 2024
@RokeJulianLockhart
Copy link
Author

#10835 (comment)

Ah, this is a duplicate of #7390 (comment). Apologies. Of course I find it just after writing a request of my own.

@RokeJulianLockhart RokeJulianLockhart closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest
Development

No branches or pull requests

1 participant