WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: status of Twitter Bootstrap and accessibility

for

From: Maraikayar Prem Nawaz
Date: Jun 13, 2013 8:27AM

Hi Len,
You are correct. Bootstrap has many accessibility issues like color
contrast, Aria, Keyboard Accessibility, etc. When i last checked with
them they were busy with their BootStrap 3.0 release.

Again what is that you are going to use the BootStrap for? If it is for
layouts etc, then use it.
If it is for JavaScript components like tooltip, dropdown, modal dialog
etc., i would recommend to use Jquery or YUI as many of these accessibility
issues have been identified and fixed.

But if you still want to use it for javascript
components<http://twitter.github.io/bootstrap/javascript.html>; you
can see my code changes and apply on top of your code.


Best Wishes
-Nawaz



On Thu, Jun 13, 2013 at 3:44 AM, Greg Gamble < <EMAIL REMOVED> > wrote:

> Twitter Bootstrap does use Aria tags. It's the custom code you add to it
> that needs to be fixed. Bootstrap in of itself is pretty good from my
> testing. They just have different ideas on how things should work, and
> considering the people who are driving it, are doing a good job with it too.
>
> Alerts are one area where they do things differently. They're developing
> it with a stoplight theme/view, where the color is the information part and
> the text is the fluff. Thats the reason they, the alerts, fail a contrast
> test.
>
> Another issue that people complain about is the size of the code base. If
> you take only what your going to use, it's actually a descent size.
>
> Greg
>
> -----Original Message-----
> From: <EMAIL REMOVED> [mailto:
> <EMAIL REMOVED> ] On Behalf Of Len Burns
> Sent: Wednesday, June 12, 2013 1:52 PM
> To: 'WebAIM Discussion List'
> Subject: Re: [WebAIM] status of Twitter Bootstrap and accessibility
>
> Nawaz and all,
>
> I am revisiting this thread because an existing client is planning a major
> project based on Twitter Bootstrap. In my follow up research to this
> thread, what I am finding is that a number of people have created example
> code incorporating ARIA into Twitter Bootstrap, but thus far this work has
> not been pulled into the main code base. This means that each project
> using
> this code must roll its own. Am I correct, or am I missing information?
> Thanks so very much for your wisdom.
>
> Regards,
> -Len
>
>
> -----Original Message-----
> From: <EMAIL REMOVED>
> [mailto: <EMAIL REMOVED> ] On Behalf Of Maraikayar Prem
> Nawaz
> Sent: Thursday, May 09, 2013 9:31 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] status of Twitter Bootstrap and accessibility
>
> Hi Jennifer,
> I did some work on it and submitted some pull requests too. But they are
> busy with Version 3.
> Here is my repo: https://github.com/mpnkhan/BootStrapExamples
> And examples :
> http://mpnkhan.github.io/BootStrapExamples/a11yfixes/bs.html
>
>
> Thanks
> -Nawaz
>
>
> On Wed, May 8, 2013 at 7:45 PM, Greg Gamble < <EMAIL REMOVED> > wrote:
>
> > The only issues I'm aware of are the colors for the alert classes, but
> > that is intentional. They're looking at a stop light style of look and
> feel
> > so the text shouldn't really be necessary when using them. Version 2.3.1
> > is current with Version 3.0 on the horizon. I really enjoy working with
> it
> > and the capabilities are amazing.
> >
> > Greg Gamble
> > SBCTC - Olympia | Information Services
> >
> > -----Original Message-----
> > From: <EMAIL REMOVED> [mailto:
> > <EMAIL REMOVED> ] On Behalf Of Jennifer Sutton
> > Sent: Tuesday, May 07, 2013 4:21 PM
> > To: WebAIM Discussion List
> > Subject: [WebAIM] status of Twitter Bootstrap and accessibility
> >
> > Greetings, WebAIM:
> >
> > I'm beginning to research where things currently stand with Twitter
> > Bootstrap and accessibility.
> >
> > I reviewed the WebAIM archives, but I suspect that, at least based on
> > the main Twitter Web site, there may have been some improvement since
> then.
> >
> > Has anyone looked into this recently?
> >
> > And/or, has anyone worked on a fork (or found one) that incorporates
> > more accessibility features/functionality?
> >
> > I glanced at the issues, but most look closed. And I found myself
> > wondering whether there might be other issues that haven't been filed.
> >
> > I started to take a further look around Github, and I saw a number of
> > forks, but I thought there might be folks on this list who would be
> > able to speed my research.
> >
> > Thanks in advance.
> >
> > Best,
> > Jennifer
> >
> > > > > > > >
> >
> > > > > > > >
> > > >
> > > >
>
> > > >