aria-expanded state is not reported correctly in narrator w/ combobox role

External Issue #12949478


Lucas S.
Jul 27, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

The combobox expanded state is never read through narrator, the following js fiddle repro’s the error:

Using firefox/NVDA aria-expanded reports correctly.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 16241 and is available in our latest Insider Preview build in the Fast ring. Specifically, when we click the collapsed dropdown box, Narrator says "editable combo box… expanded".

      Best Wishes,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Status to “Fixed”

      Changed Assigned To to “James M.”

      Changed Status from “Fixed”

      Changed Assigned To to “bbrinza”

      Changed Status to “External”

    • Thank you for the report, we took a look and there are two aspects of the behavior: 1) platform API mappings - in my testing EdgeHTML correctly maps aria-expanded to UIA Expanded property 2) reading updated state on the interactions - this currently doesn’t happen, because EdgeHTML doesn’t fire UIA property state changes when this property (Expanded) changes, which is just a gap - this is not covered by any W3C standards. Going forward we have a general work item to fire more UIA property state changes on changes like this and you’ll see this working in the future. I’ve resolved the bug as a duplicate to the work item we use to track consistent property change events firing. 

    • This issue has been resolved External. This means this issue may require a new feature to be implemented or other work that is more significant than a typical bug. You may be able to find more information on this issue by searching for related features on and

    • I forgot to mention that when you go out / back in to control the state is current state is read correctly (see 1 above - it is indeed map properly). Arguably clients can re-query common state on user interactions, see perhaps another approach would be for clients such as Narrator to make sure they update the state on user interaction (we’re currently not pursuing this path as it means all clients would need to do this).

    You need to sign in to your Microsoft account to add a comment.

    Sign in