[BUG] - The field "LegacyIAccessiblePattern.State" is displaying a digit value and the yellow pop-up state on the tested element not displaying all the statuses available

[JamesDaly01]

Describe the bug
When looking into CLAIMS 3 our software tool - The limitation of "Accessibility Insights" when compared to "Inspect Objects" is that the current "State" not not displaying all the statuses available on the yellow pop-up value tested element and the State field "LegacyIAccessiblePattern.State" is not getting decoded (A number is displayed and not a value).

The following not displayed on the yellow pop-up or "State" field:
1, Input text field: The state: "Focused/Not Focused"
2. Buttons: The state: "Checked/Not Checked"
3. Combo box: The state: "Collapsed/Expanded"

To Reproduce
Steps to reproduce the behavior:

1. Open Accessibility Tool > Select Test from the left menu> Live Inspect > Settings > Configure properties to always show > LegacyIAccessiblePattern.State
2. Go to Internal USCIS 'CLAIMS 3 application'
3. Click on 'input text field', check box or combo box
4. See the the State field "LegacyIAccessiblePattern.State" displaying a digit
   

Expected behavior
The State field "LegacyIAccessiblePattern.State" should be displaying the following:
1, Input text field: The state: "Focused"
2. Buttons: The state: "Checked/unchecked"
3. Combo box: The state: "expanded/collapsed"

Actual behavior
The State field "LegacyIAccessiblePattern.State" is displaying for Ex. "LegacyIAccessiblePattern.State: 1048580"

Screenshots or .GIF
Screenshot added to help explain your problem.

Desktop

• OS: [Windows 10 ver 22H2(OS Build 19045.4412]
• Accessibility Insights for Windows Version: v1.1.2703.01
• Target Application: [USCIS - CLAIMS 3]
• Target Application Version: [28.5]

Additional context
Priority requested - HIGH

[kkotenko]

Modification Request: please show both the plain text description AND the numeric value.

The reason for the request is that the automation API we use in tandem with Accessibility Insights only exposes the numeric value; while having the plain text description would be most helpful, it would make things more complicated for us if the numeric version disappears.

There is precedent for this, for example with ControlType, HeadingLevel, LegacyIAccessiblePattern.Role, and Orientation.

[JamesDaly01]

Good afternoon Mr. Kotenko,

I have matched some state values with their corresponding description using Accessibility Insight and Inspect Objects.exe.
Just FYI - I saw other state values being displayed by Accessibility Insight but could not get a stabled comparison with Inspect Objects.exe. I hope this helps.

1. Input text field: The state:
   focused,focusable = LegacyIAccessiblePattern.State 1048580
   focusable = LegacyIAccessiblePattern.State 1048576
   unavailable, read only, focusable = LegacyIAccessiblePattern.State 1048641

2. Buttons: The state:
   checked, focusable = LegacyIAccessiblePattern.State 1048592
   focusable = LegacyIAccessiblePattern.State 1048576

3. Combo box: The state:
   collapsed, focusable = LegacyIAccessiblePattern.State 1049600 (when hover over field with mouse)
   selected, focused, focusable, selectable = LegacyIAccessiblePattern.State 3145734 (when click on field with mouse)

Thank you for your support! :)
James