E-mail List Archives
Re: Reclaiming ADA court costs from developers
From: Brandon Keith Biggs
Date: Jul 30, 2018 1:11PM
- Next message: John Foliot: "Re: (Title element) WAS WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: Wilson, Jordan: "Re: Reclaiming ADA court costs from developers"
- Next message in Thread: None
- Previous message in Thread: Wilson, Jordan: "Re: Reclaiming ADA court costs from developers"
- View all messages in this Thread
As a customer I am asking for WCAG compliance rating when I look to buy new
systems and 95% of the time I hear: "What's WCAG, I've never heard of it in
30 years of sales". This is a plague and I can't buy most of the systems
out there because as a blind systems acquisition person, I can't evaluate
something I can't use. It is also not legal for us to buy a system I can't
use.
Most of the time companies just say they will add in accessibility later,
but they don't give a date and don't want to work with me to add
accessibility.
This is the wrong approach. You can't just "add" accessibility. You need to
design your product or service to the widest number of users possible, then
you may consider your product usable by a specific group of users.
It's really the company's fault for not getting UX testers for all the
possible users they wanted to serve, or evaluating the product from the
developer for different features that need to be included.
It's also the tools the developer is using. If they use most widget
frameworks from React, for example, Screen reader users won't be able to
use them. There is no way for the developer to know this without testing
them self.
Everyone just needs to start using AccDC and 95% of our problems about
screen reader access will be gone.
Thanks,
Brandon Keith Biggs <http://brandonkeithbiggs.com/>
On Mon, Jul 30, 2018 at 11:01 AM, Wilson, Jordan via WebAIM-Forum <
<EMAIL REMOVED> > wrote:
> This is a very slippery slope - I've seen vendors who do go out of their
> way to include accessibility (and accessibility costs) into RFPs have to
> back out of it because adding A11y costs into a project when their
> competitors do not prices them out of the RFP.
>
> I spoke about this at Accessing Higher Ground last year because its
> becoming a big problem - I recommend that agencies include accessibility as
> a line item in their RFP responses for this reason. Don't include it in the
> core prices so that your client can see that its in there and can
> differentiate your response from others.
>
> Ideally everyone includes a11y, but we're not there yet.
>
> I'd love to see a panel on this at CSUN in the future - many of us work
> with 3rd party design agencies and there's fear of liability there.
>
> Jordan
>
>
- Next message: John Foliot: "Re: (Title element) WAS WCAG 2.1 - 1.3.5 - How to capture a violation?"
- Previous message: Wilson, Jordan: "Re: Reclaiming ADA court costs from developers"
- Next message in Thread: None
- Previous message in Thread: Wilson, Jordan: "Re: Reclaiming ADA court costs from developers"
- View all messages in this Thread