Pinned ideas

PINNED SQL statements in Dashboard Widgets

I think using SQL statements in widgets would be great to leverage the entire potential of the data uploaded to IBM Process Mining. Lots of important and helpful information cannot be displayed today as it's only SQL-like. I don't think that using...

PINNED Filter UI enables having OR between filters (not just AND)

Users want to filter cases for client1 OR client2. They can't without creating a custom filter with javascript -- which they don't like at all

All ideas

Showing 2120

1 VOTE

The item display panel on the right is not interactive. However, it can be focused with a keyboard Tab

Only interactive elements should receive keyboard focus. If the panel requires tabindex property for focus managemet purpose, use tabindex="-1" instead. TS012499507

over 1 year ago in Business Automation Workflow 0 Future consideration

1 VOTE

Content overlap and horizontal scrolling is triggered when zoomed up to 200%

Ensure content and functionality is retained when viewed on mobile breakpoint. There should not be content loss, overlap or horizontal scrolling when page is zoomed at 200% TS012511136

over 1 year ago in Business Automation Workflow 0 Future consideration

1 VOTE

The Add button is placed at the start of the form. Users have to tab backwards to trigger the button when they complete entering the data

Place the button after the form TS012511147

over 1 year ago in Business Automation Workflow 1 Functionality already exists

1 VOTE

The "Advanced search" heading is not coded with a heading

Code the main heading of a modal dialog using h2 TS012511154

over 1 year ago in Business Automation Workflow 0 Future consideration

1 VOTE

Dropdown form controls such as "Case type", "Match criteria" etc are not programatically associated to the input in focus. When focusing on the component using JAWS screen reader, the label is not announced

Ensure the element on focus is programatically associated using aria-labelledby property. TS012511161

over 1 year ago in Business Automation Workflow 0 Future consideration

1 VOTE

The X button on the top right is focusable to keyboard. However, the element does not has an accessible role such as button

The X button on the top right is focusable to keyboard. However, the element does not has an accessible role such as button Code the element using button or link element. Alternaitvely, provide role="button" or role="link" PMR: TS012511121

over 1 year ago in Business Automation Workflow 0 Future consideration

1 VOTE

The filter button can be activated and a popup is visible. However, the content of the popup cannot be navigated using a keyboard alone

Ensure users can tab onto the content of the tab naturally. This can be done by programatically directing focus to the popup using .focus() method TS012511164

over 1 year ago in Business Automation Workflow 0 Future consideration

1 VOTE

The Case ID link next to the main heading "Step: Update Case" is a button/link element. However, there is not visual indication indicating the functionality except for using red colour alone

The Case ID link next to the main heading "Step: Update Case" is a button/link element. However, there is not visual indication indicating the functionality except for using red colour alone Provide visual cue such as underline to indicate interac...

over 1 year ago in Business Automation Workflow 1 Future consideration

1 VOTE

does BAW support the VPAT - Voluntary Product Accessibility Template

does BAW support the VPAT - Voluntary Product Accessibility Template TS012639264

over 1 year ago in Business Automation Workflow 1 Functionality already exists

1 VOTE

Heading text such as "Step: Updates Case" is not coded as heading

Code should using heading level 1 TS012511092

over 1 year ago in Business Automation Workflow 0 Future consideration

Shape the future of IBM!

Search existing ideas

Post your ideas

Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):

Specific links you will want to bookmark for future use

Pinned ideas

All ideas

The item display panel on the right is not interactive. However, it can be focused with a keyboard Tab

Content overlap and horizontal scrolling is triggered when zoomed up to 200%

The Add button is placed at the start of the form. Users have to tab backwards to trigger the button when they complete entering the data

The "Advanced search" heading is not coded with a heading

Dropdown form controls such as "Case type", "Match criteria" etc are not programatically associated to the input in focus. When focusing on the component using JAWS screen reader, the label is not announced

The X button on the top right is focusable to keyboard. However, the element does not has an accessible role such as button

The filter button can be activated and a popup is visible. However, the content of the popup cannot be navigated using a keyboard alone

The Case ID link next to the main heading "Step: Update Case" is a button/link element. However, there is not visual indication indicating the functionality except for using red colour alone

does BAW support the VPAT - Voluntary Product Accessibility Template

Heading text such as "Step: Updates Case" is not coded as heading

Please enter your email address

FILTER BY CATEGORY