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
consthtml=/* html */`<h2 class='signup'> please upload an image that represents you </h2>
<h3> <em> please </em> do not upload a photo of yourself to the internet, that is an extremely irresponsible thing to do! </h3>
Heading elements like h3 are there to create a page structure. If you imagine deleting everything but the headings you should be left with a table of contents that represents each section of the page. This means you should only use a new lower heading level when you're creating a sub-section within the current one.
You also should never skip heading levels—it doesn't make sense structurally to have an h1 followed by an h3; there must be an h2 in between (if you want the text to be smaller use CSS).
In this case (and a couple of others) you're using heading elements more like subtitles. Since this is just supplementary text (and not actually labelling a new section) it's ok to use a regular text element (like a <p>).
The text was updated successfully, but these errors were encountered:
week4-CASE/src/handler/addPicture.js
Lines 10 to 11 in c664941
Heading elements like
h3
are there to create a page structure. If you imagine deleting everything but the headings you should be left with a table of contents that represents each section of the page. This means you should only use a new lower heading level when you're creating a sub-section within the current one.You also should never skip heading levels—it doesn't make sense structurally to have an
h1
followed by anh3
; there must be anh2
in between (if you want the text to be smaller use CSS).In this case (and a couple of others) you're using heading elements more like subtitles. Since this is just supplementary text (and not actually labelling a new section) it's ok to use a regular text element (like a
<p>
).The text was updated successfully, but these errors were encountered: