Accessibility

Keyboard only, screen reader, or your own text size instead of ours — the site should hold up all three ways. Where it does not, we would rather be told than left assuming it is fine.

Nothing in this Spider Canada accessibility statement is a certification claim. It is a description of what has actually been built and what has not.

What Spider Canada Accessibility Covers Today

Headings run in order, so a screen reader can move through a page by structure. Every image carries alt text that says what is in it rather than repeating the product name. Forms have real labels attached to their fields, and the contact form can be completed without a mouse.

Where This Site Is Known to Fall Short

• The size guide relies on a table, and tables are harder to follow on a small screen with a screen reader.
• Some category pages are long, and there is no skip link between the product grid and the written section below it.
• The accordion used for FAQ answers opens and closes correctly but does not announce its state everywhere.
• Color contrast on a few secondary labels is lower than we would like and is on the list to fix.
• Nothing here autoplays, but any future video would need captions before it went up.

Things You Can Change Yourself

• Text scales with your browser's own zoom, so increasing it does not break the layout.
• The site follows your system setting for reduced motion, and transitions stop when that is on.
• Nothing on this site depends on hover alone; everything reachable with a mouse is reachable with a keyboard.

Anything on that list failing on your setup is a bug, not a decision we made.

Reporting a Barrier

Through the contact page. Say what you were trying to do, which page you were on, and what you were using — browser, screen reader, phone or desktop. That is usually enough to reproduce it.

• The page address, so we are looking at the same thing you were.
• What you were trying to do, in one line, rather than what went wrong.
• Your browser and any assistive software, including the version if you know it.

Which of the two it was matters: a keyboard caught in a menu, or a screen reader lost in a table. They get fixed in different places.

We cannot promise a fix by a given date. We can promise that it goes on the list rather than into an inbox nobody reads.