This is the official accessibility statement for the HeelzSoHigh web site provided by eSellerPro.
Should you have any questions or comments regarding the accessibility of this site please contact mark.withers 'at' esellerpro.com
- 1 - Home
- 2 - About
- 3 - Contact
- 4 - Delivery
- 5 - Returns
- 6 - Payment
- 7 - FAQ
- 7 - My Account
- 8 - Register New Account
- a - Accessibility
- s - Skip to Content
- c - Go to the Checkout
- r - Register New Account
- u - View My Account
- l - Log In to My Account
- o - Log Out
- m - Site Map
- t - Terms and Conditions
- p - Privacy
- e - eSellerPro.com
- The pages on this web site to our knowledge are WAI AAA approved, tested using the TAW, Web Accessibility Test meeting the Web Content Accessibility Guidelines 1.0.
- This is a judgement call; many of the accessibility features can be tested, but some can not. We have reviewed the accessibility guidelines and believe that the pages on this web site are in compliance with the standards.
- All the pages on this web site validate as XHTML 1.0 Strict. This is not a judgement call; accessibility software can determine with 100% accuracy whether a page is valid XHTML.
- All the pages on this site use semantically structured markup. H1 tags are used for the page topic, H2 tags are used for the main sub titles, H3 tags are used for the content subtitles.
- The visual layout of this web site has been built using cascading style sheets.
- This web site only uses relative sized fonts which are compatible with the users browser "text size" option.
- If your web browser or web device does not support cascading style sheets, the content of each page is still readable.
- This web site is viewable on every web browser and web browsing device including PDAs and Mobile Phones that have web capability.
WCAG 1.0 Checkpoints
We believe that checkpoint 10.4 of the Web Content Accessibility Guidelines 1.0 has now been outdated as most user agents today handle empty edit boxes and text areas correctly. An associated label has been applied to each edit box and text area control so that it can be identified by the user agents.
- Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. [Priority 3] For example, in HTML, do this for TEXTAREA and INPUT.