E-mail List Archives
Re: accessibility and bespoke systems
From: Joe Chidzik
Date: Sep 18, 2014 2:26AM
- Next message: Sailesh Panchang: "Re: Links as headings"
- Previous message: Ghita Jones: "Keyboard equiv for resizing panes"
- Next message in Thread: Julius Charles Serrano: "Re: accessibility and bespoke systems"
- Previous message in Thread: Ryan E. Benson: "Re: accessibility and bespoke systems"
- View all messages in this Thread
Even if using a bespoke system, you should wherever possible opt to use existing HTML components (links, buttons, lists, select elements etc) rather than unnecessarily creating custom UI components that do the same thing. Native HTML elements have accessibility baked in, and in creating custom UI elements this is something that needs to be done manually, adding development overheads and increasing the chance of errors or accessibility concerns creeping in.
Whilst ARIA is great for adding accessibility support for custom elements, it should only be used if existing elements are not fit for purpose.
Using established libraries such as Bootstrap, or JQuery (Or many others) that have good accessibility support built in can help reduce development time rather than coding bespoke elements from scratch (again, use existing appropriate elements where possible).
Joe
>
- Next message: Sailesh Panchang: "Re: Links as headings"
- Previous message: Ghita Jones: "Keyboard equiv for resizing panes"
- Next message in Thread: Julius Charles Serrano: "Re: accessibility and bespoke systems"
- Previous message in Thread: Ryan E. Benson: "Re: accessibility and bespoke systems"
- View all messages in this Thread