Replies posted by rschlette
Following up here, manually adding <h2> elements in the source code for tooltips and saving as a template, allows the customer to use this going forward on any new guides. However, a new template won’t help with any previously created guides with multiple steps and localizations these would all need to be recreated.from the Customer:“The easiest workaround would be for Gainsight to add this to any Divs used as the title for tooltips, guides, dialogs: role="heading" aria-level="2"This keeps all the CSS intact and doesn’t shift things around like adding an H2 tag, but it does give screen readers the information to treat these elements as headings. This could also be applied to all the legacy tooltips/dialogs and localized versions without causing any effort to update CSS.<div role="heading" aria-level="2" class="px-dialog-title" >Accessible Titles!</div>”
additional customer feedback:“In my opinion, this is critical for the appropriate use of the Recommendation tab in KB. Because we have many different sets of roles and it's impossible to create a meaningful recommendation without the ability to configure AND/OR operators”
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.