While I agree these issues should be addressed by Browser/AT vendors, there should also be a way to make this accessible today. Joanie is the only person I know that works on AT, so I’ve included her in the conversation. @Joanie: could you have a look at these accessibility tests <https://github.com/MichielBijl/font-awesome> and this issue raised by Dylan at Font Awesome <https://github.com/FortAwesome/Font-Awesome/issues/6133>. Maybe you can tell us how AT can help with this issue. —Michiel > On 01 Dec 2015, at 07:45, Phill Jenkins <pjenkins@us.ibm.com> wrote: > > I understand the immediate "almost certain need for workarounds" for screen readers and magnifiers, but has anyone queried the developers of the ATs? > What say ye: > 1. Freedom Scientific regarding JAWS and MAGic? > 2. NVDA? > 3. A I Squared Zoom Text with Speech? > 4. Microsoft Window-Eyes and other Windows assistive technologies? > 5. Apple VoiceOver and other iOS assistive technologies? > 6. Google Talkback and other Android assistive technologies? > etc.? > > Just like we need status and roadmaps from browser manufactures, this interest group also needs that same feedback and committment from the AT developers too! > > Placing, and expecially placing the burden on the bazillion web developers to constannly develop workarounds and half baked hacks, instead of lobbying and driving the relative small number of AT developers, is an inefficient and loosing battle this group seems to fall into over and over in my opinion. > ____________________________________________ > Regards, > Phill Jenkins,
Received on Tuesday, 1 December 2015 10:23:40 UTC