Comments on: Amatica Update http://www.thatstandardsguy.co.uk/2006/02/17/amatica-update/ personal blog on web standards and accessibility by Karl Dawson Wed, 18 Oct 2006 22:43:57 +0000 http://wordpress.org/?v=1.5.2 Comment on Amatica Update by: Karl Dawson http://www.thatstandardsguy.co.uk/2006/02/17/amatica-update/#comment-104 Wed, 01 Mar 2006 11:43:39 +0000 http://www.thatstandardsguy.co.uk/2006/02/17/amatica-update/#comment-104 Yes that reminds me I should post about that Grant. Dan put a lot of effort into that script and it all started over at <a href="http://www.accessites.org" title="Awards site for beautiful and accessible websites" rel="nofollow">Accessites</a> where it has been implemented. It also received valuable input, testing and discussion from fellow <acronym title="Guild of Accessible Web Designers">GAWD</acronym> members on the discussion list and currently I think this is the best solution to implementing accesskeys in a safe and reliable manner. Yes that reminds me I should post about that Grant.

Dan put a lot of effort into that script and it all started over at Accessites where it has been implemented. It also received valuable input, testing and discussion from fellow GAWD members on the discussion list and currently I think this is the best solution to implementing accesskeys in a safe and reliable manner.

]]> Comment on Amatica Update by: Grant Broome http://www.thatstandardsguy.co.uk/2006/02/17/amatica-update/#comment-103 Tue, 28 Feb 2006 16:59:38 +0000 http://www.thatstandardsguy.co.uk/2006/02/17/amatica-update/#comment-103 Loose the access keys? Haven't you heard of <a href="http://www.blether.com" rel="nofollow">Dan Champion's</a> excellent work on providing <a href="http://www.clacksweb.org.uk/site/accesskeys/" rel="nofollow">non-conflicting access keys</a> based on similar solutions worked out by Rich Pedley and Gez Lemon? Loose the access keys? Haven’t you heard of Dan Champion’s excellent work on providing non-conflicting access keys based on similar solutions worked out by Rich Pedley and Gez Lemon?

]]> Comment on Amatica Update by: Karl Dawson http://www.thatstandardsguy.co.uk/2006/02/17/amatica-update/#comment-83 Sat, 18 Feb 2006 16:27:27 +0000 http://www.thatstandardsguy.co.uk/2006/02/17/amatica-update/#comment-83 I find myself delving more into the specs this year to find all these little nuggets of truth to overcome any assumptions I may have.. Many Thanks for clarifying that Dejan :) I find myself delving more into the specs this year to find all these little nuggets of truth to overcome any assumptions I may have.. Many Thanks for clarifying that Dejan :)

]]> Comment on Amatica Update by: djn http://www.thatstandardsguy.co.uk/2006/02/17/amatica-update/#comment-82 Sat, 18 Feb 2006 12:19:46 +0000 http://www.thatstandardsguy.co.uk/2006/02/17/amatica-update/#comment-82 The specs only say there has to be a TITLE element, not that it should be the first child of HEAD. More, if you declare the character encoding inside your document with META HTTP-EQUIV ( for those saving the document on disk or when you haven't access to the server configuration ), you should do this "as soon as possible in the document", meaning right after opening HEAD, so the user agent knows how to read the title (cant't find the URL right now, but it's somewhere on W3C I18N...). Thus, putting stuff before TITLE is officially kosher. The specs only say there has to be a TITLE element, not that it should be the first child of HEAD. More, if you declare the character encoding inside your document with META HTTP-EQUIV ( for those saving the document on disk or when you haven’t access to the server configuration ), you should do this “as soon as possible in the document”, meaning right after opening HEAD, so the user agent knows how to read the title (cant’t find the URL right now, but it’s somewhere on W3C I18N…). Thus, putting stuff before TITLE is officially kosher.

]]>