Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

editor accessibility must be reenabled at the start of each lesson

See original GitHub issue

Looking forward for reporting a security issue: Please report security issues by sending an email to security@freecodecamp.org instead of raising a Github issue.

Describe the bug A clear and concise description of what the bug is. The Monaco editor contains features for accessibility, specifically a mode for screen reader users which helps in navigating and using the editor effectively. This feature, as of now, must be enabled at the start of each lesson, even after enabling it once at the beginning of the session. To Reproduce Steps to reproduce the behavior:

Go to any lesson in the curriculum.
Enter the code editor, set focus to it.
Press alt+f1 to show accessibility help for the editor, and choose to enable the screen reader mode
complete the lesson, advance to the next, and repeat steps two and three

Expected behavior A clear and concise description of what you expected to happen. The screen reader mode should have stayed enabled across lessons. Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS] Windows
Browser [e.g. chrome, safari] Chrome
Version [e.g. 22] 69.0.3497.100 (Official Build) (64-bit)

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context Add any other context about the problem here. Tested screen reader: NVDA version 2018.3.2 from https://www.nvaccess.org/download/

Issue Analytics

State:
Created 5 years ago
Reactions:2
Comments:15 (8 by maintainers)

Top GitHub Comments

1reaction

saranshacommented, Dec 3, 2018

A group of us are working on this issue for a class project in university. We aim to address this in the next couple of days. We will try and at least present the community with a first iteration of our proposed solution.

Just a heads up. If the current developers have any advice or tips, feel free to contact me. Thank you.

@oalhait is the primary developer in the team, working alongside me.

0reactions

ojeytonwilliamscommented, Nov 13, 2019

Quick update. Both the auto-focusing and the persistence of accessibility mode should be fixable. I think I’m about 90% of the way there, but for some reason it stops letting you toggle the accessibility support after a couple of toggles.

This, obviously, isn’t ideal, but most of the functionality is there.