Previous issues:

Important Dates

June 18, Thursday, 1:30-4PM, 106 McVey Hall
Register here

Web Publishers Meeting
June 16, 2009, Tuesday, 2PM, location TBA


Spring <br /> Conference - June 9 in Athens, Ohio (campus of Ohio University) -
An Event Apart 2009 - June 22-23 in Boston -
Usability Week 2009 - June 22-27, San Francisco -
Usability Week 2009 - June 22-27, San Francisco -
An Event Apart 2009 - Oct. 12-13 in Chicago -
An Event Apart 2009 - Dec. 2-3 in San Francisco -

FYI - All Things Grid - to understand and focus on grid design for your sites -

UK's netmanager - to understand the severity of outside attacks on the our websites -


UK Bands -


(From Wikipedia, the free encyclopedia) A favicon (short for favorite icon), also known as a website icon, shortcut icon, url icon, or bookmark icon is a 16x16 pixel square icon associated with a particular website or webpage. A web designer can create such an icon and install it into a website (or webpage) by several means, and most graphical web browsers will then make use of it. Browsers that provide favicon support typically display a page's favicon in the browser's Address bar and next to the page's name in a list of bookmarks. Browsers that support a tabbed document interface typically show a page's favicon next to the page's title on the tab.

You can now go to FavIcon From Pics which creates favicons from any image or logo you upload. It actually creates two favicons - a single image and an animated GIF (view this page in Firefox). You can use one or both. The HTML scripting is supplied.

The only caution is to make sure your image or logo is perfectly square or it will come out distorted. The Web 2.0 application also offers to add an Internet Explorer 8 accelerator for scrolling text and animated favicons.

Try it and let us know how it works for you.


Ever gone to a site and spent more than appropriate time trying to figure out where you wanted to go? Does your site present the same annoyance to outsiders because you built your site to please insiders? Jakob Nielsen strikes at the heart of this issue by laying down 10 mistakes we may be making within our architecture that may be turning people away. One of my favorite lines is "Uncovering navigation shouldn't be a major task: Make it permanently visible on the page. Small children like minesweeping (passing the mouse around the screen to see what's hidden), but teenagers don't like it, and adults hate it." Here's more:

Structure and navigation must support each other and integrate with search and across subsites. Complexity, inconsistency, hidden options, and clumsy UI mechanics prevent users from finding what they need.

Bad information architecture causes the majority of outright user failures and isn't improving at the rate of other Web usability issues. To determine why, I've identified 10 long-term sore thumbs that together cost websites billions of dollars each year. I divided the following list of worst IA mistakes into two parts, which corresponds to how we partition the materials across our 2-day IA course: structure on Day 1 and navigation on Day 2. Of course, you need to get both right, but they're essentially two different design levels: The invisible way the site is structured and the visible way users understand and manage that structure.

Structure Mistakes

1. No Structure
The most notable structural problem is when designers treat a site like one big swamp with no organizing principle for individual items. Yes, users can fish the swamp using search or by following links from current promotions or outside sites. But whatever they dredge up is it. No opportunities for understanding the site's other offerings or locating related items.

This sin is common on news sites and catalog-based e-commerce sites, where each item (articles and products, respectively) is treated as a stand-alone unit without connections to related items. No wonder users leave those sites so quickly.

2. Search and Structure Not Integrated
We've long known that users often exhibit search-dominant behaviors. This doesn't mean that search is all they need, however. Arriving on a page from a search is like parachuting into a city. Hopefully, if you want to go to Paris, you'll land there rather than in Amsterdam, but in any case, you're unlikely to land on the doorstep of your favorite restaurant. To get there, you'll need to walk or take a cab. Similarly, users often need to navigate the neighborhood around their search destination.

-->Read entire article

Notes from Campus

Web Security and What You Can Do

Bill Cotter, of the UK Communications and Network Systems IT Security (ITS) team, spoke about steps the University takes in protecting inside and outside sources from unscrupulous hacking attacks.

In summary:

  1. ITS scans for hacked UK web pages
  2. ITS Scans for Social Security Number’s on UK web pages (as registered in UK's SAP)
  3. ITS uses the Open Web Application Security Project (OWASP) for compliance
  4. An OWASP meeting will be held in Louisville on June 19 that anyone can attend
  5. An AppScan will soon be available on request from ITS to scan your individual department's website for attacks or hacks.
  6. Payment Card Industry Data Security Standard (PCI-DSS) for shopping cart applications

He also has mentioned a speakers series on June 11 at Northern Kentucky University that we might be interested in. From 1 to 4PM James Walden will host a workshop on "Web Security." Participants will learn penetration testing, code review techniques, tools for finding SQL injection, and XSS vulnerabilities.  More importantly, they will also learn how to write code without such vulnerabilities.

We hope Bill will join us again with updates.

Thanks Bill.