Skip to content
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

A11y Accessibility: After applying reflow, "Editor content" textbox is not visible #133

Open
joe-braley opened this issue Nov 6, 2024 · 2 comments
Labels
needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@joe-braley
Copy link

Steps to Reproduce

  1. Install Kantra tool and execute an assessment.
  2. With the report open:
    • TAB until "hamburger" icon and press ENTER key.
    • TAB until "Issues" tab and press ENTER key.
    • TAB until "Detail" key (>) in first column and press ENTER key.
    • TAB until first file entry (e.g., pom.xml) and press ENTER key.
    • TAB until "Editor content" text box.
    • Apply Reflow:
      • Open Chrome/Edge dev tools.
      • Undock dev tools so that it’s a separate window.
      • Zoom the browser to 200%
      • Adjust browser width and height to 320 x 256. As long as dev tools remain open while resizing the viewport size will be displayed in the upper right corner of the browser so the size can be verified.
    • Observe that after applying reflow, after applying resize, "Editor content" textbox is not visible

Expected Behavior
After applying resize, "Editor content" textbox should be visible.

Actual Behavior
After applying resize, "Editor content" textbox is not visible.

Environment Details
• Operating System: Windows 11 Enterprise
- Software Version: Microsoft Edge Version 130.0.2849.68 (Official build) (64-bit)

Other Resources
Image

@joe-braley
Copy link
Author

CC @kthatipally

@konveyor-ci-bot konveyor-ci-bot bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 6, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. labels Nov 6, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant