W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2012

Accessible bootstrapping is now available using semantic HTML markup.

From: Bryan Garaventa <bryan.garaventa@whatsock.com>
Date: Sun, 25 Nov 2012 00:26:17 -0800
Message-ID: <2E0F59A6647040D8AAE98C54F4E68024@WAMPAS>
To: "WebAIM Discussion List" <webaim-forum@list.webaim.org>, <free-aria@googlegroups.com>, <w3c-wai-ig@w3.org>, <accessible@googlegroups.com>
Hello, please forgive the cross-posting, this actually is quite important. I'll be brief.

If you don't know what bootstrapping is, I'm referring to the use of semantic HTML markup to configure advanced controls, which are then magically converted into dynamic interactive components when the content finishes loading.  

Twitter Bootstrap is the most well-known CMS that does this.

The problem with the vast majority of interactive components used by Twitter Bootstrap and others, is that they are not specifically designed to be accessible from the start. The result is a negative impact across millions of pages across the web, as inaccessible components are repeatedly shared and incorporated into new projects daily.
E.G http://ux.joomla.org/forum/Accessibility/435-Bootstrap-and-Accessibility
or you can simply google "bootstrap accessibility" to find more examples. Though some work is being done in this regard, the majority of complex components are not accessible by WCAG2.0 or Section-508 standards as a result of this.

So, I built AccDC Bootstrap to solve this problem, which is now available at

AccDC Bootstrap is designed to automatically enforce accessibility, while making it possible to populate individual components with any type of content, in any language, using any visual styling.

Recently, Google's Vice President Vinton G. Cerf asked "Why Is Accessibility So Hard?"

Personally, I don't believe it has to be.

Bryan Garaventa
Received on Sunday, 25 November 2012 08:26:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:46 UTC