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

Add a new idea Subscribe
Status Not under consideration
Created by Maya Cheng
Created on Oct 2, 2024

RELATED IDEAS

Links are styled as button - buttons are styled as links

GOOD TO HAVE Styling a link to look like a button is not inherently a WCAG failure, but there are important considerations to ensure accessibility:


Semantic Elements: Use the appropriate HTML elements. If it’s a link, use <a>. If it’s a button, use <button>. This helps assistive technologies understand the element’s purpose1.


ARIA Roles: If you must style a link to look like a button, ensure it has the correct ARIA roles. For example, a <button> styled as a link should have role="link"1.


Accessible Name: Ensure the link or button has an accessible name or label. This is crucial for screen readers2.


Keyboard Navigation: Make sure the element is focusable and operable via keyboard. Links should be navigable using the Tab key, and buttons should be activatable using the Enter or Space keys3.


By following these guidelines, you can style links to look like buttons without failing WCAG criteria.

Customer Name ESDC
Type of Request Idea
Market Opportunity

Accessibility Enhancement
  • Attach files
  • Admin
    ANGELA BRADY
    Reply
    |     Dec 6, 2024

    Hi Maya,

     

    We have reviewed your enhancement suggestion. 

     

    There are four individual items in this request and in our recent Curam release v8.1.3.0, which was release on Nov 28th 2024, it included improvements in many of these areas.

     

    (1) Semantic Elements, the request is to use the appropriate HTML elements. If it’s a link, use <a>. If it’s a button, use <button>. This helps assistive technologies understand the element’s purpose.

    In v8.1.3.0, for Action Controls inside a Cluster/List these will be <button> elements.

    (2) ARIA Roles: the request is if you must style a link to look like a button, ensure it has the correct ARIA roles. For example, a <button> styled as a link should have role="link".

    Based on (1) above delivered, from v8.1.3.0, we will not have <a> links styled to look like buttons (Action Controls inside a Cluster/List)

    (3) Accessible Name: the request is to ensure the link or button has an accessible name or label. This is crucial for screen readers.

    In 8.1.3.0, we have updated unspecific links with text values of 'New' or 'Edit' to have more specific and detailed labels.

    Additionally we have an existing known issue, DT037037 to ensure Links/Buttons have an accessible name or label, which is targeted for a future release.

    

    (4) Keyboard Navigation: the request is to make sure the element is focusable and operable via keyboard. Links should be navigable using the Tab key, and buttons should be activatable using the Enter or Space keys.

    From v8.1.3.0, Buttons should now be activate-able using Enter / Space for Action Controls inside a Cluster / List.


    This covers the requests raised and I am therefore going to close this out. 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