User:Tale glider/sandbox2: Difference between revisions

From VNDev Wiki
testing a possible accessibility feature
m highlight one more word
 
Line 2: Line 2:
* <span class="highwords">Marking</span> if the <span class="highwords">dialogue</span> or narration on screen has been <span class="highwords">shown before</span>, such as by changing the appearance of the <abbr title="Click-to-Continue">CTC</abbr> indicator if it has. That way players who struggle reading can spend less time on re-reading lines they've already read.
* <span class="highwords">Marking</span> if the <span class="highwords">dialogue</span> or narration on screen has been <span class="highwords">shown before</span>, such as by changing the appearance of the <abbr title="Click-to-Continue">CTC</abbr> indicator if it has. That way players who struggle reading can spend less time on re-reading lines they've already read.
* <span class="highwords">Avoid</span> really <span class="highwords">long lines</span> of text: allow text containers to be resized by the player, or to automatically shrink horizontally when the font size shrinks. Something like a width of 18 times the font height should work.
* <span class="highwords">Avoid</span> really <span class="highwords">long lines</span> of text: allow text containers to be resized by the player, or to automatically shrink horizontally when the font size shrinks. Something like a width of 18 times the font height should work.
* When the text doesn't fit on one line, try to <span class="highwords">split</span> it <span class="highwords">at punctuation marks</span>, or to split it into <span class="highwords">lines of roughly the same length</span>.<br>If the engine doesn't support that, it might help a bit to put non-breaking spaces before the last word in each piece of text so that a word doesn't end up shown on a line of its own.
* When the text doesn't fit on one line, try to <span class="highwords">split</span> it <span class="highwords">at punctuation marks</span>, <span class="highwords">or</span> to split it into <span class="highwords">lines of roughly the same length</span>.<br>If the engine doesn't support that, it might help a bit to put non-breaking spaces before the last word in each piece of text so that a word doesn't end up shown on a line of its own.
* <span class="highwords">Use correct spelling</span>, capitalization and punctuation, or provide an option to use them. Such an option would probably mean having to write several versions of some text and switching between them. But if you want to express a character's accent through misspellings, that's probably the least intrusive way to do it.
* <span class="highwords">Use correct spelling</span>, capitalization and punctuation, or provide an option to use them. Such an option would probably mean having to write several versions of some text and switching between them. But if you want to express a character's accent through misspellings, that's probably the least intrusive way to do it.
* Related to the above: <span class="highwords">Proofread</span> the script, and preferably get several people to do so. Typos or other mistakes could make the script harder to read.
* Related to the above: <span class="highwords">Proofread</span> the script, and preferably get several people to do so. Typos or other mistakes could make the script harder to read.

Latest revision as of 02:39, 20 December 2024

This is a test for the accessibility page (I could see it being useful on more pages, but being an accessibility feature that requires all text to be edited to account for it). I'm still not sure if I want to apply this, but I wanted to at least see what it could look like.

  • Marking if the dialogue or narration on screen has been shown before, such as by changing the appearance of the CTC indicator if it has. That way players who struggle reading can spend less time on re-reading lines they've already read.
  • Avoid really long lines of text: allow text containers to be resized by the player, or to automatically shrink horizontally when the font size shrinks. Something like a width of 18 times the font height should work.
  • When the text doesn't fit on one line, try to split it at punctuation marks, or to split it into lines of roughly the same length.
    If the engine doesn't support that, it might help a bit to put non-breaking spaces before the last word in each piece of text so that a word doesn't end up shown on a line of its own.
  • Use correct spelling, capitalization and punctuation, or provide an option to use them. Such an option would probably mean having to write several versions of some text and switching between them. But if you want to express a character's accent through misspellings, that's probably the least intrusive way to do it.
  • Related to the above: Proofread the script, and preferably get several people to do so. Typos or other mistakes could make the script harder to read.