A. Chavan's blog

Websites being built today need to be accessible on mobile devices such as smartphones and tablets. I will outline a prototyping process that we are experimenting with to efficiently create designs for responsive websites.

This month, the world lost two giants of computing. Steve Jobs died on Oct 5th, 2011 after a long illness. His remarkable story and influential legacy has been covered extensively in the news and social media. A week later, Dennis Ritchie died at the age of 70. His death did not receive as much attention in the media, but his legacy is as influential as that of Jobs, if not more.

At Urban Insight, we use web conferencing to facilitate collaboration between team members working in different locations as well as to communicate with our clients around the country. The critical features we need are 1) screen-sharing; 2) integrated audio over telephone or via the computer's microphone and; 3) the ability to schedule meetings and invite attendees.

While Skype is fine for quick internal meetings, for client meetings & web presentations, we have been using GoToMeeting for several years. We recently re-evaluated two web conferencing alternatives and compared them with GoToMeeting (GTM) to see if we wanted to change tools. 

Why do we still see websites that are poorly designed from an accessibility perspective even when basic web accessibility measures are well understood and fairly easy to implement?

In conversations with potential clients, at project kick-off meetings, or during Drupal training sessions, I often have to explain Drupal terms and basic concepts such as Drupal "core", contrib modules, themes, configuration options, and custom modules. To introduce these concepts I created a diagram that provides a simplified overview of the different pieces that come together to make a Drupal website.