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: https://www.merative.com/privacy

Status Not under consideration
Created by Guest
Created on Dec 19, 2023

AODA - Headings should be incremented by just one level as per WCAG 1.3.1: Info and Relationships (A)

No description provided
Customer Name Ministry of Children, Community and Social Services
  • Attach files
  • Admin
    Graham McCrindle
    Reply
    |
    Apr 29, 2024

    Hi Vahida

    We have reviewed your enhancement suggestion.

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

    • You wish for headers to be incremented by just one level


    Whilst we acknowledge the benefit of the suggestion, We do not see any WCAG criteria failure here, as there is no WCAG requirement that highlights we cannot skip heading. There are various conversations within WCAG teams and the wider accessibility community, around the heading level for modals. WCAG does not prescribe the use of H1 or H2 or H3. Actually, in the accessibility community we see a trend recommending the following:

    • avoid using H1 on dialogs, in favour of using H2 or H3

    • make sure you are consistent with the heading level you use, to avoid confusion for the end user


    On the basis that we consistently use H3 on all our modals we will not be looking to change this in the near term and this request will be closed and we will not be taking any further action.

    Thank you for taking the time to share your ideas with us. Although we cannot pursue all the submitted suggestions, we are committed to involving our users in building our product roadmap and appreciate your ideas.

    Regards,

    Graham McCrindle, CURAM Product Management Team

  • Admin
    Graham McCrindle
    Reply
    |
    Apr 10, 2024

    Hi Vahida,

    Thank you for taking the time to share your ideas with us. I must apologise for the fact that this enhancement request has not been reviewed earlier. For some reason this request and two others raised by you in December were routesd to SPAM within the enhancement tool. We were unaware there was such a facility until you raised a query last week with our support team.

    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, CURAM Product Management Team