Bringing Back the Blog

May was a big month for changes. Kelsey and I celebrated our eighth wedding anniversary, I graduated with a PhD in Science and Technology Studies from Rensselaer Polytechnic Institute (RPI), I left my job at Fingerpaint, where I had been working for over four years, and I started a new job as a Principal Software Developer with Alley Interactive, working remotely.

Being done with PhD studies and eliminating my commute has left me with a bit more time in my schedule, so I figured I would try to start blogging on a semi-regular basis. We’ll see how it goes!

Stop It with the Tiny Font

A modern design trend that drives me absolutely batty is this obsession with tiny text on websites – particularly blog and news sites, where the content is (presumably) intended to be read.

I consider myself mildly visually disabled – I use glasses to correct my nearsightedness, which is not severe. I can read what is on my computer screen equally well with or without glasses. However, I’m using a computer with a 15″ screen and a screen resolution of 1680×1050, which means the following:

  • 1680 / 1050 = 1.6 = aspect ratio of 16:10
  • Using Pythagoras’ theorem, I can calculate that one pixel on my screen is 0.225 mm
  • That means that the 11px font you are using is literally only 2.475 mm high on my screen, which is typically two feet away from my face
  • By comparison, most books are set with an 11pt (that’s point, not pixel) font, which is about 3.9 mm high, and most people read books about 6-12 inches away from their face
  • Since perceived size decreases by about half at double the distance, the 11px font on my screen appears to be about 1.24 mm at 24 inches vs. the 3.9 mm book at 12 inches
  • Conclusion: 11px font on my screen is approximately 3x smaller than the font size of a book held 12 inches from my face

As a consequence, I find myself constantly using my browser’s built-in zoom functionality (ctrl +) to zoom in items that I am reading so that they very nearly fill the screen. I find that a comfortable reading font size is somewhere around 24px on this screen (although on larger monitors, I can get away with less). On one of my 24″ external monitors, which is what I use for writing code all day, I set my font size in my text editor to 20px.

So why the obsession with small font size? Maybe it has something to do with page density and advertising space. Maybe it’s “trendy” and “cool.” As a user, and not a severely visually disabled user, I find it to be incredibly frustrating.

I suspect that part of the difficulty comes from increasing pixel density in devices and a corresponding lack of adjustment in design. The laptop I used a decade ago had a screen not much smaller than this, and its maximum resolution was 800x600px, which would yield a perceived pixel size of roughly twice what my current monitor displays, because design tracks pixels, and pixels aren’t fixed.

In Support of Information Technologists with Disabilities

The Internet, online video services, video games, and other information technologies are being developed without much regard for users with disabilities. As a result, hard-won victories by the disabled community are being erased by the shift to new technologies. Accessibility law suffers from the same problem that plagues most laws governing rapidly changing technology – the laws are not written to be future-proof, so the law lags the technology. When little to no regulation is combined with a corporate culture interested in innovation to the exclusion of accessibility, people with disabilities are left behind by modern technologies.

Why are modern technologies so inaccessible? One possible reason is that the people in charge of designing and developing the technologies aren’t disabled themselves, and thus aren’t affected by the inaccessibility of the products that they create. For example, it would be impossible for a red-green colorblind video game developer to test a game that relies on the ability to distinguish between red and green in order to play the game. New technologies have been tested by developers and (sometimes) by user testing groups, but these two groups rarely include people with disabilities. If developers were personally affected by the inaccessibility of the products that they create, they wouldn’t create inaccessible products. At a minimum, if developers were exposed to people who were personally affected by the inaccessibility of the products that they create – either by being on the same development team, or part of a user group – the likelihood that they would continue creating inaccessible products would decrease.

How can we, as a society, make modern technologies more accessible? High technology fields have long been dominated by middle class, heterosexual, white, non-disabled men. This fact has resulted in a variety of technologies that work best for middle class, heterosexual, white, non-disabled men. For instance, voice recognition software has been notoriously inaccessible to women, minorities, and people with regional dialects, because of how the technology was developed and tested. A number of academic and nonprofit groups have been active in trying to get more women, minorities, and people with disabilities involved in computing careers in order to achieve greater balance on product development and testing teams in an effort to produce more accessible technology. For example, the National Science Foundation funds a grant project called Broadening Participation in Computing that focuses on this problem.

Getting more people with disabilities involved in computing and technology careers can help produce more accessible technology. For example, a deaf Google engineer named Ken Harrenstien led the development of a project to automatically caption YouTube videos using speech recognition technology. The fact that Google had a deaf engineer on its YouTube team meant that there was someone with the skills and experience working “on the inside” to make the technology more accessible to the deaf community. In the age of user-generated content a la services like YouTube and Facebook, innovative solutions to accessibility, including “technological fixes,” are becoming a necessity.

YouTube, like many other modern websites, relies on users to upload content, so there is no central mechanism for captioning these videos – it is up to the individual user to provide a caption track, which most users do not supply. By contrast, television studios that put episodes of television shows online have a much greater ability to control whether their shows are captioned or not. Therefore, the television studios are the target of recent legislation – the Twenty-First Century Communications and Video Accessibility Act of 2010 – meant to extend the captioning requirements from broadcast television to “Internet Protocol-delivered video programming.” Such regulation would make little sense if applied to services like YouTube, where content is created by users, so more innovative methods are required. YouTube’s approach involves two different methods of attacking the problem – what we in STS call “social” intervention and “technical” intervention. The “social” intervention is YouTube’s caption track tool, which has been simplified significantly compared to most video captioning utilities. All the user needs to do is put the text of the caption and the times (in seconds) the caption should be displayed, and YouTube takes care of the rest. The “technical” intervention is the automatic captioning system, which takes care of providing captions for videos that users do not caption themselves, and is intended to be a “last resort” measure.

How can we get more people with disabilities interested and involved in technology careers? It is important to work with high school guidance counselors to encourage people with disabilities to pursue careers that interest them, regardless of perceived or actual barriers to employment in those careers. There needs to be institutional support for people with disabilities interested in technology careers to be able to participate, including whatever assistive technology is required, such as text-to-speech software, sign language interpreters, specialized hardware for people with motor impairments, and the like. Professional societies could leverage people with disabilities already working in technology careers as spokespersons for raising the interest of young people with disabilities in those careers. Professional technology conferences could devote time to discussing issues of accessibility in design, leveraging technology professionals with disabilities as keynote speakers at such events. Raising awareness of the issues facing diverse communities of people with disabilities is critical in making technology more accessible for everyone.

Cross-posted at http://rpists.org/2011/12/01/in-support-of-information-technologists-with-disabilities/

Update – Web Developer / Designer Survey

Thanks to everyone who participated in the survey! I got 330 responses in three days, which was significantly higher than what I expected. I’m working on putting together an analysis of the data, which I will post back here when I am finished. Anyone who wants to see the raw data can do so here:

https://docs.google.com/spreadsheet/ccc?key=0At194oQMMSfOdEdmV29WSWxab3BCRFQ5YVl6RUFQenc&hl=en_US#gid=0

I’m using the ATOM feed to remix the data, which is available publicly here, for anyone else who wants to remix the data:

https://spreadsheets.google.com/feeds/list/0At194oQMMSfOdEdmV29WSWxab3BCRFQ5YVl6RUFQenc/od6/public/basic?hl=en_US

Help Needed – Web Designer/Developer Survey

For my PhD program in Science and Technology Studies at Rensselaer Polytechnic Institute in Troy, NY, I am conducting a short survey of web designers and developers to assess educational background, work practices, and community norms. The results of this quantitative survey will help me shape interview questions for my research sites. If you are a web designer or developer, please take a few minutes to fill out the survey, and please pass it on to anyone you know who is a web designer or developer. Thanks!

The survey can be found on my website here: http://www.kevinfodness.com/web-developer-survey/