Responses to the A Night Below the Opera (Inform) survey

The tag after each response lists the player’s operating system, IF interpeter program (often a web browser), and a summary of their assistive technology setup.

Return to the accessibility report main page

How did you read the text and other media that the game provides? Did you encounter any consistent difficulty with this?

• sight read (Windows / Chrome / Screen magnifier)

• I read it through the web browser, I read the text as it appeared, I did not encounter issues with this. (Windows / Firefox / no AT)

• i have to use zoom function and night mode to turn screen from white to black to read the text easier (Mac / Chrome / Screen reader, Screen magnifier)

• tezt fint could be a tad darker.other then that was fine (Windows / Firefox / none)

• I read it normally. The black font on white background made it somewhat painful to read, the option to be white font on black background would be welcome. The font chosen was very difficult to read for me, I am dyslexic. Ability to use a font installed on personal computer instead would be very helpful so I could use OpenDyslexic. (Windows / Chrome / no AT)

• visual from monitor (Windows / Chrome / no AT)

• The text seemed simple and clear to read throughout. (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Text came in automatically, and I was able to see previous text with my screen reader’s review cursor.
  The console photo didn’t show the buttons and compartment.
  None of the non romantic language text could be read by my screen reader, it was just silent even when reviewing symbol by symbol. Even when I changed my screen reader’s language to that of the language on the sign, it could only pick out a few letters at most. I think I would need to install system language packs and possibly also mess with app locale to be able to hear more than that.
  The emoji’s weren’t shown properly, which is odd considering I have an add-on for my screen reader to do that. On Ilectrote and the browser how ever, I saw grinning face and thumbs up just fine… (odd) Maybe it has something to do with Wingit’s console roots?
  No screen reader has ever been able to interpret ASCII art as anything more than symbols and letters regardless of the program outputting it, so that’s all it saw, a couple plus’s on top and bottom, some X’s, O’s, and a backslash in the middle.
  I don’t have my screen reader set to show font changes, as I find it tedious at most times. But I was able to see the difference just fine when I enabled that and looked at the font sign.
  Everything else was read fine, including the extra plaque text, though that could not be reviewed in the buffer as other text could be, along with the instructions for the projector. Ilectrote and the browser failed to show it at all. (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• It was a bit different from the interpreters I’ve used before, but not necessarily in a bad way.
  Text was read automatically with little trouble, which already makes Lectrote a good interpreter for the blind, and it doesn’t even need a screen reader add-on to help it like many other interpreters do.
  I couldn’t use my screen reader’s review cursor to see previous text without moving my editing cursor as I can with Wingit or Winfrotz, instead I had to exit the edit field and scroll up, then enter it again to continue inputting commands.
  The score did update, but it didn’t show each move like with Wingit or Winfrotz. I had to go check the very top of the page to see that. But honestly the score command is easy to use and I find the continuous score readout mildly annoying regardless.
  The plaque’s extra text couldn’t be read at all. It opened the pane but it was totally blank.
  Also, every time new text finished coming in, the name of the program would be read out (the window title) as if it was refreshing. Pretty annoying after 10 times.
  When using the projector, I couldn’t see which slide I was on before selecting it, because it would just read the entire menu again every time I moved, rather than the individual item like Wingit was able to do.
  Over all it was perfectly usable reading wise, and was even able to pass the emoji’s on to my screen reader when Wingit couldn’t. (Windows / Lectrote / Screen reader, NVDA latest version)

• Nearly the same as Ilectrote, accept for the fact that the repeating window title issue wasn’t present in the browser, and that, thanks to my “translate highlighted text with google translate” extension for FF, (already built into Chrome by default) I was able to quite quickly read all the signs. How ever I still could not recognize the symbols without that… so I’m gonna call that cheating :P (Windows / Firefox / Screen reader, NVDA latest version)

• The text was automatically read to me by my screen reader. However, after a while, it started reading text from far back in the game, so I had to read the text manually using the arrow keys. (Windows / Chrome / Screen reader)

• I used a screenreader called Nonvisual Desktop Access (NVDA).
  The screenreader read the text through speech synthesizer. (Windows / WinGlulxe / Screen reader)

• either by swiping around on my screen or my screen reader automatically reading the text I did encounter some focus issues when I would type in a command it would read out some other response from a command I typed in earlier or it would jump around the screen to a button in the app ( iPhone running latest version of iOS / Frotz (iOS) / Screen reader)

• I had the screen reader, System Access, read the Chrome window and used standard web navigation commands. It actually worked very well. The only confusing part was the slideshow. This edit field didn’t seem to be recognized correctly with SA. After turning Magnifier on, I saw that the text arrow was changing slides, but SA wasn’t announcing it. Oh, and that dance floor ASCII grid didn’t make any sense until I used it with Windows Magnifier. I also didn’t think to issue commands to read each individual sign in the washroom until reading the below questions. I just figured the overall description was a general description. of a single sign with lines of several languages. (Windows / Chrome / Screen reader, Screen magnifier)

• I used google talkback. Couldn’t understand the ascii or the plaque or all but the english sign. (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• It was read aloud automaticaly after I wrote everything. (Windows / Firefox / Screen reader)

• with my eyes and glasses (Windows / Firefox / high contrast browser add on)

• The text was hard to read. It being whit text on a dark background would be much better (Windows / Chrome / Screen magnifier)

• With my eyes; no (Mac / Safari / no AT)

• I used the NVDA (Non Visual Desktop Access) screen reader to play this game. A user can install various add-ons in order to add features to NVDA. I used one called
  “Automatic speech output for interactive fiction interpreters (IF Interpreters)”
  By Nick Stockton
  Version 1.2
  As the title states, this enables automatic reading of any text that appears on screen after inputting a command and pressing enter. For example if you examine multiple items in a room, it will only read new text and not previous paragraphs. This add-on works with many different interpreters, TADS, Inform, Hugo etc. I have mostly tested it with older games such as those by Infocom. It read most of this game perfectly but for the photo of the console in the smoking room. No matter what I entered, “Examine, look”, the only response was
  “This photograph shows an ornate control console.”
  I had to use the walkthrough to pass this area of the game. I did not configure any options in the interpreter. (Windows / Windows Glulx / Screen reader)

• I used a screen reader to read the output. On Mac, I used VoiceOver’s navigation commands to read through the web area of the interpretor. On Windows, I used the IF-interpretor addon for NVDA, which makes interpretors work better with it. On iOS, Frotz sends text directly to VoiceOver to be read.
  On Mac, reading through the text is easy, but all the navigation from the command entry field, which isn’t labeled as such, back up to the game text, takes more time than most people, including me, would give even a shorter game like this.
  On Windows, there are few accessible interpretors, and with the NVDA addon, some text from previous outputs is repeated in the current output.
  On iOS, some output from previous turns is repeated instead of the current output, forcing me to “look” and possibly miss information from the first description. (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• I used NVDA coupled with an add-on that automatically reads text displayed by several IF interpretors.
  Text that wasn’t ASCII art, Arabic or Hebrew read fine. NVDA cannot interpret ASCII art. and the Arabic and Hebrew text were read from left to right as far as I can tell, which doesn’t usually happen. (Windows / Windows Glulxe / Screen reader)

• It was decent enough to read, though options to change text would be appreciated. (Windows / Chrome / Color inverter extension)

• Read it as regular printed text in the browser, i.e. without assistive tech. I had no difficulties, but the card did not play any audio when opened. (Windows / Chrome / no AT)

• I used the text to speech. Any pure text of the game read out fine, except in there was apparently some extra text that got cut off when reading the placque. The walkthrough mentions some text after “knock three times.” (Windows / winGlulxe / Screen reader)

• JAWS screen reader in JAWS mode (Windows / Quixe / Screen reader)

How did you input commands to the game? Did you encounter any consistent difficulty with this?

• keyboard (Windows / Chrome / Screen magnifier)

• I used a keyboard, i used the copy and paste function for easier navigation. (Windows / Firefox / no AT)

• i type in the command with some difficulty as I didn’t understand how command works but thankfully the help guide was there to tell me what to say (Mac / Chrome / Screen reader, Screen magnifier)

• keyboard.no issues (Windows / Firefox / none)

• Type on personal keyboard (selected for compatibility with my tremor and nerve damage). (Windows / Chrome / no AT)

• m&k (Windows / Chrome / no AT)

• Input via keyboard, no difficulty. (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• I just typed into Wingit as I normally would and got feedback perfectly fine. I did hear the end letter of each command echoed, which was somewhat annoying, but this is a problem with Wingit in general and something that the add-on I use was unable to solve for what ever reason. (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• I had to go to the edit field, enter it and then start putting in commands, rather than just typing straight into the program as with the console based Wingit, but that was no big deal, just different.
  I was also able to see the previous commands in the buffer, unlike with Wingit where they aren’t actually read out when scrolling up in the edit field.
  I also didn’t get any annoying command echo’s like with some other interpreters, which I appreciated.
  Everything else worked perfectly, even using the arrows for the projector. (Windows / Lectrote / Screen reader, NVDA latest version)

• The only difference between Quixe online and via Ilectrote was that in the browser, occasionally the first letter of my command would be chopped off, possibly do to interrupting the incoming text by typing too quickly while it was scrolling? It did not happen more than a handful of times though. (Windows / Firefox / Screen reader, NVDA latest version)

• I typed commands into the edit field. I encountered no difficulties. (Windows / Chrome / Screen reader)

• I typed commands on keyboard. (Windows / WinGlulxe / Screen reader)

• I would input commands by typing them in to my interpreter I did encounter some focus issues with the responses after I would type the commands into my interpreter ( iPhone running latest version of iOS / Frotz (iOS) / Screen reader)

• It mostly worked fine. There were a few times I didn’t know what syntax to use so the game would recognize what I meant, but I figured it out. I’ve played text adventures before. (Windows / Chrome / Screen reader, Screen magnifier)

• I used the built in samsung keyboard. No issues here. (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• By tipping them in the edit box. (Windows / Firefox / Screen reader)

• keyboard (Windows / Firefox / high contrast browser add on)

• keyboard (Windows / Chrome / Screen magnifier)

• With the keyboard; yes because it is hard for me to type (Mac / Safari / no AT)

• I was able to type commands and NVDA read the characters as they were typed. It did not read the previous command typed if I pressed up arrow or the characters of a typed command if I pressed left or right arrow. This is however a fault of the NVDA add-on. (Windows / Windows Glulx / Screen reader)

• On Mac, the Lectrote command entry field isn’t labeled as a command entry, but usually people know what a text box in an interactive fiction game means. On Windows, I had no problems. On iOS, I had no problems. (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• I used a standard QWERTY keyboard. I could input all commands with no issues. (Windows / Windows Glulxe / Screen reader)

• Typing; the game wouldn’t always pick up my first keystroke, which isn’t happening elsewhere. (Windows / Chrome / Color inverter extension)

• I use an app on my phone that functions as a realtime keyboard and touchpad to control my computer, and I typed commands that way. My main difficulty reminded me of playing this type of game way back on the Commodore 64 - I sometimes couldn’t figure out what command words were required. Even with the walkthrough, it took several minutes to figure out how to get to the basement! Since all the other movements were cardinal directions, “down” wasn’t very intuitive. Also, I tried “put vase on [something]” several times before checking the walkthrough. (Windows / Chrome / no AT)

• I typed commands. Having played IF before, this was no problem. (Windows / winGlulxe / Screen reader)

• External keyboard with no problem (Windows / Quixe / Screen reader)

Is there any other information about your disability, the assistive technology you use, or your game-testing setup that you’d like to tell us about?

• no (Windows / Chrome / Screen magnifier)

• Occasionally I use the onscreen windows keyboard. (Windows / Firefox / no AT)

• i’m deaf blind gamer who depend on visual aid and audio cue (Mac / Chrome / Screen reader, Screen magnifier)

• no (Windows / Firefox / none)

• I use specially selected tracball and keyboard to be comfortable for me to use. I use normal headphones for audio. (Windows / Chrome / no AT)

• I use a wireless keyboard and mouse so that I can lie down and still be capapble of playing. (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• I’m fully blind, and use a keyboard and headphones. (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• I’m fully blind and use a keyboard and headphones. (Windows / Lectrote / Screen reader, NVDA latest version)

• I’m fully blind and use a keyboard and headphones to play. (Windows / Firefox / Screen reader, NVDA latest version)

• I am blind and I use NVDA as my primary screen reader. (Windows / Chrome / Screen reader)

• I use some add-ons for NVDA.
  These relevant for playing this game are:

  Automatic speech output for interactive fiction interpreters (IF Interpreters)
  Description: Enables automatic speech output for interactive fiction interpreters.

  Speech history review and copying (speechHistory)
  Description: [This add-on allows you to review the 100 most recent strings spoken by NVDA‘, by default using Shift+F11 and Shift+F12. Additionally’, you can copy any spoken item to the clipboard by pressing F12.’]

  The second was especially helpful in this game. (Windows / WinGlulxe / Screen reader)

• Other than the problems above, the screen reader worked well throughout the game. (Windows / Chrome / Screen reader, Screen magnifier)

• It works on android too from what I played, but I can’t tick both obtions and I don’t use volarium or what ever it is called, I use glulcse interpreter. (Windows / Firefox / Screen reader)

• My accessibility needs mostly deal with dexterity and stamina. It is hard for me to play games that require a lot of typing. This game would’ve been much easier for me to play if I were able to click on commands rather than having to input them manually. (Mac / Safari / no AT)

• I understand that some windows interpreters are able to send text to the SAPI engine system voice but I have never had luck using them. I am use to pressing a key such as control to stop speech or enter to move to another area of text and the interpreters I’ve tried did not allow me to do so. They also did not allow me to set the voice rate or choose a specific voice. The NVDA add-on may not be the best way to go for full accessibility but it does allow me to play games from many interpreters. I have been playing IF since 1996 so am definitely familiar with how games are structured. If there are any interpreters that work with SAPI speech or in other ways in windows for a totally blind player, I would love to know of them. (Windows / Windows Glulx / Screen reader)

• Usually, in native applications within operating systems, screen readers cannot automatically speak information as it occurs. Some screen readers have controller clients, and there are a few universal speech tools, and it is best to use the screen reader to speak, since a user can control the voice and speech, and stop speech easily. In HTML5, there is the live regions characteristic, which tells a screen reader to focus on a certain part of a page and speak it when it changes. This could be used in web clients. Generally, go under the assumption that screen readers are stupid and don’t know what to do unless they’re told by the operating system or application; a screen reader does not figure things out on its own, which is rather sad in the “age of AI.” (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• I am totally blind and use NVDA from NVAcces. (Windows / Windows Glulxe / Screen reader)

• I am only on the cusp of legally blind, so I don’t need much accommodation. (Windows / Chrome / Color inverter extension)

• I’m paralyzed chest-down from a high-level spinal cord injury, and I have minimal finger dexterity. As previously mentioned, I use a keyboard/touchpad app on my phone to control my computer. I occasionally use dictation software for longer writing, but not on this test. (Windows / Chrome / no AT)

• I’m completely blind. (Windows / Quixe / Screen reader)

Were you able to complete the game to your satisfaction?

• No (Windows / Chrome / Screen magnifier)

• No (Windows / Firefox / no AT)

• No (Mac / Chrome / Screen reader, Screen magnifier)

• Yes (Windows / Firefox / none)

• No (Windows / Chrome / no AT)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Yes (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• Yes (Windows / Lectrote / Screen reader, NVDA latest version)

• Yes (Windows / Firefox / Screen reader, NVDA latest version)

• Yes (Windows / Chrome / Screen reader)

• Yes (Windows / WinGlulxe / Screen reader)

• Yes ( iPhone running latest version of iOS / Frotz (iOS) / Screen reader)

• Yes (Windows / Chrome / Screen reader, Screen magnifier)

• No (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• Yes (Windows / Firefox / Screen reader)

• Yes (Windows / Firefox / high contrast browser add on)

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Mac / Safari / no AT)

• Yes (Windows / Windows Glulx / Screen reader)

• No (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• No (Windows / Windows Glulxe / Screen reader)

• No (Windows / Chrome / Color inverter extension)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / winGlulxe / Screen reader)

• No (I used the walkthrough) (Windows / Quixe / Screen reader)

Did any of the accessibility challenges pose insurmountable obstacles to you? If so, describe them here.

• Yes. could not find basement, even with walkthrough (Windows / Chrome / Screen magnifier)

• I was unable to solve the dance puzzle to get the sandal, even with the guide. (Windows / Firefox / no AT)

• the background of white didn’t really help me as i have hard time following the texts (Mac / Chrome / Screen reader, Screen magnifier)

• no (Windows / Firefox / none)

• The need to specifically pull a button never occured to me since it was a button. Also, the specific commands for each thing posed impossible as someone with aphasia. (Windows / Chrome / no AT)

• card - only had description of “[Sound effect number 6 here.]” which was not sufficient to solve without walkthrough (Windows / Chrome / no AT)

• The only thing that was difficult was the ASCII puzzle, I had to look that one up. The other bit was using ‘DROP’ Vase instead of ‘PLACE’. (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Without the walkthrough I’d never have been able to finish the game do to the ASCII map. (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• The map was of course impossible, but that’s universal for any game using ASCII art.
  I also wouldn’t have been able to finish the game without the card, and it didn’t work on Ilectrote at all. No alt text was shown either, just a (sound 6 goes here) placeholder… Which I find odd as the console photo’s alt text was read just fine. (Windows / Lectrote / Screen reader, NVDA latest version)

• Same as Ilectrote. (Windows / Firefox / Screen reader, NVDA latest version)

• I had to refer to the walkthrough for the console puzzle involving twisting the 6 to 9. It was completely counterintuitive to me that the button could be twisted, probably because the similarity between the numerals 6 and 9 did not occur to me. This is a very visual way of thinking, and many blind people do not know what the numerals look like. (Windows / Chrome / Screen reader)

• I was unable to read the map and had to use the walkthrough for this puzzle.
  I used SpeechHistory to read the text on the plaque, because only part of it was readable normally.
  Only the part:
  “The plaque is still grungy, but you puzzle out the text.
  ” is readable using key shortcuts for reading the text.
  I was unable to find the verse if I wanted it repeated.
  I kept examining the plaque until NVDA repeated the whole text and then copied it using SpeechHistory.
  I had a weird issue while reading signs on the notice board.
  Normally NVDA reads the text automatically.
  After typing a command and pressing Enter NVDA should read the text which appears after the last typed command.
  After reading the Emoji sign and typing a command NVDA started reading text from anywhere on the screen and not the text after the command I typed, as it usually does.
  It took a few rounds of typing commands for NVDA to return to the normal behaviour.
  For the emoji itself, I noticed NVDA read it automatically, but not when using shortcuts to read the text manually.
  The emoji said “thumbs up”, if I understand correctly. (Windows / WinGlulxe / Screen reader)

• not really just the focus issues and when I would type in a command and then click the enter button it would jump to different parts of the screen sometimes and the slide projector was kind of hard to use and of course the maps not accessible ( iPhone running latest version of iOS / Frotz (iOS) / Screen reader)

• Admittedly I did cheat and look at the walkthrough a couple of times. As I said, that ASCII map didn’t make sense without magnification. Even then, I was stupid and didn’t think to use SW, NE, etc to go diagnal. I got the general directions, but didn’t think to use SW, NE, etc. I also didn’t think to examine each photo individually, just as a group. I pushed button 6, but didn’t think to turn it. Also, when opening the card, it didn’t give me the button sequence, but just said Tone 6, but I’m not sure why. I did otherwise figure things out with a few hints. (Windows / Chrome / Screen reader, Screen magnifier)

• Don’t know what the plaque says, or what the ascii on the note means. (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• It was easy as a piece of cake. (Windows / Firefox / Screen reader)

• no (Windows / Firefox / high contrast browser add on)

• See answer above regarding console photograph. (Windows / Windows Glulx / Screen reader)

• In Windows, having text repeated and not getting the newest output was pretty off putting, so I switched to iOS early on. There, I had better luck, but:

• Emoji weren’t read on the sign in the bathroom

• Frotz wouldn’t play the sound in the gift card.

• The book wasn’t readable, Voiceover said nothing as I scrolled through it.

• the diagram didn’t make sense at all. No screen reader can make sense of ascii graphics. (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• As I am blind, I was unable to see the image in the display case so had to resort to the walkthrough from then on.
  The same is true for the ASCII art map.
  (Windows / Windows Glulxe / Screen reader)

• I couldn’t figure out the ASCII map, despite being able to see it. There also were no audio cues coming through my speakers, I didn’t know there was alt text until I read this survey, and some of the puzzles were just difficult to understand in general (though I’m not as familiar with these games). Also, it took me a while to realize that reading the plaque put text on the top of the screen, rather than actually in the box. (Windows / Chrome / Color inverter extension)

• No - but the audio cue didn’t play on my system, so I used the walkthrough for that part. (Windows / Chrome / no AT)

• The ascii map did pose obstacles, and so did the photograph picture as it didn’t actually describe the buttons. Experimentation, or reading the walkthrough, was the way to work around that, though there was no way around the map without reading the walkthrough. (Windows / winGlulxe / Screen reader)

• The ASCII art was predictably incomprehensible. Couldn’t read the plaque text or the console text.
  (Windows / Quixe / Screen reader)

How did you feel about the accessibility experience as a whole?

• It was so-so. It was hard to scroll up and down to keep myself oriented. I kept getting lost. (Windows / Chrome / Screen magnifier)

• I felt, the text could be larger, remembering the directions I could go was sometimes complicated, the text description was mostly fine. I noticed the photographs had text description which is a great thing. Some of the puzzles are complex particularly figuring out the dance movement. (Windows / Firefox / no AT)

• i would like it if have option to switch from light theme to dark theme (Mac / Chrome / Screen reader, Screen magnifier)

• 19 out of 19 for me personaly. (Windows / Firefox / none)

• eh (Windows / Chrome / no AT)

• This was a pleasant experience for me, the puzzles weren’t difficult (except for the ASCII one) and it really sent me back to playing text adventures in college. It was fun. (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Most of it was fine, just as most IF has been for the last 20+ years.
  The rest was always meant to be a stress test and my screen reader and a couple of the interpreters failed it… The only parts of IF and all text games really that have ever been a consistent problem for me over the years would be color coded text and ASCII/PDF maps, and only when there is no way around either of them without a walkthrough.
  But even that doesn’t come up much…More and more in the last few years particularly on the mobile end yes but the huge majority of allIF is still usable. (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• It was meant to be a stress test, and it definitely exposed some deficiencies, in a pretty much equal spread between screen reader and interpreter.
  It’s a bit disheartening, particularly the ASCII thing, but it’s not like I didn’t know about it before :P
  The invisible text pane thing is new to me though, and I hope games don’t start using it allot. Thankfully my interpreter of choice can handle them alright and my screen reader has it’s own ways of reviewing previous text separate from the interpreter’s own buffer, but it’s still a bit worrying. (Windows / Lectrote / Screen reader, NVDA latest version)

• It wasn’t quite as good on the browser, but it reads text automatically unlike parchment and that’s worth allot. (Windows / Firefox / Screen reader, NVDA latest version)

• It had some rough spots but was mostly enjoyable. The biggest frustration was that NVDA’s reading behavior changed at some point, suddenly automatically reading text from far back instead of most recent output. (Windows / Chrome / Screen reader)

• The game is mostly accessible in my opinion.
  I can work around other problems.
  The exception is the map. (Windows / WinGlulxe / Screen reader)

• it could definitely use some work based off of the reasons I’ve given above ( iPhone running latest version of iOS / Frotz (iOS) / Screen reader)

• Overall, not too bad, except for the ASCII map. It was more user error, not thinking to examine some things in more detail, or to look under the shelves… (Windows / Chrome / Screen reader, Screen magnifier)

• Pretty good, except for the obsticles above. (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• It was nice and shiny. (Windows / Firefox / Screen reader)

• it was very accessible (Windows / Firefox / high contrast browser add on)

• Needs better accessibility for people who have a hard time typing (Mac / Safari / no AT)

• See answer above regarding any other information. (Windows / Windows Glulx / Screen reader)

• It was disappointing. It’s all text, but as I said above, screen readers are stupid. They don’t have any way of getting any more information, or interpolating data, or guessing at what should be read out of a huge element of scrolling text, which is what most interpreters seem to be. (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• It could be drastically improve. The game should have not relied on purely auditory or visual clues. (Windows / Windows Glulxe / Screen reader)

• Not really great, and if it wasn’t great for me, it’d probably be worse for those who have more difficulties than me. (Windows / Chrome / Color inverter extension)

• It was easy enough to operate, functioning like basic web browsing and text entry. (Windows / Chrome / no AT)

• Apart from the map, I thought this was a solidly accessible game. (Windows / winGlulxe / Screen reader)

• I would have been frustrated without the walkthrough.
  (Windows / Quixe / Screen reader)

On a scale of 1 to 5, how would you rate the overall experience of playing this game, in terms of accessibility?

• 2 (Windows / Chrome / Screen magnifier)

• 3 (Windows / Firefox / no AT)

• 2 (Mac / Chrome / Screen reader, Screen magnifier)

• 5 (Windows / Firefox / none)

• 3 (Windows / Chrome / no AT)

• 3 (Windows / Chrome / no AT)

• 4 (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• 3 (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• 3 (Windows / Lectrote / Screen reader, NVDA latest version)

• 3 (Windows / Firefox / Screen reader, NVDA latest version)

• 3 (Windows / Chrome / Screen reader)

• 4 (Windows / WinGlulxe / Screen reader)

• 4 (Windows / Chrome / Screen reader, Screen magnifier)

• 3 (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• 5 (Windows / Firefox / Screen reader)

• 5 (Windows / Firefox / high contrast browser add on)

• 3 (Windows / Chrome / Screen magnifier)

• 3 (Mac / Safari / no AT)

• 4 (Windows / Windows Glulx / Screen reader)

• 2 (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• 2 (Windows / Windows Glulxe / Screen reader)

• 2 (Windows / Chrome / Color inverter extension)

• 4 (Windows / Chrome / no AT)

• 4 (Windows / winGlulxe / Screen reader)

• 3 (Windows / Quixe / Screen reader)

What could the developer of the game (or the program you used to play the game) do to improve the game’s accessibility?

• Put the exit options in a clear line of text. Simplify the text pertaining to orientation. (Windows / Chrome / Screen magnifier)

• Improve text size, maybe include a direction compass so folks can keep track, a map could also be useful. (Windows / Firefox / no AT)

• add a little more tip/guide for commands to make it easier to remember (Mac / Chrome / Screen reader, Screen magnifier)

• not sure (Windows / Firefox / none)

• Include other possible phrasings that work such as “go through..” “go to…” as possible inputs for “go…” Provide prompts when you are meant to use an item in an alternative manner like describe a button as a knob or that you feel a shudder when the correct one to turn is pushed. I could not place the vase no matter what phrase I used. (Windows / Chrome / no AT)

• visible volume control (mute and slider)
  having to walk all the way across the dance floor instead of just ‘go up’ from the east side is a pain
  (Windows / Chrome / no AT)

• The only thing I would do is change the ASCII puzzle in some way. (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Avoid flashy features if they don’t actually add much to the finished product, or integrating features exclusively because they are within the program’s capabilities and you as an author want to try them out to see if you can do it, rather than for a concrete ingame reason. Particularly those that aren’t supported by some of the commonly used interpreters.
  Is the tradeoff really worth it though? Old school purists don’t tend to like most of it anyway, so maybe it is. And no one wants wide compatibility headaches that can’t simply be addressed by upgrading from a legacy interpreter to a modern one either, so if the blind happen to get caught up in that I’ll be happy to take it. (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• Nothing I haven’t already mentioned… The blank text pane, no sound, and the title bar refresh issue. (Windows / Lectrote / Screen reader, NVDA latest version)

• Same as Ilectrote minus the window title issue. (Windows / Firefox / Screen reader, NVDA latest version)

• Correct the automatic reading behavior, provide an alternative to ASCII art, provide better clues for the twisting 6 to 9 puzzle. (Windows / Chrome / Screen reader)

• I do not care for games which use pictures to give clues without providing a text description in game.
  So I would ditch the map. (Windows / WinGlulxe / Screen reader)

• to fix the focus issues during gameplay and to fix the experience with the slide projector and also to make the map accessible by making it into a text Matp ( iPhone running latest version of iOS / Frotz (iOS) / Screen reader)

• There maybe could have been a help command list, so you knew what commands the parser recognized. I’m not sure how to give the instructions to the dance floor without simply giving everything away. I figured out most directions and tasks, but didn’t realize I could turn a button, or look under a shelf. (Windows / Chrome / Screen reader, Screen magnifier)

• Providing an option to play without ascii and replacing that portion with a textual description of what it means would help. Not sure about the plaque, but if its supposed to be dirty text thats hard to read maybe show just enough of the letters regularly for the player to guess at what it says. (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• I can’t think of anything (Windows / Firefox / high contrast browser add on)

• Allow selection of commands rather than requiring them to be manually entered (Mac / Safari / no AT)

• Interpreters either should use TTS on their own (please don’t, operating systems have perfectly fine screen readers already) or send the text to the screen reader being used.

  One may then think, “why not just navigate the window with screen reader commands?” It takes quite a bit more seconds, and keystrokes, to go to the top line, read line by line, or have the reader say-all in the window, than it would to just hear output and respond right away.

  Another consideration should be given to users of Braille displays. It is possible that screen reader output can be sent to a braille display, but another way to increase accessibility for this case is to set braille focus on the first line of new output.

  One other thing, for Mac and Linux users, terminal apps are the best. Sure, that won’t help the ascii graphics and messy keyboard navigable menus, but it does make sure that the screen reader is in more control of what it says, as it always speaks new content, not old content while scrolling, unless that functionality is toggled off. A terminal experience is great for braille users as well.

  On Windows, there is the power shell, and it also seems to turn well with screen readers.

  On iOS, VoiceOver seems to do well with having text sent to it, usually. Maybe it’s just the Frotz app, or possibly the implimentation of Glolx it uses. (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• The game developer should provide a text description of the console picture, describe the sounds that the card makes, and not use ASCII art. Also make the dance floor less convoluted.
  The plaque’s inscription should also be printed in the same window as the rest of the game’s text. (Windows / Windows Glulxe / Screen reader)

• Make sure all important text is acknowledged inside the play field, or give a sound cue for popups. Give clearer instructions. Caption photos. (Windows / Chrome / Color inverter extension)

• I assume audio played after the “open card” command was entered, but there was no text description of the sound (only “[sound effect number 6 here]” or link/button to replay it. Without the walkthrough, I wouldn’t have known the clue. (Windows / Chrome / no AT)

• I’d say if the map wasn’t done on purpose to demonstrate what not to do considering that’s not accessible, that would be the first thing I would change in a game; have textual substitutes for the graphic elements in the game. (Windows / winGlulxe / Screen reader)

• Keep it simple. Extra windows, unusual text, pictures … anything that is visual should have text alternatives.
  (Windows / Quixe / Screen reader)

If you did complete the game, which of these endings did you reach?

• I did not complete the game (Windows / Chrome / Screen magnifier)

• I did not complete the game (Windows / Firefox / no AT)

• I did not complete the game (Mac / Chrome / Screen reader, Screen magnifier)

• I did not complete the game (Windows / Firefox / none)

• I did not complete the game (Windows / Chrome / no AT)

• “You have collected.” (Windows / Chrome / no AT)

• Both of the above (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• I did not complete the game (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• I did not complete the game (Windows / Lectrote / Screen reader, NVDA latest version)

• I did not complete the game (Windows / Firefox / Screen reader, NVDA latest version)

• “You have tidied.” (Windows / Chrome / Screen reader)

• Both of the above (Windows / WinGlulxe / Screen reader)

• “You have tidied.” (Windows / Chrome / Screen reader, Screen magnifier)

• I did not complete the game (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• Both of the above (Windows / Firefox / Screen reader)

• I did not complete the game (Windows / Firefox / high contrast browser add on)

• “You have collected.” (Windows / Chrome / Screen magnifier)

• “You have tidied.” (Mac / Safari / no AT)

• “You have tidied.” (Windows / Windows Glulx / Screen reader)

• I did not complete the game (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• “You have tidied.” (Windows / Windows Glulxe / Screen reader)

• I did not complete the game (Windows / Chrome / Color inverter extension)

• “You have tidied.” (Windows / Chrome / no AT)

• “You have tidied.” (Windows / winGlulxe / Screen reader)

• “You have tidied.”, ”You have collected.”, Both of the above
  (Windows / Quixe / Screen reader)

Which of the signs in the washroom were you able to read? (For signs in languages you don’t know, were you able to perceive that the sign contained writing in the given language?)

• English, German, Japanese (Windows / Chrome / Screen magnifier)

• English, “Font”, German, Arabic, Hebrew, Russian, Japanese, Emoji (Windows / Firefox / no AT)

• English (Mac / Chrome / Screen reader, Screen magnifier)

• English (Windows / Firefox / none)

• English (Windows / Chrome / no AT)

• English, “Font”, German, Arabic, Hebrew, Russian, Japanese, Emoji (Windows / Chrome / no AT)

• English (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• English, “Font”, German (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• English, “Font”, German, Emoji (Windows / Lectrote / Screen reader, NVDA latest version)

• English, “Font”, German, Emoji (Windows / Firefox / Screen reader, NVDA latest version)

• English, German, Arabic, Hebrew, Russian, Japanese (Windows / Chrome / Screen reader)

• English, “Font”, Emoji (Windows / WinGlulxe / Screen reader)

• English (Windows / Chrome / Screen reader, Screen magnifier)

• English, “Font” (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• English, “Font”, German, Arabic, Hebrew, Emoji (Windows / Firefox / Screen reader)

• English (Windows / Firefox / high contrast browser add on)

• English (Windows / Chrome / Screen magnifier)

• English, “Font”, German, Arabic, Hebrew, Russian, Japanese, Emoji (Mac / Safari / no AT)

• English, “Font”, German, Emoji (Windows / Windows Glulx / Screen reader)

• English, “Font”, German, Arabic, Hebrew, Russian, Japanese (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• English, “Font”, German, Arabic, Hebrew, Japanese (Windows / Windows Glulxe / Screen reader)

• English, “Font”, German, Arabic, Hebrew, Russian, Japanese, Emoji (Windows / Chrome / Color inverter extension)

• English, “Font”, German, Arabic, Hebrew, Russian, Japanese, Emoji (Windows / Chrome / no AT)

• English, German, Arabic, Hebrew, Russian, Japanese (Windows / winGlulxe / Screen reader)

• English, ”Font”, German, Arabic (Windows / Quixe / Screen reader)

Were the emoji on the emoji-sign readable?

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Windows / Firefox / no AT)

• No (Mac / Chrome / Screen reader, Screen magnifier)

• Yes (Windows / Firefox / none)

• Yes (Windows / Chrome / no AT)

• No (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• No (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• Yes (Windows / Lectrote / Screen reader, NVDA latest version)

• Yes (Windows / Firefox / Screen reader, NVDA latest version)

• No (Windows / Chrome / Screen reader)

• Yes (Windows / WinGlulxe / Screen reader)

• No (Windows / Chrome / Screen reader, Screen magnifier)

• No (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• Yes (Windows / Firefox / Screen reader)

• Yes (Windows / Firefox / high contrast browser add on)

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Mac / Safari / no AT)

• Yes (Windows / Windows Glulx / Screen reader)

• No (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• No (Windows / Windows Glulxe / Screen reader)

• Yes (Windows / Chrome / Color inverter extension)

• Yes (Windows / Chrome / no AT)

• No (Windows / winGlulxe / Screen reader)

• No (Windows / Quixe / Screen reader)

Were the boldface and italic words on the font sign distinguishable?

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Windows / Firefox / no AT)

• No (Mac / Chrome / Screen reader, Screen magnifier)

• Yes (Windows / Firefox / none)

• No (Windows / Chrome / no AT)

• Yes (Windows / Chrome / no AT)

• No (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Yes (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• Yes (Windows / Lectrote / Screen reader, NVDA latest version)

• Yes (Windows / Firefox / Screen reader, NVDA latest version)

• No (Windows / Chrome / Screen reader)

• Yes (Windows / WinGlulxe / Screen reader)

• No (Windows / Chrome / Screen reader, Screen magnifier)

• No (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• Yes (Windows / Firefox / Screen reader)

• No (Windows / Firefox / high contrast browser add on)

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Mac / Safari / no AT)

• Yes (Windows / Windows Glulx / Screen reader)

• No (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• Yes (Windows / Windows Glulxe / Screen reader)

• Yes (Windows / Chrome / Color inverter extension)

• Yes (Windows / Chrome / no AT)

• No (Windows / winGlulxe / Screen reader)

• No (Windows / Quixe / Screen reader)

Each time you pulled the lever, were you able to see your total-score counter increase? (This is separate from the “Your score has just gone up by one point” message appearing.)

• Yes (Windows / Chrome / Screen magnifier)

• No (Windows / Firefox / no AT)

• No (Mac / Chrome / Screen reader, Screen magnifier)

• No (Windows / Firefox / none)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Yes (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• Yes (Windows / Lectrote / Screen reader, NVDA latest version)

• Yes (Windows / Firefox / Screen reader, NVDA latest version)

• No (Windows / Chrome / Screen reader)

• Yes (Windows / WinGlulxe / Screen reader)

• Yes (Windows / Chrome / Screen reader, Screen magnifier)

• No (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• Yes (Windows / Firefox / Screen reader)

• No (Windows / Firefox / high contrast browser add on)

• Yes (Mac / Safari / no AT)

• Yes (Windows / Windows Glulx / Screen reader)

• No (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• Yes (Windows / Windows Glulxe / Screen reader)

• Yes (Windows / Chrome / Color inverter extension)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / winGlulxe / Screen reader)

• Yes (Windows / Quixe / Screen reader)

Were you able to example the crumpled paper, and understand it as a map with a path drawn across it?

• Yes (Windows / Chrome / Screen magnifier)

• No (Windows / Firefox / no AT)

• No (Mac / Chrome / Screen reader, Screen magnifier)

• No (Windows / Firefox / none)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / no AT)

• No (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• No (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• No (Windows / Lectrote / Screen reader, NVDA latest version)

• No (Windows / Firefox / Screen reader, NVDA latest version)

• Yes (Windows / Chrome / Screen reader)

• No (Windows / WinGlulxe / Screen reader)

• No (Windows / Chrome / Screen reader, Screen magnifier)

• No (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• No (Windows / Firefox / Screen reader)

• Yes (Windows / Firefox / high contrast browser add on)

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Mac / Safari / no AT)

• No (Windows / Windows Glulx / Screen reader)

• No (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• No (Windows / Windows Glulxe / Screen reader)

• Yes (Windows / Chrome / Color inverter extension)

• Yes (Windows / Chrome / no AT)

• No (Windows / winGlulxe / Screen reader)

• No (examine it, yes; understand it, no)
  (Windows / Quixe / Screen reader)

Were you able to open the holiday card, and understand the sequence of clicks that it plays?

• No (Windows / Chrome / Screen magnifier)

• Yes; I was able to read the alt-text describing the clicks. (Windows / Firefox / no AT)

• No (Mac / Chrome / Screen reader, Screen magnifier)

• Yes; I was able to hear the clicks. (Windows / Firefox / none)

• No (Windows / Chrome / no AT)

• No (Windows / Chrome / no AT)

• No (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Yes; I was able to hear the clicks. (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• No (Windows / Lectrote / Screen reader, NVDA latest version)

• No (Windows / Firefox / Screen reader, NVDA latest version)

• No (Windows / Chrome / Screen reader)

• Yes; I was able to hear the clicks. (Windows / WinGlulxe / Screen reader)

• No (Windows / Chrome / Screen reader, Screen magnifier)

• Yes; I was able to hear the clicks. (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• Yes; I was able to read the alt-text describing the clicks. (Windows / Firefox / Screen reader)

• No (Windows / Firefox / high contrast browser add on)

• Yes; I was able to hear the clicks. (Windows / Chrome / Screen magnifier)

• No (Mac / Safari / no AT)

• Yes; I was able to hear the clicks. (Windows / Windows Glulx / Screen reader)

• No (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• Yes; I was able to hear the clicks. (Windows / Windows Glulxe / Screen reader)

• No (Windows / Chrome / Color inverter extension)

• No (Windows / Chrome / no AT)

• Yes; I was able to hear the clicks. (Windows / winGlulxe / Screen reader)

• Yes; I was able to hear the clicks., Yes; I was able to read the alt-text describing the clicks.
  (Windows / Quixe / Screen reader)

Were you able to read the paragraph of text contained in the book?

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Windows / Firefox / no AT)

• Yes (Mac / Chrome / Screen reader, Screen magnifier)

• Yes (Windows / Firefox / none)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Yes (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• Yes (Windows / Lectrote / Screen reader, NVDA latest version)

• Yes (Windows / Firefox / Screen reader, NVDA latest version)

• Yes (Windows / Chrome / Screen reader)

• Yes (Windows / WinGlulxe / Screen reader)

• Yes (Windows / Chrome / Screen reader, Screen magnifier)

• Yes (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• Yes (Windows / Firefox / Screen reader)

• Yes (Windows / Firefox / high contrast browser add on)

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Mac / Safari / no AT)

• Yes (Windows / Windows Glulx / Screen reader)

• No (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• Yes (Windows / Windows Glulxe / Screen reader)

• Yes (Windows / Chrome / Color inverter extension)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / winGlulxe / Screen reader)

• Yes (Windows / Quixe / Screen reader)

Were you able to examine the three photographs?

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Windows / Firefox / no AT)

• Yes (Mac / Chrome / Screen reader, Screen magnifier)

• Yes (Windows / Firefox / none)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Yes (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• Yes (Windows / Lectrote / Screen reader, NVDA latest version)

• Yes (Windows / Firefox / Screen reader, NVDA latest version)

• Yes (Windows / Chrome / Screen reader)

• Yes (Windows / WinGlulxe / Screen reader)

• Yes (Windows / Chrome / Screen reader, Screen magnifier)

• Yes (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• Yes (Windows / Firefox / Screen reader)

• Yes (Windows / Firefox / high contrast browser add on)

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Mac / Safari / no AT)

• Yes (Windows / Windows Glulx / Screen reader)

• Yes (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• Yes (Windows / Windows Glulxe / Screen reader)

• Yes (Windows / Chrome / Color inverter extension)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / winGlulxe / Screen reader)

• Yes (the text description).
  (Windows / Quixe / Screen reader)

Were you able to understand the console photograph in enough detail to learn the six numbers shown on it?

• Yes; I was able to learn about the numbers through the alt-text. (Windows / Chrome / Screen magnifier)

• Yes; I could visually see and understand the numbers. (Windows / Firefox / no AT)

• No (Mac / Chrome / Screen reader, Screen magnifier)

• Yes; I could visually see and understand the numbers. (Windows / Firefox / none)

• No (Windows / Chrome / no AT)

• Yes; I could visually see and understand the numbers. (Windows / Chrome / no AT)

• Yes; I could visually see and understand the numbers. (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• No (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• Yes; I was able to learn about the numbers through the alt-text. (Windows / Lectrote / Screen reader, NVDA latest version)

• Yes; I was able to learn about the numbers through the alt-text. (Windows / Firefox / Screen reader, NVDA latest version)

• Yes; I was able to learn about the numbers through the alt-text. (Windows / Chrome / Screen reader)

• No (Windows / WinGlulxe / Screen reader)

• Yes; I was able to learn about the numbers through the alt-text. (Windows / Chrome / Screen reader, Screen magnifier)

• No (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• Yes; I was able to learn about the numbers through the alt-text. (Windows / Firefox / Screen reader)

• Yes; I could visually see and understand the numbers. (Windows / Firefox / high contrast browser add on)

• Yes; I could visually see and understand the numbers. (Windows / Chrome / Screen magnifier)

• Yes; I could visually see and understand the numbers. (Mac / Safari / no AT)

• No (Windows / Windows Glulx / Screen reader)

• No (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• No (Windows / Windows Glulxe / Screen reader)

• No (Windows / Chrome / Color inverter extension)

• Yes; I could visually see and understand the numbers. (Windows / Chrome / no AT)

• No (Windows / winGlulxe / Screen reader)

• No (Windows / Quixe / Screen reader)

Were you able to turn on the slide projector and read the descriptions of the six slides (including the location of the Left Glove of Darkness)?

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Windows / Firefox / no AT)

• Yes (Mac / Chrome / Screen reader, Screen magnifier)

• Yes (Windows / Firefox / none)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Yes (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• Yes (Windows / Lectrote / Screen reader, NVDA latest version)

• Yes (Windows / Firefox / Screen reader, NVDA latest version)

• Yes (Windows / Chrome / Screen reader)

• Yes (Windows / WinGlulxe / Screen reader)

• No (Windows / Chrome / Screen reader, Screen magnifier)

• Yes (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• Yes (Windows / Firefox / Screen reader)

• Yes (Windows / Firefox / high contrast browser add on)

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Mac / Safari / no AT)

• Yes (Windows / Windows Glulx / Screen reader)

• No (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• Yes (Windows / Windows Glulxe / Screen reader)

• Yes (Windows / Chrome / Color inverter extension)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / winGlulxe / Screen reader)

• Yes (Windows / Quixe / Screen reader)

Were you able to clean the plaque and read the verse printed on it?

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Windows / Firefox / no AT)

• No (Mac / Chrome / Screen reader, Screen magnifier)

• No (Windows / Firefox / none)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Yes (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• No (Windows / Lectrote / Screen reader, NVDA latest version)

• No (Windows / Firefox / Screen reader, NVDA latest version)

• Yes (Windows / Chrome / Screen reader)

• Yes (Windows / WinGlulxe / Screen reader)

• Yes (Windows / Chrome / Screen reader, Screen magnifier)

• No (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• Yes (Windows / Firefox / Screen reader)

• Yes (Windows / Firefox / high contrast browser add on)

• Yes (Windows / Chrome / Screen magnifier)

• Yes (Mac / Safari / no AT)

• Yes (Windows / Windows Glulx / Screen reader)

• No (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• Yes (Windows / Windows Glulxe / Screen reader)

• Yes (Windows / Chrome / Color inverter extension)

• Yes (Windows / Chrome / no AT)

• Yes (Windows / winGlulxe / Screen reader)

• No (clean, yes; read, no)
  (Windows / Quixe / Screen reader)

Do you have any other comments or questions about your experience testing this game?

• Could not find basement described in walkthrough. Had to give up (Windows / Chrome / Screen magnifier)

• It was interesting and a genre I am now more interested in. (Windows / Firefox / no AT)

• this was interesting game, i was bit confused on how command work but overall, all i have to say i would love to keep going if the background was change to black or dark color to help make it easier to read (Mac / Chrome / Screen reader, Screen magnifier)

• the plaque had issues showing words after cleaning and wiping.nice story thank you for the experience. (Windows / Firefox / none)

• The change in location of text when reading the plaque was confusing. It appeared as a sepperate scroll box at the top of my browser instead of in-line or as a fresh page.
  The counter only counting shadow items was confusing since it read items. The reading of items implies to me (an experienced gamer) that it would count ALL items that are acquired not just the shadow items.
  The description of the current room being occupied occuring in-line so it scrolled out of sight made it that I had to scroll a lot to find out what I could examine in a room since I have memory issues and cannot hold onto details for extended amounts of time. Having the room text stay in a sepperate box at the top of the screen would help. Additionally a box displaying a list of general items held in the interface would be nice to be able to re-examine items without having to scroll through the entire text performed to find out what you had and then re-examining (crumpled note).
  Points only accrued in the wash room for washing hands and did not accrue from using same command in kitchen. The response you feel grimy do not really clue me in that I need to go somewhere else to wash them.
  (Windows / Chrome / no AT)

• couldn’t find a command to restate the room opening text - super obnoxious when the room activities print a lot of text and idk where the doors are
  (Windows / Chrome / no AT)

• None, thank you for the experience. (Windows / Chrome / Screen magnified at 130% to assist in reading text. This is my ususal setting for such.)

• Tell Andrew thanks for making a game that’s actually somewhat interesting to play :) The dreamhold was what got me into IF as a child and though I still can’t really fathom the ending of it, he was the one that first filled me with that intense sense of aw and got me really invested in a game’s universe. The Brandon Sanderson of IF.
  And I like how many useful tests you managed to cram in their too! You guys clearly did your research. (Windows / I used Win Git latest version, with an add-on for my screen reader that helps the program to be more accessible called “automatic output for interactive fiction interpreters” / Screen reader, “NVDA” latest version.)

• Despite the issues presented by this particular game, Ilectrote and quicks via the browser are both really quite good with screen readers without any hacks on the user’s end, which is really cool.
  I’ll probably still stick with Wingit my self, but it’s great to know I have alternatives, so I’m glad this survey introduced me to it. (Windows / Lectrote / Screen reader, NVDA latest version)

• I’m glad to have a quick on the go browser based solution that’s highly accessible! I just really wish IFDB would replace parchment with Quixe… (Windows / Firefox / Screen reader, NVDA latest version)

• Chrome did not play the audio, which is why I was not aware of the clicks. (Windows / Chrome / Screen reader)

• Some of my problems with this game were me just not thinking of things I could do. I did consult the walkthrough a few times for hints in a couple areas, and for the dance floor solution. (Windows / Chrome / Screen reader, Screen magnifier)

• Had fun with what I could play. I don’t know many other games where a sound is needed for a puzzle. Those “a-hah” moments were satisfying. (Galaxy s9 plus using latest version of android / Fabularium (Android) / Screen reader)

• I had to consult the walkthrough for the holiday card because no audio played and no text describing the audio displayed. (Mac / Safari / no AT)

• My only other comment is that I hope accessibility is seriously considered when creating interpreters, or working on existing ones. Sure, MUD’s are all the rage now, but I think that, until blind people are given vision, IF will still have a big audience besides readers and tale weavers. (Windows, Mac, iOS 12 / Lectrote, Frotz, WinGlolx / Screen reader)

• I do not have any hearing loss, so I was able to hear the clicks.
  However I was unaware until reading this survey that the card had alt text describing them, if it did.
  I would like to participate in further projects. (Windows / Windows Glulxe / Screen reader)

• It was mostly playable, but the latter half forced me to go through the walkthrough either due to glitches, the game not understanding synonyms, unclear commands, and in the end the game bugged and did not do anything after I put down all the Items of Darkness exactly as stated in the walkthrough, rendering me unable to finish. I know these aren’t technically accessibility concerns, but they’re what stood out to me. Also, the ASCII map isn’t just confusing for people with screen readers, I couldn’t make any sense of it and had to go to the walkthrough. (Windows / Chrome / Color inverter extension)

• Nothing else to add. (Windows / Chrome / no AT)

• I think, other than a few minor inconveniences with images, this was a very accessible game and, to an extent, very playable. The walkthrough is needed for achieving certain tasks, but I think the obvious demonstration of inaccessibility with the picture map was a good way of showing future developers what not to do. (Windows / winGlulxe / Screen reader)

• To read the status bar – to read the changing score – I need to move my cursor to the top of the screen. If I wasn’t notified of the change, I probably wouldn’t have known about it. (Windows / Quixe / Screen reader)

Return to the accessibility report main page