Skip to content

Various accessibility issues #588

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
alranel opened this issue Nov 1, 2021 · 1 comment
Closed

Various accessibility issues #588

alranel opened this issue Nov 1, 2021 · 1 comment
Assignees
Labels
conclusion: duplicate Has already been submitted topic: accessibility Enabling the use of the software by everyone topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project

Comments

@alranel
Copy link
Contributor

alranel commented Nov 1, 2021

Describe the problem

This report was shared by Ken Perry on the developers mailing list:

  1. No way to get to the error window that I can find.
  2. Open the menus and the menus don't focus. Note this is with NVDA or Jaws the two most popular screen readers.
  3. The only thing I can do right now is open code and edit it. I might be able to compile it and uploaded it with the short cuts but so far I have no idea because I can't get to the error / messages window to tell me what is going on.
  4. There is no way to get to any other window but the main window. Something like alt0 -alt 9 would help if each one focused different windows. It might not be the best way to go about things but it would be a short cut start.
  5. I can change from tab in the edit box and out but when I switch with control +m and then try to tab around the interface nothing happens.
  6. There is no view window to open and close windows that I need or do not need. Not that I can get to them anyway.

Expected behavior

All operations in Arduino IDE can be accomplished using the keyboard alone.

Arduino IDE version

2.0.0-beta.12

Operating system

All

Operating system version

Not stated

Additional context

We need to investigate more and eventually split them into multiple issues. Some of these may be already tracked in this repository or Theia's.

@alranel alranel added type: imperfection Perceived defect in any part of project topic: accessibility Enabling the use of the software by everyone labels Nov 1, 2021
@per1234 per1234 added the topic: code Related to content of the project itself label Nov 1, 2021
@91volt 91volt self-assigned this Jan 12, 2022
@per1234
Copy link
Contributor

per1234 commented Nov 10, 2022

  1. No way to get to the error window that I can find.

From reading the discussion on the Arduino Developers mailing list, I see that "No way" means "no way to accomplish it via the keyboard" and I interpret "error window" as meaning the "Output" view. This, and the deficiency as it applies generally to the difficulty in accessing all panels and views is tracked here: #1561

  1. Open the menus and the menus don't focus. Note this is with NVDA or Jaws the two most popular screen readers.

I am not able to reproduce this using NVDA, even with the Arduino IDE 2.0.0-beta.12 that was the latest at the time of the report.

  1. The only thing I can do right now is open code and edit it. I might be able to compile it and uploaded it with the short cuts but so far I have no idea because I can't get to the error / messages window to tell me what is going on.

Tracked at #1561

  1. There is no way to get to any other window but the main window. Something like alt0 -alt 9 would help if each one focused different windows. It might not be the best way to go about things but it would be a short cut start.

Tracked at #1561

  1. I can change from tab in the edit box and out but when I switch with control +m and then try to tab around the interface nothing happens.

Tracked at #1561

  1. There is no view window to open and close windows that I need or do not need. Not that I can get to them anyway.

All views can be opened and closed via the "Toggle ___ View" commands, which can be assigned arbitrary keyboard shortcuts by the user or accessed via the Command Palette.

These methods may not be considered a sufficient alternative to a mechanism available via the primary GUI. However, the primary GUI already provides the capability to open and close any view. So the problem is not that the UI doesn't exist, but that the existing UI is not accessible. I think it would be better to focus on making the existing UI elements accessible via keyboard rather than adding additional redundant UI components as a bandaid for the current lack of accessibility.

My impression is that #360 and #1561 provide reasonably good coverage of the problems that currently harm the accessibility of those elements.

@per1234 per1234 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 10, 2022
@per1234 per1234 assigned per1234 and unassigned ubidefeo, rsora and 91volt Nov 10, 2022
@per1234 per1234 added the conclusion: duplicate Has already been submitted label Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: duplicate Has already been submitted topic: accessibility Enabling the use of the software by everyone topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project
Projects
None yet
Development

No branches or pull requests

5 participants