Make A Dark Room accessible to the blind. about adarkroom HOT 20 OPEN

I've been thinking a lot about this issue and how it can be remedied. How does the iOS version handle takeoff that the visually impaired can successfully navigate it? I haven't played the mobile version.

from adarkroom.

I'm working on that myself. It's a bit easier on the iOS version because they can touch the screen and have different UI controls read out information to them.

Most of the complaints I've gotten so far have been around the map:

• What's around me
• How can I get back to the village
• How far are things

from adarkroom.

I actually feel kind of bad about this issue. At first glance, ADR appears
to be a fairly accessible game. Once the world map is unlocked, however,
I'm totally at a loss for how to maintain accessibility. This, I'm sure,
leaves a lot of people stuck with no way to progress. I'd love to address
this, but I have no idea how. Any ideas would definitely be appreciated.

On 9 December 2013 13:32, Amir Rajan [email protected] wrote:

I'm working on that myself. It's a bit easier on the iOS version because
they can touch the screen and have different UI controls read out
information to them.

Most of the complaints I've gotten so far have been around the map:

• What's around me
• How can I get back to the village
• How far are things

—
Reply to this email directly or view it on GitHubhttps://github.com/Continuities/adarkroom/issues/70#issuecomment-30158435
.

from adarkroom.

I'm making good progress on the iOS version. And hopefully will have an accessible version out by the end of the month. I'll post what I've learned from that here.

from adarkroom.

What I know so far is that the reading speed of the voice over devices used are set to an extremely fast rate.

from adarkroom.

One idea I can think of is showing that data that @amirrajan pointed out in the top bar or somewhere.

Super quick example:

(Forgive my incomplete map. I restarted my game.)

from adarkroom.

It may just be easier to serve up another view all together. Though some work will have to be put in to unravel DOM manipulation from the engine itself. The problem with the current view is that the readers will literally read every ascii character.

from adarkroom.

Yeah, this is pretty much why the idea of accessibility fills my heart with
dread.

On 9 December 2013 14:18, Amir Rajan [email protected] wrote:

It may just be easier to serve up another view all together. Though some
work will have to be put in to unravel DOM manipulation for the engine
itself. The problem with the current view is that the readers will
literally read every ascii character.

—
Reply to this email directly or view it on GitHubhttps://github.com/Continuities/adarkroom/issues/70#issuecomment-30163890
.

from adarkroom.

If much, or any more is to be changed or added to this game, it needs to be rewritten; as you've said before, Angular would make management of the DOM so much easier, and make fundamental changes like this more feasible. Unfortunately, at this stage of the game's lifecycle, I just don't see that happening.

from adarkroom.

Agreed. Too much would need to be done.

Sent from my iPhone

On Dec 31, 2013, at 6:12 AM, Nathan Munk [email protected] wrote:

If much, or any more is to be changed or added to this game, it needs to be rewritten; as you've said before, Angular would make management of the DOM so much easier, and make fundamental changes like this more feasible. Unfortunately, at this stage of the game's lifecycle, I just don't see that happening.

—
Reply to this email directly or view it on GitHub.

from adarkroom.

Hello,
I found A Dark Room through Portableapps and decided to give it a try. I found out that it was playable, although it had some issues (dynamic content not read automatically, clickable elements, no headings). That was until today, when I discovered the compass and the outside world. (Did I mention I'm blind?)
In case you are interested in implementing accessibility, I can give you some ideas. I don't know how to write JS, but I can more or less understand it.
I would say that a separate view is required for this to work properly. That is to say, the original map would be hidden with aria-hidden=true, showing a blank (or dependent on the hidden one) div, with role=application. Then, keyboard shortcuts could be introduced to query the necessary information from the map, and this information could be communicated to the screen reader using ARIA. I don't know if this makes sense to you or if it's possible, but I believe it's logical enough.

As for the other issues I've encountered:

• Dynamic content: aria-live could be used, though it may be too chatty at times, especially with supplies.
• Clickable eleements and lack of headings: The most straightforward method is to use the standard elements instead of (or outside) the clickable spans (links or buttons and headings). ARIA roles can also be used.

Thank you very much for this great game.

from adarkroom.

@sukiletxe Thank you for sharing your experience! You have definitely helped me think of some ideas for combatting this issue. I'll do some research on a few of the tips that you gave us, and at the very least, make some of the smaller changes.

Thank you again!

from adarkroom.

from adarkroom.

I don't know much about accessible interfaces, but why not allow the character to be moved by point-and-click? Just let users control a cursor moving square by square, and allow them to target a square to move the character there. Additionally, the UI could show the closest point of interest in all directions, like:

      T 4
       ^
A 3 <  B  > H 2
       v
      A 3

Home: 6 South-East

In this instance, the cursor is over a square with POI type B which is exactly 3 squares right and 3 squares up from A, and A is the closest POI in both left and down directions, hence why the repeat. Also, Home: x always give the distance from currently highlighted square to the base, because that's a crucial information (along with water and food, the rest is not so important, so I guess they should be make <strong> or something like that). The path could be computed with a simple algorithm such as Djikstra algo, or A* breadth-first if you want something faster (but in any case, you don't need to walk through the whole map, just find the closest point to each cardinal direction) with Manhattan distance.

If an enemy is encountered, a message box could be shown to ask if user want to continue with some infos like health and stuff. Also of course, the battles would need to be turn-by-turn, because I hardly see how a blindhelper reading software could be as fast as some enemies attacks.

Also an alternative HUD that would be super accessible without any loss of information:

Home at 6 squares South-East, Current: B, left: A at 3 squares, down: A at 3 squares, right: H at 2 squares, up: T at 4 squares

Just my 2cents about a possible alternative view for blind people,

from adarkroom.

I do like this issue, how could we do this?

from adarkroom.

I'm playing this on iOS and really enjoy it so far, so just wanted to say thanks for everything that's been done there.
One thing I notice is that the web version is a lot less accessible for whatever reason. The main issue is that none of the buttons actually have a button role, and the percentage bars (for instance, to indicate when you can stoke the fire or check traps) are not readable. Can this be fixed? I would think adding a role to the buttons and a screen-reader-only (invisible) text label for the percentages would do it. I have no clue about the world map on the web. I'm likely going to be playing it on iOS for the most part unless this issue looks like it's likely to happen, and then I'm happy to test and poke around in the DOM more.

I'm an accessibility tester and super newbie coder, hoping to get to a point where I can start doing pull requests for this kind of thing myself but I'm not there yet. Thank you for your consideration.

from adarkroom.

from adarkroom.

Sorry for the confusion.

I was using the native iOS app on iOS and that has a lot of accessibility built in. I didn't realize there was a web version for quite some time, and was using it on Windows. I wouldn't call it inaccessible, but there's almost no meaningful HTML markup on the page, which means shortcut keys for moving to next/previous control don't work and keyboard navigation (tab, shift+tab, etc.) also doesn't work. Screen reader users rely on the ability to do things like moving to the next heading or button, so not having these control types defined on the page causes the interface to feel extremely clunky.

from adarkroom.

from adarkroom.

That's good to know. I saw that it was linked on the page, so didn't realize the two projects were maintained by separate developers.

I mostly mentioned the iOS app because of the extra accessibility though; I'm here because I'm interested in using this web version.

from adarkroom.