Skip to main content
Show what the example text produces; add level 4 through 6, which are now available (new).
Source Link
Makyen
  • 113
  • 1
  • 1
  • 4

The fix

Fake headers are easily fixed. When you want to make a header, there are three ways to create one:

  • Click the Heading editor button:

    A screenshot of the editor toolbar. The Heading button is a stack of five horizontal lines that alternate between short and wide lines, the first two black and the last three grey, visually representing a paragraph with a heavier header on top. The button is picked out with a red freehand circle around it.

  • Select the heading text and type ctrlh.

  • Manually type the Markdown code for a header, which is either an underline made from dashes or equal signs, or one to three hash marks in front of or surrounding it (“or”, because the trailing ones are optional).

    The exact symbol used defines the logical level (and visual size) of the resulting heading:

      # Level 1 heading #
    
      ## Level 2 heading ##
    
      ### Level 3 heading ###
    
      #### Level 4 heading ####
    
      ##### Level 5 heading #####
    
      ###### Level 6 heading ######
    
      ### No hashes at the end is also OK for any heading level
    
      Level 1 heading
      ===============
    
      Level 2 heading
      ---------------
    

    Which produces:

    Level 1 heading

    Level 2 heading

    Level 3 heading

    Level 4 heading

    Level 5 heading
    Level 6 heading

    No hashes at the end is also OK for any heading level

    Level 1 heading

    Level 2 heading

If you have existing fake headings, the easiest fix is to edit the post and replace the ** around the fake headings with ##.

It's not just for human accessibility

This isn't just a matter of accessibility to visually-impaired humans either, it's a matter of accessibility to computers in general. The more we use correct formatting, the more the meaning and structure of the contents is reflected in the HTML of the post. This makes for more useful material for future uses that we might not yet have imagined.

And in the meantime, making our site less annoying to use for visually-impaired members, by avoiding easily-avoided formatting errors, is worthwhile all by itself.

What about bolding the leading sentence, thesis statement, or question summary?

That's fine! That's not a header, that's just a sentence being emphasised due to its importance in the answer, question, or paragraph. That's what our bold formatting is for. In fact, marking it as bold will correctly indicate that it's not supposed to be understood as a section header, improving meaning and accessibility. Using section heading formatting is only recommended for things that are actually section headings.

The fix

Fake headers are easily fixed. When you want to make a header, there are three ways to create one:

  • Click the Heading editor button:

    A screenshot of the editor toolbar. The Heading button is a stack of five horizontal lines that alternate between short and wide lines, the first two black and the last three grey, visually representing a paragraph with a heavier header on top. The button is picked out with a red freehand circle around it.

  • Select the heading text and type ctrlh.

  • Manually type the Markdown code for a header, which is either an underline made from dashes or equal signs, or one to three hash marks in front of or surrounding it (“or”, because the trailing ones are optional).

    The exact symbol used defines the logical level (and visual size) of the resulting heading:

      # Level 1 heading #
    
      ## Level 2 heading ##
    
      ### Level 3 heading ###
    
      ### No hashes at the end is also OK for any heading level
    
      Level 1 heading
      ===============
    
      Level 2 heading
      ---------------
    

If you have existing fake headings, the easiest fix is to edit the post and replace the ** around the fake headings with ##.

It's not just for human accessibility

This isn't just a matter of accessibility to visually-impaired humans either, it's a matter of accessibility to computers in general. The more we use correct formatting, the more the meaning and structure of the contents is reflected in the HTML of the post. This makes for more useful material for future uses that we might not yet have imagined.

And in the meantime, making our site less annoying to use for visually-impaired members, by avoiding easily-avoided formatting errors, is worthwhile all by itself.

What about bolding the leading sentence, thesis statement, or question summary?

That's fine! That's not a header, that's just a sentence being emphasised due to its importance in the answer, question, or paragraph. That's what our bold formatting is for. In fact, marking it as bold will correctly indicate that it's not supposed to be understood as a section header, improving meaning and accessibility. Using section heading formatting is only recommended for things that are actually section headings.

The fix

Fake headers are easily fixed. When you want to make a header, there are three ways to create one:

  • Click the Heading editor button:

    A screenshot of the editor toolbar. The Heading button is a stack of five horizontal lines that alternate between short and wide lines, the first two black and the last three grey, visually representing a paragraph with a heavier header on top. The button is picked out with a red freehand circle around it.

  • Select the heading text and type ctrlh.

  • Manually type the Markdown code for a header, which is either an underline made from dashes or equal signs, or one to three hash marks in front of or surrounding it (“or”, because the trailing ones are optional).

    The exact symbol used defines the logical level (and visual size) of the resulting heading:

      # Level 1 heading #
    
      ## Level 2 heading ##
    
      ### Level 3 heading ###
    
      #### Level 4 heading ####
    
      ##### Level 5 heading #####
    
      ###### Level 6 heading ######
    
      ### No hashes at the end is also OK for any heading level
    
      Level 1 heading
      ===============
    
      Level 2 heading
      ---------------
    

    Which produces:

    Level 1 heading

    Level 2 heading

    Level 3 heading

    Level 4 heading

    Level 5 heading
    Level 6 heading

    No hashes at the end is also OK for any heading level

    Level 1 heading

    Level 2 heading

If you have existing fake headings, the easiest fix is to edit the post and replace the ** around the fake headings with ##.

It's not just for human accessibility

This isn't just a matter of accessibility to visually-impaired humans either, it's a matter of accessibility to computers in general. The more we use correct formatting, the more the meaning and structure of the contents is reflected in the HTML of the post. This makes for more useful material for future uses that we might not yet have imagined.

And in the meantime, making our site less annoying to use for visually-impaired members, by avoiding easily-avoided formatting errors, is worthwhile all by itself.

What about bolding the leading sentence, thesis statement, or question summary?

That's fine! That's not a header, that's just a sentence being emphasised due to its importance in the answer, question, or paragraph. That's what our bold formatting is for. In fact, marking it as bold will correctly indicate that it's not supposed to be understood as a section header, improving meaning and accessibility. Using section heading formatting is only recommended for things that are actually section headings.

Source Link
Someone_Evil Mod
  • 48.9k
  • 1
  • 28
  • 84

The fix

Fake headers are easily fixed. When you want to make a header, there are three ways to create one:

  • Click the Heading editor button:

    A screenshot of the editor toolbar. The Heading button is a stack of five horizontal lines that alternate between short and wide lines, the first two black and the last three grey, visually representing a paragraph with a heavier header on top. The button is picked out with a red freehand circle around it.

  • Select the heading text and type ctrlh.

  • Manually type the Markdown code for a header, which is either an underline made from dashes or equal signs, or one to three hash marks in front of or surrounding it (“or”, because the trailing ones are optional).

    The exact symbol used defines the logical level (and visual size) of the resulting heading:

      # Level 1 heading #
    
      ## Level 2 heading ##
    
      ### Level 3 heading ###
    
      ### No hashes at the end is also OK for any heading level
    
      Level 1 heading
      ===============
    
      Level 2 heading
      ---------------
    

If you have existing fake headings, the easiest fix is to edit the post and replace the ** around the fake headings with ##.

It's not just for human accessibility

This isn't just a matter of accessibility to visually-impaired humans either, it's a matter of accessibility to computers in general. The more we use correct formatting, the more the meaning and structure of the contents is reflected in the HTML of the post. This makes for more useful material for future uses that we might not yet have imagined.

And in the meantime, making our site less annoying to use for visually-impaired members, by avoiding easily-avoided formatting errors, is worthwhile all by itself.

What about bolding the leading sentence, thesis statement, or question summary?

That's fine! That's not a header, that's just a sentence being emphasised due to its importance in the answer, question, or paragraph. That's what our bold formatting is for. In fact, marking it as bold will correctly indicate that it's not supposed to be understood as a section header, improving meaning and accessibility. Using section heading formatting is only recommended for things that are actually section headings.

Post Made Community Wiki by Someone_EvilMod