<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Signals from Mars &#187; Accessibility</title>
	<atom:link href="http://blog.marsworks.com/archives/category/accessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.marsworks.com</link>
	<description>News and happenings on the Red Planet</description>
	<lastBuildDate>Tue, 15 Jun 2010 12:34:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The &#8220;Mega&#8221; Drop Down</title>
		<link>http://blog.marsworks.com/archives/the-mega-drop-down/</link>
		<comments>http://blog.marsworks.com/archives/the-mega-drop-down/#comments</comments>
		<pubDate>Fri, 03 Apr 2009 13:18:29 +0000</pubDate>
		<dc:creator>Sean</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[User Interfaces]]></category>
		<category><![CDATA[Web Design]]></category>

		<guid isPermaLink="false">http://blog.marsworks.com/?p=40</guid>
		<description><![CDATA[I love it when the web development world comes up with a cool name for a new interface element&#8230;this one may not qualify as being all that original.  I&#8217;m starting to see these types of elements alot more often on websites and a recent post in Signal vs. Noise was my starting point for looking [...]]]></description>
			<content:encoded><![CDATA[<p>I love it when the web development world comes up with a cool name for a new interface element&#8230;this one may not qualify as being all that original.  I&#8217;m starting to see these types of elements alot more often on websites and a recent post in <a href="http://www.37signals.com/svn/posts/1647-mega-drop-down-navigation-at-basecamp-and-rails-guides-site" target="_blank">Signal vs. Noise</a> was my starting point for looking at this a bit further.</p>
<p>So&#8230;what makes a drop down &#8220;MEGA&#8221;? According to <a href="http://www.useit.com/alertbox/mega-dropdown-menus.html" target="_blank">Jacob Neilsen</a>, a Mega Drop Downs are:</p>
<p> </p>
<ul>
<li>Big, <strong>two-dimensional panels</strong> divided into <strong>groups</strong> of navigation options</li>
<li>Navigation choices <strong>structured</strong> through layout, typography, and (sometimes) icons</li>
<li>Everything <strong>visible at once</strong> — no scrolling<strong></strong></li>
<li><strong>Vertical or horizontal</strong> form factors when activated from top navigation bars; when activated from left-hand navigation, they might appear as <strong>mega fly-outs</strong> (not shown). </li>
</ul>
<div>I saw this a while ago, but really like this example at Apple&#8217;s website when searching:</div>
<div style="padding: 20px; text-align: center;"><a href="http://blog.marsworks.com/wp-content/uploads/2009/04/apple_search.gif"><img title="Apple - Search MEGA Drop Down" src="http://blog.marsworks.com/wp-content/uploads/2009/04/apple_search-210x300.gif" alt="" width="210" height="300" /></a></div>
<div><a href="http://www.hillandknowlton.co.uk/" target="_blank">Hill and Knowlton&#8217;s UK website</a> uses one that&#8217;s less visual, but starts to expand on the concept of a regular drop down menu:</div>
<div style="padding: 20px; text-align: center;"><a href="http://blog.marsworks.com/wp-content/uploads/2009/04/hk_life_menu.gif"><img title="H&amp;K UK's Life Menu" src="http://blog.marsworks.com/wp-content/uploads/2009/04/hk_life_menu-300x157.gif" alt="" width="300" height="157" /></a></div>
<div>Neilsen goes even further in his analysis of these menus with the following rules:</div>
<div>
<ul>
<li>the menu should render within 0.1 seconds</li>
<li>the mouse should remain stationary for 0.5 seconds before displaying the menu</li>
</ul>
<div>Fairly strict rules that most sites don&#8217;t seem to follow&#8230;and good luck making sure that a complex UI element like this will display in 0.1 seconds on all systems, but at least there are some goals for which we can attempt to attain.</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://blog.marsworks.com/archives/the-mega-drop-down/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A site for everyone</title>
		<link>http://blog.marsworks.com/archives/a-site-for-everyone/</link>
		<comments>http://blog.marsworks.com/archives/a-site-for-everyone/#comments</comments>
		<pubDate>Tue, 22 Jan 2008 14:35:20 +0000</pubDate>
		<dc:creator>Sean</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://blog.marsworks.com/archives/a-site-for-everyone/</guid>
		<description><![CDATA[We&#8217;ve been building websites here at MARSWorks Inc. for many years and have faced many challenges.  We&#8217;ve often struggled to decide whether or not we&#8217;d become more of a FLASH shop or stick to our current style which can best be described as &#8220;build anything and in any platform&#8221;.  We&#8217;ve always believed in [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve been building websites here at MARSWorks Inc. for many years and have faced many challenges.  We&#8217;ve often struggled to decide whether or not we&#8217;d become more of a FLASH shop or stick to our current style which can best be described as &#8220;build anything and in any platform&#8221;.  We&#8217;ve always believed in the philosophy of determining the situation our client and the web audience is in, and then determine the best possible tools and technologies to apply to that situation.  Often, the choice of a platform or tool like FLASH poses many challenges in making the site truly accessible, or friendly to Search Engines, or people without the ability to download the FLASH plugin.</p>
<p><span id="more-4"></span></p>
<p>In the development of our latest website, a long overdue revamp of our corporate online presence at <a title="MARSWorks.com Website" href="http://www.marsworks.com/">MARSWorks.com</a> we decided to embark on the challenge of building a website that could use the rich and animated features of FLASH, but also be readable to those without FLASH and be fully readable to search engines or other indexing tools.</p>
<p>Although we&#8217;re only at the beginning of this process, we have finally managed to make this a reality, and in the process learn a great deal about trying to have the best of both worlds on a site.  The site uses a single set of content data to populate both the xHTML and FLASH versions, and we do our best to detect the version of FLASH and then display the site in the proper format for each visitor.</p>
<p>What&#8217;s next? We&#8217;re next going to work on making sure we have proper support and display for various mobile platforms, including of course the iPhone from Apple and some popular Blackberry versions.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.marsworks.com/archives/a-site-for-everyone/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
