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

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

From: Sean Murphy (seanmmur) <seanmmur@cisco.com>
Date: Mon, 11 Jul 2016 01:37:55 +0000
To: Thad C <inclusivethinking@gmail.com>
CC: "<w3c-wai-ig@w3.org>" <w3c-wai-ig@w3.org>, Mark Weiler <mweiler@alumni.sfu.ca>, "SALES, TERRY LYNN" <TERRYLYNN.SALES@cbp.dhs.gov>, Mitchell Evan <mtchllvn@gmail.com>
Message-ID: <5d0c5495b6ae48e9b46cac7fd20d2d47@XCH-RCD-001.cisco.com>
Fully agree. Just highlighting the cracks that exists.

From: Thad C [mailto:inclusivethinking@gmail.com]
Sent: Monday, 11 July 2016 11:16 AM
To: Sean Murphy (seanmmur) <seanmmur@cisco.com>
Cc: <w3c-wai-ig@w3.org> <w3c-wai-ig@w3.org>; Mark Weiler <mweiler@alumni.sfu.ca>; SALES, TERRY LYNN <TERRYLYNN.SALES@cbp.dhs.gov>; Mitchell Evan <mtchllvn@gmail.com>
Subject: RE: Strategies sighted web developers have come up with...

The issue of code reuse that someone may not fully understand is not specific to accessibility but is an issue for computer engineering in general.

The best way to mitigate this is to provide open, inclusive communities like this one, where developers of all levels are not afraid to ask questions and can receive thoughtful and supportive advice when needed from the community.

On Jul 10, 2016 6:04 PM, "Sean Murphy (seanmmur)" <seanmmur@cisco.com<mailto:seanmmur@cisco.com>> wrote:
One issue with re-code usage is people just cut and copying without understanding the code itself. Attended a meeting on web accessibility within Australia and the example given was a developer having no clue about ARIA and just re-using thinking it will fulfil the WCAG requirements when it didn’t.

So a spin off from the re-use is how many developers out there really understand the code they are using?

The challenge of course is the unrealistic time  pressures design teams as a whole are placed under. They will use shortcuts to achieve the end result. The shorter time lines developers are given is going to eventually break from my point of view.


Sean Murphy
Tel: +61 2 8446 7751<tel:%2B61%202%208446%207751>

Cisco Systems, Inc.
The Forum 201 Pacific Highway

[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<http://www.cisco.com/web/about/doing_business/legal/cri/index.html> for Company Registration Information.

From: Mitchell Evan [mailto:mtchllvn@gmail.com<mailto:mtchllvn@gmail.com>]
Sent: Friday, 8 July 2016 5:26 PM
To: SALES, TERRY LYNN <TERRYLYNN.SALES@cbp.dhs.gov<mailto:TERRYLYNN.SALES@cbp.dhs.gov>>; Mark Weiler <mweiler@alumni.sfu.ca<mailto:mweiler@alumni.sfu.ca>>; WAI Interest Group <w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>>
Subject: Re: Strategies sighted web developers have come up with...

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.



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<mailto:TERRYLYNN.SALES@cbp.dhs.gov>> wrote:
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<tel:%2B1%20%28510%29%20375-6104>

(image/jpeg attachment: image001.jpg)

(image/png attachment: image002.png)

Received on Monday, 11 July 2016 01:38:27 UTC

This archive was generated by hypermail 2.3.1 : Monday, 11 July 2016 01:38:27 UTC