W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2016

Re: Strategies sighted web developers have come up with...

From: Mitchell Evan <mtchllvn@gmail.com>
Date: Fri, 08 Jul 2016 07:25:37 +0000
Message-ID: <CAK=xW6ssC+ii=-OHffDc4FK39AOEhPchJ9Z4AAfjJEBhZ=AyBw@mail.gmail.com>
To: "SALES, TERRY LYNN" <TERRYLYNN.SALES@cbp.dhs.gov>, Mark Weiler <mweiler@alumni.sfu.ca>, WAI Interest Group <w3c-wai-ig@w3.org>
The most common technique is code reuse. This could mean copying coding
techniques from colleagues or from snippets on the internet, using a
front-end widget library, or using an authoring tool like a CMS.

Look at stats for global usage of JavaScript widget libraries, plus CMSs
like WordPress and Drupal, and you'll get one measure of how widespread
code reuse is.

http <http://trends.builtwith.com/javascript>://

http <http://trends.builtwith.com/cms>:// <http://trends.builtwith.com/cms>
trends.builtwith.com <http://trends.builtwith.com/cms>/
<http://trends.builtwith.com/cms>cms <http://trends.builtwith.com/cms>

Several factors determine the success of code reuse for accessibility. How
suitable is the coding pattern to the current use case? Does the developer
understand how to apply the pattern, e.g. what kind of content is expected
in the widget? Were the accessibility claims of the original developer
accurate? The responsibility to get these questions right is shared between
the original author and the reuser.

Another important strategy is coding to standards.

I'm not saying these strategies are sufficient, only that they are common.

On Thu, Jul 7, 2016, 9:00pm SALES, TERRY LYNN <TERRYLYNN.SALES@cbp.dhs.gov>

> I work for DHS in the USA and we test not for specific tools, but for the
> markup that feeds them. So I put together a training deck for our
> developers that covers the 'most often failed' tests and how to build the
> applications to pass versus testing in compliance.  Sort of a how to for
> the key features our Web pages typically include. Hits probably 75% of the
> issues and has drastically reduced testing finds.
> ------------------------------
> *From:* Mark Weiler
> *Sent:* Thursday, July 07, 2016 10:11:18 PM
> *To:* WAI Interest Group
> *Subject:* Strategies sighted web developers have come up with...
> I'm curious about the range of strategies sighted web developers have come
> up with to verify that what they are creating actually works well with
> assistive technologies.  Developers would use these strategies before
> functional or user testing.
> Examples might include: a) learning to use a range of assistive
> technologies b) using specialized software or plugins to simulate the
> experience of the assitive technology in a visual format (eg. Claws or
> Fangs plugins for Firefox; browser plugins that highlight boundary of ARIA
> landmarks; accessibility tree visualizers, etc. or c) some other techniques
> --

Mitchell Evan
+1 (510) 375-6104
Received on Friday, 8 July 2016 07:26:18 UTC

This archive was generated by hypermail 2.3.1 : Friday, 8 July 2016 07:26:19 UTC