<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: ARIAs with Flash, Flex, and AIR</title>
	<atom:link href="http://alastairc.ac/2009/09/arias-with-flash-flex-and-air/feed/" rel="self" type="application/rss+xml" />
	<link>http://alastairc.ac/2009/09/arias-with-flash-flex-and-air/</link>
	<description>Kything web interactions</description>
	<lastBuildDate>Fri, 13 Apr 2012 05:33:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: AlastairC</title>
		<link>http://alastairc.ac/2009/09/arias-with-flash-flex-and-air/comment-page-1/#comment-127428</link>
		<dc:creator>AlastairC</dc:creator>
		<pubDate>Tue, 22 Sep 2009 22:08:07 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/?p=542#comment-127428</guid>
		<description>&lt;ins&gt; is possible, although now I try it, you&#039;ll see I have setup styles that are more suited to the normal (such as it is) use as edited text.

Well, it kinda works?

Most of the other stuff is basically down to me not doing enough to the raw notes. Although the &lt;br&gt; tags are either intended, or it&#039;s how Wordpress is interpreting single breaks, but I don&#039;t see many of them.</description>
		<content:encoded><![CDATA[<p>&lt;ins&gt; is possible, although now I try it, you&#8217;ll see I have setup styles that are more suited to the normal (such as it is) use as edited text.</p>
<p>Well, it kinda works?</p>
<p>Most of the other stuff is basically down to me not doing enough to the raw notes. Although the &lt;br&gt; tags are either intended, or it&#8217;s how WordPress is interpreting single breaks, but I don&#8217;t see many of them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Millard</title>
		<link>http://alastairc.ac/2009/09/arias-with-flash-flex-and-air/comment-page-1/#comment-127426</link>
		<dc:creator>Ben Millard</dc:creator>
		<pubDate>Tue, 22 Sep 2009 20:02:34 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/?p=542#comment-127426</guid>
		<description>&lt;blockquote&gt;What’s the most suitable element for interjecting comments into an outline of someone else’s text in HTML 4 or 5?&lt;/blockquote&gt;

I would probably use &lt;code&gt;&lt;ins&gt;&lt;/code&gt; for this.

A few of your paragraphs in this and the previous article seem be using &lt;code&gt;&lt;br&gt;&lt;/code&gt; instead of &lt;code&gt;&lt;/p&gt;&lt;p&gt;&lt;/code&gt;, by the way.

Your list in the &quot;Pertinent WCAG 2 checkpoints&quot; section looks like it would suit &lt;code&gt;&lt;dl&gt;&lt;/code&gt;. Indeed, this seems a closer match than any other structure I know of, including the &lt;code&gt;&lt;p&gt;&lt;strong&gt;&lt;/code&gt; approach it currently takes.

How come you wrote ins-f5 instead of Ins+F5? (Both the casing and the punctuation you used are contrary to convention, at least on Windows.)

Finally, I&#039;m pretty sure the forward slashes to should not have spaces on either side when punctuating prose. &quot;Name/role/value&quot; should probably be &quot;Name, role and value&quot; since it is a list of features, not a list of interchangeable options.

Nothing significant, just a few bits and bobs I noticed.</description>
		<content:encoded><![CDATA[<blockquote><p>What’s the most suitable element for interjecting comments into an outline of someone else’s text in HTML 4 or 5?</p></blockquote>
<p>I would probably use <code>&lt;ins&gt;</code> for this.</p>
<p>A few of your paragraphs in this and the previous article seem be using <code>&lt;br&gt;</code> instead of <code>&lt;/p&gt;&lt;p&gt;</code>, by the way.</p>
<p>Your list in the &#8220;Pertinent WCAG 2 checkpoints&#8221; section looks like it would suit <code>&lt;dl&gt;</code>. Indeed, this seems a closer match than any other structure I know of, including the <code>&lt;p&gt;&lt;strong&gt;</code> approach it currently takes.</p>
<p>How come you wrote ins-f5 instead of Ins+F5? (Both the casing and the punctuation you used are contrary to convention, at least on Windows.)</p>
<p>Finally, I&#8217;m pretty sure the forward slashes to should not have spaces on either side when punctuating prose. &#8220;Name/role/value&#8221; should probably be &#8220;Name, role and value&#8221; since it is a list of features, not a list of interchangeable options.</p>
<p>Nothing significant, just a few bits and bobs I noticed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

