You have built the perfect web site, the colours invoke the right emotional response, the visual imagery leads customers to the relevant information while allowing the audience to personally relate to the site. The content is ideal for the web, not to much but enough to convince people of the service. The major call to actions are in the right locations, and easy to find. Everything is set, the web site is ready to take on the world!
Still no matter how perfect your site is, if the last step, when they encounter the web form, isn’t streamlined and usable, the rest is a waste of time.
- Rating:
- 4.5
As I’m designing forms I don’t usually have an issue making then usable or accessible within the limits of the clients budget.
However taking the form to the next level technically can sometimes be an issue. This is exactly what Fancy Form Design by Jina Bolton, Tim Connell and Derek Featherstone is all about, designing and building those great forms on the web.
When I first purchased this book (yes I do purchase my books, they aren’t usually review freebies) I was a little skeptical as to whether this book would have any content in it that would be relevant to me. This is an issue that I’m running into more and more these days.
Tagged: accessibility, design, enhancement, forms, jquery, project-52, review, ui, usability, ux, webdesign
I’m seeing an interesting trend here in Perth. Recently, job adverts and recruiters looking for Test Analysts to do usability and accessibility testing as part of their duties. Now this is a good thing in a way.
At least the traditional roles of the IT software project are understanding the need for usability and accessibility testing in web and general software projects. I guess something is better than nothing, right?
Well maybe not.
You know in accessibility circles we are constantly telling people using drop down CSS menus that when the menus are not visible we shouldn’t be using display:none to achieve this. We all know this one, right. Just to refresh your memory, remember the display:none rule takes an element assigned right out of the picture completely, for anyone using a screen reader the assigned content will just not “exist”.
This is all well and good. Well that depends, maybe there is a case for the use of display:none afterall.
