<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"
	xml:lang="en">
	<title>graphicdivine</title>
	<subtitle>Precision design for music, culture, commerce and education</subtitle>
        <link rel="alternate" type="text/html" href="http://graphicdivine.co.uk/blog.php"/>
        <link rel="self" type="application/atom+xml" href="http://graphicdivine.co.uk/atom.xml"/>
	<updated>2010-06-14T17:46:52+01:00</updated>
	<author>
	<name>Chris</name>
	<uri>http://graphicdivine.co.uk/blog.php</uri>
	<email>chris@graphicdivine.co.uk</email>
	</author>
	<id>tag:graphicdivine,2010:graphicdivine</id>
	<generator uri="http://www.pivotlog.net" version="Pivot - 1.40.7: 'Dreadwind'">Pivot</generator>
	<rights>Copyright (c) 2010, Authors of graphicdivine</rights>
	
	
	
	<entry>
		<title>HTML5 and what?</title>
		<link rel="alternate" type="text/html" href="http://graphicdivine.co.uk/entry/17/HTML5_and_what" />
		<updated>2010-06-14T17:33:00+01:00</updated>
		<published>2010-06-14T17:33:00+01:00</published>
		<id>tag:graphicdivine,2010:graphicdivine.17</id>
		<link rel="related" type="text/html" href=""  />
		<summary type="text">What I don't understand is why, on a page titled &amp;quot;HTML 5 and web standards&amp;quot;*, Apple are browser sniffing and won't let you in unless you use Safari? Browser War 2.0 anyone?

* or is it &amp;quot;HTML and the future&amp;quot; -- inaccurate alt text like this is Very Bad Practice, and also smacks of a last minute change of heart.</summary>
        <content type="html" xml:lang="en" xml:base="http://graphicdivine.co.uk/entry/17/HTML5_and_what"><![CDATA[
                <p>
What I don't understand is why, on <a rel="external" href="http://www.apple.com/html5/">a page titled &quot;HTML 5 and web standards&quot;</a>*, Apple are browser sniffing and won't let you in unless you use Safari? Browser War 2.0 anyone?<br />
<br />
* or is it &quot;HTML and the future&quot; -- inaccurate alt text like this is Very Bad Practice, and also smacks of a last minute change of heart.
</p>
<p>
<img src="http://graphicdivine.co.uk/images/html5-and-what.jpg" style="float:left;margin-right:10px;margin-bottom:5px;border:0px solid" title="screengrab of apple site showing innacurate alt text" alt="screengrab of apple site showing innacurate alt text" class="pivot-image" /></p>
		]]></content>
		<author>
			<name>chris</name>
		</author>
	</entry>
	
	
	
	<entry>
		<title>Ah, the irony of it all</title>
		<link rel="alternate" type="text/html" href="http://graphicdivine.co.uk/entry/16/Ah_the_irony_of_it_all" />
		<updated>2010-02-18T19:28:00+01:00</updated>
		<published>2010-01-06T13:49:00+01:00</published>
		<id>tag:graphicdivine,2010:graphicdivine.16</id>
		<link rel="related" type="text/html" href=""  />
		<summary type="text">You might think that of all people The Office of Disability Issues would manage to produce a fully accessible website, and on the surface, it's not bad.


Their failure, though, is both subtle and significant.</summary>
        <content type="html" xml:lang="en" xml:base="http://graphicdivine.co.uk/entry/16/Ah_the_irony_of_it_all"><![CDATA[
                <p>
You might think that of all people The Office of Disability Issues would manage to produce a fully accessible website, and on the surface, it's not bad.
</p>
<p>
Their failure, though, is both subtle and significant.</p>Lets start on the '<a rel="external" href="http://www.odi.gov.uk/iod/background/background08.php">background to digital communications</a>'
page.  All looks good.  We have a tidy, consistent layout equipped with
a clear navigation structure.  Look what happens, though, if we pick an
option from the menu at the top of the central content area, '<a rel="external" href="http://www.odi.gov.uk/iod/background/background0802.php">inclusive websites</a>',
for example. Suddenly our menu highlighting is gone, our breadcrumb
trail is truncated, and we lose all sense of our location within the
site heirachy.
<p>
It's not all about ALT texts and code validity.  As the <a rel="external" href="http://www.w3.org/WAI/WCAG20/glance/">WCAG quicktips</a> emphasise, we need to: &quot;Make content appear and operate in predictable
ways&quot;. Accessibility is about much more than disablity: it's about consistent design and robust information architecture.</p>
		]]></content>
		<author>
			<name>chris</name>
		</author>
	</entry>
	
	
	
	<entry>
		<title>w3c site bugs</title>
		<link rel="alternate" type="text/html" href="http://graphicdivine.co.uk/entry/15/w3c_site_bugs" />
		<updated>2009-12-15T09:39:00+01:00</updated>
		<published>2009-11-23T09:18:00+01:00</published>
		<id>tag:graphicdivine,2010:graphicdivine.15</id>
		<link rel="related" type="text/html" href=""  />
		<summary type="text">While browsing for information on web authoring tools I came accross these two apparently un-populated boilerplate templates, and a nasty little menu bug.http://www.w3.org/standards/agents/authoring.html |http://www.w3.org/standards/agents/browsers.html</summary>
        <content type="html" xml:lang="en" xml:base="http://graphicdivine.co.uk/entry/15/w3c_site_bugs"><![CDATA[
                <p>While browsing for information on web authoring tools I came accross these two apparently un-populated boilerplate templates, and a nasty little menu bug.</p><p><a rel="external" href="http://www.w3.org/standards/agents/authoring.html">http://www.w3.org/standards/agents/authoring.html</a> |<a rel="external" href="http://www.w3.org/standards/agents/browsers.html">http://www.w3.org/standards/agents/browsers.html </a></p><p><img src="http://graphicdivine.co.uk/images/menu-bug.png" style="float:left;margin-right:10px;margin-bottom:5px;border:0px solid" title="Layout bug on w3c site" alt="Layout bug on w3c site" class="pivot-image" /></p><h3> Update </h3><p>The menu bug has been <a rel="external" href="http://lists.w3.org/Archives/Public/site-comments/2009Nov/0041.html">quietly</a> fixed.</p>
		]]></content>
		<author>
			<name>chris</name>
		</author>
	</entry>
	
	
	
</feed>
