E-mail List Archives
Re: Where does it say to use native HTML features rather than re-create them in ARIA and JS?
From: Bryan Garaventa
Date: Dec 22, 2016 11:02AM
- Next message: Tyllick,Cliff S (HHSC/DADS): "Re: Where does it say to use native HTML features rather than re-create them in ARIA and JS?"
- Previous message: Steve Faulkner: "Re: Where does it say to use native HTML features rather than re-create them in ARIA and JS?"
- Next message in Thread: Tyllick,Cliff S (HHSC/DADS): "Re: Where does it say to use native HTML features rather than re-create them in ARIA and JS?"
- Previous message in Thread: Steve Faulkner: "Re: Where does it say to use native HTML features rather than re-create them in ARIA and JS?"
- View all messages in this Thread
It's also very important not to use conflicting roles on native interactive elements, and preferably, don't use ARIA roles on any native interactive elements.
E.G I've seen recently where role="button" was added to input+type="text" elements, making them totally inaccessible using VoiceOver in iOS, and role="listbox" on native HTML select elements which caused other issues to occur, and others adding roles to select element option elements with the same inaccessible results.
These are all extremely bad practices.
Bryan Garaventa
Accessibility Fellow
SSB BART Group, Inc.
<EMAIL REMOVED>
415.624.2709 (o)
www.SSBBartGroup.com
- Next message: Tyllick,Cliff S (HHSC/DADS): "Re: Where does it say to use native HTML features rather than re-create them in ARIA and JS?"
- Previous message: Steve Faulkner: "Re: Where does it say to use native HTML features rather than re-create them in ARIA and JS?"
- Next message in Thread: Tyllick,Cliff S (HHSC/DADS): "Re: Where does it say to use native HTML features rather than re-create them in ARIA and JS?"
- Previous message in Thread: Steve Faulkner: "Re: Where does it say to use native HTML features rather than re-create them in ARIA and JS?"
- View all messages in this Thread