I received some feedback to say that Accessify is “horribly broken” in IE7 but, alas, I have no way of checking this for myself or fixing because:

1. I am a Mac owner/user and have hardly any space left on my hard drive to install something like Virtual PC (which could help me to resolve the problems)
2. I am unable to install IE7 on my work PC because of various corporate security issues (regarding what a user, such as me, can get access to using a browser that hasn’t been hobbled in many ways prior to company-wide rollout!)

So, I’m kinda stuck - and asking for your help. If you are accessing this in IE7 and everything looks right to you, please let me know (it could have been a stray bug on a certain page, but the words “horribly broken” don’t sound all that nice, do they?!). But if it looks wrong and you think you know why this is the case, please drop me a line (email to lloydi_admin at this domain) and attach any relevant screen shots that you think may help.

If you want to be really helpful, perhaps you could try some of the other page styles on offer to see how they fare in IE7?

Thanks in advance to anyone who can let me know where it’s going wrong here

One of the comments I read after our WCAG (Web Content Accessibility Guidelines) 2.0 panel is that it would have been good to have a “what you can go back and do at your place of work now” type summary. Well, I agree that this is often a good thing to do and so I’d like to retrospectively offer a few suggestions on that basis:

1. Go read the core documentation now. Ignore the preamble if you can - although you may need to familiarise yourself with some of the new terminology. If you stick to reading the core part of the core document, you may be surprised at how much you understand and how it’s not as bad as it may have been painted to be
2. Keep an open mind - don’t believe everything that you read on the web about WCAG 2.0, instead form your own opinions (step 1 here is essential for this)
3. Register at Accessify Forum. There’s a great starter for discussing all accessibility matters and certainly a lot less daunting for a relative beginner than registering for the WAI (Web Accessibility Initiative) mailing list
4. Make sure your site still stands up to WCAG 1.0 - it’s still the only referenceable accessibility guidelines from the W3C. If your site is still good to go with WCAG 1.0, when 2.0 is finalised you’ll have a lot less to do
5. If you work in a team, ask your developers or your management team what they know about accessibility. Do you need to do some education on a general level (without mentioning documentation or version numbers)?
6. Take a look at the new WCAG 2.0 Quick Reference. Try it out, put in some realistic baselines and see how it works for you
7. Finally (for now at least), remember that you have a very short time now left to comment. The deadline was extended for final comments (as posted here) but that deadline ends on the 22nd. That’s three days from now. Yikes! Find out how you can comment here.