- From: Bryan Garaventa <bryan.garaventa@levelaccess.com>
- Date: Thu, 16 May 2019 23:17:40 +0000
- To: David MacDonald <david100@sympatico.ca>
- CC: "public-aria@w3.org" <public-aria@w3.org>
- Message-ID: <BYAPR03MB48051C5F075D062859053A0DF20A0@BYAPR03MB4805.namprd03.prod.outlook.com>
No problem, I’ve made the pull request https://github.com/kenwheeler/slick/pull/3773 Unfortunately I expect the same. This is one of the main reasons why I hardly ever contribute to public open source projects, because I detest wasting my time when my work is usually automatically dismissed. In this case though, I needed to fix this for a client anyway, so I decided to share it with those who might find it helpful. I agree it would be good if it were encorporated with the master branch, and the test results by comparing the index.html of the primary project with the one I have hosted in this repo plainly show that the unmodified one has critical accessibility issues for screen reader users if left unaddressed. Bryan Garaventa Principal Accessibility Architect Level Access, Inc. Bryan.Garaventa@LevelAccess.com 415.624.2709 (o) www.LevelAccess.com<http://www.levelaccess.com/> From: David MacDonald <david100@sympatico.ca> Sent: Thursday, May 16, 2019 8:23 AM To: Bryan Garaventa <bryan.garaventa@levelaccess.com> Cc: public-aria@w3.org Subject: Re: Accessible carousels in public Slick.js archive CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. AMAZING!!!! Thanks.... Brian.... you are making the world a better place... This is going to reduce accessibility costs all over the world. I hope the owner accepts the pull requests... apparently he has not be that open to accessibility help previously, even from seasoned professionals, it appears he's always asserted that it is accessible. Cheers, David MacDonald CanAdapt Solutions Inc. Tel: 613-806-9005 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd<http://twitter.com/davidmacd> GitHub<https://github.com/DavidMacDonald> www.Can-Adapt.com<http://www.can-adapt.com/> Adapting the web to all users Including those with disabilities If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html> On Wed, May 15, 2019 at 7:58 PM Bryan Garaventa <bryan.garaventa@levelaccess.com<mailto:bryan.garaventa@levelaccess.com>> wrote: Hi, In case it's of interest, I forked a copy of Slick.js, which is a common carousel that is used by thousands across the web, but has critical accessibility issues. So I fixed all of them. This uses all of the expected behaviors we've been discussing in the APG for the carousel design pattern. You are welcome to try this out at https://github.com/accdc/slick (This also works accessibly when auto-rotation is enabled via autoplay: true.) Note I only fixed the carousel issues, not all of the unnamed images within index.html, so presumably people will actually make sure their content is accessible when they implement this within their own projects. However, I am not holding out for common sense to prevail at this point. I'll make a pull request for the project owner once I finish some final testing, but here it is in case it's of help to anyone. All the best, Bryan Bryan Garaventa Principal Accessibility Architect Level Access, Inc. Bryan.Garaventa@LevelAccess.com<mailto:Bryan.Garaventa@LevelAccess.com> 415.624.2709 (o) www.LevelAccess.com<http://www.LevelAccess.com>
Received on Thursday, 16 May 2019 23:18:07 UTC