When we first put the idea and mockups in front of Ben Brumfield, the lead developer for the project, his enthusiasm erased any doubt we might have had about how far we could actually go. For designers, after all, that road between concept and implementation is seldom trod faithfully. I mean, the concept is like the charted course at the beginning of the voyage, and one can only hope s/he doesn’t end up like Columbus in a totally different place, on an unpredicted, unplanned route.

We’re very thankful to say the designer/developer rift prevalent in much of our industry didn’t exist at all in this project. And what was produced is, I think, a rather pleasant and rich user experience. From static experience to a fluid, inline, fully CRUD (create, read, update, delete) UI, we were pleased at the result:

This cross-posted from the original post on our Convio company blog.

Accessibility isn’t an easy thing to address. What with all the different codes and standards out there, our team is left wondering: how accessible do we have to be? And what does it mean to be “accessible” anyway?

Good free resource online. Description:

Accessibility is designing products so that people with disabilities can use them. Accessibility makes user interfaces perceivable, operable, and understandable by people with a wide range of abilities, and people in a wide range of circumstances, environments, and conditions.

The whole book, Just Ask: Integrating Accessibility Throughout Design, is online. Valuable stuff.