Dear Chad and Michael:
I agree and disagree with Michael. Yes, include aria data directly in the
DOM as needed and consider whether components are necessary. But including
the arias in the HTML alone does not account for any interactive elements
where the page updates. The accessibility plugin is supposed to help add
those dynamic changes to the aria values (e.g. aria-hidden) so JAWS and
other users know when a part of the page updates. This is based on my
amateur level of understanding, though, so please correct me if I am wrong.
That said, I had attempted to use it but could not get it to integrate
properly (our JS is a bit of a spaghetti bowl at the moment). I am looking
forward to additional responses to this question.
In peace,
Amy M. Drayer, MLIS
Senior IT Specialist, Web Developer
[log in to unmask]
http://www.puzumaki.com
On Tue, Dec 9, 2014 at 9:43 AM, Michael Schofield <[log in to unmask]>
wrote:
> Hi Chad,
>
> I used the Paypal a11y add-on for a recent project and found it pretty
> straight forward. It doesn't affect how you use Bootstrap because it just
> tacks on the aria roles after page load.
>
> I actually don't think this plugin is all that necessary.
>
> Here's my thing: if you're using Bootstrap responsibly (
> http://acrl.ala.org/techconnect/?p=4439) you will use a custom build that
> doesn't include components you aren't using. Bootstrap 3 is already fairly
> accessible out of the box, and I would argue that keeping your dependencies
> small is more valuable than tacking on javascript.
>
> The questionable usability of modules like the carousel, collapse,
> popovers, and tooltips is worth rethinking before using a plugin that
> supports that accessibility. If you don't use them, you don't need the
> plugin. You can always add aria roles to the markup you use.
>
> Anyway, if you do use the plugin, it's really easy to integrate. You can
> concatenate your jquery, bootstrap.min, and bootstrap-accessibility.min
> into a single file - and like I said it doesn't change how you would
> approach Bootstrapping a site.
>
> I really like Paypal's Accessible HTML5 Video player, which they support
> really well. So I've nothing but good feels for their team.
>
> Michael
> @schoeyfield
>
>
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> Chad Mills
> Sent: Monday, December 08, 2014 3:03 PM
> To: [log in to unmask]
> Subject: [CODE4LIB] Bootstrap and accessiblity
>
> Hi,
>
> Has anyone implemented Bootstrap v3.3.0 with the PayPal accessibility
> add-on and have any pointers, caveats, gotchas etc?
>
> https://github.com/paypal/bootstrap-accessibility-plugin
>
> Thanks!
> --
> Chad Mills
> Digital Library Architect
> Ph: 848.932.5924
> Fax: 848.932.1386
> Cell: 732.309.8538
>
> Rutgers University Libraries
> Scholarly Communication Center
> Room 409D, Alexander Library
> 169 College Avenue, New Brunswick, NJ 08901
>
> https://rucore.libraries.rutgers.edu/
>
|