accessibility > aesthetics.
it's been said many times, but accessibility in the rpc is a real issue - i have seen quite a few people tag graphics with eyestrain, which is good, but we can do more. particularly when it comes to fonts as screen readers cannot read some of the fonts used and, honestly, the rpc in general tends to over-format their posts. aesthetics is one thing, but you really don't need 7 different fonts and styles in your posts ( personally i only really use it for character names so the post doesn't get thrown into the char tags even though it's untagged, thanks tumblr! ) though most often i see it used for headings which i think is fine in small doses - but it's quite common to see several fonts, styles and colours in peoples posts which is far less accessible. spacing is a complicated matter as personally it makes things much harder for me to read and i know several roleplayers who have said the same, but have also seen people argue that it makes things easier for others to read. it differs person for person, so it's best to ask! similarly, whilst it's rare i do see it still - posting your replies as images completely disregards accessibility.
below is a list of those that it can read and those it cannot - when in doubt, it doesn't hurt to temporarily use a screen reader to double check or asking the person you are writing with if it's a thread. make your writing and your blog accessible and ask if those you are writing with need any particular formatting in order to assist with any dyslexia or visibility problems. when plotting or discussing threads, it only takes a few seconds to ask "hey, do you need anything specific regarding accessibility or visibility in these posts?"
unfortunately i am unable to test all available screen readers that are available, so if you have any additions do let me know! i have tested on a few screen readers and text-to-speech programs: ttsreader, ChromeVox, Pericles: screen reader extension on chrome and firefox, NVDA (windows), murfai, tts by Readme, Screen Reader by UserWay, Google text-to-speech, NaturalReader text-to-speech and textmagic.
๏ฝ๏ฝ๏ฝ๏ฝใ๏ฝ๏ฝ๏ฝ๏ฝ
these ones may or may not work depending on the text-to-speech or screenreader. they appear to work on textmagic, on Screen reader by UserWay, Pericles: screen reader extension on chrome and firefox, and google text-to-speech. i have tested it with ChromeVox and these fonts sometimes work and sometimes don't for some reaso - if i would suggest that if you are in doubt, ask:
๐๐๐๐ ๐๐๐๐
๐ญ๐ก๐ข๐ฌ ๐๐จ๐ง๐ญ
๐๐ต๐ถ๐ ๐ณ๐ผ๐ป๐
๐ฉ๐๐๐จ ๐๐ค๐ฃ๐ฉ
these fonts do not work with most screen readers / tss:
๐ฑ๐ฅ๐ฆ๐ฐ ๐ฃ๐ฌ๐ซ๐ฑ ( works with Pericles )
๐๐๐๐ ๐๐๐๐ ( works with Pericles )
โ๐นโโ๐ญโโ๐ฎโโ๐ธโ โ๐ซโโ๐ดโโ๐ณโโ๐นโ
แตสฐโฑหข แถ แตโฟแตโ
๐ฅ๐๐๐ค ๐๐ ๐๐ฅ ( works with Pericles )
๐๐๐๐ ๐๐๐๐ ( works with Pericles )
๐๐ฝ๐พ๐ ๐ปโด๐๐ ( works with Pericles )
๐ฝ๐ฑ๐ฒ๐ผ ๐ฏ๐ธ๐ท๐ฝ ( works with Pericles )
tฬทhฬทiฬทsฬท ฬทfฬทoฬทnฬทt
those that don't work simply will not read out the words, skipping them altogether if there is text it can read either side of it, resulting in large amounts of text being unread. if you absolutely have to use several fonts or large amounts of text in these fonts ( i wouldn't think so, though ) then please add "captions" below the text, possibly in a blockquote or read-more, where the text is plainly typed so it can be read.
tฬธฬอ อ
ฬชฬฃฬฏอฬผฬ ฬบอฬกฬ อฬงฬผhฬทฬอฬอฬฬ ฬบฬซฬiฬธอออฬฬฬฬพฬกsฬธฬฬอฬฬฃฬฅฬฎอฬขฬฒอฬฃ ฬตอฬฬอออฬฝฬฬอออฬฎฬอฬชฬผฬณอออฬปฬฌอfฬทออออฬฬฬฬฬออฬซอฬฒฬปฬกฬผฬขฬคฬชฬ ฬชอฬกอoฬธอฬฬอฬฬฬออฬอฬฬฃอฬฬซอnฬทฬอฬอฬฬอฬฬออฬฬอtฬทฬฬอฬอฬอออฬอฬญฬคอฬจ
the above "cursed text" font...kind of works? it reads it out letter by letter, as does tอhอiอsอ อfอoอnอtอ, so i would recommend against using them for anything but short single words.
please keep this in mind and try to make your blog accessible!