#Blind and #visionimpaired people, and those who design accessible #PenPaper #rpg rulebooks in my followers: How do you read roleplaying game books, and what do you do with charts, map and illustrations?
-
#Blind and #visionimpaired people, and those who design accessible #PenPaper #rpg rulebooks in my followers: How do you read roleplaying game books, and what do you do with charts, map and illustrations?
Right now, most of my rulebook is text (see https://roa.5f9.de), and relies on purely textual information to convey things. That should be decently accessible with a screen reader.
BUT: I am thinking of redoing the skill "tree" with a hex map, so that each skill learned unlocks those that are touching that hex for future learning.
So, assuming you learn the skill "Physical Combat", that has "Stalwart Defender", "Hold Ground" and "Shield Use" adjacent to it - so these are unlocked now, even though "Shield Use" is part of a different skill group.
Visually, it is pretty easy to lay out and read. But how would that translate that to a screen reader? Would it be enough to list all adjacent skills in a skills description, and then people compile the map in their head?
My design goal is to lower cognitive load and lookups wherever I can, and this is a great way to do it visually, but I fear that it'll make things a lot harder for non-seeing people?
*edit: Boosts welcome
-
E energisch_@troet.cafe shared this topic
-
#Blind and #visionimpaired people, and those who design accessible #PenPaper #rpg rulebooks in my followers: How do you read roleplaying game books, and what do you do with charts, map and illustrations?
Right now, most of my rulebook is text (see https://roa.5f9.de), and relies on purely textual information to convey things. That should be decently accessible with a screen reader.
BUT: I am thinking of redoing the skill "tree" with a hex map, so that each skill learned unlocks those that are touching that hex for future learning.
So, assuming you learn the skill "Physical Combat", that has "Stalwart Defender", "Hold Ground" and "Shield Use" adjacent to it - so these are unlocked now, even though "Shield Use" is part of a different skill group.
Visually, it is pretty easy to lay out and read. But how would that translate that to a screen reader? Would it be enough to list all adjacent skills in a skills description, and then people compile the map in their head?
My design goal is to lower cognitive load and lookups wherever I can, and this is a great way to do it visually, but I fear that it'll make things a lot harder for non-seeing people?
*edit: Boosts welcome
-
S svenja@mstdn.games shared this topic
