1. Open the https://answers.microsoft.com/en-us/msoffice/ using valid credentials.
2. open any related article.
3. Navigate to 'Reply' button and invoke it.
4. Navigate to 'ordered list' button and invoke it.
5. Navigate to the edit region and type some ordered list items.
6. Now, Navigate to the ordered list items and listen to Narrator announcement.

Actual Result:

On navigating to ordered list items with arrow keys, Narrator is only announcing first letters of the text and while navigating with 'caps-arrow' keys, Narrator is only announcing position details of the list items.

Note: this issue is not observed with nvda

Nvda version: 2020.2

Expected 
On navigating to ordered list items with 'arrow keys' or using 'caps-arrow' keys, Narrator should announce the whole text of the list item including position details.

User Impact 
Knowing how many items are in a list is extremely useful to assistive technology users as they can know if they should attempt to skip the list, navigate to the end, help them recall placement of certain items, or orient themselves within the list.  

1. open the https://answers.microsoft.com/en-us/msoffice/ using valid credentials.
2. Select 'reply' button.
3. Navigate to 'Insert image' button and invoke it.
4. Now Run the fast pass using Accessibility Insights for web and observe the failure 'label'.

1. open the given URL using valid credentials.
2. Navigate to 'Reply' button and invoke it.
3. Navigate to 'Insert image' button and invoke it.
4. Now Run the fast pass using Accessibility Insights for web and observe the failure 'Nested- interactive'.

1. open answers.microsoft.com/en-us/msoffice/ using valid credentials.
2. Navigate to any article link and hit enter.
3. Select 'reply' button.
4. Navigate to 'format' list and invoke it.
5. Now Run the fast pass using Accessibility Insights for web and observe the failure 'aria input field name'.

1. open the given URL using valid credentials.
2. Navigate to 'Reply' button and invoke it.
3. Navigate to 'color group' and invoke it.
4. Now, Navigate to the colors in color group and listen to Narrator announcement.

Actual Result:

On navigating to colors, Narrator is staying mute and not announcing anything.

Expected 
On navigating to colors, Narrator should announce the name of the color.

1. open the given URL using valid credentials.
2. Navigate to 'Reply' button and invoke it.
3. Navigate to 'table' button and invoke it.
4. Now, try to navigate to table cells to select the size of the table and observe

Actual Result:

After invoking 'table' button, user is unable to select the size of the table i.e, Keyboard focus is not going to 'Insert row and column cell components.

Tab index property is not defined.

Expected 
Control(s) must be accessible to keyboards and other assistive technology. Common causes of this problem include a) the element does not have a proper role assigned, b) the element needs tab-index="0" attribute to be focusable, or c) the component is not registering keypresses.  

User should be able to navigate to insert row and column cell components to select the size of the table.

User Impact 
When interactive components are not accessible, assistive technology users are blocked, which leads to everything from inaccessible content, features, and functionality, up to entire applications or sites. 

1. open the given URL using valid credentials.
2. Navigate to 'Reply' button and invoke it.
3. Navigate to 'insert image' button and invoke it.
4. Now, try to upload the image and observe

Actual Result:

User is unable to navigate to 'upload' button in 'insert image' dialogue. On invoking 'insert image' dialogue focus is navigating in the background and after navigating whole page then focus is going to the 'insert image' dialogue. Now, when user try to upload the image, focus is going out of the dialogue (going to the top of the page).

Expected Result:

Expected 
All components need an accessible name, ideally using semantic elements and attributes. In rare cases, aria-label or aria-labelled by may be needed to alter the name. Learn more by reading about the accessible name property. 

User Impact 
When interactive elements have an incorrect name, it is difficult for people using assistive technology (like screen readers) to understand the purpose of control and its relationship to other content.  

1. open the given URL using valid credentials.
2. Select 'reply' button.
3. Now Run the fast pass using Accessibility Insights for web and observe the failure aria required children.

Actual Result:

While navigating in table, Narrator is not announcing as 'enter table' and it is also not announcing rows and column information. while navigating in table, With arrow keys or table navigation keys or tab key, Narrator is announcing as 'end of line/blank'.

With caps-arrow keys, Narrator is giving row and column information.

Expected 
While navigating in table, Narrator should announce as enter table and it should also give row and column information. And while navigating with arrow keys or table navigation keys or tab key, Narrator should not announce as 'end of line/blank' instead it should give row or column information

if (_this.element && document.activeElement === _this.element) {
                _this.element.setSelectionRange(selection.start, selection.end);
            }

if (_this.element && document.activeElement === _this.element) {
                _this.element.setSelectionRange(selection.start, selection.end);
            }

if (document.activeElement !== _this.element)