Gender equality in Web Design

The staff at A List Apart (quite honestly the best web design zine I know of) just recently released the results from their massive annual survey conducted amongst new media professionals (web designers, developers, webmasters, etc). There is a lot of data, and you can view their analysis here (pdf file, 1.6mb). I'll write a few posts about things that surprised me.

Gender demographics
83% of web professionals are men. Despite the fact that most computer related occupations share a similar statistic, I thought that it would be a little different in this field.

First off, a good number of the respondents' job titles were: web designer (19.9%), designer (10.4%), or creative director (5.4%). Unlike other responses, such as developer, webmaster, information architect, these titles suggest a "left brain" approach to the web. Typically, women are well represented in other artistic or creative fields.

Second, this industry has a very high rate of self-employed/freelance individuals (23.4%). Again, this is the type of employment that is well suited to those who crave a positive work-life balance: a factor that is often more important to women than men.

Typically, the barriers to entry in this industry are quite low. Higher education can often provide a great starting point for a career, but I suppose a prerequisite that overshadows that is an active interest and familiarity with computers.

Even more than an interest though is the approach. To use an example: the hard core gaming industry (a very male focused business) encourages not just participation amongst customers, but also modifications to the games themselves. Boys and young men learn how to script AI, create electronic models, and design experiences through these games. They are empowered and rewarded for it.

Games targeted at women are still few and far between, but those that lend themselves well to broader audiences prefer to offer intuitive interfaces that hide the mechanics so as not to confuse or scare away the audience. While this may make them more attractive to casual users, it may also be doing a disservice to them as then the customers are taught to become receptive and not active participants. They are reliant on the developers to incorporate things they'd like to see and are taught to wait patiently for that to happen rather than being given the tools to do it themselves.