Skip to main content
added 74 characters in body
Source Link
Thomas Markov
  • 154.5k
  • 1
  • 35
  • 125

It's a somewhat common habit at RPG.se to use bold sentences to make the appearance of a header for a section of text, rather than using our existing header formatting. This is probably because it's a common hack elsewhere on the Internet where heading formatting isn't available, and because the button in the editor for bold is more obvious than the button for a heading.

The problem

This habit causes problems though, and is so easily avoided.

The Internet in general has many visually-impaired users, and we're no exception — we know of a number of site members who have said they are visually impaired. Visually impaired users commonly use one or more of a variety of accessibility software to navigate a question and its answers, and to have the part of interest read aloud. The problem with bold sentences used to make fake headers is twofold:

  1. They aren't recognised as headings, so they can't be used for assisted navigation.
  2. They aren't read aloud as headings, making it harder to figure out what the text is supposed to mean when read aloud.

Return to FAQ Index

It's a somewhat common habit at RPG.se to use bold sentences to make the appearance of a header for a section of text, rather than using our existing header formatting. This is probably because it's a common hack elsewhere on the Internet where heading formatting isn't available, and because the button in the editor for bold is more obvious than the button for a heading.

The problem

This habit causes problems though, and is so easily avoided.

The Internet in general has many visually-impaired users, and we're no exception — we know of a number of site members who have said they are visually impaired. Visually impaired users commonly use one or more of a variety of accessibility software to navigate a question and its answers, and to have the part of interest read aloud. The problem with bold sentences used to make fake headers is twofold:

  1. They aren't recognised as headings, so they can't be used for assisted navigation.
  2. They aren't read aloud as headings, making it harder to figure out what the text is supposed to mean when read aloud.

It's a somewhat common habit at RPG.se to use bold sentences to make the appearance of a header for a section of text, rather than using our existing header formatting. This is probably because it's a common hack elsewhere on the Internet where heading formatting isn't available, and because the button in the editor for bold is more obvious than the button for a heading.

The problem

This habit causes problems though, and is so easily avoided.

The Internet in general has many visually-impaired users, and we're no exception — we know of a number of site members who have said they are visually impaired. Visually impaired users commonly use one or more of a variety of accessibility software to navigate a question and its answers, and to have the part of interest read aloud. The problem with bold sentences used to make fake headers is twofold:

  1. They aren't recognised as headings, so they can't be used for assisted navigation.
  2. They aren't read aloud as headings, making it harder to figure out what the text is supposed to mean when read aloud.

Return to FAQ Index

deleted 2465 characters in body
Source Link
Someone_Evil Mod
  • 48.9k
  • 1
  • 28
  • 84

It's a somewhat common habit at RPG.se to use bold sentences to make the appearance of a header for a section of text, rather than using our existing header formatting. This is probably because it's a common hack elsewhere on the Internet where heading formatting isn't available, and because the button in the editor for bold is more obvious than the button for a heading.

The problem

This habit causes problems though, and is so easily avoided.

The Internet in general has many visually-impaired users, and we're no exception — we know of a number of site members who have said they are visually impaired. Visually impaired users commonly use one or more of a variety of accessibility software to navigate a question and its answers, and to have the part of interest read aloud. The problem with bold sentences used to make fake headers is twofold:

  1. They aren't recognised as headings, so they can't be used for assisted navigation.
  2. They aren't read aloud as headings, making it harder to figure out what the text is supposed to mean when read aloud.

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.

It's a somewhat common habit at RPG.se to use bold sentences to make the appearance of a header for a section of text, rather than using our existing header formatting. This is probably because it's a common hack elsewhere on the Internet where heading formatting isn't available, and because the button in the editor for bold is more obvious than the button for a heading.

The problem

This habit causes problems though, and is so easily avoided.

The Internet in general has many visually-impaired users, and we're no exception — we know of a number of site members who have said they are visually impaired. Visually impaired users commonly use one or more of a variety of accessibility software to navigate a question and its answers, and to have the part of interest read aloud. The problem with bold sentences used to make fake headers is twofold:

  1. They aren't recognised as headings, so they can't be used for assisted navigation.
  2. They aren't read aloud as headings, making it harder to figure out what the text is supposed to mean when read aloud.

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.

It's a somewhat common habit at RPG.se to use bold sentences to make the appearance of a header for a section of text, rather than using our existing header formatting. This is probably because it's a common hack elsewhere on the Internet where heading formatting isn't available, and because the button in the editor for bold is more obvious than the button for a heading.

The problem

This habit causes problems though, and is so easily avoided.

The Internet in general has many visually-impaired users, and we're no exception — we know of a number of site members who have said they are visually impaired. Visually impaired users commonly use one or more of a variety of accessibility software to navigate a question and its answers, and to have the part of interest read aloud. The problem with bold sentences used to make fake headers is twofold:

  1. They aren't recognised as headings, so they can't be used for assisted navigation.
  2. They aren't read aloud as headings, making it harder to figure out what the text is supposed to mean when read aloud.
Bumped by Community user
replaced http://meta.rpg.stackexchange.com/ with https://rpg.meta.stackexchange.com/
Source Link
replaced http://meta.rpg.stackexchange.com/ with https://rpg.meta.stackexchange.com/
Source Link
Loading
making an explicit note of this in the code example. it's in the paragraph above, but many won't read that & just want the code.
Source Link
doppelgreener
  • 36.6k
  • 4
  • 171
  • 366
Loading
edited tags
Link
SevenSidedDie Mod
  • 244.5k
  • 4
  • 144
  • 371
Loading
added 36 characters in body
Source Link
SevenSidedDie Mod
  • 244.5k
  • 4
  • 144
  • 371
Loading
trailing number signs / hashes / pound signs / octothorp(e)s are optional; what about thesis statements in bold?
Source Link
SevenSidedDie Mod
  • 244.5k
  • 4
  • 144
  • 371
Loading
not all bold, just fake heading bold
Source Link
SevenSidedDie Mod
  • 244.5k
  • 4
  • 144
  • 371
Loading
Tweeted twitter.com/StackRPG/status/769223871543246848
Source Link
SevenSidedDie Mod
  • 244.5k
  • 4
  • 144
  • 371
Loading