Accessibility statement
The Pollen Shop is committed to website accessibility and the open and fair access to technology by disabled people.
This site conforms to level Double-A of the Web Content Accessibility Guidelines 2.0 (WCAG 2.0). These guidelines are developed by the World Wide Web Consortium's (W3C) Web Accessibility Initiative. They are the most widely used accessibility guidelines.
- If you have any comments or questions about the accessibility of this website, please contact us
Using this site
Sighted users viewing this website with most modern browsers will see the navigation for the main areas of the website on a horizontal bar at the top of the screen and the content displayed in the centre. On the left is the sub-navigation menu relevant to the area you are currently in and links to related pages, related external sites and documents.
Users of screen readers and text only browsers will have the website rendered, top to bottom, in the following order. As will those with style sheets switched off.
- Help navigation, including a link to 'skip to main content' and link to acessibility
- Main navigation
- Page content
- Sub-navigation and relevant external links
Increasing the size of the text
The text on this website is scaleable. You can increase and decrease the size using options in your browser.
For Internet Explorer select 'View' followed by 'Text Size'
For Firefox select 'View' followed by Zoom'
For Opera select 'View' followed by 'Zoom'
Browsers
The Pollen Shop website is developed to work with a wide range of different browsers.
Fully supported browsers
The website will work perfectly and look as intended with the following browsers:
- Internet Explorer 8
- Internet Explorer 7
- Internet Explorer 6
- Firefox 2 and 3
- Chrome
Partially supported browsers
The website will work perfectly but there may be small visual differences from the 'intended' look.
- Internet Explorer 5.5
- Internet Explorer 5
- Firefox 1
- Safari 4
- Opera 9.5
- Konquorer
- Camino
We also test other browsers wherever possible and always try to be 'backwards-compatible' if this doesn't compromise standards or accessiblity. However we do not support all the quirks and errors of legacy browsers.