What are some strategies for modifying or overriding inaccessible third-party components without breaking their functionality?
Question
Answer
This is often a tricky scenario depending on the level of customization the third-party code offers. We usually recommend using ARIA markup when working with custom widgets. Let's say the third party created a button instead of using a button tag. In this example, adding the recommended ARIA to ensure it has its accessible name, states, properties, and roles properly communicated is the best way to go. Editing this is less likely to break any functionality because instead of removing anything, you added labels to make it accessible.
Free Tools to Continue Learning
Accessible Web RAMP
Monitor your website and manage your progress towards WCAG conformance.
Accessible Web Academy
Career specific courses to help power up your accessibility knowledge.