Accessibility, without the fine print.

What we try to do on every page

These aren't claims of perfection — they're the checklist we actually run through before anything ships. If you spot one that's broken, that's a real bug and we want to hear about it.

• Real HTML, not div soup. Headings, landmarks, lists, and buttons use the tags they're supposed to, so screen readers and browser shortcuts work out of the box.
• Everything reachable by keyboard. You should be able to tab through links, buttons, and the contact form without a mouse, and always see where focus is.
• Visible focus rings. We use oxblood outlines, not the "hide all focus" trick. Focus never disappears just because it's ugly.
• Respect for reduced motion. If your OS has "reduce motion" enabled, scroll animations, video backgrounds, and hover transforms turn off automatically.
• Contrast that works in sunlight. Body text is warm near-black on linen (~15:1), well above the AA 4.5:1 threshold. The oxblood accent is only used on short or large text where it passes.
• Alt text on meaningful images. Photos that carry information have descriptive alt text; purely decorative flourishes use empty alt so screen readers skip them.
• Form labels, not just placeholders. Every input on the contact form has a real <label>, so the field name is still announced when you've started typing.
• Text you can zoom. Nothing is baked into an image. Zoom to 200% and the layout reflows.

Where we know we're not there yet

The part most accessibility statements skip. These are the things on our list that aren't fixed yet — listed publicly because pretending otherwise helps no one.

• Screen-reader testing is not exhaustive. We've tested with VoiceOver on macOS and NVDA on Windows in Firefox and Chrome. JAWS, TalkBack, and mobile Safari/VoiceOver on older devices haven't been formally audited.
• Some case-study images need longer descriptions. Alt text on the work section conveys the subject but not the visual detail of the design itself. A richer description would be better for non-sighted visitors evaluating our craft.
• Hero videos don't have captions or transcripts. They're decorative and silent, but we still owe a text alternative describing what they show.
• Color is not the only cue, except in one place. The "currently booking" pulse in the footer relies partly on color and motion. We're rethinking that indicator.
• Third-party Google Fonts can fail. If the font CDN is blocked or slow, the fallback is a system serif/sans. It works, but it's not tuned for line-height or letter-spacing the way our primary fonts are.
• No formal third-party audit yet. Everything above is based on our own testing plus automated tools (axe, Lighthouse). A paid audit from an accessibility specialist is on our roadmap, not a line we've already crossed.

Quick reference

A few shortcuts and settings that make this site easier to use.

Tell us if something's broken

The most useful thing you can do is email us. Seriously — one message from someone who's hitting a real-world problem is worth more than any automated audit we can run. We read every one, and we reply.

If you can include it, the most helpful details are: what you were trying to do, what browser and assistive tech you're using, and where on the site it went wrong. No screenshots needed unless you have them handy.

Write to hello@ignitewebstudios.ca and put "Accessibility" somewhere in the subject line so we spot it quickly. We aim to acknowledge within one business day and fix confirmed issues within five. If we can't fix something, we'll tell you why and what the workaround is.

A note on the sites we build for clients

This statement covers ignitewebstudios.ca only. When we build for a client, accessibility is baked into the scope from day one: semantic structure, keyboard support, contrast-checked colour systems, alt-text workflows for the CMS, and a pre-launch audit using axe and manual keyboard testing. We'd rather build one site right than ten sites that look good in a screenshot.