Override Question

[Website Rob]

You're certainly heading in the right direction by removing that label tags. It shouldn't really be there.

It's a shame you feel that way and support others to remove them as well.

It's nice to see default Accessibility coding for such as the Blind already included within Zen Cart and we can expect more in future releases. To remove Accessibility coding and/or not use it all, can only mean losing potential buyers.

[chipt4]

OOH I never thought of that. Line-height! (a lightbulb just flickered on above my head)

It's a shame you feel that way and support others to remove them as well.

While I agree that accessibility is important, the tag wasn't properly implemented. The search header was the only one (that i've found so far; i haven't used all the sideboxes) that had the <label> tag. If ALL the sidebox headers were wrapped in a <label>, then the offsets would match and I could live with it.

[kuroi]

It's a shame you feel that way and support others to remove them as well.

It's nice to see default Accessibility coding for such as the Blind already included within Zen Cart and we can expect more in future releases. To remove Accessibility coding and/or not use it all, can only mean losing potential buyers.

Website Rob

I understand where you're coming from, but these label tags aren't properly implemented. They neither wrap around a control element allowing it to be toggled by clicking on the label. Nor do they carry carry the "for" attribute to link them to an input field. So their accessibility value is close to zero and may even be negative due to the confusion that could be caused by label tags with not explicit linkage to anything.

However, if you were to argue that a better approach would be to add "for" attributes and deal with the visual issues by setting their font-size to 1em (instead of 1.1em), I would probably agree, though with a small lingering doubt about the advisability of nesting label tags inside headers.

[Website Rob]

Although true that some Accessibility coding could be done better, it is a start; which is more than most other Open Source / eCommerce scripts are providing.

Glad we're on the same page though and recommend every Coder brush up on their Accessibility coding. Situations like Target being sued on behalf of the Blind and the USA already requiring Government sites to meet Section 508 Standards, I think much work is available on the horizon -- for those Coders that are ready.