Problem : Keyboard option is available in all portals that use section pyTableToolbar.

The understanding is that this has been added as inline with the Pega's commitment towards Accessibility. But when the end users doesn't want this to be displayed , customization is needed to add visibillity condition on this field in the section.

Probale Solution : Instead of customizing this in every application where this is not needed, a Visibility condition can be added with Dynamic System settings, so that it would be much simpler in terms of implementation.

***Edited by Moderator Marije to add current functionality ***

Details below for the keyboard option in table.

• The "keyboard instructions" are added to provide assistance to the Keyboard users.
• This change is inline with the Pega's commitment towards Accessibility. Refer below.
• https://www.pega.com/accessibility
• The details are also mentioned under Pega's documentation for accessibility in tables
• https://docs.pega.com/bundle/platform/page/platform/user-experience/accessible-navigation-tables.html

*** *** *** ****** ****** ****** ****** ****** ****** ****** ***