search

haltersweb / Accessibility

Accessible solutions to web widgets and applications
http://haltersweb.github.io/Accessibility/
MIT License
125 stars 28 forks source link

Any info on how these components are tested? #20

Closed NateWr closed 7 years ago

NateWr commented 7 years ago

I'm really liking your autocomplete solution. I'm wondering if you have any information about how these components are tested, what problems might exist with certain screen-readers, etc.

Thanks! :+1:

haltersweb commented 7 years ago

Thanks Nate!

Depending on the pattern I will test on all desktop and mobile devices or just desktop or just mobile.

On desktop I usually test FF/NVDA and IE/JAWS. I also test keyboard only.

On mobile I usually test iOS/VO and iOS with switch device.

I will often have someone else test in Android.

I also will post a pattern I'm working on onto the International Association of Accessibility Professionals forum and have them bang on it.

If I find issues with certain screen readers I often note them on the example page.

You will also notice that some of the solutions are works in progress. I will usually comment in the JS or in the HTML things I still want to do.

One of the things I want to explore with autocomplete is allow mobile to use the OS default dropdown by doing a feature detection. Of course I don't know when that will actually happen :-P

Let me know if you have any other questions.

Adina

NateWr commented 7 years ago

Thanks!