microsoft / microsoft/SqlNexus

Screen readers are announcing 'Textbox edit read only' information for the normal links and non-interactive text resent in the page.

Open
#345 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accessibility enhancement
Dominant language
C#
Stars
427
Forks
111
Avg merge
3d 42m
Merged PRs (30d)
8

Description

Note: Same issue is observed throughout the application Including links.
Same issue replicates in 'Loaded Module pages', 'Active Traces and XEvents report', 'Query store query analysis report page'.

Other instance
1.Same issue is observed for 'SQL Pref main' page.
Issue: Screen readers are announcing 'Textbox edit read only' information for the normal links and non-interactive text resent in the page.
Path: Open the SQL Nexus app in desktop-> Connect to server Dialog gets displayed-> SQL Perf Main page gets displayed.

2.Same issue is observed for 'Server configuration and properties' page.
Issue: Screen readers are announcing 'Textbox edit read only' information for the normal links and non-interactive text resent in the page.
Path: Open the SQL Nexus app in desktop-> Connect to server Dialog gets displayed-> SQL Perf Main page gets displayed->Sever configuration

3.Same issue is observed for 'SQL server bottle neck analysis' page.
Issue: Screen readers are announcing 'Textbox edit read only' information for the normal links and non-interactive text resent in the page.
Path: Open the SQL Nexus app in desktop-> Connect to server Dialog gets displayed-> SQL Perf Main page gets displayed->Bottle neck analysis.

4.Same issue is observed for 'Memory metrics' page.
Issue: Screen readers are announcing 'Textbox edit read only' information for the normal links and non-interactive text resent in the page.
Path: Open the SQL Nexus app in desktop-> Connect to server Dialog gets displayed-> SQL Perf Main page gets displayed->Perfmon summary->memory metrics

Impact on a Person with Disability (PWD):
Users who rely on screen readers are getting confused as an element of the given control type is not supporting the text pattern.

Test Environment:​
OS: Windows 11 [Version 22H2 (OS Build 22621.2283)].

Desktop application: SQL Nexus.

Tool: Narrator, JAWS (2022.2110.6).

Prerequisite:

  1. Install SQLNexus application in the desktop.
  2. Turn on Accessibility Insights for windows.
  3. Enable Narrator/JAWS.

Repro Steps:
Step 1: Open the SQL Nexus app in desktop.
Step 2: Connect to server Dialog gets displayed. Connect to the server by invoking connect button.
Step 3: Navigate to SQL Perf Main and invoke it.
Step 4: Navigate to Best practices & Analysis summary and invoke it.
Step 5: Run accessibility insights for Windows tool and Verify whether The element of the given ControlType must support the text pattern or not.

Actual Result:
Screen readers are announcing 'Textbox edit read only' information for the normal links and non-interactive text resent in the page.
Screen reader behavior: NVDA is announcing as 'Textbox edit read only bottlneck analysis'

Expected Result:
The element of the given ControlType must support the text pattern.

Suggestive Fixes:
Make sure ARIA roles are properly used.
Links should have role="link" attribute.
Use semantic HTML tags for all elements.
Remove unnecessary ARIA attributes.

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

Reproduce the issue in SQL Nexus using Narrator or JAWS, following the Connect to server, SQL Perf Main, and Best practices & Analysis summary paths. Check the named Loaded Module, Active Traces and XEvents, Query store, SQL Perf Main, Server configuration, bottleneck analysis, and Memory metrics pages for incorrect control types or ARIA usage. Done means normal links and non-interactive text are announced with appropriate semantics rather than as read-only textboxes.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
accessibility, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.