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.
• Seeing as we are using a Q&A format, should the solution to this problem (i.e. 'The Fix' and onwards) be moved to an answer? Having our accepted solution as an answer should save Community-friend from bumping it if nothing else. – Someone_Evil Nov 4 at 15:36
• @Someone_Evil Probably! The guidance for the main SE FAQ is to frame them as a question, and I added that to our own FAQ index at some point, but we had a lot of older [faq] metas that hadn’t been written that way. It wasn’t high on the list of priorities to change them then. – SevenSidedDie Nov 4 at 15:49
• I went ahead and made that change. If we could now get upvotes/accept mark so it shows at the top that would be lovely. (If this was out of line, please inform and/or revert) – Someone_Evil Nov 8 at 11:27
• @Someone_Evil Thank you! – SevenSidedDie Nov 8 at 14:55

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:

• 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 #

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

===============

---------------


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.