[Image description in Alt Text.] [ID: Red, block text on a transparent background. The text reads: ‘Fanfic Author PSA’. The dark red Archive of Our Own logo is depicted on either side of the lettering. End ID.]
Many people who read fanfiction also require the assistance of text-to-speech or audio description software. Blind and visually impaired people are very much present in the fanfiction and fandom communities, but are so frequently disregarded or forgotten about.
If you are writing a work and like to utilise paragraph breaks, please do not use combinations such as the following:
[Image description in Alt Text. I have used an image to avoid what I will describe below.] [ID: Four examples of punctuation and icons that are disruptive when used as line breakers. The first line is a series of O letters. The second is a series of asterisks. The third is a series of dots, circles and stars. The last is a series of tildes. End ID.]
The software will read these combinations out loud letter for letter or symbol for symbol. For example; it would read to the user the word ‘asterisk’ six times in a row, or the word ‘tilde’ five times in a row.
This is unpleasant, confusing and often irritating for blind or visually impaired readers. If you would like a similar sample of what it would sound like, enter one of the above combinations into Google Translate and use the audio button.
Here is a post by @ao3commentoftheday that also details this difficulty and provides links to downloadable audio transcribers and fanfiction audio readers. These are also helpful for if you simply wish to listen to fanfiction but can’t find a podfic of the work.
Screen Reader Friendly and Screen Reader Compatible are AO3 tags that help visually impaired readers track and access fanfiction that is consciously created with their needs in mind. Please consider adding these tags to your works in order to expand the range of works that visually impaired readers can safely and confidently access.
Alternatives to these are:
Utilise HTML or embedded line break functions where possible, such as the feature on the Archive’s editing functions. Most screen readers should be equipped to understand these.
[Line breaker] can also be read by most screen readers. While not as aesthetic, it’s still functional.
Use an image divider/breaker and utilise the Alt Text or [ ] descriptor functions to label it as a line breaker.
Reminder: ‘liking’ this post does not spread awareness.
Even if you don’t rely on it, I highly recommend using a reader to listen to your fic once you’re done writing. I always do that, because it’s easier to find typos and errors and you also realise how it sounds to people who listen to it.
Firefox has a reading mode on PC where you can turn on text-to-speech, the mobile version doesn’t have one, but you can use the on-board version every phone has.
I’m not seeing the simple answer to this problem.
The html is <hr>
This is what it looks like in my most recent fic.
It makes a very lovely simple break. Even if you don’t use the html entry, you can switch to html after entering rich text and then put in your breaks.
