E-mail List Archives
Thread: accessibility and bespoke systems
Number of posts in this thread: 5 (In chronological order)
From: Julius Charles Serrano
Date: Wed, Sep 17 2014 3:10PM
Subject: accessibility and bespoke systems
No previous message | Next message →
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 ADDRESS REMOVED =
Phone: +64 (4) 803-2436
From: Olaf Drümmer
Date: Wed, Sep 17 2014 3:18PM
Subject: Re: accessibility and bespoke systems
← Previous message | Next message →
I have found the requirement, that a website must be fully operable by keyboard (i.e. without ever using the mouse or a trackpad or gestures etc.) in a modern browser (i.e. without using assistive technology) to work wonders. Especially as it might take a lot of time and energy to make others understand how all this WCAG and related stuff is supposed to work.
Olaf
On 17 Sep 2014, at 23:10, Julius Charles Serrano < = EMAIL ADDRESS REMOVED = > wrote:
> 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 ADDRESS REMOVED =
> Phone: +64 (4) 803-2436
>
> > >
From: Ryan E. Benson
Date: Wed, Sep 17 2014 3:20PM
Subject: Re: accessibility and bespoke systems
← Previous message | Next message →
Is it actually custom or are you buying a COTS product and tweaking. If it
is made by hand there isn't anything special to do. WebAIM, among other
places, has various resources on how to code/check for accessibility. If
you are buying a COTS it really depends on the overall accessibility of the
base system, what you want/need to do, and how much access do you have to
the system. Some products you can easily fix, whereas others, you'd need to
re-engineer the product to make it accessible.
--
Ryan E. Benson
On Wed, Sep 17, 2014 at 5:10 PM, Julius Charles Serrano <
= EMAIL ADDRESS REMOVED = > wrote:
> 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 ADDRESS REMOVED =
> Phone: +64 (4) 803-2436
>
> > > >
From: Joe Chidzik
Date: Thu, Sep 18 2014 2:26AM
Subject: Re: accessibility and bespoke systems
← Previous message | Next message →
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
>
From: Julius Charles Serrano
Date: Thu, Sep 18 2014 7:47PM
Subject: Re: accessibility and bespoke systems
← Previous message | No next message
Thank you all for your comments and opinions.
I appreciate the advice on keyboard accessibility and use of native HTML
components.
By the way, this is for people who opt for an actual custom system.
Thanks again.
Julius