zaproxy / zaproxy/zaproxy

Unable to set port for proxy chain using just the keyboard

Open
#1,423 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

assistive Component-UI
Dominant language
Java
Stars
15.8k
Forks
2.6k
Avg merge
13h 16m
Merged PRs (30d)
17

Description

When I am using zap with a screenreader (JAWS), and I want to set a proxy chain, I can
set the host, but when I tab to the port field, I am unable to set it using the keyboard.
 I have tried using the arrow keys to scroll down to port 80, but that takes forever,
and when I click ok, the value is not saved.

This field should be combobox so that the user can either scroll to the desired port,
or simply enter it.  Also the setting should be saved when the ok button is clicked.2.3.1
on windows 7 64-bit using jdk 1.7.0_67reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.


Original issue reported on code.google.com by don.raikes on 2014-12-04 17:38:32

Contributor guide

Open the contributing guide

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 the proxy-chain port-field problem with keyboard navigation and a screenreader on the described Windows and JDK setup. The work is done when the port can be entered or selected without prolonged scrolling and the chosen value remains saved after clicking OK.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
accessibility, desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.