<?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: When Accessibility is Not Your Problem</title>
	<atom:link href="http://learningtheworld.eu/2007/not-your-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://learningtheworld.eu/2007/not-your-problem/</link>
	<description></description>
	<lastBuildDate>Fri, 15 Oct 2010 13:07:20 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.1</generator>
	<item>
		<title>By: wendy</title>
		<link>http://learningtheworld.eu/2007/not-your-problem/comment-page-1/#comment-29782</link>
		<dc:creator><![CDATA[wendy]]></dc:creator>
		<pubDate>Fri, 14 Sep 2007 09:55:44 +0000</pubDate>
		<guid isPermaLink="false">http://learningtheworld.eu/2007/not-your-problem/#comment-29782</guid>
		<description><![CDATA[&lt;p&gt;the more we coddle the browsers with hacks and workarounds the longer it will take them to get their asses into gear because we sweetly make them look good to the people who pay for the licenses etc - im not saying i don&#039;t do it but i do see a good reason to refuse&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>the more we coddle the browsers with hacks and workarounds the longer it will take them to get their asses into gear because we sweetly make them look good to the people who pay for the licenses etc &#8211; im not saying i don&#8217;t do it but i do see a good reason to refuse</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paulio</title>
		<link>http://learningtheworld.eu/2007/not-your-problem/comment-page-1/#comment-14935</link>
		<dc:creator><![CDATA[Paulio]]></dc:creator>
		<pubDate>Sun, 10 Jun 2007 00:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://learningtheworld.eu/2007/not-your-problem/#comment-14935</guid>
		<description><![CDATA[&lt;p&gt;The whole issue of who is to blame or rather who should have the responsibility is a very tricky one. I have a lot of sympathy with the &#8220;blame the browser&#8221; stance but obviously you can&#8217;t simply say to a client, &#8220;tough luck it doesn&#8217;t work, if you want to use the site get a new browser&#8221;. Then again, the more you pander to the problem browser the longer they won&#8217;t fix the problems, like I said tricky. I mention this because I think it is relevant to your question about link texts. I believe the point made in the session was that you can derive the context from the hierarchy and therefore shouldn&#8217;t have to duplicate the text. Whereas I believe your argument is that this is nice in principle but the the readers don&#8217;t utilise the context? Again, who&#8217;s responsibility is it?&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>The whole issue of who is to blame or rather who should have the responsibility is a very tricky one. I have a lot of sympathy with the &ldquo;blame the browser&rdquo; stance but obviously you can&rsquo;t simply say to a client, &ldquo;tough luck it doesn&rsquo;t work, if you want to use the site get a new browser&rdquo;. Then again, the more you pander to the problem browser the longer they won&rsquo;t fix the problems, like I said tricky. I mention this because I think it is relevant to your question about link texts. I believe the point made in the session was that you can derive the context from the hierarchy and therefore shouldn&rsquo;t have to duplicate the text. Whereas I believe your argument is that this is nice in principle but the the readers don&rsquo;t utilise the context? Again, who&rsquo;s responsibility is it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Kliehm</title>
		<link>http://learningtheworld.eu/2007/not-your-problem/comment-page-1/#comment-14742</link>
		<dc:creator><![CDATA[Martin Kliehm]]></dc:creator>
		<pubDate>Sat, 09 Jun 2007 03:18:27 +0000</pubDate>
		<guid isPermaLink="false">http://learningtheworld.eu/2007/not-your-problem/#comment-14742</guid>
		<description><![CDATA[&lt;p&gt;Tomas, could you elaborate a little? Does that mean that in your opinion all link texts pointing to the same URL have to be identical, or does that mean you think we don&#039;t need to care?&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Tomas, could you elaborate a little? Does that mean that in your opinion all link texts pointing to the same URL have to be identical, or does that mean you think we don&#8217;t need to care?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Caspers</title>
		<link>http://learningtheworld.eu/2007/not-your-problem/comment-page-1/#comment-14587</link>
		<dc:creator><![CDATA[Tomas Caspers]]></dc:creator>
		<pubDate>Fri, 08 Jun 2007 08:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://learningtheworld.eu/2007/not-your-problem/#comment-14587</guid>
		<description><![CDATA[&lt;blockquote&gt;&lt;p&gt;in Germany there is a consensus&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Just for the sake of accuracy, as this would include me: &#8722;1&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<blockquote><p>in Germany there is a consensus</p></blockquote>

<p>Just for the sake of accuracy, as this would include me: &minus;1</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Clark</title>
		<link>http://learningtheworld.eu/2007/not-your-problem/comment-page-1/#comment-14444</link>
		<dc:creator><![CDATA[Joe Clark]]></dc:creator>
		<pubDate>Thu, 07 Jun 2007 22:42:26 +0000</pubDate>
		<guid isPermaLink="false">http://learningtheworld.eu/2007/not-your-problem/#comment-14444</guid>
		<description><![CDATA[&lt;p&gt;When the notes are published, you will find that I never said pixel units causing unresizability is not a problem. I said that critics are constantly on our case about &lt;em&gt;px&lt;/em&gt; units, that they pick on standardistas who occasionally use it, and that they don&#039;t pick on the real offenders (the kind of people who also use 37 tables for layout). I explained that px is a relative unit and we may use any unit to size anything. IE6 and IE7 are broken. But the actual semantics of the pixel unit rarely come up for standards-compliant developers&#160;&#8212; maybe only in a copyright notice at the bottom of the page. They are scarcely ever used.&lt;/p&gt;

&lt;p&gt;The central point is that font resizing is a browser issue, not something that an â€œauthorâ€? has to worry about. So donâ€™t be ginning up your own JavaScript font-resizers. And I specifically stated that font resizing is not an  issue of â€œclassicâ€? accessibility for people with a visual handicap (as opposed to someone, including a senior citizen, with a correctable vision loss).&lt;/p&gt;

&lt;p&gt;So bravo for accuracy there.&lt;/p&gt;

&lt;p&gt;You arenâ€™t â€œceas[ing] to supportâ€? lists of links by writing link text that actually works and makes sense in your document. You just can&#8217;t have both: Your link text either works in context or it doesn&#039;t. Same for headlines. So let&#039;s not pretend that a list of headings or links is any form of guidance on how to write link or headline text.&lt;/p&gt;

&lt;p&gt;And, finally, I specifically and unambiguously stated that &lt;acronym title=&quot;Hypertext Markup Language&quot;&gt;HTML&lt;/acronym&gt; semantics should be followed. abbr and acronym should be used, but expansions should be limited to cases where a reasonable reader would misunderstand something&#160;&#8212; hence, no, you wouldn&#039;t expand â€œE. coliâ€? on a public-health site.&lt;/p&gt;

&lt;p&gt;So again, bravo on the accuracy there.&lt;/p&gt;

&lt;p&gt;The artist who drew sketches of the various speakers is a buxom blonde woman. Une fois encore, bravo.&lt;/p&gt;

&lt;p&gt;You could have come and said hello. Tomorrow you still could.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>When the notes are published, you will find that I never said pixel units causing unresizability is not a problem. I said that critics are constantly on our case about <em>px</em> units, that they pick on standardistas who occasionally use it, and that they don&#8217;t pick on the real offenders (the kind of people who also use 37 tables for layout). I explained that px is a relative unit and we may use any unit to size anything. IE6 and IE7 are broken. But the actual semantics of the pixel unit rarely come up for standards-compliant developers&nbsp;&mdash; maybe only in a copyright notice at the bottom of the page. They are scarcely ever used.</p>

<p>The central point is that font resizing is a browser issue, not something that an â€œauthorâ€? has to worry about. So donâ€™t be ginning up your own JavaScript font-resizers. And I specifically stated that font resizing is not an  issue of â€œclassicâ€? accessibility for people with a visual handicap (as opposed to someone, including a senior citizen, with a correctable vision loss).</p>

<p>So bravo for accuracy there.</p>

<p>You arenâ€™t â€œceas[ing] to supportâ€? lists of links by writing link text that actually works and makes sense in your document. You just can&rsquo;t have both: Your link text either works in context or it doesn&#8217;t. Same for headlines. So let&#8217;s not pretend that a list of headings or links is any form of guidance on how to write link or headline text.</p>

<p>And, finally, I specifically and unambiguously stated that <acronym title="Hypertext Markup Language">HTML</acronym> semantics should be followed. abbr and acronym should be used, but expansions should be limited to cases where a reasonable reader would misunderstand something&nbsp;&mdash; hence, no, you wouldn&#8217;t expand â€œE. coliâ€? on a public-health site.</p>

<p>So again, bravo on the accuracy there.</p>

<p>The artist who drew sketches of the various speakers is a buxom blonde woman. Une fois encore, bravo.</p>

<p>You could have come and said hello. Tomorrow you still could.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Kliehm</title>
		<link>http://learningtheworld.eu/2007/not-your-problem/comment-page-1/#comment-14454</link>
		<dc:creator><![CDATA[Martin Kliehm]]></dc:creator>
		<pubDate>Thu, 07 Jun 2007 22:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://learningtheworld.eu/2007/not-your-problem/#comment-14454</guid>
		<description><![CDATA[&lt;p&gt;Right, IE6 and IE7 are broken, but it is our responsibility to enable resizing. Of course standardistas rarely use &lt;em&gt;px&lt;/em&gt; units, but most indecent developers do. As long as &lt;acronym title=&quot;Internet Explorer&quot;&gt;IE&lt;/acronym&gt; is broken, they need to be educated about &lt;em&gt;em&lt;/em&gt; units.&lt;/p&gt;

&lt;p&gt;In the discussion about link texts in Germany there is a consensus that they can differ as long as the title clarifies the link target. However, creative headlines might have a literary value, but they do not enhance readability or understandability for cognitive disabled users. I prefer headlines that do make some sense apart from adding visual structure.&lt;/p&gt;

&lt;p&gt;Sorry for any inaccuracies, but that&#8217;s how I and other people I have spoken to interpreted your talk. I couldn&#8217;t check your presentation first because it was (and still is) not online. Of course I will say hello tomorrow. Still the original scetch was from a guy, his female designer colleague made a copy of it.  ;)&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Right, IE6 and IE7 are broken, but it is our responsibility to enable resizing. Of course standardistas rarely use <em>px</em> units, but most indecent developers do. As long as <acronym title="Internet Explorer">IE</acronym> is broken, they need to be educated about <em>em</em> units.</p>

<p>In the discussion about link texts in Germany there is a consensus that they can differ as long as the title clarifies the link target. However, creative headlines might have a literary value, but they do not enhance readability or understandability for cognitive disabled users. I prefer headlines that do make some sense apart from adding visual structure.</p>

<p>Sorry for any inaccuracies, but that&rsquo;s how I and other people I have spoken to interpreted your talk. I couldn&rsquo;t check your presentation first because it was (and still is) not online. Of course I will say hello tomorrow. Still the original scetch was from a guy, his female designer colleague made a copy of it.  <img src="http://learningtheworld.eu/wp-includes/images/smilies/icon_wink.gif" alt=";)" class="wp-smiley" /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
