Erik Olson, ON THE TOPIC OF General

I found it hard to contain my joy when Google announced on its Official Blog that it is now able to index Flash content. Hooray!

According to Google, they have perfected an algorithm, "that explores Flash files in the same way that a person would, by clicking buttons, entering input, and so on. Our algorithm remembers all of the text that it encounters along the way, and that content is then available to be indexed."

This is not in the future; Google is indexing Flash sites right now.

While this is a huge step in the direction of having Flash files as crawlable as HTML files, some major hurdles still need to be overcome.  Currently, the only content being indexed is embedded directly in the swf. "This includes Flash ‘gadgets’ such as buttons or menus, self-contained Flash websites, and everything in between," as well as URLs.  It doesn’t, however, index content loaded externally from HTML, XML, or other swfs. Those files will be indexed as a separate resource and not associated with the parent Flash file.

Another major limitation is the inability to see Flash files loaded using Javascript. This is unfortunate since a large number of Flash files are embedded using swfObject.  Also, they do not index non-textual content like images or FLV files; essentially, Google’s only indexing text.

As a Flash developer and designer, I’ve learned that the greatest limitation to Flash is its separation from other elements on the page. With getting information in and out of Flash using External Interface in Actionsript—and now that Flash content is now beginning to be indexed—the tide is turning for Flash accessibility.

Read more about the SEO-related benefits of this new announcement from our very own faux-hawked Josh Chambers. (And yes, Josh, a post on how to design SEO-friendly Flash is forthcoming.  And no, you still can’t sit at the designers’ lunch table). 

Leave a comment ( 5 )

Samantha Warren, ON THE TOPIC OF Tips and Tricks

For those who have survived a traditional education in typography, the limitations of the web can be a very scary place (there was a time when I was even scared... very very scared). On more than a handful of occasions, I have been asked by people designing for the web why making text an image is a bad thing, and here are my answers:

Reasons why you should never make body-copy an image online:

• The information is not selectable for those who may want to copy and paste it.
• The text is not resize-able, making it very difficult for those who prefer larger type to scale it up to read.
• It is not accessible by a screen-reader for those who are visually impaired.
• It doesn't allow content to be; indexed by search engines.

Continue reading "Typography Tuesday: Why Type Shouldn’t Be Images"

Leave a comment ( 8 )