Skip to Main Content
Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at Merative, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Merative External Privacy Statement:

Status Not under consideration
Created by Guest
Created on Jan 26, 2024

AODA: Elements with an ARIA role don't contain child roles, WCAG 2.0 Guideline 4.1.2 Level A

Ensures elements with an ARIA role that require child roles contain them

Why it Matters:
The inclusion of an ARIA role attribute in an element serves to guide assistive technologies in treating the element differently from its inherent HTML element type. For instance, assigning role="listbox" to a <ul> element directs assistive technologies to perceive it as a listbox control rather than a static list.

Suggested Fix:

  1. Identify the elements serving as managed controls and add the appropriate "child" roles to them.

  2. Remove any child elements of the managing control which are not serving as managed controls.

  3. Make sure the value of each ARIA state attribute updates as needed to reflect the element’s current state.

  4. Identify the ARIA role that best identifies the element’s function.

Fails WCAG 4.1.2: Name, Role and Value (A) success criteria

Steps to reproduce:

  1. Login as a case worker

  2. inspect the Section area (Home, Clients and outcome, Inbox, Calendar) please see attached screenshot.

Note: This error occurs in many places across the application.

Market Segment WH Government
Type of Request Other
Market Opportunity

AODA Compliancy

  • Attach files
  • Admin
    Graham McCrindle
    Mar 18, 2024

    Hi Vahida,

    We have reviewed your enhancement suggestion.

    Based on the information provided, our understanding of your request is as follows:

    • ARIA roles should contain child roles

    Following internal investigation of DOM, we can see that children with role=tab exist, it would seem for some reason they are not picked up by the AXE tool you are using.

    We have also performed some further manual testing with screenreaders, and the user experience is as expected.

    We are closing this request and do not plan to take any further action. If you believe we have misunderstood your request, please respond within 7 days with clarifications.

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.


    Graham McCrindle, CURAM Product Management Team

  • Admin
    Graham McCrindle
    Jan 29, 2024

    Hi Vahida

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    We will review the information you have provided and get back to you within 30 days. If additional details are required to complete our evaluation, we will send you a request for more information.

    Thank you,

    Graham McCrindle, SPM Product Management Team