Adding Accessibility in My Code?

[manonamora (Manon)]

Twine being a basic HTML page when compiled is already accessible, see this thread, with SugarCube being more ARIA-compliant than Harlowe.

@poetoaster

I tried just switching my builder from Harlowe to Sugarcube since I know that one has some accessibility-minded structure (I didn’t have high hopes this would work but figured I’d try anyway), and predictably the code didn’t transfer well.

This is because Harlowe and SugarCube have different ways of formatting their code. The SugarCube documentation has a chapter on some of the differences, but not all macros are easily transferable.
If you do run into some specific errors, please share the erroneous code with us and we can help find an alternative.

@poetoaster

I’m wondering, if I export my Twine file to Twee, would I be able to switch format to Sugarcube? Is there a way to “transfer” my Harlowe code that way? I’ve never used Twee so I don’t yet know how it works.

To change a project from one format to another, you will need to change it for the project, in Story → Details (see Screenshots) and edit the code from Harlowe to SugarCube.


(Twee is just another output format, think the difference between PDF and Word Document - unlike HTML it’s not playable, but useful when sharing code)

@poetoaster

heading structure

Headings can be done with the ! at the start of a new line, like ! This is a header or with <h1> (see this section in the SugarCube documentation).
Semantic tags (info) aren’t used by default, but you can include them yourself in passages or when creating your own interface from scratch with StoryInterface.