What fresh hell is THIS now? - Patrick Lauke
[cehfisher] nice list @mgifford! i’ll be sharing it with my team :) wondering if there is a list someplace of a11y certifications too?
p.s. we could discuss the pros/cons to certifications to no end, but the clients i work with (who typically know nothing about accessibility) like to see them. shows some sort of quantifiable measure of a11y knowledge
[scottohara] hi @ilwcss what browser combination are you using?
just tested in safari and firefox w/voice over and it announced “[current value] what’s your favorite fruit, popup button”
[karlgroves] A long time ago I used to work at a Harley dealership. The service department had two techs next to each other who used to argue all the time - one was a young guy named Rob who thought he was the coolest guy on earth. He had to have all the latest shiny tools and things. The guy in the next bay - who he’d always argue with - was a guy we affectionately called “Old Man Brian”. Old Man Brian was a member of the Boozefighters motorcycle club. Boozefighters, BTW, was the group portrayed in the old movie The Wild One. (For the record, Boozefighters by this point were all old men who didn’t fight much anymore and didn’t drink much booze)
Anyway, Old Man Brian used to ride Rob pretty hard, as men do sometimes, and used to say “it is a poor mechanic who blames his tools”.
And in my long rambling way, what I’m saying is a good developer can get the job done with either framework. Personally, I hate anything Angular-based so I’d steer away from Ionic. I can bet $10 that @marcysutton would disagree.
[karlgroves] > I actually don’t have a preference as they’re all tools for getting the job done. Shrug
I meant more in terms of my aversion to Angular. ;)
[karlgroves] @starla175 Oh, so thats what you meant by Native.
IMO, I’d always opt for using the platform objects. That said, I don’t have any data to suggest doing otherwise is bad. The thing is, the native UI objects should have everything needed for accessibility. If the hybrid framework doesn’t do what’s necessary to create those objects accessibly, things go south
[scottohara] i got some major push back from a dev partner of ours, when i was telling them “you really don’t need role=“form” on your <form>”
not sure if they were using ng-aria or what, but they were adamant that “this is what angular recommends, so we don’t think we should remove it”
just let that one go…
:focus-ring
pseudo-class that would let you handle it in CSS, but I don't think it's implemented anywhere yet: https://drafts.csswg.org/selectors-4/#the-focusring-pseudo
prefers-reduced-motion
perhaps? https://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure-does-not-violate.html