The short cut Ctrl + Shift + D to toggle the detail level of screen reader conflicts with the browser's short cut

Question

The short cut Ctrl + Shift + D to toggle the detail level of screen reader conflicts with the browser's short cut

Tongchen Gu 20 Microsoft Employee

For a better A11y experience, we want to use the short cut Ctrl + Shift + D to toggle the detail level of screen reader https://learn.microsoft.com/en-us/azure/azure-maps/map-accessibility#screen-reader-support, but this short cut conflicts with the browser's short cut which adds the page to bookmark.

SRILAKSHMI C 11,755 Reputation points Microsoft External Staff Moderator

2025-12-17T03:19:10.91+00:00

Hello Tongchen Gu,

Welcome to Microsoft Q&A and Thank you for reaching out.

you’re right that Ctrl + Shift + D conflicts with the browser’s built-in bookmark shortcut, and because browser shortcuts take priority, the Azure Maps screen reader toggle cannot reliably capture this key combination. This is a known limitation when running inside standard web browsers.

A few options you can consider:

Some browsers allow limited shortcut customization or management via settings or extensions, but core shortcuts like bookmarking often can’t be fully disabled.

If your screen reader or application supports it, using a different key combination that doesn’t conflict with browser-reserved shortcuts is the most reliable approach.

You can also rely on the screen reader’s native commands to adjust verbosity or detail levels, instead of using the Azure Maps shortcut.

If this is part of a custom app, implementing your own non-conflicting keyboard shortcut at the application level can help ensure consistent accessibility behavior.

I Hope this helps. Do let me know if you have any further queries.

Thank you!
Tongchen Gu 20 Reputation points Microsoft Employee

2025-12-17T04:11:54.2666667+00:00

Thanks SRILAKSHMI C srilasksfor our answer!
I am conducting an accessibility review for our SharePoint web part, which has been migrated from Bing Maps to Azure Maps. We are using Microsoft Narrator as the screen reader, and I am curious about what Ctrl + Shift + D does under the hood.When I use NVDA as the screen reader, it announces state changes as I navigate the map with the arrow keys. However, Narrator does not provide the same behavior. I suspect this is because, in Narrator, Ctrl + Shift + D is required or Azure Maps doesn't fully support Narrotor.

Do you have any suggestions specifically for improving the experience with Narrator? Also, shouldn’t the Azure Maps team address this issue, since it could impact all users relying on Narrator for accessibility?
rbrundritt 21,581 Reputation points Moderator

2025-12-18T04:45:47.19+00:00

Interesting. I was the PM for this SDK in its early days, and this short cut combination was provided to us from the Microsoft accessibility team. The SDK eventually went through 3 months of user testing with several user groups of people who use accessibility tools every day, and this is the first time anyone noticed this conflict, 8 years since it was introduced. I'm not on the maps team, or at Microsoft these days, but several people on the Azure Maps team monitor these forums for issues like this. I'm sure one of them will pick it up.

Your answer

SRILAKSHMI C 11,755 Reputation points Microsoft External Staff Moderator

2025-12-17T03:19:10.91+00:00

Hello Tongchen Gu,

Welcome to Microsoft Q&A and Thank you for reaching out.

you’re right that Ctrl + Shift + D conflicts with the browser’s built-in bookmark shortcut, and because browser shortcuts take priority, the Azure Maps screen reader toggle cannot reliably capture this key combination. This is a known limitation when running inside standard web browsers.

A few options you can consider:

Some browsers allow limited shortcut customization or management via settings or extensions, but core shortcuts like bookmarking often can’t be fully disabled.

If your screen reader or application supports it, using a different key combination that doesn’t conflict with browser-reserved shortcuts is the most reliable approach.

You can also rely on the screen reader’s native commands to adjust verbosity or detail levels, instead of using the Azure Maps shortcut.

If this is part of a custom app, implementing your own non-conflicting keyboard shortcut at the application level can help ensure consistent accessibility behavior.

I Hope this helps. Do let me know if you have any further queries.

Thank you!
Tongchen Gu 20 Reputation points Microsoft Employee

2025-12-17T04:11:54.2666667+00:00

Thanks SRILAKSHMI C srilasksfor our answer!
I am conducting an accessibility review for our SharePoint web part, which has been migrated from Bing Maps to Azure Maps. We are using Microsoft Narrator as the screen reader, and I am curious about what Ctrl + Shift + D does under the hood.When I use NVDA as the screen reader, it announces state changes as I navigate the map with the arrow keys. However, Narrator does not provide the same behavior. I suspect this is because, in Narrator, Ctrl + Shift + D is required or Azure Maps doesn't fully support Narrotor.

Do you have any suggestions specifically for improving the experience with Narrator? Also, shouldn’t the Azure Maps team address this issue, since it could impact all users relying on Narrator for accessibility?
rbrundritt 21,581 Reputation points Moderator

2025-12-18T04:45:47.19+00:00

Interesting. I was the PM for this SDK in its early days, and this short cut combination was provided to us from the Microsoft accessibility team. The SDK eventually went through 3 months of user testing with several user groups of people who use accessibility tools every day, and this is the first time anyone noticed this conflict, 8 years since it was introduced. I'm not on the maps team, or at Microsoft these days, but several people on the Azure Maps team monitor these forums for issues like this. I'm sure one of them will pick it up.

Share via

The short cut Ctrl + Shift + D to toggle the detail level of screen reader conflicts with the browser's short cut

Your answer