07:43 | <Noam Rosenthal> | It's a sub-heading, having a list of sections each with its own subheading kind of makes sense to me as one of the rationales:
Not sure about the history etc. |
07:46 | <유신> |
|
07:51 | <유신> | Noam Rosenthal: If it's not uncomfortable, can you answer one more question? |
07:51 | <Noam Rosenthal> | Noam Rosenthal: If it's not uncomfortable, can you answer one more question? |
07:52 | <유신> |
|
07:52 | <유신> | I was actually curious about this. There's no grammatical error in this structure. And semantically correct? |
07:53 | <유신> | My colleague who works with me told me that the heading level cannot be used in the <li> tag, so I wonder if it is correct. |
07:53 | <Noam Rosenthal> | I was actually curious about this. |
07:55 | <유신> | So only in terms of grammar? |
07:55 | <Noam Rosenthal> | it can be semantically correct if organizing the sections and heading in this way would also make sense for your content in a screen reader, automatic table-of-contents generator etc. |
07:57 | <Noam Rosenthal> | e.g. if you're using <h3> as a way to affect the style but it doesn't represent an actual heading, then it's not "semantically correct", as that H3 would appear in your table of contents as a heading (as one example) |
07:57 | <유신> | My colleage called it a grammatical error that <h2> or <h3> is contained in <li>. But I didn't think it was an error, and I couldn't detect any errors in the actual validation. |
08:03 | <Noam Rosenthal> | My colleage called it a grammatical error that <h2> or <h3> is contained in <li>. But I didn't think it was an error, and I couldn't detect any errors in the actual validation. |
08:04 | <유신> | Noam Rosenthal: Thank you for your kind reply:) |