- From: ALAN SMITH <alands289@gmail.com>
- Date: Wed, 18 Sep 2019 17:41:49 -0400
- To: Michellanne Li <michellanne.li@gmail.com>, WAI IG <w3c-wai-ig@w3.org>
- Message-ID: <5d82a49d.1c69fb81.f08f4.9716@mx.google.com>
Michellanne, I looked and listed to their own site and found these issues. These types of tools make a great case for themselves but often do not make a page WCAG 2.0 compliant. Violations on their own site after a 15 minute glance: 3.2.2 On Input Their own social media links do not announce that they will open in new windows. 4.1.2 Name, Role, Value Their own hamburger menu does not announce the proper state of the button. It announces “open navigation menu” upon Tab focus but it is actually closed. This is announcing what it will do and it opens upon Tab focus which is confusing for non-visual users because they would think to select it to open it but it is already opened upon focus. 2.4.1 Bypass Blocks If the user back tabs with Shift+Tab the menu closes on it own but tabbing forward with display it again and the user cannot skip past the hamburger menu since it opens upon tab focus. They must tab through all the sub-menus before they can proceed through the page. The skip to main content link is in their own tool’s menu and not on the page. 1.3.1 Info and Relationships There are two region landmarks that do not have labels. The many others do. 1.3.1 Info and Relationships On the Contact Us page, the radio buttons do not announce their grouping label of “Do you already have a UserWay widget installed on your site?”. The Yes button announces via an aria-label "Yes, my site has an accessibility statement". The No button announces via an aria-label "No, my site does not have, or I don't know if my site has, an accessibility statement". 1.3.1 Info and Relationships and/or 3.3.2 Labels or Instructions On the Contact Us page, the required fields are not visibly labeled or announced by the screen reader as required. 3.3.2 Labels or Instructions On the Get widget page, the checkbox does not announce its displayed text of “I agree to the UserWay EULA , Terms of Service , Privacy Policy and Cookie Policy”. It announces via an aria-label "Please agree to the UserWay terms and of service and privacy policy" I refused to consider taking the IAAP web accessibility certification for the past 3 years because their site had violations of WCAG 2.0. I would not go with this company for the same reason. Alan Smith From: Michellanne Li Sent: Wednesday, September 18, 2019 3:53 PM To: WAI IG Subject: userway web accessibility widget Hello all, I just came across Userway's web accessibility widget and thought it was an innovative approach to a11y. Has anyone had experience using this widget to help make an experience more accessible? I'd love to hear thoughts on its effectiveness. Thanks! Michellanne Li (512) 718-2207 http://www.michellanne.com
Received on Wednesday, 18 September 2019 21:42:13 UTC