@DAVIDLEY

If you’re seeing that buttons are being skipped, it might be possible that a custom Pega configuration or a script is being used to control focus prioritizes certain elements over others. We would need more details or the exact scenario to figure it out.

@DAVIDLEY

There was a recent change in Platform version '24.1 that updated the initial focus behavior logic on page load to include button elements. In previous versions it is as you described, including just input fields and links.

@DAVIDLEY In Pega, the "first interactive element" for initial focus refers to elements users can interact with, like text inputs, links, and buttons. However, by default, Pega prioritizes text inputs and links over buttons for initial focus. This behavior is influenced by both Pega's internal logic and browser standards. Browsers typically consider inputs, links, buttons, and elements with a tabindex attribute as focusable, but Pega may deprioritize buttons because they are often seen as action triggers rather than primary interaction points. To ensure a specific element, such as a button, receives focus, you can explicitly set focus in Pega using the Set Focus action in the Actions tab of the element. Additionally, you can use the tabindex attribute to control the order of focusable elements on the page. For consistent results, it's a good idea to test the focus behavior across different browsers and adjust the configuration as needed. By taking these steps, you can control the initial focus behavior and meet your specific requirements. Thanks