microsoft / microsoft/AzureStorageExplorer
[Usable - ADF - Azure data factory] No heading structure defined on Add data factory window.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
User Experience:
User would find difficulty to navigate the page efficiently if there is no H1 heading defined on the page and will be very confusing to the user that they would have no way to differentiate the content.
Test Environment:
Application Version: 1.16.0-dev
Build Number: 20200921.1
Screen reader: Narrator, NVDA
Pre-Requisite:
Navigate to the storage expoler.exe and select it
Repro Steps:
- Launch Azure Storage Explorer app.
- Navigate and select Add data factory control at left panel.
- Set to scan mode using Caps + Space keys.
- Now, navigate in heading mode by pressing H/Shift H.
- Verify heading structure on Azure data factory.
Actual Result:
No heading structure defined on Add data factory window and due to this, user won't be differentiate between the content.
Expected Result:
There should be heading structure defined on Add data factory window so that end user could easily differentiate within the content.
Note:
NVDA also doesn't announce heading structure on Azure data factory window.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in Azure Storage Explorer by opening Add data factory, entering scan mode, and navigating with H/Shift H in NVDA or Narrator. Inspect the window's UI structure and identify where its heading structure is defined; done means the window exposes a clear heading structure that differentiates its content.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100