<?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: Hidden barriers - bad language</title>
	<atom:link href="http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/</link>
	<description></description>
	<pubDate>Thu, 28 Aug 2008 03:39:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Ben 'Cerbera' Millar</title>
		<link>http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/#comment-30697</link>
		<dc:creator>Ben 'Cerbera' Millar</dc:creator>
		<pubDate>Sun, 05 Aug 2007 20:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-bad-language/#comment-30697</guid>
		<description>I've commented on this in &lt;a href="http://projectcerbera.com/blog/2007/08#lang-changes" rel="nofollow"&gt;Absent lang on Root Element&lt;/a&gt;. Basically: I'm pretty sure the screen reader is wrong and &lt;code&gt;&#60;i&#62;&lt;/code&gt; is a sensible choice.

Responses on my comment should go here, since this is where the discussion is taking place.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve commented on this in <a href="http://projectcerbera.com/blog/2007/08#lang-changes" rel="nofollow">Absent lang on Root Element</a>. Basically: I&#8217;m pretty sure the screen reader is wrong and <code>&lt;i&gt;</code> is a sensible choice.</p>
<p>Responses on my comment should go here, since this is where the discussion is taking place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben 'Cerbera' Millar</title>
		<link>http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/#comment-30511</link>
		<dc:creator>Ben 'Cerbera' Millar</dc:creator>
		<pubDate>Sat, 04 Aug 2007 04:13:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-bad-language/#comment-30511</guid>
		<description>I've written &lt;a href="http://projectcerbera.com/blog/2007/08#lang-changes" rel="nofollow"&gt;Absent &lt;code&gt;lang&lt;/code&gt; on Root Element&lt;/a&gt; to get around the problem I was having. The code for that entry is what I was trying to use here earlier, except I wasn't including &lt;code&gt;&#60;p&#62;&lt;/code&gt;.

(Commenting on my comment should happen here, since this is where the discussion is taking place.)

The comments here allow some &lt;acronym title="Hypertext Markup Language"&gt;HTML&lt;/acronym&gt;. But if you use an element which isn't allowed, some sort of Out of Cheese Error occurs on the server which results in a Connection was reset for the client. &lt;a href="http://cheeaun.phoenity.com/weblog/2005/07/commenting-system-in-weblogs.html" title="Commenting systems in weblogs" rel="nofollow"&gt;Commenting systems are difficult&lt;/a&gt;, so please don't take my niggle reports as criticisms. :)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve written <a href="http://projectcerbera.com/blog/2007/08#lang-changes" rel="nofollow">Absent <code>lang</code> on Root Element</a> to get around the problem I was having. The code for that entry is what I was trying to use here earlier, except I wasn&#8217;t including <code>&lt;p&gt;</code>.</p>
<p>(Commenting on my comment should happen here, since this is where the discussion is taking place.)</p>
<p>The comments here allow some <acronym title="Hypertext Markup Language">HTML</acronym>. But if you use an element which isn&#8217;t allowed, some sort of Out of Cheese Error occurs on the server which results in a Connection was reset for the client. <a href="http://cheeaun.phoenity.com/weblog/2005/07/commenting-system-in-weblogs.html" title="Commenting systems in weblogs" rel="nofollow">Commenting systems are difficult</a>, so please don&#8217;t take my niggle reports as criticisms. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bim</title>
		<link>http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/#comment-30470</link>
		<dc:creator>Bim</dc:creator>
		<pubDate>Fri, 03 Aug 2007 17:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-bad-language/#comment-30470</guid>
		<description>&lt;p&gt;Ok Jack, here's the test, first we have the French language attribute applied to the &#60;em&#62; tag,&lt;em lang="fr"&gt;c'est la vie&lt;/em&gt;. Then we do the same thing using the &#60;i&#62; tag, &lt;i lang="fr"&gt;c'est la vie&lt;/i&gt;. This was originally done on a test page that was checked as valid XHTML Transitional, so if wordPress makes the attributes disappear, at least I know it's not due to faulty code.
&lt;/p&gt;
The audible output of both seems to be identical, which is what I would expect, I haven't ever heard any tone changes due to using any specific element.  

However, there are plenty of more experienced JAWS users out there than I am, Adrian, for example, perhaps one of you could answer the question: does JAWS give any tone indication that a piece of text has been given emphasis either by use of the &#60;em&#62; element or the &#60;strong&#62; element??</description>
		<content:encoded><![CDATA[<p>Ok Jack, here&#8217;s the test, first we have the French language attribute applied to the &lt;em&gt; tag,<em lang="fr">c&#8217;est la vie</em>. Then we do the same thing using the &lt;i&gt; tag, <i lang="fr">c&#8217;est la vie</i>. This was originally done on a test page that was checked as valid XHTML Transitional, so if wordPress makes the attributes disappear, at least I know it&#8217;s not due to faulty code.
</p>
<p>The audible output of both seems to be identical, which is what I would expect, I haven&#8217;t ever heard any tone changes due to using any specific element.  </p>
<p>However, there are plenty of more experienced JAWS users out there than I am, Adrian, for example, perhaps one of you could answer the question: does JAWS give any tone indication that a piece of text has been given emphasis either by use of the &lt;em&gt; element or the &lt;strong&gt; element??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JackP</title>
		<link>http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/#comment-30450</link>
		<dc:creator>JackP</dc:creator>
		<pubDate>Fri, 03 Aug 2007 15:01:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-bad-language/#comment-30450</guid>
		<description>Hmm. It obviously doesn't work here: looking at the source, it appears that while the italic and emphasis elements have been retained, it has actually removed the language attributes inside 'em both.

Bim - you couldn't try knocking up a quick test of that could you, and let me know how it sounds?</description>
		<content:encoded><![CDATA[<p>Hmm. It obviously doesn&#8217;t work here: looking at the source, it appears that while the italic and emphasis elements have been retained, it has actually removed the language attributes inside &#8216;em both.</p>
<p>Bim - you couldn&#8217;t try knocking up a quick test of that could you, and let me know how it sounds?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JackP</title>
		<link>http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/#comment-30449</link>
		<dc:creator>JackP</dc:creator>
		<pubDate>Fri, 03 Aug 2007 14:59:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-bad-language/#comment-30449</guid>
		<description>Bim, I deliberately used i rather than em, because I wasn't seeking to add emphasis: I was presuming that there would - for example - be an audible cue because of a change in accent or tone that &lt;i&gt;c'est la vie&lt;/i&gt; was in french, and therefore I used i only to attempt to give an equivalent visual cue.

If I was attempting to add emphasis, then I would have used &lt;em&gt;c'est la vie&lt;/em&gt; like so! 

Hopefully, the screenreader will have pronounced both of them in french, but have added emphasis to the second...</description>
		<content:encoded><![CDATA[<p>Bim, I deliberately used i rather than em, because I wasn&#8217;t seeking to add emphasis: I was presuming that there would - for example - be an audible cue because of a change in accent or tone that <i>c&#8217;est la vie</i> was in french, and therefore I used i only to attempt to give an equivalent visual cue.</p>
<p>If I was attempting to add emphasis, then I would have used <em>c&#8217;est la vie</em> like so! </p>
<p>Hopefully, the screenreader will have pronounced both of them in french, but have added emphasis to the second&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bim</title>
		<link>http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/#comment-30397</link>
		<dc:creator>Bim</dc:creator>
		<pubDate>Fri, 03 Aug 2007 08:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-bad-language/#comment-30397</guid>
		<description>Jack,, sorry, I didn't comment on your technique about applying the LANG attribute to the &#60;i&#62; element.  Neat idea. giving a visual clue that the language is different. It might not be ideal for entire paragraphs, people with dyslexia find italics more difficult to read, but it's a great idea for short phrases.

I didn't notice any difference in the audible output tone though. I don't know of any emphasis elements that do change screen reader tone, does anyone else?</description>
		<content:encoded><![CDATA[<p>Jack,, sorry, I didn&#8217;t comment on your technique about applying the LANG attribute to the &lt;i&gt; element.  Neat idea. giving a visual clue that the language is different. It might not be ideal for entire paragraphs, people with dyslexia find italics more difficult to read, but it&#8217;s a great idea for short phrases.</p>
<p>I didn&#8217;t notice any difference in the audible output tone though. I don&#8217;t know of any emphasis elements that do change screen reader tone, does anyone else?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bim</title>
		<link>http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/#comment-30396</link>
		<dc:creator>Bim</dc:creator>
		<pubDate>Fri, 03 Aug 2007 08:10:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-bad-language/#comment-30396</guid>
		<description>Good post Adrian, and the point's well made.  If the page is coded as having the wrong natural language from the start, screen readers will mispronounce everything. It's good that JAWS has an "ignore languages" setting, but I wonder if all of the screen readers  have one.</description>
		<content:encoded><![CDATA[<p>Good post Adrian, and the point&#8217;s well made.  If the page is coded as having the wrong natural language from the start, screen readers will mispronounce everything. It&#8217;s good that JAWS has an &#8220;ignore languages&#8221; setting, but I wonder if all of the screen readers  have one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Higginbotham</title>
		<link>http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/#comment-30312</link>
		<dc:creator>Adrian Higginbotham</dc:creator>
		<pubDate>Thu, 02 Aug 2007 10:51:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-bad-language/#comment-30312</guid>
		<description>and of course specifying the correct language in the first place is rather important, &lt;code&gt;&lt;a href="http://accessbrit.wordpress.com/2007/07/06/accessibility-and-internationalisation-are-related/" rel="nofollow"&gt;see my recent post&lt;/a&gt;&lt;/code&gt; re exactly this problem.</description>
		<content:encoded><![CDATA[<p>and of course specifying the correct language in the first place is rather important, <code><a href="http://accessbrit.wordpress.com/2007/07/06/accessibility-and-internationalisation-are-related/" rel="nofollow">see my recent post</a></code> re exactly this problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bim</title>
		<link>http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/#comment-30234</link>
		<dc:creator>Bim</dc:creator>
		<pubDate>Wed, 01 Aug 2007 17:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-bad-language/#comment-30234</guid>
		<description>Erk, did you use any bad language?  :)  What I mean is did you use anything other than alpha numeric or standard punctuation ?  If you'd like to e-mail me with the message I'll see if there's any reason within the message, and send back suggestions.  My e-mail address is &lt;a href="mailto:bim.egan@rnib.org.uk" rel="nofollow"&gt;bim.egan@rnib.org.uk&lt;/a&gt;;</description>
		<content:encoded><![CDATA[<p>Erk, did you use any bad language?  :)  What I mean is did you use anything other than alpha numeric or standard punctuation ?  If you&#8217;d like to e-mail me with the message I&#8217;ll see if there&#8217;s any reason within the message, and send back suggestions.  My e-mail address is <a href="mailto:bim.egan@rnib.org.uk" rel="nofollow">bim.egan@rnib.org.uk</a>;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben 'Cerbera' Millar</title>
		<link>http://www.rnib.org.uk/wacblog/internationalisation/hidden-barriers-bad-language/#comment-30230</link>
		<dc:creator>Ben 'Cerbera' Millar</dc:creator>
		<pubDate>Wed, 01 Aug 2007 17:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.rnib.org.uk/wacblog/articles/hidden-barriers/hidden-barriers-bad-language/#comment-30230</guid>
		<description>Gah, getting more "Connect was reset" errors when trying to reply to this article. :-(</description>
		<content:encoded><![CDATA[<p>Gah, getting more &#8220;Connect was reset&#8221; errors when trying to reply to this article. :-(</p>
]]></content:encoded>
	</item>
</channel>
</rss>
