<?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>The Tink Tank &#187; Web Development</title>
	<atom:link href="http://tink.co.uk/category/web-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://tink.co.uk</link>
	<description></description>
	<lastBuildDate>Sun, 28 Mar 2010 18:52:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Screen Reader Support For Disabled &amp; Read Only Form Fields</title>
		<link>http://tink.co.uk/2010/02/screen-reader-support-for-disabled-read-only-form-fields/</link>
		<comments>http://tink.co.uk/2010/02/screen-reader-support-for-disabled-read-only-form-fields/#comments</comments>
		<pubDate>Sun, 21 Feb 2010 16:12:52 +0000</pubDate>
		<dc:creator>Léonie Watson</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Screen Readers]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://tink.co.uk/?p=146</guid>
		<description><![CDATA[Some while ago I was asked how screen readers handle disabled and read only form fields. Despite forms being commonplace on most websites, there&#8217;s remarkably little information available on the subject. It turns out that there&#8217;s also very little consistency in the way different screen readers behave either.

The HTML 4.01 specification defines two attributes that [...]]]></description>
		<wfw:commentRss>http://tink.co.uk/2010/02/screen-reader-support-for-disabled-read-only-form-fields/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Contacting Organisations About Inaccessible Websites</title>
		<link>http://tink.co.uk/2010/01/contacting-organisations-about-inaccessible-websites/</link>
		<comments>http://tink.co.uk/2010/01/contacting-organisations-about-inaccessible-websites/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 21:46:18 +0000</pubDate>
		<dc:creator>Léonie Watson</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://tink.co.uk/?p=140</guid>
		<description><![CDATA[Contacting an organisation to explain why you find their website difficult to use, can seem a bit daunting. Who should you talk to? What should you say? How should you approach it?
Contacting Organisations About Inaccessible Websites is a splendid new resource from the Web Accessibility Initiative (WAI).

People who are familiar with web accessibility will have [...]]]></description>
		<wfw:commentRss>http://tink.co.uk/2010/01/contacting-organisations-about-inaccessible-websites/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Wave Screen Reader Accessibility</title>
		<link>http://tink.co.uk/2009/10/google-wave-screen-reader-accessibility/</link>
		<comments>http://tink.co.uk/2009/10/google-wave-screen-reader-accessibility/#comments</comments>
		<pubDate>Sat, 24 Oct 2009 19:11:46 +0000</pubDate>
		<dc:creator>Léonie Watson</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Screen Readers]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://tink.co.uk/?p=124</guid>
		<description><![CDATA[Google Wave is the latest innovation in online communication. It&#8217;s caused a great deal of interest across the industry, and may well herald a new era in online social interaction. It&#8217;s new, it&#8217;s cutting edge and it&#8217;s exciting. It&#8217;s also a catastrophic accessibility failure for screen reader users.

As Jared Smith rightly points out, Google Wave [...]]]></description>
		<wfw:commentRss>http://tink.co.uk/2009/10/google-wave-screen-reader-accessibility/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Accessibility 2.0</title>
		<link>http://tink.co.uk/2009/09/accessibility-2-0/</link>
		<comments>http://tink.co.uk/2009/09/accessibility-2-0/#comments</comments>
		<pubDate>Sun, 27 Sep 2009 18:34:12 +0000</pubDate>
		<dc:creator>Léonie Watson</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://tink.co.uk/?p=108</guid>
		<description><![CDATA[Accessibility 2.0 is a one day conference hosted by AbilityNet. With six presentations and two panel discussions, topics ranged from mobile interface design and accessibility beyond the desktop, through to HTML 5, WAI ARIA and Silverlight accessibility.

Considerations for Accessible Mobile Application Graphical User Interface Design
Greg Fields from RIM kicked things off by presenting 10 guidelines [...]]]></description>
		<wfw:commentRss>http://tink.co.uk/2009/09/accessibility-2-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Standards.Next Cognition &amp; Accessibility</title>
		<link>http://tink.co.uk/2009/09/standards-next-cognition-accessibility/</link>
		<comments>http://tink.co.uk/2009/09/standards-next-cognition-accessibility/#comments</comments>
		<pubDate>Sun, 20 Sep 2009 22:50:14 +0000</pubDate>
		<dc:creator>Léonie Watson</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://tink.co.uk/?p=105</guid>
		<description><![CDATA[
Standards.Next is an informal meetup hosted by Opera, and attended by anyone with an interest in web standards and beyond. On Saturday 19th September focus turned to one of the most unchartered areas of user experience: Cognition and Accessibility.

Cognition covers an incredibly wide range of conditions and requirements. It&#8217;s one of the least well documented [...]]]></description>
		<wfw:commentRss>http://tink.co.uk/2009/09/standards-next-cognition-accessibility/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Jaws 11 ARIA Drag &amp; Drop Support</title>
		<link>http://tink.co.uk/2009/08/jaws-11-aria-drag-drop-support/</link>
		<comments>http://tink.co.uk/2009/08/jaws-11-aria-drag-drop-support/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 20:46:35 +0000</pubDate>
		<dc:creator>Léonie Watson</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Screen Readers]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://tink.co.uk/?p=98</guid>
		<description><![CDATA[Jaws 11 public beta introduces support for drag and drop with WAI ARIA. Although Jaws has included desktop drag and drop capability for some while, the same functionality on a web page has always been more difficult. Jaws 11 now indicates which elements on the page can be dragged, and where they can be dropped.

ARIA [...]]]></description>
		<wfw:commentRss>http://tink.co.uk/2009/08/jaws-11-aria-drag-drop-support/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Screen Reader Support for ARIA Live Regions</title>
		<link>http://tink.co.uk/2009/06/screen-reader-support-for-ajax-live-regions/</link>
		<comments>http://tink.co.uk/2009/06/screen-reader-support-for-ajax-live-regions/#comments</comments>
		<pubDate>Mon, 01 Jun 2009 18:02:29 +0000</pubDate>
		<dc:creator>Léonie Watson</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Screen Readers]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://tink.co.uk/?p=46</guid>
		<description><![CDATA[
Rich Internet Application (RIA) websites encourage people to generate content, collaborate online and make choices about the information they receive. Unsurprisingly, RIA websites can represent a considerable challenge for screen reader users. The WAI&#8217;s Accessible Rich Internet Applications (ARIA)is an emerging standard that aims to bridge the gap between RIA websites and screen reading technology.

ARIA [...]]]></description>
		<wfw:commentRss>http://tink.co.uk/2009/06/screen-reader-support-for-ajax-live-regions/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Jaws Scripts for Accessibility Links</title>
		<link>http://tink.co.uk/2009/05/jaws-scripts-for-accessibility-links/</link>
		<comments>http://tink.co.uk/2009/05/jaws-scripts-for-accessibility-links/#comments</comments>
		<pubDate>Mon, 04 May 2009 20:20:21 +0000</pubDate>
		<dc:creator>Léonie Watson</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Screen Readers]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://alastairc.ac/~tink/?p=11</guid>
		<description><![CDATA[Bruce Lawson recently asked whether adding rel=accessibility to the HTMl 5 specification was a good idea. Among the initial comments, Jared Smith noted that getting assistive technologies to support the idea might be a problem. For the major screen readers at least, I thought it could be easily solved though.

Bruce&#8217;s idea went a little something [...]]]></description>
		<wfw:commentRss>http://tink.co.uk/2009/05/jaws-scripts-for-accessibility-links/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Guide to WCAG</title>
		<link>http://tink.co.uk/2009/02/guide-to-wcag/</link>
		<comments>http://tink.co.uk/2009/02/guide-to-wcag/#comments</comments>
		<pubDate>Sun, 01 Feb 2009 19:12:34 +0000</pubDate>
		<dc:creator>Léonie Watson</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://alastairc.ac/~tink/?p=5</guid>
		<description><![CDATA[
The Web Content Accessibility Guidelines are developed by the Web Accessibility Initiative (WAI). The WAI are a branch of the World Wide Web Consortium (W3C), the organisation that provides guidelines and specifications for many web technologies.


The mission statement for the W3C explains the organisation&#8217;s aim:


&#8220;The World Wide Web Consortium (W3C) develops interoperable technologies (specifications, guidelines, [...]]]></description>
		<wfw:commentRss>http://tink.co.uk/2009/02/guide-to-wcag/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
