WebAIM - Web Accessibility In Mind

E-mail List Archives

Using github for sharing accessibility techniques

for

From: Julie Lewis
Date: Nov 30, 2015 2:07PM

With all due respect Cliff, why does it matter who hosts it?

All developers should be treating accessibility the same way they treat
performance and device independence. Why create a silo for it?

Github allows for everything you describe below. Start-up cost is minimal.
And most importantly, developers already go there to discuss and share
technical problems and solutions. As a matter of fact it's already there:

https://github.com/w3c/wcag/


If the problems are being solved, then compliance and conformance to
standards are less of an issue.

The open source community has pushed web technology farther and faster
than any government entity or standards body ever will.

>
>From: Cliff Tyllick < <EMAIL REMOVED> >
>
>
>Julie, it would have to be hosted by an entity that nations, their
>courts, and corporations would recognize as being authoritative.
>Otherwise, it's just some group's notion of best practices―not a resource
>for ensuring compliance with laws or conformance to standards.
>
>So who hosts it is far more important than how it's hosted.
>
>Cliff Tyllick
>
>
>> On Nov 30, 2015, at 9:07 AM, Julie Lewis < <EMAIL REMOVED> >
>>wrote:
>>
>> Is there any reason the accessibility community can¹t use github for
>>this?
>> We could even maintain a plain language version of the WCAG
>> recommendations there. ;^)
>>
>>>
>>> 2. The accessibility community should build and maintain an
>>> application any Web professional can use to discover known
>>> techniques for producing usable and accessible interactions in
>>> the presentation technology they are using. The same application
>>> would allow developers to submit new techniques they have used to
>>> solve a previously unsolved problem or to improve upon an
>>> existing solution. Each technique submitted should be specific;
>>> include appropriate examples of its implementation; be tagged
>>> according to the interface or interaction (form, text input,
>>> error checking, labels for fieldsets, navigation menus, and so
>>> on), the presentation technology (HTML, PDF, XHTML, Word for
>>> Windows, Open Office, Drupal, WordPress, Plone, Bootstrap.js, and
>>> so on), the presentation environments in which it works (video,
>>> audio, wearables, smart phones, large monitors, haptic
>>> interfaces, and others), the disability addressed, the relevant
>>> WCAG success criteria, and other relevant features if I've missed
>>> any; and be linked to closely related solutions, relevant
>>> tutorials, explanations of the underlying principles, and the
>>> like.
>>
>>