<?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: Simplish version 2.1.9</title>
	<atom:link href="http://simplish.pomfolio.com/dev/2009/05/26/simplish-219/feed/" rel="self" type="application/rss+xml" />
	<link>http://simplish.pomfolio.com/dev/2009/05/26/simplish-219/</link>
	<description>is a kind of Scribbish</description>
	<lastBuildDate>Fri, 18 Jun 2010 07:29:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: josh</title>
		<link>http://simplish.pomfolio.com/dev/2009/05/26/simplish-219/comment-page-/#comment-84</link>
		<dc:creator>josh</dc:creator>
		<pubDate>Sun, 09 Aug 2009 05:14:38 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=92#comment-84</guid>
		<description>After &lt;a&gt;Brianna&lt;/a&gt; enlightened me a bit on the &lt;a href=&quot;http://www.w3.org/WAI/PF/aria/&quot; rel=&quot;nofollow&quot;&gt;WAI-ARIA&lt;/a&gt; proposals, I finally had time to get some education on the specifics of the &lt;code&gt;role&lt;/code&gt; attribute.

While the W3C validator will flunk the &lt;code&gt;role&lt;/code&gt; attribute, several other validators tentatively accept the proposed additions. The unofficially-declared WordPress preference is for &lt;a href=&quot;http://core.trac.wordpress.org/ticket/9408&quot; rel=&quot;nofollow&quot;&gt;accessibility over validation&lt;/a&gt;, so Simplish will follow that.

The &lt;code&gt;role&lt;/code&gt; attribute will remain in Simplish via the core engine&#039;s &lt;em&gt;get_search_form&lt;/em&gt;. If the resulting no-go at the W3C validator is a major problem at your site, you can override the default search form through several fairly well-known options, some of which are hinted at in &lt;a href=&quot;http://core.trac.wordpress.org/ticket/10108&quot; rel=&quot;nofollow&quot;&gt;this thread&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>After <a>Brianna</a> enlightened me a bit on the <a href="http://www.w3.org/WAI/PF/aria/" rel="nofollow">WAI-ARIA</a> proposals, I finally had time to get some education on the specifics of the <code>role</code> attribute.</p>
<p>While the W3C validator will flunk the <code>role</code> attribute, several other validators tentatively accept the proposed additions. The unofficially-declared WordPress preference is for <a href="http://core.trac.wordpress.org/ticket/9408" rel="nofollow">accessibility over validation</a>, so Simplish will follow that.</p>
<p>The <code>role</code> attribute will remain in Simplish via the core engine&#8217;s <em>get_search_form</em>. If the resulting no-go at the W3C validator is a major problem at your site, you can override the default search form through several fairly well-known options, some of which are hinted at in <a href="http://core.trac.wordpress.org/ticket/10108" rel="nofollow">this thread</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: josh</title>
		<link>http://simplish.pomfolio.com/dev/2009/05/26/simplish-219/comment-page-/#comment-83</link>
		<dc:creator>josh</dc:creator>
		<pubDate>Sat, 11 Jul 2009 01:06:03 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=92#comment-83</guid>
		<description>Discussion of the invalid attribute &lt;code&gt;role&lt;/code&gt; is &lt;a href=&quot;http://wordpress.org/support/topic/280103&quot; title=&quot;WordPress forums&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Discussion of the invalid attribute <code>role</code> is <a href="http://wordpress.org/support/topic/280103" title="WordPress forums" rel="nofollow">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: josh</title>
		<link>http://simplish.pomfolio.com/dev/2009/05/26/simplish-219/comment-page-1/#comment-82</link>
		<dc:creator>josh</dc:creator>
		<pubDate>Sat, 11 Jul 2009 01:04:57 +0000</pubDate>
		<guid isPermaLink="false">http://labs.utopian.net/blogs/simplish/?p=92#comment-82</guid>
		<description>A known issue in Simplish v2.1.9 with WordPress &#8805;2.8 is that the &lt;em&gt;get_search_form&lt;/em&gt; function produces output using a &lt;code&gt;role&lt;/code&gt; attribute not yet valid for XHTML 1.0. &lt;code&gt;Role&lt;/code&gt; is apparently part of (the stillborn?) XHTML 2.

So pages will fail most validators because of the search box in the sidebar.

No fix or change is planned for this issue. It will be remedied upstream in the core WordPress code.</description>
		<content:encoded><![CDATA[<p>A known issue in Simplish v2.1.9 with WordPress &ge;2.8 is that the <em>get_search_form</em> function produces output using a <code>role</code> attribute not yet valid for XHTML 1.0. <code>Role</code> is apparently part of (the stillborn?) XHTML 2.</p>
<p>So pages will fail most validators because of the search box in the sidebar.</p>
<p>No fix or change is planned for this issue. It will be remedied upstream in the core WordPress code.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
