WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Improving Bootstrap’s woeful accessibi lity Daniel Nixon

for

From: Thomas McKeithan II
Date: Oct 18, 2014 5:45AM

I agree with you Deborah.

Have an awesome day.

Respectfully,
Thomas Lee McKeithan II
QSSI
http://www.qssinc.com
508 SME, SSQA Solutions Center
10480 Little Patuxent Pkwy , Suite 350
Columbia , MD 21044
(301 )977-7884 x1058 (Work)
(202) 276-6437 (Cell)
 

This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify the sender by reply email and delete the original message (including any attachments) in its entirety.



-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of <EMAIL REMOVED>
Sent: Friday, October 17, 2014 3:28 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Improving Bootstrap’s woeful accessibi lity Daniel Nixon

I'd like to add to this a general practice from the open source community where I help run the Accessibility Team: all of those different skills people bring to the table are hugely important.

For example, if you have a bug report, then verifying it is still a bug in the most recent version of the code, and writing up a good, specific bug report can be very helpful -- and if it's too much overhead to figure out how to add that to a bug tracker, then write to somebody directly. Creating documentation is hugely valuable. Heck, you know what every single open source community doesn't have enough of? Testers with disabilities, so that we can put out calls saying "this works for me with NVDA but I hear mixed reports with JAWS 11-- I need a tester with that software."
(Because remember, most open source projects cannot buy licenses of expensive software for testing.)

Reporting bugs, writing documentation, helping prioritize accessibility bugs, QA, explaining accessibility use cases:
these are also all very valuable skills and tasks. Not all open source community value these out of the gate -- some open source communities have an unfortunate tendency to value contributions by "number of lines of code submitted" -- but all open source projects SHOULD value these things, and probably most can be shown how important they are.

-Deborah Kaplan

On Fri, 17 Oct 2014, Jennifer Sutton wrote:
> I will conclude, though, by adding that while I'm in 100%+ agreement
> with the "passion requires pull requests" campaign, not everyone here
> has the time to contribute to open source communities/projects, is
> subsidized (and perhaps even encouraged) by their employer(s) to do
> so, has the accessibility knowledge to know how to make informed and
> accurate changes, and/or has the programming skills that making pull requests requires.
>
> We each have different skills to bring to the table, and I hope mine
> are mostly about sharing timely and accurate information to enable
> others to work for integrated and substantive change.