<?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: Surprise! Your &#8220;semantic, accessible, search engine friendly&#8221; WordPress theme is none of the above.</title>
	<atom:link href="http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/</link>
	<description></description>
	<lastBuildDate>Fri, 23 Apr 2010 15:46:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: wp-popular.com &#187; Blog Archive &#187; Surprise! Your “semantic, accessible, search engine friendly” WordPress theme is none of the above. &#8211; Bushido Designs Web Development Blog</title>
		<link>http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/comment-page-1/#comment-81</link>
		<dc:creator>wp-popular.com &#187; Blog Archive &#187; Surprise! Your “semantic, accessible, search engine friendly” WordPress theme is none of the above. &#8211; Bushido Designs Web Development Blog</dc:creator>
		<pubDate>Fri, 23 Apr 2010 15:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.bushidodesigns.net/blog/?p=27#comment-81</guid>
		<description>[...] Surprise! Your “semantic, accessible, search engine friendly” WordPress theme is none of the abo... Tags: [...]</description>
		<content:encoded><![CDATA[<p>[...] Surprise! Your “semantic, accessible, search engine friendly” WordPress theme is none of the abo&#8230; Tags: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Welcome to our website.Demo Site</title>
		<link>http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/comment-page-1/#comment-80</link>
		<dc:creator>&#187; Welcome to our website.Demo Site</dc:creator>
		<pubDate>Wed, 07 Apr 2010 18:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.bushidodesigns.net/blog/?p=27#comment-80</guid>
		<description>[...] demonstration accessibility website. Built using Wordpress it features a theme based on a design by Bushido Designs with the addition of a font sizer plugin from Permanent [...]</description>
		<content:encoded><![CDATA[<p>[...] demonstration accessibility website. Built using Wordpress it features a theme based on a design by Bushido Designs with the addition of a font sizer plugin from Permanent [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: soqijebage</title>
		<link>http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/comment-page-1/#comment-77</link>
		<dc:creator>soqijebage</dc:creator>
		<pubDate>Sat, 22 Aug 2009 18:35:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.bushidodesigns.net/blog/?p=27#comment-77</guid>
		<description>&lt;strong&gt;soqijebage...&lt;/strong&gt;

 &lt; a href=http://namelindablog.info/b5-bio-bryan/&gt;B5 Bio Bryan&lt; / a &gt; ...</description>
		<content:encoded><![CDATA[<p>&lt;strong&gt;soqijebage&#8230;&lt;/strong&gt;</p>
<p> &lt; a href=http://namelindablog.info/b5-bio-bryan/&gt;B5 Bio Bryan&lt; / a &gt; &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Songket WordPress Theme Review - Dani Iswara .Net</title>
		<link>http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/comment-page-1/#comment-70</link>
		<dc:creator>Songket WordPress Theme Review - Dani Iswara .Net</dc:creator>
		<pubDate>Sat, 30 May 2009 12:33:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.bushidodesigns.net/blog/?p=27#comment-70</guid>
		<description>[...] May 30, 2009] More challenges, theme switcher, please check Semantic, Accessible, SEO Friendly WordPress Theme by Dean [...]</description>
		<content:encoded><![CDATA[<p>[...] May 30, 2009] More challenges, theme switcher, please check Semantic, Accessible, SEO Friendly WordPress Theme by Dean [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: showard</title>
		<link>http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/comment-page-1/#comment-68</link>
		<dc:creator>showard</dc:creator>
		<pubDate>Sun, 03 May 2009 02:15:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.bushidodesigns.net/blog/?p=27#comment-68</guid>
		<description>I&#039;ve been working on a local copy of the theme fixing bugs that I&#039;ve found:

- Styles added for &quot;blockquotes&quot; and unordered lists + list items.
- Page validation error when no custom fields are used on pages.  Further validation errors happen when user is logged in and viewing a single post.  Both fixed.
- Removed a duplicate &quot;Edit this Post&quot; link.
- Changed a forced &quot;the_author_firstname()&quot; and &quot;the_author_lastname()&quot; to &quot;the_author()&quot; as this setting can be managed by the users/contributors within their profile pages.  Forcing the prior setting requires users to set the information in their profile *and* removes the flexibility of the &quot;Display Name Publicly As:&quot; dropdown menu.

-- Patch File --

Patch files are to be used on installations that have not been modified.  Patch files are created not to overwrite other files like &quot;sprites.png&quot; (which contains your site&#039;s logo).  It can be downloaded here: http://www.stfu.org/2_1_0-to-2_1_1.patch  or in zip form: http://www.stfu.org/2_1_0-to-2_1_1.zip

Apply a patch from your shell account by copying the patch file into your /wp-content/themes/Access directory and typing:  patch &lt; 2_1_0-to-2_1_1.patch

-- Full Theme --

http://www.stfu.org/Access-2_1_1-with-bugfixes.zip

NOTE:  Unzipping over your existing Access directory will cause it to overwrite your custom &quot;sprites.png.&quot;  Be sure to make a backup of your existing theme directory before unzipping.</description>
		<content:encoded><![CDATA[<p>I&#039;ve been working on a local copy of the theme fixing bugs that I&#039;ve found:</p>
<p>- Styles added for &quot;blockquotes&quot; and unordered lists + list items.<br />
- Page validation error when no custom fields are used on pages.  Further validation errors happen when user is logged in and viewing a single post.  Both fixed.<br />
- Removed a duplicate &quot;Edit this Post&quot; link.<br />
- Changed a forced &quot;the_author_firstname()&quot; and &quot;the_author_lastname()&quot; to &quot;the_author()&quot; as this setting can be managed by the users/contributors within their profile pages.  Forcing the prior setting requires users to set the information in their profile *and* removes the flexibility of the &quot;Display Name Publicly As:&quot; dropdown menu.</p>
<p>&#8211; Patch File &#8211;</p>
<p>Patch files are to be used on installations that have not been modified.  Patch files are created not to overwrite other files like &quot;sprites.png&quot; (which contains your site&#039;s logo).  It can be downloaded here: <a href="http://www.stfu.org/2_1_0-to-2_1_1.patch" rel="nofollow">http://www.stfu.org/2_1_0-to-2_1_1.patch</a>  or in zip form: <a href="http://www.stfu.org/2_1_0-to-2_1_1.zip" rel="nofollow">http://www.stfu.org/2_1_0-to-2_1_1.zip</a></p>
<p>Apply a patch from your shell account by copying the patch file into your /wp-content/themes/Access directory and typing:  patch &lt; 2_1_0-to-2_1_1.patch</p>
<p>&#8211; Full Theme &#8211;</p>
<p><a href="http://www.stfu.org/Access-2_1_1-with-bugfixes.zip" rel="nofollow">http://www.stfu.org/Access-2_1_1-with-bugfixes.zip</a></p>
<p>NOTE:  Unzipping over your existing Access directory will cause it to overwrite your custom &quot;sprites.png.&quot;  Be sure to make a backup of your existing theme directory before unzipping.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dean</title>
		<link>http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/comment-page-1/#comment-67</link>
		<dc:creator>dean</dc:creator>
		<pubDate>Thu, 30 Apr 2009 09:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.bushidodesigns.net/blog/?p=27#comment-67</guid>
		<description>Mayor: contact forms usually aren&#039;t a problem when it comes to accessibility because they are fairly simple. I have only used one with Wordpress, so I can&#039;t tell you which one is the best. But you need to look for two things:

1. Each field in the form needs to have a label attached using the &quot;for&quot; attribute like this:

&lt;label for=&quot;name&quot;&gt;Name:&lt;/label&gt;&lt;input type=&quot;text&quot; id=&quot;name&quot; /&gt;

2. Captchas are notorious for being inaccessible. So I would look for one that uses Akamai to screen out spam, or one that uses a simple question (like &quot;what is 2 + 2&quot;), rather than an image.

John: yes, the default theme uses a basic &quot;css reset&quot; to make everything the same size. If you want to modify those things, you can do them in the default.css file. To make headers bigger just do something like:

h3{font-size:120%}

The high contrast theme doesn&#039;t set font sizes for headers, it uses the browser defaults, which is generally what you want for accessibility.</description>
		<content:encoded><![CDATA[<p>Mayor: contact forms usually aren&#039;t a problem when it comes to accessibility because they are fairly simple. I have only used one with Wordpress, so I can&#039;t tell you which one is the best. But you need to look for two things:</p>
<p>1. Each field in the form needs to have a label attached using the &quot;for&quot; attribute like this:</p>
<p>&lt;label for=&quot;name&quot;&gt;Name:&lt;/label&gt;&lt;input type=&quot;text&quot; id=&quot;name&quot; /&gt;</p>
<p>2. Captchas are notorious for being inaccessible. So I would look for one that uses Akamai to screen out spam, or one that uses a simple question (like &quot;what is 2 + 2&quot;), rather than an image.</p>
<p>John: yes, the default theme uses a basic &quot;css reset&quot; to make everything the same size. If you want to modify those things, you can do them in the default.css file. To make headers bigger just do something like:</p>
<p>h3{font-size:120%}</p>
<p>The high contrast theme doesn&#039;t set font sizes for headers, it uses the browser defaults, which is generally what you want for accessibility.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: showard</title>
		<link>http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/comment-page-1/#comment-64</link>
		<dc:creator>showard</dc:creator>
		<pubDate>Thu, 30 Apr 2009 03:48:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.bushidodesigns.net/blog/?p=27#comment-64</guid>
		<description>Oops, apparently it didn&#039;t like the &quot;pre&quot; tags... paste everything inbetween the open and close &quot;pre&quot; tags into the appropriate CSS file(s).</description>
		<content:encoded><![CDATA[<p>Oops, apparently it didn&#039;t like the &quot;pre&quot; tags&#8230; paste everything inbetween the open and close &quot;pre&quot; tags into the appropriate CSS file(s).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: showard</title>
		<link>http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/comment-page-1/#comment-63</link>
		<dc:creator>showard</dc:creator>
		<pubDate>Thu, 30 Apr 2009 03:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.bushidodesigns.net/blog/?p=27#comment-63</guid>
		<description>John -

I noticed it too and (though it may not be the correct way as I&#039;m not a CSS/web designer) pasting this into the &quot;default.css&quot; (in wp-content/themes/Access/css/default.css) worked:

&lt;pre&gt;.post ul li {background:url(../img/sprites.png) no-repeat left -400px;padding-left:12px;margin:.75em 0;color:#666}&lt;/pre&gt;

Note: This has to be done to both &quot;default.css&quot; and &quot;print.css.&quot;  As for the high contrast version (wp-content/themes/Access/css/hc.css), this line must be used until a high contrast &quot;sprites.png&quot; is created:

&lt;pre&gt;.post ul li {list-style:square;padding-left:12px;margin:.75em 0;color:#FFFF00}&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>John -</p>
<p>I noticed it too and (though it may not be the correct way as I&#039;m not a CSS/web designer) pasting this into the &quot;default.css&quot; (in wp-content/themes/Access/css/default.css) worked:</p>
<p>&lt;pre&gt;.post ul li {background:url(../img/sprites.png) no-repeat left -400px;padding-left:12px;margin:.75em 0;color:#666}&lt;/pre&gt;</p>
<p>Note: This has to be done to both &quot;default.css&quot; and &quot;print.css.&quot;  As for the high contrast version (wp-content/themes/Access/css/hc.css), this line must be used until a high contrast &quot;sprites.png&quot; is created:</p>
<p>&lt;pre&gt;.post ul li {list-style:square;padding-left:12px;margin:.75em 0;color:#FFFF00}&lt;/pre&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JohnGaltWasRight</title>
		<link>http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/comment-page-1/#comment-62</link>
		<dc:creator>JohnGaltWasRight</dc:creator>
		<pubDate>Wed, 29 Apr 2009 20:32:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.bushidodesigns.net/blog/?p=27#comment-62</guid>
		<description>While testing this theme I noticed that unordered lists are not indented nor show bullets. Also setting the various headings (H3, H4, etc..) does not affect text size. Are these intentional settings for reasons I do not understand or functions that I should set up myself (how)? Thanks for taking an interest in a much needed area of WordPress development. 

~John Galt</description>
		<content:encoded><![CDATA[<p>While testing this theme I noticed that unordered lists are not indented nor show bullets. Also setting the various headings (H3, H4, etc..) does not affect text size. Are these intentional settings for reasons I do not understand or functions that I should set up myself (how)? Thanks for taking an interest in a much needed area of WordPress development. </p>
<p>~John Galt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mayor_of_Kentonville.com</title>
		<link>http://www.bushidodesigns.net/blog/semantic-accessible-seo-friendly-wordpress-theme/comment-page-1/#comment-61</link>
		<dc:creator>Mayor_of_Kentonville.com</dc:creator>
		<pubDate>Wed, 29 Apr 2009 03:33:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.bushidodesigns.net/blog/?p=27#comment-61</guid>
		<description>This seem to be a thread for accessibility minded individuals. So I will pose a question, if this is improper I apologize. What contact form plug-in has the most complete accessibility features? Also does anyone know a website or forum that discusses accessibility and WordPress concerns . Thank you.</description>
		<content:encoded><![CDATA[<p>This seem to be a thread for accessibility minded individuals. So I will pose a question, if this is improper I apologize. What contact form plug-in has the most complete accessibility features? Also does anyone know a website or forum that discusses accessibility and WordPress concerns . Thank you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
