Further to my last comment. The theming in Magento is very powerful and allows you to do anything that you would like to / need to. Take the time to learn it (there is a lot to learn) and you will see that you are not limited in any way as to what you can do. Cheers Adam
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of tee Sent: 08 June 2009 10:51 To: [email protected] Subject: [WSG] SPRI accesibility Anybody familiar with SPRI accessibility from Spain? Is this something similar to Section 508 in US, DDA of Australia and UK? I want to assist a customer who purchased my Magento theme whose client requires website be conformance with SPRI, but she didn't tell me any info regarding SPRI and what priorities are to be conformance with and I can't read Spanish. I am presuming that it's not likely that entire site needs to meet all three priorities per the SPRI requirement yet I couldn't get any info from her. My assumption is, she is clueless as well. The theme she purchased meets priority 2 except "E823 [WAI 3.5 (AA)] Nest headings properly" which I don't think important and it's quite impossible to fix this in a template driven eCommerce site or a blog (just look at all WordPress blogs, you know what I meant). Likely pass most checkpoint in priority 3 but I never run the validation on priority 3 for Magento sites I built. It appears that her client bases the accessibility check solely on the errors validator found. And this is the validator they use. ttp://www.sidar.org/hera/index.php.en In that site, there are three 3 priority checkpoints failed which I think are judgement call - this is just the homepage, likely more errors to be found in other pages. Checkpoint 9.5 - Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. [Priority 3] Checkpoint 10.4Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. [Priority 3] Checkpoint 10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. [Priority 3] tee ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [email protected] ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [email protected] *******************************************************************
