question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Accessibility, a11y] Screen reader isn't reading quick pick title field

See original GitHub issue

VS Code Version: 1.67.1

Operating System: Windows 11

Screen Reader: NVDA

Extensions Installed: Put together an extension to quickly demo the bare VS Code UI features without our normal SDK and extension wrappers. “a11y-kit” (https://marketplace.visualstudio.com/items?itemName=MicroFish.accessibility-testkit)

Repro Steps:

  1. Install a11y-kit from VS Code Marketplace
  2. Open command palette and run a11y-kit’s menu command
  3. Next, select: “Quick Picks: Show Quick Picks - Single” and observe.

Expected: When entering the quick pick selection screen, the title should be read by the screen reader so that the user understands the context of the selection environment.

Actual: Certain other descriptors are picked up and read, but not the “Quick Pick Placeholder Title”.

Note: A user posted an issue on one of our extensions explaining that the title is picked up on JAWS but not NVDA. I have only verified this on VoiceOver and NVDA - neither screen reader reads the title as far as I can tell.

Attachments: sqp_macos

Thank you

Issue Analytics

  • State:open
  • Created a year ago
  • Comments:13 (9 by maintainers)

github_iconTop GitHub Comments

2reactions
isidorncommented, Nov 2, 2022

@MicroFish91 your a11y-kit does not work for vscode.dev. Can you please transition it to a web extension https://code.visualstudio.com/api/extension-guides/web-extensions

I think you do not depend on any node api so it might be just that you declare it as a web extension.

2reactions
isidorncommented, Jun 6, 2022

@TylerLeonhardt it is up to the screen reader to decide if it is read. If the title is now append when it gets read then we are good. Let’s close and give @MicroFish91 time to verify. I can also bring it up with the screen reader folk if needed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Handling common accessibility problems - MDN Web Docs
The key to accessible link text is that people using screen readers will often use a common feature whereby they pull up a...
Read more >
I thought title text improved accessibility. I was wrong. - Silktide
I thought it was read aloud by screenreaders, to solve the problem of weak link text like “read more” and “click here”, adding...
Read more >
Screen Readers: A Guide to Punctuation and Typographic ...
Symbol The character by itself In Context tilde ~ https:// www.website.com/ ~user backtick mark ? &id=?1? exclamation mark ! This is exciting! This is exciting.
Read more >
Easy Checks – A First Review of Web Accessibility - W3C
used for browser bookmarks/favorites; read by screen readers. (In the web page markup they are the <title> within the <head>.) The image below ......
Read more >
Quick tip: Starting a design with accessibility - The A11Y Project
The source order of elements in the HTML. This is the order that a screen reader will read the page in. The hierarchy...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found