Hey @ItsLarry
My approach to addressing accessibility issues in the past has been to follow these steps: 1) Identify if the configuration you want to make is possible, 2) if possible, see if the configuration would introduce customization that would force us to review at next upgrade and then 3) if it would create a conflict during the next upgrade, then I would open a case in HI to have them confirm this is an accessibility issue and provide the recommendation or targeted fix version. Since these types of issues often have a lot of sensitivity around them, I often try and have ServiceNow as the vendor be the one to hold responsible for fixing these things.
All of these things considered - if your organization just wants to fix it and move on, you should be able to clone that widget on the Topic page and then swap it out as such on the same page. Just keep in mind this will become customization that you have to review and test each upgrade.
These also may be helpful if you are working through accessibility:
- ServiceNow Accessibility Conformance Reports (ACR): https://docs.servicenow.com/bundle/accessibility/page/administer/accessibility-508-compliance/concep...
- ServiceNow Accessibility Roadmap: https://www.servicenow.com/accessibility-statement.html
Hope this helps!
~Nick
