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 Is a defect
Created by Guest
Created on Jan 5, 2024

RELATED IDEAS

AODA: Form elements do not contain visible label, and do not conform with WCAG 2.0 Guideline 3.3.2 Level A

Description:
The elements do not contain visible label tag

Every form / input element must have a visible <label> tag that's not solely labeled using hidden labels, or the title or aria-describedby attributes. E.g., <input type="text" aria-labelledby="search">

Why it Matters: The title and aria-describedby attributes are used to provide additional information such as a hint. Hints are exposed to accessibility APIs differently than labels and as such, this can cause problems with assistive technologies. When form inputs such as text entry fields, radio buttons, check boxes, and select menus contain no labels other than title and aria-describedby attribute values, screen readers interpret the content as advisory information only. Labels created by the title and aria-describedby values are not sufficient to create a true label that can be determined programmatically from the code to convey the purpose of the input form element.

Steps to Reproduce: (Scenario 1 - Edit Income Reporting Evidence)
1. Log in as a Caseworker
2. Navigate to income support page
3. Navigate to Evidence tab
4. Open the income reporting evidence
5. From the ellipsis, select "Continue Editing"
6. From the modal, locate the input field
Result / Issue: The input element is missing a required label tag

Resolution: The input elements are using label tags.

Fix Suggestion (Example only):

<label for="rtype">Report Type:</label> <input type="text" name="rtype" id="rtype"><br>
<label for="rname">Report Name:</label> <input type="text" name="rname" id="rname">

This provides a one-to-one mapping between the label and the element. This is the expected usage for labeling as it is supported by all modern browsers and all major assistive technologies for all form / input elements.

Following pages are with the defect (but not limited to):

  1. Notes page

  2. Person Search page

  3. Edit Note page

  4. Person > Financials page

Note: This doesn't conform to Best Practices, however, it could potentially fail the 3.3.2: Labels or Instructions (A) success criteria

Customer Name Ministry of Children, Community and Social Services
Market Segment Eligibility & Entitlement
Type of Request Other
Market Opportunity

AODA Compliant
  • Attach files
  • Admin
    Graham McCrindle
    Reply
    |     Jan 10, 2024

    Hi Vahida,

    We have reviewed your enhancement suggestion.

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

    • Label Tags for accessibility users are not present which results in

    We have determined this is a defect that requires a code change to correct and request that you raise a support ticket documenting the issue, this will then enable you to track the progress of this issue, we are now closing this enhancement request.

    Regards,

    Graham McCrindle, SPM Product Management team

  • Admin
    Graham McCrindle
    Reply
    |     Jan 8, 2024

    Hi Vahida,

    Thank you for taking the time to share your ideas with us. Can you confirm which version of SPM you have encountered the Accessibility issues.

    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