To make up for the lack of post last week (apologies, things have just been too busy), a special post this week. Before working on the new website, I once again did some searching for an accessible WordPress theme. Unfortunately, I found little that would meet my needs as I required WCAG (Web Content Accessibility Guidelines) level AA at the minimum, but preferably something that would be as accessible as possible.
UPDATE (March 6, 20104) : Added a new example, and did some minor fixes.
This is not by any means a new idea, but as I am in the process of redesigning the website, I did think about the carousel. The existing website doesn’t have one, but glancing at my WordPress statistics, the image carousel plugin review post has been getting the highest number of hits, and I have that post for a reason (that is I had to put one into the last site I did). Continue reading “Death to the Website Carousel”
So I promised
@gmcharlt a while ago (think last November) that I would do a blog post on comparing how the US and Canadian legislation regulations align with the Web Content Accessibility Guidelines (WCAG) 2.0. Continue reading “Alignment of WCAG with Section 508 (US) & Canadian Legislation”
I’ve been working on our new website and as usual, I decided to start with a card sort. Continue reading “Card Sort & Goal-Oriented IA”
During the Code4LibBC breakout sessions, we had an ‘accessibility corner’. We talked about a lot of different things, but we covered two major topics: the process we might go through, and how to get buy in. While we have a google doc with notes from the breakout, hopefully this blog post organizes those notes and other thoughts into something a little more cohesive. Continue reading “Code4LibBC: Accessible Website Process Toolkit & Buy In”
For this presentation, I decided to speak more broadly on accessibility (rather than focus specifically on web accessibility), partly because it’s so short (5-10 minute lightning talk) and partly due to the fact that despite it being a “Code4Lib” regional, we wanted to promote cross collaboration across all skill and knowledge levels. I still used a technology example, but had physical space related examples as well. Continue reading “Code4LibBC: Shifting Perspectives: From Disability Accommodation to Universal Design”
I can take no credit at all for the development of the tutorials pane of Thimble (that goes to Tom Park for development and Pomax for reviewing), but I was so excited by it that as soon as it was pushed out into production (before it was officially announced), I decided to try it by “converting” one of the existing starter makes. Continue reading “Webmaker: “Education Friendly” Tutorials in Thimble”
Okay, so I know we have the CSS3 multiple column layout “columns” property in the newest browsers, but working in public institutions where we are expected to support IE as far back as version 8 or sometimes 7 (in the very rare case even 6 still), we cannot rely on the columns property… yet. Continue reading “User Readable CSS: Columns”
I’ve written on making forms accessible before in the WCAG series, but I thought I’d document some real examples using the work that I’ve been doing. This one is a fairly simple, but important example especially since we’re moving to PDA (patron driven acquisitions). Continue reading “Making Forms Accessible”
If you’ve read my previous posts on web accessibility, then most of this will be a rehash. This is the version that I did for the TRY 2013 conference, where I reorganized a few things and put in different examples. Continue reading “TRY 2013: Implementing WCAG by Making Your Website Accessible for Everyone”