<?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"
	>
<channel>
	<title>Comments on: The Sound of the Accessible Title Tag Separator</title>
	<atom:link href="http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/</link>
	<description>A pragmatic approach to web standards and accessibility</description>
	<pubDate>Sun, 06 Jul 2008 08:28:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Tilgjengelig tittelstruktur - bza.no</title>
		<link>http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/#comment-42504</link>
		<dc:creator>Tilgjengelig tittelstruktur - bza.no</dc:creator>
		<pubDate>Thu, 01 May 2008 17:48:41 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=15#comment-42504</guid>
		<description>[...] elementene i tittelen er litt estetikk og personlige preferanser. Det man kan tenke over er hvordan tegnet man separerer elementene med hørers ut. Min bindestrek vil uttales som &#8220;em dash&#8221;, noe som jeg mener kan forsvares som [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] elementene i tittelen er litt estetikk og personlige preferanser. Det man kan tenke over er hvordan tegnet man separerer elementene med hørers ut. Min bindestrek vil uttales som &#8220;em dash&#8221;, noe som jeg mener kan forsvares som [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Content Writing Advice &#171; Nice, Smile</title>
		<link>http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/#comment-33038</link>
		<dc:creator>Content Writing Advice &#171; Nice, Smile</dc:creator>
		<pubDate>Fri, 25 Jan 2008 21:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=15#comment-33038</guid>
		<description>[...] Accessible Title Tag Separator Sounds The site has souns clips of how the title tag separators that are commonly used sound to people that &#60;em&#62;hear&#60;/em&#62; the internet. Lightly touches on the proper use of the separtors used in title tags as well. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Accessible Title Tag Separator Sounds The site has souns clips of how the title tag separators that are commonly used sound to people that &lt;em&gt;hear&lt;/em&gt; the internet. Lightly touches on the proper use of the separtors used in title tags as well. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Data Tramp &#187; Getting seen by the blind</title>
		<link>http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/#comment-18936</link>
		<dc:creator>Data Tramp &#187; Getting seen by the blind</dc:creator>
		<pubDate>Wed, 12 Sep 2007 01:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=15#comment-18936</guid>
		<description>[...] I don&#8217;t think the average person needs a marketing expert to tell them that a trained broadcaster reading content will be more pleasant sounding than a computerized screen reader &#8211; especially on sites with hard to pronounce locations, industry terms or acronyms. Recording an audio alternative to text content on the site will also ensure proper pronunciation of complicated words. Link it at the top or as an item in internal navigation - or offer it as a hidden link at the top of each section of content. All love for Freedom Scientific, but if I were a corporation I wouldn&#8217;t want to trust how my marketing sounds to JAWS. Might as well have a speak and spell read beer commercials. For the uninitiated, listen to JAWS read punctuation. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I don&rsquo;t think the average person needs a marketing expert to tell them that a trained broadcaster reading content will be more pleasant sounding than a computerized screen reader &ndash; especially on sites with hard to pronounce locations, industry terms or acronyms. Recording an audio alternative to text content on the site will also ensure proper pronunciation of complicated words. Link it at the top or as an item in internal navigation - or offer it as a hidden link at the top of each section of content. All love for Freedom Scientific, but if I were a corporation I wouldn&#8217;t want to trust how my marketing sounds to JAWS. Might as well have a speak and spell read beer commercials. For the uninitiated, listen to JAWS read punctuation. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fixing my Wordpress Title Tags - MeganJack.com</title>
		<link>http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/#comment-897</link>
		<dc:creator>Fixing my Wordpress Title Tags - MeganJack.com</dc:creator>
		<pubDate>Tue, 21 Nov 2006 21:24:40 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=15#comment-897</guid>
		<description>[...] That still has the &#187; characters so I replaced those with hyphens (when choosing a title separator, think about how a screen reader would read it. &#187; reads &#8220;right double angle bracket&#8221;. No good. I used to like &#124; but that is read as &#8220;vertical bar&#8221;. Also no good. A plain old &#8220;dash&#8221; or &#8220;colon&#8221; work best). [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] That still has the &raquo; characters so I replaced those with hyphens (when choosing a title separator, think about how a screen reader would read it. &raquo; reads &#8220;right double angle bracket&#8221;. No good. I used to like | but that is read as &#8220;vertical bar&#8221;. Also no good. A plain old &#8220;dash&#8221; or &#8220;colon&#8221; work best). [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emil Virkki</title>
		<link>http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/#comment-317</link>
		<dc:creator>Emil Virkki</dc:creator>
		<pubDate>Tue, 28 Mar 2006 14:56:37 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=15#comment-317</guid>
		<description>&lt;p&gt;I like to use a double colon " :: ". It's easily distinguished from the surrounding text as the colon appears twice, which is unnatural in normal text. The word colon is also short, so reading "colon colon" outloud doesn't require a lot of waiting.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I like to use a double colon &#8221; :: &#8220;. It&#8217;s easily distinguished from the surrounding text as the colon appears twice, which is unnatural in normal text. The word colon is also short, so reading &#8220;colon colon&#8221; outloud doesn&#8217;t require a lot of waiting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lymmo</title>
		<link>http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/#comment-285</link>
		<dc:creator>Lymmo</dc:creator>
		<pubDate>Tue, 28 Mar 2006 14:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=15#comment-285</guid>
		<description>&lt;p&gt;I think it's ironic that this website uses a dash in its own title...&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s ironic that this website uses a dash in its own title&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sandy</title>
		<link>http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/#comment-173</link>
		<dc:creator>sandy</dc:creator>
		<pubDate>Wed, 27 Jul 2005 08:49:47 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=15#comment-173</guid>
		<description>&lt;p&gt;I kind of like the look of this vertical swirl &#8747; (&#38;int;). But wondering what it is called in a screen reader... Unlike arrows, IE for Macs can actually parse this correctly. Another possibility is this variation on the pipe: &#166; (&#38;brvbar;) and I am also wondering what screen readers call this symbol.&lt;/p&gt; &lt;p&gt;Although subtle, I do like the interpunct, and I still like the pipe (after reading the various pros and cons). I also like the fact that the screen reader just reads short one syllable words for these entities.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I kind of like the look of this vertical swirl &int; (&amp;int;). But wondering what it is called in a screen reader&#8230; Unlike arrows, IE for Macs can actually parse this correctly. Another possibility is this variation on the pipe: &brvbar; (&amp;brvbar;) and I am also wondering what screen readers call this symbol.</p>
<p>Although subtle, I do like the interpunct, and I still like the pipe (after reading the various pros and cons). I also like the fact that the screen reader just reads short one syllable words for these entities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan</title>
		<link>http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/#comment-147</link>
		<dc:creator>Bryan</dc:creator>
		<pubDate>Wed, 08 Jun 2005 04:49:44 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=15#comment-147</guid>
		<description>&lt;p&gt;If I'm separating a page title from  a site title, would it make sense to separate them with the '@' symbol? Not only would it make semantic sense, but I'm guessing the screen reader would pronounce it as "at"?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>If I&#8217;m separating a page title from  a site title, would it make sense to separate them with the &#8216;@&#8217; symbol? Not only would it make semantic sense, but I&#8217;m guessing the screen reader would pronounce it as &#8220;at&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastian Crump</title>
		<link>http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/#comment-126</link>
		<dc:creator>Sebastian Crump</dc:creator>
		<pubDate>Wed, 20 Apr 2005 12:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=15#comment-126</guid>
		<description>&lt;p&gt;Do remember that JAWS is not the only screen-reader and others can read differently.&lt;/p&gt; &lt;p&gt;Sometimes what is spoken will depend on context. For example, 1-10 may read as "1 minus 10", not "1 dash 10" or the ideal meaning "1 to 10"&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Do remember that JAWS is not the only screen-reader and others can read differently.</p>
<p>Sometimes what is spoken will depend on context. For example, 1-10 may read as &#8220;1 minus 10&#8243;, not &#8220;1 dash 10&#8243; or the ideal meaning &#8220;1 to 10&#8243;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sunny</title>
		<link>http://www.standards-schmandards.com/2004/the-sound-of-the-accessible-title-tag-separator/#comment-109</link>
		<dc:creator>Sunny</dc:creator>
		<pubDate>Wed, 30 Mar 2005 14:01:25 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/?p=15#comment-109</guid>
		<description>&lt;p&gt;I'm curious how â€¹, the single right-pointing angle quote (&#38;rsaquo;)	 sounds in jaws.&lt;/p&gt; &lt;p&gt;Hopefully not "single right-pointing angle quote" !&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I&#8217;m curious how â€¹, the single right-pointing angle quote (&amp;rsaquo;)	 sounds in jaws.</p>
<p>Hopefully not &#8220;single right-pointing angle quote&#8221; !</p>
]]></content:encoded>
	</item>
</channel>
</rss>
