WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Improving Bootstrap’s woeful accessibi lity Daniel Nixon

for

From: Patrick H. Lauke
Date: Oct 17, 2014 1:43PM

On 17/10/2014 20:28, <EMAIL REMOVED> wrote:
> 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.

Of course even just filing bugs or raising issues are important (but
ideally this should be done in the right place - in the case of
Bootstrap, the actual issue tracker on GitHub). However, once filed, a
bug report will linger until somebody else finds the time to read it,
understand it, replicate the problem, and fix it. And it's often
unlikely on big, busy projects that core maintainers will have the
time/head-space to do this...hence, I would suggest a good way forward
for these types of problems would be to file an issue/bug, and then try
to get people with enough actual programming knowledge to take a look at
it and ideally create a fix that's then merge-able by the core
maintainers (which, I won't lie, takes some effort - even for trivial
additions/fixes, it needs to follow contribution rules, code
conventions, have unit tests and so on).

In short: find something that's not quite right in an open-source
product, but don't have the expertise to fix it yourself? File a
bug/issue, then point to it in places where people with that expertise
(and an interest in accessibility) are, like here :)

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke