Outlook 2024 Classic: NVDA not announcing "High Priority" status via QAT shortcut (Alt + 1)

41 views
Skip to first unread message

Mister Kayne

unread,
Mar 9, 2026, 12:50:51 PMMar 9
to NVDA-Users Group (nvda-users@nvaccess.org)

Hello NVDA Users Group,

 

I am experiencing a regression in how NVDA reports message priority changes in Outlook.

 

Environment:

• OS: Windows 11

• Outlook: Outlook 2024 Classic

• NVDA Version: 2025.3.3 (2025.3.3.54605)

 

The Issue:

I have customized my Quick Access Toolbar (QAT) to include the "High Priority" command, assigned to the Alt + 1 position. While the shortcut successfully toggles the high priority flag on the message, NVDA has stopped announcing the state change (e.g., it no longer says "High Priority" or "Importance: High" when the shortcut is pressed). This used to work reliably in previous versions of Outlook/NVDA.

The visual indicator changes correctly, but there is no speech feedback.

 

Has anyone else encountered this with Outlook 2024 Classic? I am wondering if this is a known issue with the way the new Classic ribbon handles QAT updates, or if there is a specific "Object Presentation" or "UIA" setting I should toggle in NVDA to force it to report this status change again.

Any advice or workarounds would be greatly appreciated.

 

Warm regards,

 

Mister Kayne
"It's a bitter, sweet symphony this life…"

Author: The Somebody, Nobody, Anybody & Everybody Blog!

Mail: writ...@mister-kayne.com

Sent from Outlook® for Windows 11

 

 

Quentin Christensen

unread,
Mar 10, 2026, 11:01:09 PMMar 10
to nvda-...@nvaccess.org
Can you please confirm what command you have assigned to alt+1? (as in what it is called / where to find it in the list of commands so I can find to try, because I can't find a mail action which seems to relate to priority or importance).

I think Outlook might be depreciating that feature - as I can't find a ribbon or context menu to set or change it either.  I can set it when I am composing a message.  There is a "Flag for follow up" message, though TBH that doesn't seem to work.  I can set it (which NVDA doesn't report though visually it puts a little red flag next to the message), but I can't clear it - and in fact the option to flag it is still available.

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/TYZPR02MB9171394CD07484E68D3E0C9E9D79A%40TYZPR02MB9171.apcprd02.prod.outlook.com.


--

Quentin Christensen
Training and Support Manager

NV Access

Subscribe to email updates (blog, new versions, etc): https://eepurl.com/iuVyjo

Mister Kayne

unread,
Mar 10, 2026, 11:18:41 PMMar 10
to nvda-...@nvaccess.org

Hi Quentin,

 

I can certainly clarify that for you. The command is called "High Importance" (sometimes labeled as "High Priority" depending on the specific view).

 

In Outlook 2024 Classic, you don't actually need to dig into the full Options menu to set this up. You can do it directly from the main window using the keyboard:

To add High Importance to your QAT:

1. Navigate to the QAT: In the main Outlook window, press the Alt key to activate the ribbon.

2. Move to the Customization Menu: Press Shift + Tab repeatedly. You will cycle past your account details and the search bar until you reach the Customize Quick Access Toolbar button.

3. Expand the Menu: Press the Space bar to expand the list of available actions.

4. Select the Command: Arrow down through the list to find High Importance and press the Space bar to check it.

5. Assigning Alt + 1: The shortcut is determined by the order in the list. To ensure it is Alt + 1, "High Importance" needs to be the first active item on your QAT.

 

Important Note: Even though you can set this up from the main window, the command is context-specific. It will only be active and functional when you are composing, replying, or forwarding a mail. If you try to use Alt + 1 while just browsing your Inbox, the command will be unavailable.

Quentin Christensen

unread,
Mar 10, 2026, 11:36:27 PMMar 10
to nvda-...@nvaccess.org
Ah thank you, I found it.

So, interesting, I never realised that menu was so different when you are composing a message to when you are on the inbox etc.  I initially tried to follow your steps from the inbox and couldn't quite follow but did find the command in the customise quick access toolbar options this time.

And when I do it that was on messages in my inbox, it DOES still report whether high importance is on or off as you toggle it.

When I did compose a message and follow your steps, I can again toggle high importance on or off in the message I am composing, and it also works here.  I MAY have a different version of Outlook to you.

I am using:

Windows 11 (64-bit) Version: 25H2, Build: 26200.7922
Office 365 (64-bit) Version: 16.0.19725.20152 
NVDA 2025.3.3

I also tried
nvda_snapshot_alpha-55033,41999585.exe from https://download.nvaccess.org/snapshots/alpha/

And in both cases, it is reporting the change in high importance.



Gene Asner

unread,
Mar 10, 2026, 11:51:17 PMMar 10
to nvda-...@nvaccess.org
There are various possibilities and I think the first thing to try is to
run NVDA with add-ons disabled and see what happens.


Gene
> *From:*Quentin Christensen <que...@nvaccess.org>
> *Sent:* Wednesday, March 11, 2026 8:31 AM
> *To:* nvda-...@nvaccess.org
> *Subject:* Re: [NVDA] Outlook 2024 Classic: NVDA not announcing
> <https://www.mister-kayne.com/>
>
> Mail: writ...@mister-kayne.com <mailto:writ...@mister-kayne.com>
>
> Sent from Outlook® for Windows 11
>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor
> Code of Conduct.
> NV Access expects that all community members will read and
> abide by the rules set out in this document while
> participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org
> <mailto:nvda-users%2Bman...@nvaccess.org>.
> ---
> You received this message because you are subscribed to the
> Google Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to nvda-users+...@nvaccess.org.
> To view this discussion visit
> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/TYZPR02MB9171394CD07484E68D3E0C9E9D79A%40TYZPR02MB9171.apcprd02.prod.outlook.com
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/TYZPR02MB9171394CD07484E68D3E0C9E9D79A%40TYZPR02MB9171.apcprd02.prod.outlook.com?utm_medium=email&utm_source=footer>.
>
>
> --
>
> Quentin Christensen
>
> Training and Support Manager
>
> NV Access
>
> www.nvaccess.org <http://www.nvaccess.org>
>
> Training: https://www.nvaccess.org/shop/
>
> Certification: https://certification.nvaccess.org/
>
> Subscribe to email updates (blog, new versions, etc):
> https://eepurl.com/iuVyjo
>
> User group: _https://groups.google.com/a/nvaccess.org/g/nvda-users_
>
> Other groups: https://github.com/nvaccess/nvda/wiki/Connect
>
> Mastodon: https://fosstodon.org/@NVAccess
>
> Facebook: http://www.facebook.com/NVAccess
> <http://www.facebook.com/NVAccess>
>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code
> of Conduct.
> NV Access expects that all community members will read and abide
> by the rules set out in this document while participating in this
> group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org.
> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to nvda-users+...@nvaccess.org.
> To view this discussion visit
> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAKsDpFh4Vsz8QgNEtHhcmaB5giJd_oJUrT84v-3%3D6xSn_194VQ%40mail.gmail.com
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAKsDpFh4Vsz8QgNEtHhcmaB5giJd_oJUrT84v-3%3D6xSn_194VQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code
> of Conduct.
> NV Access expects that all community members will read and abide
> by the rules set out in this document while participating in this
> group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org
> <mailto:nvda-users%2Bman...@nvaccess.org>.
> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to nvda-users+...@nvaccess.org.
> To view this discussion visit
> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/TYZPR02MB9171D7E958C35AF5EEEDFB0E9D47A%40TYZPR02MB9171.apcprd02.prod.outlook.com
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/TYZPR02MB9171D7E958C35AF5EEEDFB0E9D47A%40TYZPR02MB9171.apcprd02.prod.outlook.com?utm_medium=email&utm_source=footer>.
>
>
>
> --
>
> Quentin Christensen
> Training and Support Manager
>
> NV Access
> www.nvaccess.org <http://www.nvaccess.org>
>
> Training: https://www.nvaccess.org/shop/
> Certification: https://certification.nvaccess.org/
> Subscribe to email updates (blog, new versions, etc):
> https://eepurl.com/iuVyjo
> User group: _https://groups.google.com/a/nvaccess.org/g/nvda-users_
> Other groups: https://github.com/nvaccess/nvda/wiki/Connect
> Mastodon: https://fosstodon.org/@NVAccess
> Facebook: http://www.facebook.com/NVAccess
> <http://www.facebook.com/NVAccess>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of
> Conduct.
> NV Access expects that all community members will read and abide by
> the rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org.
> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to nvda-users+...@nvaccess.org.
> To view this discussion visit
> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAKsDpFh_2_My9C7ECzCcjXggyfS2zQ7-KQi%3D0CWm71nOrQXj_w%40mail.gmail.com
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAKsDpFh_2_My9C7ECzCcjXggyfS2zQ7-KQi%3D0CWm71nOrQXj_w%40mail.gmail.com?utm_medium=email&utm_source=footer>.

Mister Kayne

unread,
Mar 11, 2026, 12:37:09 PMMar 11
to nvda-...@nvaccess.org
Hi Gene,

Thank you for suggesting that approach.

I followed your advice and tried running NVDA with all add-ons disabled, but unfortunately, it did not resolve the issue. NVDA still fails to announce the selected state of the message priority when I use the shortcut.
It seems there might be something specific within my Outlook profile or system configuration that is preventing this from being reported correctly. I plan to look into the profile settings this weekend to see if I can pinpoint what's blocking the announcement.

I appreciate the help in narrowing this down!
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/21a866fa-30d0-4e12-8549-230f4bd92642%40gmail.com.

Mister Kayne

unread,
Mar 11, 2026, 12:40:52 PMMar 11
to nvda-...@nvaccess.org

Hi Quentin,

 

Thank you so much for investigating this and for checking across different versions, including the alpha snapshot. It is very helpful to know that it is working on your end, as that confirms the issue is likely local to my environment.

 

I will need until this weekend to sit down and gather the full details of my complete setup to share with you. To give you an update on what I’ve tried so far: following Gene's suggestion, I tested this with NVDA add-ons disabled, but unfortunately, it didn't provide a fix—the announcement still isn't triggering.

My next step is to dive into the Outlook application profile. I'm going to experiment with toggling various settings on and off to see if a specific configuration is causing the conflict. Once I have some time this weekend to troubleshoot properly, I will get back to the group with any findings.

 

I really appreciate the support!

Matthew Horspool

unread,
Mar 12, 2026, 8:33:38 AMMar 12
to nvda-...@nvaccess.org

Hi Quentin,

Piggybacking onto this thread a bit: do you know what is causing NVDA to announce the high importance status when high importance is switched on? For example, is it a UIA notification or something that NVDA implements internally?

I am wondering whether the problem is as simple as Mr Kayne’s Outlook not sending the UIA notification – or, perhaps, NVDA not receiving the UIA notifications that Outlook is sending.

Thanks,

Matthew

Mister Kayne

unread,
Mar 12, 2026, 12:22:40 PMMar 12
to nvda-...@nvaccess.org

Hi Matthew and Quentin,

 

I wanted to provide a collective update on the troubleshooting for the Outlook High Importance announcement issue.

 

As of today, I have deleted my Outlook configuration profile, closed the application, and restarted NVDA with all add-ons disabled to ensure a clean testing environment. Unfortunately, I am still having no luck with the situation—NVDA remains silent when using the Alt+1 QAT shortcut to mark a message as High Importance.

 

For your reference, here are my current system and setup details:

• Operating System: Microsoft Windows 11 Pro (64-Bit, Version: 10.0.26200 Build 26200)

• Outlook: Microsoft® Outlook® LTSC MSO (Version 2408 Build 16.0.17932.20670) 64-bit

• Screen Reader: NVDA 2025.3.3

 

Please let me know if these build details help narrow down why the behavior is inconsistent, or if there are further logs you would like me to provide.

Quentin Christensen

unread,
Mar 12, 2026, 6:34:18 PMMar 12
to NVDA Screen Reader Discussion
I did actually test with NVDA set to use uia always or only when necessary, though I just realised that was in word (which outlook uses for reading individual messages) so probably didn't make a difference when navigating the message list. 

The only other thing which jumps out is that you are using an older LTSC version of outlook and it may be as simple as it not working in that version but working in the newer version I have?


Quentin Christensen
Training and Support Manager

NV Access

Subscribe to email updates (blog, new versions, etc): https://eepurl.com/iuVyjo

Mister Kayne

unread,
Mar 13, 2026, 8:25:56 AM (13 days ago) Mar 13
to nvda-...@nvaccess.org

Hi Quentin,

 

I’ve also found that another way to set high priority is using the shortcut Alt + H, H, but this too does not announce that the priority has changed to High Importance. It seems the silence is consistent regardless of the method I use to toggle it.

 

Regarding the QAT, it’s a productivity hack I’ve relied on for over 20 years to quickly set priority, attach files, and forward messages. It’s second nature at this point, so I suppose I’ll just have to live with this state for now.

 

I did also test with NVDA set to use UIA "always" or "only when necessary," but no luck. Deleting the Outlook profile on NVDA, starting NVDA without add-ons all troubleshooting steps failed.

The version difference you mentioned is a very strong possibility. Being on an older LTSC version of Outlook might simply mean the fix or behavior present in your newer version hasn't reached my build yet.

 

Thanks for sticking with me on this troubleshooting!

Matthew Horspool

unread,
Mar 13, 2026, 12:09:47 PM (13 days ago) Mar 13
to nvda-...@nvaccess.org

HI Quentin,

The message list isn’t the OP’s problem, I don’t think.

The steps are, roughly:

  1. Start a new message.
  2. Put High Importance on your Quick Access Toolbar (position 1 in the OP’s case).
  3. Press your Quick Access Toolbar shortcut for High Importance (ALT+1 in the OP’s case).

Expected: NVDA says: high importance.

Actual: NVDA says nothing.

NVDA is my secondary screen reader, so I’ve just ran those steps with JAWS and I can see that “High importance on” is sent by Outlook as a UIA notification here. Likewise, if I press the keystroke again, I get “High importance off” as a UIA notification.

My guess is that NVDA will speak the notification if it receives it, which suggests that the OP’s Outlook is not sending the notification.

Mister Kayne, how long has NVDA been telling you about high importance when you turn it on and off? Likewise, how long has it not been telling you about it? Has anything changed, e.g. you got a new computer, which might have caused the behaviour to change?

Matthew

joseph....@gmail.com

unread,
Mar 13, 2026, 12:46:55 PM (13 days ago) Mar 13
to nvda-...@nvaccess.org

Hi,

Yes, “high importance” message is reported as a UIA notification event (this is on Outlook classic 365 version 16.0.19822.20044).

Cheers,

Joseph

Mister Kayne

unread,
Mar 14, 2026, 1:49:57 AM (13 days ago) Mar 14
to nvda-...@nvaccess.org

Hi Matthew,

 

It is very difficult to recall the exact sequence of events or the specific point when the behavior changed. I did upgrade my Office to 2024 and then later upgraded my hardware to meet Windows 11 requirements. As for NVDA, I always have it set to check for updates automatically, so it stays current.

 

Thank you for your help with this. I believe you are right—my guess is that NVDA would speak the notification if it received it, which suggests that my version of Outlook is simply not sending the UIA notification when the toggle is triggered via the QAT.

Mister Kayne

unread,
Mar 14, 2026, 2:04:57 AM (13 days ago) Mar 14
to nvda-...@nvaccess.org

Hi Joseph,

 

Thank you for confirming that! That is incredibly helpful information.

 

It appears we’ve found the root cause. My version is Outlook LTSC 2024 (Build 16.0.17932.20700), which is significantly older than your Microsoft 365 (Build 16.0.19822.20044). It seems that while the 365 version has the refined UIA notification events for the QAT, this LTSC build is either missing them entirely or they haven't been backported.

 

This confirms Matthew's suspicion that my version of Outlook simply isn't sending the notification event for NVDA to catch. I'll likely need to look into migrating to the 365 track to resolve this and access newer features.

 

I really appreciate you taking the time to check your version for me.

Sean Randall

unread,
Mar 14, 2026, 3:19:14 AM (13 days ago) Mar 14
to nvda-...@nvaccess.org
meantime, perhaps you could adjust your workflow. 
pressing alt+enter allows you to cursor to the level of import your messages require, with all the associated feedback a standard windows listbox gives you. This could provide a temporary alternative, perhaps. 
Thanks

Sean


On 14 Mar 2026, at 06:04, Mister Kayne <mister...@outlook.com> wrote:



Mister Kayne

unread,
Mar 14, 2026, 6:54:09 AM (13 days ago) Mar 14
to nvda-...@nvaccess.org

Hi Sean,

 

Thank you for that workflow. I appreciate the suggestion, but honestly, I am a bit disappointed that what used to work earlier is now broken, especially after updating both Outlook and Windows. It feels quite silly, but I guess one has to live with such technical limitations sometimes.

 

I also tried the Outlook Enhancement add-on with my version of Outlook, but it does not help much. Not that I do not appreciate the effort behind the add-on, but for my specific use case, I just do not find it very handy.

 

Thank you for your support on this, much appreciated.

Justin coffin

unread,
Mar 14, 2026, 7:30:31 AM (13 days ago) Mar 14
to NVDA Screen Reader Discussion, Mister Kayne
Hi, 

It looks like the core of the problem comes down to a difference in how various Outlook builds handle UIA notifications. NVDA can only announce the High Importance toggle if Outlook actually sends a UIA notification when the state changes. From what everyone has tested, the Microsoft 365 builds do send those notifications consistently, which is why Quentin and others are hearing NVDA report “High importance on/off.”
Your LTSC 2024 build, however, appears not to send that UIA event at all. That would explain why NVDA stays silent no matter which method you use—QAT shortcut, ribbon command, or Alt+H, H. NVDA isn’t ignoring anything; it simply never receives the event it needs in order to speak the change.
This also lines up with the fact that:

Add-ons don’t affect the behavior.

Resetting your Outlook profile didn’t change anything.

UIA mode in NVDA doesn’t make a difference.

Other users on newer Outlook builds can reproduce the expected announcement.
So the behavior isn’t a regression in NVDA—it’s a limitation (or missing implementation) in the LTSC branch of Outlook. LTSC versions often lag behind Microsoft 365 in UIA improvements, and features like these sometimes never get backported.
In short: NVDA will announce the priority change if Outlook sends the UIA event, but your LTSC build simply isn’t generating it. Upgrading to a newer Microsoft 365 build is probably the only way to restore the old behavior.

Reply all
Reply to author
Forward
0 new messages