Cannot set to local analysis in accessible blind mode

Deep thanks to the liChess team for implementing accessibility for the blind, you are all the best.
I have been analyzing games recently on liChess, and it works great if I go to analysis after a game played on liChess, I turn on local mode, I can arrow through moves, and explore alternate lines with no problem.
However, if I import a game, I can't seem to set analysis mode to local while in blind mode.
The only fix I have found is to switch blind mode off, turn local on, then go back to blind mode so I can arrow through the moves and view secondary lines.
It says in the instructions that pressing the "l" key will turn local mode on, but this isn't working for me, and I have turned virtual cursor off for my screen reader to make sure the command is going through.
Am I missing something here? Is there a way to simply set analysis mode to local in blind mode after importing a game?
Much thanks for any help.
Ché

It's weird that the behavior is different when importing a game. I can't reproduce that behavior on my machine.
When you switch blind mode off, how are you turning local analysis on? Are you using the "l" key or the "Toggle local evaluation" checkbox? I ask because the checkbox should exist in blind mode as well now, and maybe that would work better. It is under the "Computer analysis" heading.
Another thing to try is reloading after importing a game.
Do the arrow keys work after importing a game? If so, something might be special about the "l" key for you. In that case, you can also use the space key to turn on local evaluation. Space tries to play the best move, but it will turn local evaluation on instead if it hasn't been turned on yet.

Hey, that was very helpful, I had no idea that space would turn local mode on as well.
This time, when I imported a game, and checked to do a computer analysis, I had the option to turn local mode on via a checkbox, which I for sure did not have earlier, very odd. Maybe I am simply losing my mind...
I have done quite a few evaluations of liChess games right after the game, and I always find the checkbox for local, but it wasn't there earlier today when I imported a game..
We really need some solid documentation and perhaps tutorials for blind mode on liChess, and apologies if I just don't know where it is, but almost all I've learned about how to play blind here has come from experimentation and trial and error.
I have recorded an audio tutorial for getting started with liChess for the blind to help out my fellow blind players that I've posted to a couple blind chess lists, it is about 12 minutes long, and covers the basics:
https://www.dropbox.com/s/6g7233fzagjuqfa/liChess%20Basics%20Tutorial.mp3?dl=0

Thanks very much for your help, if I might ask one more question, would it be possible to have the "e" key read out loud the current evaluation when going through moves?
As it is, I have to jump into browse mode, go back to the command input, type in eval, then go back out of browse mode and repeat the next time I want to see how the evaluation changed.
So maybe the output would just be: "plus 1.2" or "minus .8"
Not complaining at all, just a suggestion to help make things more efficient and closer to what the sighted experience when analyzing games.
Fantastic job again to all that have worked on accessibility here. Your efforts are deeply appreciated.
If I can help in any way, with testing or anything, I'll be glad to do so, and I am making a donation as soon as I finish this forum post.

Thanks very much for your help, if I might ask one more question, would it be possible to have the "e" key read out loud the current evaluation when going through moves?

Good suggestion. Looking into it.

Yes, my original implementation used the "c" key ("e" is taken by the opening explorer). So the code is in my pr's history if that would help @schlawg.

Thanks for feedback. Hearing from actual users is invaluable. I can code, and I can muddle my way around a screen reader, but I don't know how people prefer to use them.

For documentation, there is an old blog post https://lichess.org/blog/U5AX_DcAADkAz-L5/accessibility-for-blind-players and a more recent youtube video https://www.youtube.com/watch?v=cOdZ6AyhwPw . Many features haven't been covered yet, and there's not a lot of discoverability of the documentation.

I'm very interested in improving the documentation situation. I thought your tutorial was excellent. Do you know any examples of well-documented accessible software that Lichess can use as precedent? Or if not, would you like to help set that precedent? One of the big strengths of Lichess as an open-source project is that the all the work that goes into Lichess comes from Lichess users. That should extend to the accessibility of the platform as well.

Finally, going back to the checkbox, it is possible that the checkbox truly was gone. The "z" key toggles (almost) all computer evaluation features on and off, which is mainly useful if you want to avoid getting spoiled by the evaluation of a position.

@user370417
I saw where they requested you to leave eval to the input box. Are the pull request comments the extent of the communication?

I'd just make sure they are clear on the inconvenience that reliance on the command input box for eval presents. I realize it's a slippery slope with new keyboard shortcuts but this one seems legit.

Yes, the pull requests comments contain all the communication.

Hi both,
Ok, thanks for mentioning the z key, that is exactly what the problem was. An easy accidental toggle when using a screen reader, as the z key is used with a modifier key to cycle browse mode.
So I had seen that blog post about accessibility before, which was all the docs I'd run across on here.
I watched the video as well. It was well done, but imho not really an instruction guide for the blind when it comes to learning how to use the interface.
I'd like to explore providing documentation. I have some thoughts, and personally think a web page with headings for each section would be the way to go, so the blind can easily find relevant sections.
Email works best for communication for me, and my email address is:
blindadrenaline at gmail dot com
If you guys would rather keep it to the forum here, I understand.
Also, in regards to the eval key, it looks like the accessibility mode is its own layer of input polling. Can this particular key not be set so it only affects output when in blind mode? I understand they don't want to mess with the interface in general, but it would seem that user convenience and efficiency for the blind would take precedence here, especially if it is a feature only implemented when in blind mode, and thus not affecting the sighted interface in any way.
Thanks so much for the feedback, great to know you guys are open to discussion about accessibility.