Here are some articles that discuss the use of Userway for accessibility on websites and the potential legal issues that are happening to people that are.
Article:
- https://accessibe.com/blog/...
- Article with Userway's free widget: https://accessibe.com/blog/knowledgebase/using-an-accessibility-plugin-like-userway-you-are-at-risk-of-litigation
- Article with USerway's AI: https://accessibe.com/blog/knowledgebase/userway-ai-widget-can-risk-your-accessibility-compliance
Highlights:
- "UserWay's main website, which obviously uses the full "AI'' plugin and not the free version, has also been manually adjusted to incorporate accessibility features, more specifically on top of the "AI'' widget. Unfortunately, we found dozens of accessibility violations after running the audits. Some can be summed up as just bad practices and incorrect implementations." - https://accessibe.com/blog/knowledgebase/userway-ai-widget-can-risk-your-accessibility-compliance
- "Many plugins are very tempting to use because they are free or very low cost and are simple to install. Also, it is easy to mistake them for a real solution, as their websites are often misleading, claiming to “enhance” accessibility and provide a “framework” for compliance. The problem is, well, they never did and probably never will be able to make your website compliant. Note that they also never vividly state that they will." - https://accessibe.com/blog/knowledgebase/using-an-accessibility-plugin-like-userway-you-are-at-risk-of-litigation
My Thoughts:
- Overall, web accessibility plugins don't/can't make your website 100% compliant, there are a lot of factors that come into consideration and a plugin is not the entire solution. It covers most of the dev portion, but there are still other elements that need to be addressed. (Design elements, keyboard navigations, etc...)
- There are rules and regulations that need to be followed in order to make a website compliant, and that's through WCAG (https://www.w3.org/TR/WCAG21/). These guidelines are internationally accepted and are adopted by almost all current legislation, including those in US courts.
- The vast majority of the accessibility requirements, screen reader and keyboard navigation adjustments are just way too complex for a plugin to cover.
AccesiBe provided a list of requirements that can help with keyboard navigation below: **( This can be used as a checklist for all our websites)**
# | Requirement | Category | Covered? |
1 | The keyboard focus moves to within a popup right when it appears | Keyboard Navigation | Yes/No |
2 | Popups and dropdowns can be closed using the Esc key | Keyboard Navigation | Yes/No |
3 | The keyboard focus loop within a popup or a dropdown and doesn’t let it escape | Keyboard Navigation | Yes/No |
4 | Failed form submissions move the keyboard focus directly to the error. | Keyboard Navigation | Yes/No |
5 | Quick navigation/skip links are provided to help users skip blocks, sections, and pages. For example, to quickly focus on the navigation, the footer, or the main content of the website | Keyboard Navigation | Yes/No |
6 | Popups are being described to screen-readers using aria-modal=true and role=dialog | Screen-reader | Yes/No |
7 | All menus are tagged for screen-readers using role=navigation or the nav tag, and dropdowns are tagged for screen-readers using aria-haspopup=true, and their dynamic state is announced using aria-expanded=true/false | Screen-reader | Yes/No |
8 | Deleted prices, bold and emphasized texts that are visually decorated using CSS are tagged appropriately to screen-readers | Screen-reader | Yes/No |
9 | Images receive Alt attributes describing both the objects and the text that is embedded within them | Screen-reader | Yes/No |
10 | All form fields receive a proper field description using a connected label or an aria-label | Screen-reader | Yes/No |