Curam Ideas Portal

Shape the future of Curam!

We invite you to shape the future of Curam, 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 Curam team to refine your idea

Help Curam prioritize your ideas and requests

The Curam 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

Add a new idea Subscribe
Status Future consideration
Categories Social Program Management Platform
Created by Darren Kenny
Created on Jun 6, 2024

RELATED IDEAS

Headings should be created in an hierarchical order

In the current implementation, it is possible to have skipped heading levels. For example on the Search pages you often have H1 followed directly by one or more H3.


As per WCAG 2.1 AA, the ruling is to ensure that correct HTML semantics are used. But in one of the WCAG technique (H42: Using h1-h6 to identify headings | WAI | W3C) suggested to implement the headings states that heading markup should indicate the appropriate heading level for the content.

Note that it is not required to implement the WCAG technique. You can achieve the same objective in various ways such as using ARIA instead of html mark up in this case. But when WCAG technique is implemented, it will make your site more accessible and at the same time, usable.

Below are some of the adverse impacts when using inconsistent headings:

  • Headings provide context about the content that follows. Inconsistent headings can confuse users, making it hard to determine the relationship between sections and the importance of content.

  • Screen reader users often rely on headings to navigate a page. Inconsistent or improperly structured headings can make it difficult for them to understand the layout and hierarchy, hindering efficient navigation.

  • Users with cognitive disabilities may struggle with understanding the structure and flow of the content. Consistent headings help in reducing cognitive load by providing a clear, predictable structure.

Though it is not a direct WCAG failure, but it would be highly recommended that the headings are created in an hierarchical order.

Customer Name ESDC
Type of Request Idea
Market Opportunity

A better accessible application
  • Attach files
  • Guest
    Sep 5, 2025

    The issue impacts clint facing intake applications in UA portal and SPM and is a strong recommendation from WCAG per technique H42.
    https://www.w3.org/WAI/WCAG22/Techniques/html/H42


    WCAG Technique H42 — Using <h1>–<h6> to identify headings — is a foundational accessibility practice that plays a critical role in making web content understandable and navigable, especially in customer-facing applications.

    Why H42 Is Important

    H42 supports WCAG Success Criterion 1.3.1: Info and Relationships, which ensures that information conveyed visually (like headings) is also available programmatically. This is crucial for users relying on assistive technologies, such as screen readers.

    Here’s why it matters:

    • Semantic Structure: Using proper heading tags (<h1> to <h6>) gives content a logical structure. This helps all users — especially those with cognitive disabilities — understand how content is organized.

    • Screen Reader Navigation: Screen readers allow users to jump between headings. Without proper heading markup, users may struggle to find relevant sections.

    • Visual Consistency: Assistive technologies that modify visual layouts (e.g., high contrast modes or custom styles) can still preserve the structure if headings are correctly marked.

    Impacts on Customer-Facing Applications


    Impact Area

    Description

    Accessibility

    Users with disabilities can navigate and understand content more easily.

    User Experience

    Clear headings improve readability and reduce cognitive load.

    Compliance

    Helps meet legal and regulatory requirements from Canada.gov


    Best Practices

    • Use <h1> for the main page title, and nest subsequent headings logically (<h2>, <h3>, etc.).

    • Ensure headings reflect the actual structure and importance of content.

    Reply
  • Guest
    Apr 24, 2025

    Morning Angela,

    The client, ESDC, has requested that this idea be prioritized by the Product Team as this is an Accessibility issue for clients who use Assistive Technologies and would request that this be included in a future enhancement as soon as possible.

    Thanks,

    Tammy

    Reply
  • Admin
    ANGELA BRADY
    Sep 30, 2024

    Hi Benoit,

     

    We have reviewed your enhancement suggestion. 

     

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

    •        Preserve the hierarchical order for headings on pages so that no heading levels are skipped

     

    The theme is aligned with our current multi-year strategy for our product, and we have accepted your suggestion as a consideration for a future release. Not all items under consideration will make it into a release. As plans are confirmed, you will be notified when a specific release includes this enhancement.

     

    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.

     

    Regards,

    Angela Brady, Cúram Product Management Team


    Reply
  • Admin
    Graham McCrindle
    Jun 6, 2024

    Hi Darren,

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

    Reply