<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>The '58 sound &#187; aesthetics</title>
	<atom:link href="http://58sound.com/tag/aesthetics/feed/" rel="self" type="application/rss+xml" />
	<link>http://58sound.com</link>
	<description>David Sloan on Accessibility, Inclusive Interaction design - and other topics of interest</description>
	<lastBuildDate>Tue, 24 Apr 2012 12:25:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='58sound.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://0.gravatar.com/blavatar/ca4cc2976952aa6eec811cb0b6477932?s=96&#038;d=http%3A%2F%2Fs2.wp.com%2Fi%2Fbuttonw-com.png</url>
		<title>The '58 sound &#187; aesthetics</title>
		<link>http://58sound.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://58sound.com/osd.xml" title="The &#039;58 sound" />
	<atom:link rel='hub' href='http://58sound.com/?pushpress=hub'/>
		<item>
		<title>Accessibility for Architects, Accessibility for Web designers</title>
		<link>http://58sound.com/2010/01/21/accessibility-for-architects-accessibility-for-web-designers/</link>
		<comments>http://58sound.com/2010/01/21/accessibility-for-architects-accessibility-for-web-designers/#comments</comments>
		<pubDate>Thu, 21 Jan 2010 14:25:52 +0000</pubDate>
		<dc:creator>David Sloan</dc:creator>
				<category><![CDATA[Accessibility and Usability]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[advocacy]]></category>
		<category><![CDATA[aesthetics]]></category>
		<category><![CDATA[built-environment]]></category>
		<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://58sound.com/?p=272</guid>
		<description><![CDATA[How similar is the challenge of promoting and supporting accessibility in architecture and in web and ICT design?<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=58sound.com&#038;blog=6581407&#038;post=272&#038;subd=58sound&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>Often, when working to promote accessibility of the digital environment, we look to the physical environment for comparisons and analogies. A PhD study at the <a title="School of Architecture, University of Dundee" href="http://www.architecture.dundee.ac.uk/">School of Architecture here in Dundee</a> has made me realise just how many parallels there are in the challenge of raising the profile of accessibility both amongst architects and amongst web and software developers.</p>
<p><span id="more-272"></span><a title="Lesley McIntyre: Finding My Way" href="http://www.dundee.ac.uk/geddesinstitute/phdmcintyre.htm">Lesley McIntyre&#8217;s work</a> aims to explore how architects can be provided with tools to help them understand better the impact of design features on the navigability of a building to visually impaired people. As with the Web, the attitude of architecture towards accessibility and considering disabled people in design is typically positive, but may be defined &#8211; and probably perceived as being constrained &#8211; by the need to comply with legislation (in the UK, <a title="Google Search: 'DDA Compliance'" href="http://www.google.co.uk/search?q=dda+compliance&amp;ie=utf-8&amp;oe=utf-8&amp;aq=t&amp;rls=org.mozilla:en-GB:official&amp;client=firefox-a">&#8220;DDA compliance&#8221;</a> can sound as doom-laden to architects as it does to web designers!) rather than as an opportunity to improve the quality and usability of a design. So there is a need to help architects understand the problems faced by people with sensory, physical and cognitive impairments when navigating the built environment, and how design can help to minimise the chances of these problems occurring.</p>
<p>Part of Lesley&#8217;s work involved asking a number of people, each with some form of visual impairment, to navigate through an unfamiliar building, and tracking their journey to identify the location of barriers to progress. She now has a rich collection of data and is working on ways in which this can be presented to architects in a meaningful and helpful way. The aim is to use this data &#8211; whether presented through videos, illustrated scenarios, guidelines, manuals, whatever -to help architects avoid making incorrect assumptions about disability, and instead give them a more accurate understanding of the common &#8211; and different &#8211; problems that face visually impaired people when navigate a building that might be unfamiliar to them (which, let&#8217;s not forget, might include sighted people trying to leave a smoke-filled building in an emergency). In turn, the hope is that this knowledge helps them to avoid well-recognised design pitfalls and inspires them to think of new solutions to make the built environment more accessible.</p>
<p>People who create, design and construct objects, whether physical or virtual, benefit from appreciating the diversity of their target audience, which in turn gives  meaning to accessibility-related design guidelines, and thus a sense of the constraints and freedom that such design guidelines offer. As <a title="Pixeldiva: Expand the Awesome - Design for a Wider Audience" href="http://www.pixeldiva.co.uk/shares/expand-the-awesome-design-for-a-wider-audience/">Ann McMeekin (@pixeldiva)</a> and <a title="Design Meets Disability: MIT Press" href="http://mitpress.mit.edu/catalog/item/default.asp?ttype=2&amp;tid=11673">Graham Pullin</a> have both recently and brilliantly demonstrated, designing for disability can lead to great design rather than compromised design.</p>
<p>I&#8217;m looking forward to exploring how web accessibility can learn from (and contribute to) Lesley&#8217;s work.</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/58sound.wordpress.com/272/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/58sound.wordpress.com/272/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/58sound.wordpress.com/272/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/58sound.wordpress.com/272/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/58sound.wordpress.com/272/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/58sound.wordpress.com/272/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/58sound.wordpress.com/272/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/58sound.wordpress.com/272/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/58sound.wordpress.com/272/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/58sound.wordpress.com/272/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/58sound.wordpress.com/272/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/58sound.wordpress.com/272/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/58sound.wordpress.com/272/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/58sound.wordpress.com/272/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=58sound.com&#038;blog=6581407&#038;post=272&#038;subd=58sound&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://58sound.com/2010/01/21/accessibility-for-architects-accessibility-for-web-designers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/5ea9f871cbb6425e9501bd99710487e3?s=96&#38;d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D96&#38;r=G" medium="image">
			<media:title type="html">58sound</media:title>
		</media:content>
	</item>
		<item>
		<title>Living well is the best revenge</title>
		<link>http://58sound.com/2009/03/25/living-well-is-the-best-revenge/</link>
		<comments>http://58sound.com/2009/03/25/living-well-is-the-best-revenge/#comments</comments>
		<pubDate>Wed, 25 Mar 2009 23:29:55 +0000</pubDate>
		<dc:creator>David Sloan</dc:creator>
				<category><![CDATA[Accessibility and Usability]]></category>
		<category><![CDATA[academia]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[advocacy]]></category>
		<category><![CDATA[aesthetics]]></category>
		<category><![CDATA[conference]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[w4a09]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://58sound.com/?p=111</guid>
		<description><![CDATA[Accessibility conference web sites - should you judge the conference's quality by the site?<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=58sound.com&#038;blog=6581407&#038;post=111&#038;subd=58sound&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>Last week I gave a session to third year HCI students on the relationship between accessibility, usability and aesthetics. Part of this session was to explore how aesthetic appeal can override apparent usability limitations in influencing the success of a product or interface; and we also explored the extent to which accessibility and aesthetic appeal can co-exist.</p>
<p>One of the discussion topics was &#8220;do accessibility and usability advocates lead by example?&#8221; Do their web sites exist as inspiring examples of good design? We had a good laugh finding examples of where that answer was a resounding &#8216;no&#8217; &#8211; although disability charity web sites are certainly improving in terms of design quality &#8211; and I pointed students to the fantastic <a href="http://www.designbyfire.com/000094.html">Design Eye for a Usability Guy</a> makeover of Jakob Nielsen&#8217;s <a href="http://www.useit.com">Useit.com</a> web site. The serious point was that if people wish to inspire designers to think about accessibility while maintaining creativity and design appeal, we need to show that it can be done. Not all accessibility advocates are talented designers (I wish I was), but we recognise the importance of getting the message over in an appealing way.</p>
<p><span id="more-111"></span></p>
<p>It&#8217;s a topic we care a lot about in Dundee; one of my colleagues, Graham Pullin has just written a book <a title="Graham Pullin: Design Meets Disability (MIT Press)" href="http://mitpress.mit.edu/catalog/item/default.asp?ttype=2&amp;tid=11673">Design meets Disability</a>, while by fortunate timing, tonight I became aware of the <a title="Enabled by design; collection of well designed, usable products" href="http://enabledbydesign.org/">Enabled by Design</a> web site.</p>
<p>It was ironic, then, that having publicised the schedule for <a title="W4A 2009" href="http://www.w4a.info">W4A 2o09</a> today, I noticed a couple of <a title="Tomas Caspers - twitter message" href="http://twitter.com/tcaspers/statuses/1387277895">twitter</a> <a title="Clive Lavery - Twitter message" href="http://twitter.com/cklavery/status/1387447506">messages</a> deriding the design of the conference web site. You can decide for yourself in what kind of light these comments shed on a <a title="WASP: Tomas Caspers" href="http://www.webstandards.org/about/members/tcaspers/">web standards advocate</a>; whatever, I&#8217;ll not be too proud to take any criticism on behalf of the conference team who developed it. But I did immediately think of Kynn Bartlett&#8217;s 2001 article on <a title="ICDRI: How to complain to a webmaster about accessibility" href="http://www.icdri.org/Kynn/how_to_complain_to_a_webmaster.htm">How to complain to a webmaster about accessibility</a>.</p>
<p>So having used the &#8216;look at the poor design of some accessibility and usability advocacy sites&#8217; arguments in talking to students, here I am on the end of the very same criticism! It made me wonder &#8211; just how critical is the design of a web accessibility conference web site in giving it credibility? How many potential attendees are we (or these Twitter comments) turning away?</p>
<p>I think my answer is that it depends on the target audience. W4A is a <strong>research-oriented</strong> conference where research is presented &#8211; new findings, new theories, new perspectives on an issue, new commercial approaches. Its target market is academics, corporate and public organisations &#8211; people who want to learn and share research and development. The attraction is the opportunity to present and publish new work, and to gain &#8211; and offer &#8211; feedback through talking to one&#8217;s peers. If our web site isn&#8217;t achingly clever or outstandingly beautiful, are we turning away prospective attendees? Are we stabbing accessibility in the back? I&#8217;m not so sure we are.</p>
<p>By contrast, there is a whole other group of web standards and accessibility focused conferences, which are <strong>targeted at industry</strong> &#8211; at web design professionals. The attraction is to come and hear the superstars talk about their new design techniques and web applications, be convinced that accessibility, web standards and a rewarding user experience is something achievable and worthwhile, and go home with knowledge that can be applied straightaway.</p>
<p>Like an academic conference, there is revelation of new information, there is peer-to-peer discussion and sharing, but I think these conferences also have a much bigger role in attracting non-experts &#8211; people who are there to learn and be inspired. Thus the conference web site must &#8211; I think &#8211; work that much harder as a way of attracting people to attend, people who don&#8217;t yet know a huge amount about the subject but who may be encouraged by a cool-looking web site much more than a bunch of academics (not that academics have no aesthetic values!).</p>
<p>I&#8217;m not writing this to excuse bad design, nor will I take a &#8216;yeah, but what about THEM?&#8217; approach and write a long post about the usability problems regularly present on HCI and usability conference web sites. Instead, I&#8217;ll finish by hoping that W4A 2009 is as successful as last year&#8217;s, in bringing together a terrific mix of people to talk about and share new ideas and discoveries in web design &#8211; people who want to attend because of what they&#8217;ll find out, what they&#8217;ll contribute and who they&#8217;ll meet, regardless of the appearance of the conference web site.</p>
<p>Just as I hope <a title="CSUN conference" href="http://www.csunconference.org">CSUN</a>, <a title="ACM Conference on Computers and Accessibility - ASSETS 2009" href="http://www.sigaccess.org/assets09/">ASSETS</a>, <a title="European Accessibility Forum event" href="http://eafra.eu/">EAFRA</a>, <a title="@media 2009 conference" href="http://www.vivabit.com/atmedia2009/">@media</a>, <a title="Future of Web Design conference series" href="http://events.carsonified.com/fowd">FOWD</a> etc etc all do with equal success.</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/58sound.wordpress.com/111/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/58sound.wordpress.com/111/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/58sound.wordpress.com/111/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/58sound.wordpress.com/111/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/58sound.wordpress.com/111/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/58sound.wordpress.com/111/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/58sound.wordpress.com/111/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/58sound.wordpress.com/111/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/58sound.wordpress.com/111/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/58sound.wordpress.com/111/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/58sound.wordpress.com/111/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/58sound.wordpress.com/111/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/58sound.wordpress.com/111/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/58sound.wordpress.com/111/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=58sound.com&#038;blog=6581407&#038;post=111&#038;subd=58sound&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://58sound.com/2009/03/25/living-well-is-the-best-revenge/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/5ea9f871cbb6425e9501bd99710487e3?s=96&#38;d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D96&#38;r=G" medium="image">
			<media:title type="html">58sound</media:title>
		</media:content>
	</item>
	</channel>
</rss>
