WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: accessibility and bespoke systems

for

From: Joe Chidzik
Date: Sep 18, 2014 2:26AM

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

> -----Original Message-----
> From: <EMAIL REMOVED> [mailto:webaim-forum-
> <EMAIL REMOVED> ] On Behalf Of Julius Charles Serrano
> Sent: 17 September 2014 22:11
> To: WebAIM Discussion List
> Subject: [WebAIM] accessibility and bespoke systems
>
> Hello, everyone.
>
> I just want to get your thoughts on specific ways to implement accessibility in
> bespoke websites ( i.e. one that is custom-built, often from scratch, to suit the
> needs of a business or organization)
>
> What are the pieces of advice we could give to companies opting specifically for
> bespoke websites?
>
> I would greatly appreciate any information or comments on this.
>
> Thanks.
>
> Julius
>
>
>
>
>
> --
> Julius Charles Serrano
> Accessibility Tester
> Catalyst IT
> http://www.catalyst.net.nz
> Mail: <EMAIL REMOVED>
> Phone: +64 (4) 803-2436
>
> > > to <EMAIL REMOVED>