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
This is an issue from both semantics and accessibility aspect. If I have the following structure in my markdown:
# My page/document title## Section heading
Some introduction about this heading and here's a special note:
:::caution Something to keep in mind
some text here
:::
...
The above will produce the following hierarchy when the html page is generated:
h1 My page/document title
h2 Section heading
Some introduction about this heading and here's a special note:
h5 Something to keep in mind
some text here
...
Semantically that's inaccurate because after h2, the next sub-heading should be h3. For the same reason, it also fails the accessibility tests in Google's Lighthouse audit.
I think this plugin should not use h5 as the title of the notes. It can probably use a span (or something more appropriate) with a classname and then adjust the font size accordingly.
The text was updated successfully, but these errors were encountered:
Sounds good. I didn't know this was changed in new version. I'd probably go for reverting this change instead of adding option to maintain something that is not correct.
The plugin currently generates an html code where the title of the special notes/admonitions are given an html heading
h5
.remarkable-admonitions/src/renderer.ts
Lines 19 to 25 in 042d6e1
This is an issue from both semantics and accessibility aspect. If I have the following structure in my markdown:
The above will produce the following hierarchy when the html page is generated:
Semantically that's inaccurate because after h2, the next sub-heading should be h3. For the same reason, it also fails the accessibility tests in Google's Lighthouse audit.
I think this plugin should not use
h5
as the title of the notes. It can probably use aspan
(or something more appropriate) with a classname and then adjust the font size accordingly.The text was updated successfully, but these errors were encountered: