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 Future consideration
Created by Guest
Created on Dec 20, 2023

AODA: User should be able to zoom upto 200% without a loss of functionality and using workaround as per WCAG 2.0 Guideline 1.4.4 Level AA

Issue:

When the page is resized to 200%, there is a loss of content and functionality, particularly with the Page with Context panel, as indicated in the attached screenshot. This results in a failure to meet the WCAG 1.4.4: Resize Text (AA) success criteria.



Workaround:

Navigate to the toggle buttons for the Context, Shortcuts, and Smart panels.

Click the toggle buttons to collapse the panels and access the navigation bar tabs and content area.



Impact:

While the workaround allows access to the main content of the page, it does not meet the criteria outlined in 1.4.4 Resize text: Text should be resizable up to 200 percent without loss of content or functionality. This implies that a user should be able to view all information at both 100% and 200% without the need to collapse top or side panels at 200%. Additionally, text at 200% zoom should be presented in a readable format without overlaps, truncation, or line breaks.

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

WCAG Compliance

  • Attach files
  • Guest
    Reply
    |
    Apr 3, 2024

    I would like to add that IBM accessibility requirements – IBM Accessibility also confirms and aligns with our request to make the Curam complaint with 200% zoom.


    1.4.4 Resize Text

    Copy link for 1.4.4

    Text can be resized without assistive technology up to 200 percent without loss of content or functionality.

    Rationale

    This requirement ensures visually rendered text can be scaled successfully so more users are able to read the information without requiring the use of assistive technology such as a screen magnifier. This increase in size can be achieved either by zooming all content OR by increasing just the text size. In both cases, this resizing is normally achieved by the user agent (i.e., web browser or view controller). The author’s responsibility is to create content that does not prevent the user agent from scaling the content effectively.

    To meet this requirement, confirm that scaling works and ensure there are no visual or functional issues as a result of the increase, such as:

    • a lack of appropriate line wrapping

    • truncated, overlapped or obscured text

    • missing scrollbars when content is zoomed

    In cases where content fails to respond to the platform’s scaling features authors must provide a way of resizing text.

    Note: For some interactive content, such as editable cells in a table, truncation is acceptable if the component’s full content is available on focus or after user activation, and an indication that this information can be accessed is provided to the user in some way besides the fact that it is truncated.

    Exception: Media captions and images of text are excluded from this requirement. Resizing the closed captions is normally a feature of the player or platform, not the author’s responsibility. Images of text, which are covered under 1.4.5 Images of text, do not normally scale well.

    Refer to Understanding 1.4.4 Resize Text (external link to WCAG 2.1) for more information on exceptions, intent, benefits, and techniques.

    Regards,

    Vahida

  • Guest
    Reply
    |
    Feb 26, 2024

    Attaching the screenshot mentioned in the previous comment.

  • Guest
    Reply
    |
    Feb 26, 2024

    I would like to add the below scenario as part of the 200% zoom accessibility issue.

    The calendar is cut off at 150% zoom and doesn't have a scrollbar to scroll to the bottom of the calendar. if the user clicks on the page content area scrollbar the calendar is disappeared.

    I have attached the screenshot for reference.

    1 reply
  • Admin
    Graham McCrindle
    Reply
    |
    Feb 22, 2024

    Hi Vahida

    We have reviewed your enhancement suggestion.

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

    • Users should be able to increase Zoom up to 200% in their browser window without the loss of functionality

    The theme is aligned with our current multi-year strategy for our product to support accessible users, 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,

    Graham McCrindle, CURAM Product Management Team

  • Guest
    Reply
    |
    Jan 19, 2024

    Please refer to the screenshot attached.

  • Admin
    Graham McCrindle
    Reply
    |
    Dec 21, 2023

    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 we need more details to complete our evaluation, we will send you a request for more information.


    Thank you,

    Graham, Curam Product Management Team