I have recently run a seminar on prioritising web accessibility during the build of a web site for both DrupalGov and Joomla Day Sydney. You can download the slides for Prioritising web accessibility in the build of a web site from Prezentt. I have highlighted the main issues I covered in this blog post. For more information, have a look at our Services section on Accessibility testing during the web development lifecycle.
I spoke at dev/world on Tuesday about mobile and accessibility. I focused mostly on mobile apps and found some great examples of #ThingsNotToDo.
I’m waiting for my flight back to Melbourne after a very interesting WordCamp Sydney. I met some great people and learnt some interesting things.
You can download my presentation and associated links and documents from Prezentt. Most of the speaker slides are also available on the WordCamp Sydney web site.
We’re likely going to be doing the transcribing, captioning and audio descriptions too, so stay tuned!
Not convinced that CAPTCHAs are inaccessible? Read Part 1 – CAPTCHAs: Inaccessible to everyone.
Although WCAG2 does allow for CAPTCHAs, there are much more accessible alternatives.
My next post for GovHack is accessible maps. Now at a later date, have a look at OzWiki: Interactive Maps factsheets. But for now, I know you’re all busy, so I’ll summarise it for you. The important things you need to do to make a map accessible is: Providing a long description of the map
Apologies to all the GovHackers! I meant to post this yesterday, but was struck down with a migraine. I hope it’s not too late! Colour contrast The most important thing to remember when it comes to designing an accessible web site, app or interface is colour contrast. This is the kind of thing that needs