I am currently away on leave returning to the office on 25th June
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************
--- Begin Message ---
*********************************************************************
WEB STANDARDS GROUP MAIL LIST DIGEST
*********************************************************************
From: Richard Stephenson <donkeyma...@gmail.com>
Date: Mon, 8 Jun 2009 11:30:12 +0100
Subject: Re: [WSG] SPRI accesibility
I'd have thought the biggest issue with Magento accessibility is it's
reliance on JavaScript for the checkout process? It's impossible to
order anything without JS enabled. Although I'm not sure that is such
an issue with WCAG 2. Anyone else know?
Rich
> 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]
>
*********************************************************************
From: "Adam Martin" <ajmartin...@gmail.com>
Date: Mon, 8 Jun 2009 12:22:17 +0100
Subject: RE: [WSG] SPRI accesibility
Magento by default uses javascript for its one page checkout. However you
can easily turn this off and use a more traditional checkout procedure.
Also, magento is an ecommerce framework allowing you to change anything that
you like. The comment that it relies on javascript is only true by its
default settings - in fact it would be very easy to detect if javascript was
available ad if not provide an alternative checkout path.
My 2c worth as an Magento Enterprise Partner ;)
Adam
-----Original Message-----
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Richard Stephenson
Sent: 08 June 2009 11:30
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] SPRI accesibility
I'd have thought the biggest issue with Magento accessibility is it's
reliance on JavaScript for the checkout process? It's impossible to
order anything without JS enabled. Although I'm not sure that is such
an issue with WCAG 2. Anyone else know?
Rich
> 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]
>
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************
*********************************************************************
From: "Adam Martin" <ajmartin...@gmail.com>
Date: Mon, 8 Jun 2009 12:24:33 +0100
Subject: RE: [WSG] SPRI accesibility
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: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of tee
Sent: 08 June 2009 10:51
To: wsg@webstandardsgroup.org
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: memberh...@webstandardsgroup.org
*******************************************************************
*********************************************************************
From: tee <weblis...@gmail.com>
Date: Mon, 8 Jun 2009 04:39:12 -0700
Subject: Re: [WSG] SPRI accesibility
Hi Adam,
Many JS are built in the core and hard to get rid off.
I would love to see example of the magento site you did that is js
free as I'd been working on removing all JS obstacles from the
template files, and I have hunted down a handful, still it's an
undertake to do a JS free Magento site in my opinion.
Would love to see your exceptional skill reflects on a JS free Magento
site.
Thanks!
tee
On Jun 8, 2009, at 4:22 AM, Adam Martin wrote:
> Magento by default uses javascript for its one page checkout.
> However you
> can easily turn this off and use a more traditional checkout
> procedure.
> Also, magento is an ecommerce framework allowing you to change
> anything that
> you like. The comment that it relies on javascript is only true by its
> default settings - in fact it would be very easy to detect if
> javascript was
> available ad if not provide an alternative checkout path.
>
*********************************************************************
From: kevin mcmonagle <kvn...@mcmonagledesign.com>
Date: Mon, 08 Jun 2009 14:58:59 +0100
Subject: no scrollbars in ff
Whats the problem with firefox and vertical scroll bars.
I have a centered layout here most of the pages would require scrolling
but no bars show up in ff.
I've tried all the solutions on this page:
http://hicksdesign.co.uk/journal/forcing-scrollbars-now-even-better
but no use.
Any suggestions?
-best
kevin
*********************************************************************
From: "David Dorward" <da...@dorward.me.uk>
Date: Mon, 8 Jun 2009 15:20:58 +0100 (BST)
Subject: Re: [WSG] no scrollbars in ff
kevin mcmonagle wrote:
> Any suggestions?
I suggest not asking people to debug code based on third party examples
that work instead of the code that actually causes the problems.
--
David Dorward
http://dorward.me.uk/
*********************************************************************
From: kevin mcmonagle <kvn...@mcmonagledesign.com>
Date: Mon, 08 Jun 2009 16:29:55 +0100
Subject: Re: [WSG] no scrollbars in ff
thanks david.
David Dorward wrote:
> kevin mcmonagle wrote:
>
>> Any suggestions?
>>
>
> I suggest not asking people to debug code based on third party examples
> that work instead of the code that actually causes the problems.
>
>
*********************************************************************
From: Mathew Robertson <mat...@optusnet.com.au>
Date: Tue, 09 Jun 2009 11:58:30 +1000
Subject: Re: [WSG] no scrollbars in ff
[undecodable format: binary]
*********************************************************************
From: "Foskett, Mike" <mike.fosk...@uk.tesco.com>
Date: Tue, 9 Jun 2009 09:48:57 +0100
Subject: RE: [WSG] no scrollbars in ff
Did you try this from the articles comments?
:root {overflow-y:scroll}
I gave it a quick test and it appeared to work well in Firefox and Chrome.
Regards
Mike Foskett
-----Original Message-----
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On B
ehalf Of Mathew Robertson
Sent: 09 June 2009 02:59
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] no scrollbars in ff
> Whats the problem with firefox and vertical scroll bars.
> I have a centered layout here most of the pages would require scrolling
> but no bars show up in ff.
>
> I've tried all the solutions on this page:
>
> http://hicksdesign.co.uk/journal/forcing-scrollbars-now-even-better
>
> but no use.
>
> Any suggestions?
have you tried:
html { overflow-y: scroll; }
regards,
Mathew Robertson
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************
This is a confidential email. Tesco may monitor and record all emails. The
views expressed in this email are those of the sender and not Tesco.
Tesco Stores Limited
Company Number: 519500
Registered in England
Registered Office: Tesco House, Delamare Road, Cheshunt, Hertfordshire EN8
9SL
VAT Registration Number: GB 220 4302 31
*********************************************************************
From: <michael.brocking...@bt.com>
Date: Tue, 9 Jun 2009 09:50:41 +0100
Subject: RE: [WSG] no scrollbars in ff
Kevin,
I think that was meant to be a hint that we might be able to debug your
code if we could see some of it - very few of us enjoy the extra
challenge of 'working blind'.
Mike
-----Original Message-----
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of kevin mcmonagle
Sent: 08 June 2009 16:30
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] no scrollbars in ff
thanks david.
David Dorward wrote:
> kevin mcmonagle wrote:
>
>> Any suggestions?
>>
>
> I suggest not asking people to debug code based on third party
> examples that work instead of the code that actually causes the
problems.
>
>
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************
**************************************************************
Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
**************************************************************
--- End Message ---
