racket / racket/drracket

DrRacket Is Inaccessible with Screenreaders

Open
#219 10 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
516
Forks
103
PR merge metrics
No merged PRs in 30d

Description

Hello,

I have tried running DrRacket on a Windows and Linux box with the NVDA and Orca screenreaders, respectively, and I am noticing some accessibility issues that need some addressing. Under Linux, the only parts of the DrRacket interface that are accessible are the menu bars and the preference dialogs; as for the main interface, I hear only the phrase "drawing area". On Windows, I wasn't able to get the interface to speak at all with NVDA; I will do further testing tomorrow to see if I missed a step when trying to get the interface working. Sorry I cannot be more informative than that; I am just starting my Racket adventure so haven't delved too deeply in to the code, but I hope this issue can be resolved.

Additionally, I spoke on Slack about this problem, and I heard that there is work done in this area; is this available for testing as of yet? If so, which branch should I track and what steps are necessary to get it working?

Thanks,

Hunter

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing DrRacket with NVDA on Windows and Orca on Linux, checking whether the main interface exposes anything beyond the menu bars and preference dialogs. Review the existing accessibility work mentioned in the Slack discussion and determine which branch and testing steps apply; done means the main interface is usable through both screenreaders.

Written by the indexing model from the issue text.

Assessment

Domain
accessibility, desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.