MSFT_Accessibility_AP [S2] [DTA:21Q3] Bug 7725962: Screen reader fails on elements with an ARIA role that require parent rolesDescriptionScreen Reader MSFT_Accessibility_AP [S2] [DTA:21Q3] should ensure required parent roles to be contained by elements with an ARIA role. Users who rely on screen readers may not be able to understand the purpose and functionality of parent element (undefined role) present in the page.This issue was found using the Accessibility Insights for Web 2.24.0 (axe-core 4.1.1), a tool that helps find and fix accessibility issues.MAS Reference:MAS 1.3.1 – Info and RelationshipsWCAG Reference:https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html WCAG 1.3.1: Ensures elements with an ARIA role that require parent roles are contained by them (option[value="assignment_group"])Accessibility, WCAG 1.3.1, aria-required-parent ( https://accessibilityinsights.io/info-examples/web/aria-required-parent ).Element path: #gsft_main;option[value="assignment_group"]Snippet: <option value="assignment_group" role="option">Assignment group</option> Environment: Microsoft Edge version 89.0.774.75Steps to Reproduce 1: Navigate to the Filter section in the Quebec instance itil homepage. 2: Provide data as "Incidents" and activate the filter. 3: Move to the Resolved list item in the expanded section and activate it. 4: Run Accessibility Insights for web tool. Elements with an ARIA role that require parent roles are not contained by them (option[value="assignment_group"]) for all buttons. The required ARIA parent role is not present in the listbox.WorkaroundThis problem affects Quebec Patch 4 Hot Fix 2 and above patches. After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in later Quebec. The issue does not occur in Rome or later releases.Related Problem: PRB1518096