<?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: Proposed Public Sector Web Accessibility Guidelines</title>
	<atom:link href="http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/</link>
	<description>ranting and rambling to anyone willing to listen</description>
	<lastBuildDate>Sat, 11 Feb 2012 17:07:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: JackP</title>
		<link>http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/comment-page-1/#comment-21329</link>
		<dc:creator>JackP</dc:creator>
		<pubDate>Thu, 22 Nov 2007 21:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/#comment-21329</guid>
		<description>Julian -
I haven&#039;t got a definitive list of either what AT works with &lt;em&gt;or&lt;/em&gt; without postbacks. I don&#039;t particularly have access to AT; I&#039;m not disabled -- but you&#039;re right, it really &lt;em&gt;would&lt;/em&gt; be worthwhile knowing.

But it&#039;s as pointless banning &lt;em&gt;all&lt;/em&gt; javascript for no good reason as it is allowing javascript that discriminates against users. I don&#039;t have access to the tech myself, but it is a set of tests that needs doing.

And regarding the whole &quot;proposed public sector web guidelines&quot;, I think we&#039;re more waiting to see what the COI comes back with (of which more later)...</description>
		<content:encoded><![CDATA[<p>Julian -<br />
I haven&#8217;t got a definitive list of either what AT works with <em>or</em> without postbacks. I don&#8217;t particularly have access to AT; I&#8217;m not disabled &#8212; but you&#8217;re right, it really <em>would</em> be worthwhile knowing.</p>
<p>But it&#8217;s as pointless banning <em>all</em> javascript for no good reason as it is allowing javascript that discriminates against users. I don&#8217;t have access to the tech myself, but it is a set of tests that needs doing.</p>
<p>And regarding the whole &#8220;proposed public sector web guidelines&#8221;, I think we&#8217;re more waiting to see what the COI comes back with (of which more later)&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian</title>
		<link>http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/comment-page-1/#comment-21298</link>
		<dc:creator>Julian</dc:creator>
		<pubDate>Wed, 21 Nov 2007 11:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/#comment-21298</guid>
		<description>Well, bloody hell, I really thought this would get more attention/feedback....

Jack, can I raise C4 again... Do you know of a definitive list of AT that postback (and other javascript) works with (or that it doesn&#039;t work with!)? Unless that is available then C4 cannot realistically have the &#039;OR&#039; clause.</description>
		<content:encoded><![CDATA[<p>Well, bloody hell, I really thought this would get more attention/feedback&#8230;.</p>
<p>Jack, can I raise C4 again&#8230; Do you know of a definitive list of AT that postback (and other javascript) works with (or that it doesn&#8217;t work with!)? Unless that is available then C4 cannot realistically have the &#8216;OR&#8217; clause.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian</title>
		<link>http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/comment-page-1/#comment-18832</link>
		<dc:creator>Julian</dc:creator>
		<pubDate>Tue, 25 Sep 2007 08:58:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/#comment-18832</guid>
		<description>sorry, my point 3 should read I8 at the end. Seems that 8 followed by a closing parenthesis is converted to some sort of smug-looking face which obviously was not my intention.

J</description>
		<content:encoded><![CDATA[<p>sorry, my point 3 should read I8 at the end. Seems that 8 followed by a closing parenthesis is converted to some sort of smug-looking face which obviously was not my intention.</p>
<p>J</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian</title>
		<link>http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/comment-page-1/#comment-18831</link>
		<dc:creator>Julian</dc:creator>
		<pubDate>Tue, 25 Sep 2007 08:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/#comment-18831</guid>
		<description>&lt;em&gt;originally posted on public sector web managers forum - moved to here for completion&lt;/em&gt;

Jack

an ambitious and worthy project and sure to create discussion. here&#039;s my initial tuppence :

1) no mention of the validity of code (wcag1 3.2) I always thought this was perhaps *the* most important checkpoint of them all. If code doesn&#039;t validate to specified dtd how can we be sure that it will work as intended -&gt;should be critical.

2) no mention of table summaries. (Desirable?)

3)no mention of how to handle frames (maybe add to I 8)

4) re I 11: how exactly would you allow a form submission to be reversed? I&#039;m not being intentionally antagonistic, I really don&#039;t know.

5) re D12: should this be justified per se or right-aligned (both are poor practice [unless of course you happen to be writing in a R to L language!])

Julian</description>
		<content:encoded><![CDATA[<p><em>originally posted on public sector web managers forum &#8211; moved to here for completion</em></p>
<p>Jack</p>
<p>an ambitious and worthy project and sure to create discussion. here&#8217;s my initial tuppence :</p>
<p>1) no mention of the validity of code (wcag1 3.2) I always thought this was perhaps *the* most important checkpoint of them all. If code doesn&#8217;t validate to specified dtd how can we be sure that it will work as intended -&gt;should be critical.</p>
<p>2) no mention of table summaries. (Desirable?)</p>
<p>3)no mention of how to handle frames (maybe add to I <img src='http://www.thepickards.co.uk/wp-includes/images/smilies/icon_cool.gif' alt='8)' class='wp-smiley' /> </p>
<p>4) re I 11: how exactly would you allow a form submission to be reversed? I&#8217;m not being intentionally antagonistic, I really don&#8217;t know.</p>
<p>5) re D12: should this be justified per se or right-aligned (both are poor practice [unless of course you happen to be writing in a R to L language!])</p>
<p>Julian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seb</title>
		<link>http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/comment-page-1/#comment-18795</link>
		<dc:creator>Seb</dc:creator>
		<pubDate>Mon, 24 Sep 2007 14:27:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/#comment-18795</guid>
		<description>Wow - great start Jack.

I have signed up for the forum, but don&#039;t have posting rights yet. So, I&#039;m posting this here now, but will copy over once I have been approved. Hope that&#039;s OK.

I have a few comments for your consideration... all references to Cx Ix and Dx are your guidelines/checkpoints and WCAG-x are for WCAG 1.0 x checkpoint.

C2 - not sure about the wording; to me it implies that I have to create a black and white version of the site if I use colours. What I think you mean is that users should be able to apply there own CSS colour scheme (although this would not work for images, so not sure whether the are included in this cp or not).

C3 - (as appropriate in the output code)?

C4 - I assume that this is derived from WCAG-6.2 However, I don&#039;t know whether this adequately covers the problem of AJAX replacing/inserting new content into the existing page and how that works with screen readers. What spec of assistive tech? some screen-reader version implementation is really bad, I understand. Also, would a screen-reader user (especially of one of those that doesn&#039;t play nicely with scripting) have it disabled by default and therefore may not get the functionality the developer is expecting &#039;because it works&#039; anyway?

C5 - warnings no longer adequate? I would demote this to Important and/or keep with warnings in Critical

C6 - I need more explanation on this - does it mean lots of links &#039;more...&#039; are OK as each is identifiable when with the context of the preceding text? If so, I&#039;m not sure I agree - I thought one of the common screen-reader features used was the list of links read out. See D7 comment.

C8 - This implies that images of text is acceptable even though it wouldn&#039;t be resizeable... I think more guidance/caveat along the lines of &#039;if you really have to...&#039; is needed for images of text.

C11/12/13 - I&#039;m sure these can be combined. The caveat from C13 surely applies to C11 too?

I6 - I would strengthen this to say that audio content is not auto-started.

I12 - should this be at the top of the page or in context of the input?

I15 - should this be broadened to all proprietary content? This implies MS Word/Excel/Visio files are all fine and dandy

D7 - I personally think this should be Important, if not Critical (see C6 comment).

D12 - or both justified? Although if right to left reading language this needs to be reversed.

You haven&#039;t covered image-maps explicitly - are you assuming coverage by C14, etc. If so, then I would cite as an example.

Auto-refresh (as in WCAG-7.4) is not covered as far as I can see. I think it should be Critical.

I think it would be useful to incorporate some more AJAX specific warnings, e.g. about not using &#039;hidden&#039; property to not display content (ignored by assistive tech)</description>
		<content:encoded><![CDATA[<p>Wow &#8211; great start Jack.</p>
<p>I have signed up for the forum, but don&#8217;t have posting rights yet. So, I&#8217;m posting this here now, but will copy over once I have been approved. Hope that&#8217;s OK.</p>
<p>I have a few comments for your consideration&#8230; all references to Cx Ix and Dx are your guidelines/checkpoints and WCAG-x are for WCAG 1.0 x checkpoint.</p>
<p>C2 &#8211; not sure about the wording; to me it implies that I have to create a black and white version of the site if I use colours. What I think you mean is that users should be able to apply there own CSS colour scheme (although this would not work for images, so not sure whether the are included in this cp or not).</p>
<p>C3 &#8211; (as appropriate in the output code)?</p>
<p>C4 &#8211; I assume that this is derived from WCAG-6.2 However, I don&#8217;t know whether this adequately covers the problem of AJAX replacing/inserting new content into the existing page and how that works with screen readers. What spec of assistive tech? some screen-reader version implementation is really bad, I understand. Also, would a screen-reader user (especially of one of those that doesn&#8217;t play nicely with scripting) have it disabled by default and therefore may not get the functionality the developer is expecting &#8216;because it works&#8217; anyway?</p>
<p>C5 &#8211; warnings no longer adequate? I would demote this to Important and/or keep with warnings in Critical</p>
<p>C6 &#8211; I need more explanation on this &#8211; does it mean lots of links &#8216;more&#8230;&#8217; are OK as each is identifiable when with the context of the preceding text? If so, I&#8217;m not sure I agree &#8211; I thought one of the common screen-reader features used was the list of links read out. See D7 comment.</p>
<p>C8 &#8211; This implies that images of text is acceptable even though it wouldn&#8217;t be resizeable&#8230; I think more guidance/caveat along the lines of &#8216;if you really have to&#8230;&#8217; is needed for images of text.</p>
<p>C11/12/13 &#8211; I&#8217;m sure these can be combined. The caveat from C13 surely applies to C11 too?</p>
<p>I6 &#8211; I would strengthen this to say that audio content is not auto-started.</p>
<p>I12 &#8211; should this be at the top of the page or in context of the input?</p>
<p>I15 &#8211; should this be broadened to all proprietary content? This implies MS Word/Excel/Visio files are all fine and dandy</p>
<p>D7 &#8211; I personally think this should be Important, if not Critical (see C6 comment).</p>
<p>D12 &#8211; or both justified? Although if right to left reading language this needs to be reversed.</p>
<p>You haven&#8217;t covered image-maps explicitly &#8211; are you assuming coverage by C14, etc. If so, then I would cite as an example.</p>
<p>Auto-refresh (as in WCAG-7.4) is not covered as far as I can see. I think it should be Critical.</p>
<p>I think it would be useful to incorporate some more AJAX specific warnings, e.g. about not using &#8216;hidden&#8217; property to not display content (ignored by assistive tech)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Dunmore</title>
		<link>http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/comment-page-1/#comment-18730</link>
		<dc:creator>Ian Dunmore</dc:creator>
		<pubDate>Sun, 23 Sep 2007 08:58:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/#comment-18730</guid>
		<description>Thanks Jack.

Everyone else.....

MORE FEEDBACK HERE PLEASE!!!!!</description>
		<content:encoded><![CDATA[<p>Thanks Jack.</p>
<p>Everyone else&#8230;..</p>
<p>MORE FEEDBACK HERE PLEASE!!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JackP</title>
		<link>http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/comment-page-1/#comment-18700</link>
		<dc:creator>JackP</dc:creator>
		<pubDate>Sat, 22 Sep 2007 09:07:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/#comment-18700</guid>
		<description>Ian, not a problem, since I&#039;ve written the guidelines &lt;em&gt;for&lt;/em&gt; the PSWMG! - I&#039;ve sent you an email.</description>
		<content:encoded><![CDATA[<p>Ian, not a problem, since I&#8217;ve written the guidelines <em>for</em> the PSWMG! &#8211; I&#8217;ve sent you an email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Dunmore</title>
		<link>http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/comment-page-1/#comment-18687</link>
		<dc:creator>Ian Dunmore</dc:creator>
		<pubDate>Fri, 21 Sep 2007 21:01:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.thepickards.co.uk/index.php/200709/proposed-public-sector-web-accessibility-guidelines/#comment-18687</guid>
		<description>Jack, superb first stab and a fantastic starting place.  Could I re-distribute these:

a) via psf (&amp; newsletter etc) and
b) draw them to attention of the PSWMG list?

What thoughts do you have about how/where people contribute/add etc should they wish to? 

Oh for a wiki of some sort for this one!</description>
		<content:encoded><![CDATA[<p>Jack, superb first stab and a fantastic starting place.  Could I re-distribute these:</p>
<p>a) via psf (&amp; newsletter etc) and<br />
b) draw them to attention of the PSWMG list?</p>
<p>What thoughts do you have about how/where people contribute/add etc should they wish to? </p>
<p>Oh for a wiki of some sort for this one!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

