Accessibility
Accessibility Statement
What this site was built to do, what was actually implemented, where the limits are, and how to tell us when something does not work for you.
The standard we build to
The target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.
That target was chosen before the first page was designed, not audited in afterwards. The consequence is visible in the layout: a single readable column measure, generous line height, large touch targets, and no design element that depends on a mouse, a hover state or a steady hand.
A statement of intent is easy to write. What follows is the specific list of what is in the code, so that a claim here can be checked against the page you are reading.
What is built into this site
Each of these is implemented site-wide, not on selected pages.
Structure and navigation
So the page can be understood without seeing it.
- Semantic headings in order, one H1 per page and no skipped levels, so a screen reader can build a correct outline
- A skip link as the first focusable element, letting keyboard users jump past the header straight to the main content
- Landmark regions for header, navigation, main content and footer
- No keyboard traps: every interactive element can be reached and left using the keyboard alone, including menus and accordions
- Visible focus indicators on every interactive element, with enough contrast against the surface behind them to be seen without hunting
Colour and contrast
Verified against what actually renders, not against a swatch in a design file.
- Text and background contrast verified against the real rendered backgrounds, including gradient sections where the darkest and lightest points of the gradient were both measured
- Contrast checked for interface components and focus rings, not text alone
- No reliance on colour alone to convey meaning: status, emphasis and required information are also carried by text, shape or position
- Links distinguishable from surrounding text by more than hue
Text, reflow and zoom
For magnification, small screens and narrow windows.
- Text reflows without horizontal scrolling down to a 320 pixel viewport width, and at 400 per cent zoom
- Relative units throughout, so text scales with the browser or operating system text size setting
- Line lengths kept to a readable measure rather than stretched across a wide screen
- Tables and wide content scroll within their own container instead of forcing the whole page sideways
Media, motion and delivery
Nothing on the page moves or loads without reason.
- Alternative text on all images, describing purpose rather than restating the caption, and empty alt on decorative graphics so they are skipped
- No auto-playing audio or video anywhere on the site
- No carousels, no timed content changes and no animation that starts on its own
- A self-hosted typeface served from this domain, so no external request is made to render a page and text does not disappear while a remote font loads
How this was checked
Pages were navigated end to end using the keyboard alone, confirming tab order matches visual order and that focus is never lost or hidden behind a sticky element.
Contrast values were measured against the colours the browser actually paints, which is why gradient sections were sampled at both extremes rather than at a single nominal background value.
Headings were reviewed as a document outline to confirm levels are sequential and describe the content that follows them.
Automated checking catches a share of problems and misses the ones that matter most, so it is used as a first pass rather than as evidence of conformance. Accessibility is treated as part of building a page, and is re-checked when a template changes.
Ontario context: AODA and the IASR
Skyfal Security operates in Ontario, where the Accessibility for Ontarians with Disabilities Act (AODA) and its Integrated Accessibility Standards Regulation (O. Reg. 191/11) set out requirements for accessible information and communications, including web content.
The information and communications standard under the IASR points to WCAG Level AA conformance for web content, with defined exceptions for live captioning and audio description. This site targets WCAG 2.2 Level AA, which is at or above that reference point.
The IASR also requires that accessible formats and communication supports be provided on request, in a timely way and at no additional cost. If you need information from this site in another format, ask and we will provide it.
Third-party content added later
The statements above cover content and code built for this site. They do not automatically extend to third-party content added later.
An embedded form, a map, a video player, a booking widget or a document produced in another application may not meet the same standard, because its markup and behaviour are controlled by the provider rather than by us. This is a known and honest limit, not an oversight.
Any such addition will be assessed against WCAG 2.2 Level AA before it goes live. Where a component falls short and no accessible alternative from that provider exists, we will either not use it or publish an accessible route to the same information, and note the limitation on this page.
Feedback
If a page on this site is difficult or impossible for you to use, tell us. A specific report is more useful than a general one.
Send accessibility feedback to support@skyfalsecurity.com. Include the page address, what you were trying to do, what happened instead, and the browser, operating system and assistive technology you were using if you know them.
Accessibility feedback is answered in the same way as any other enquiry: by a person, through the same contact routes, within the same business hours of 8:00 AM – 5PM. It is not routed to a separate queue and it is not treated as lower priority than a commercial message.
If you need content from this site in an accessible format or with a communication support, ask through the same address and we will arrange it.
Last reviewed: (date to be entered at publication).
For anything that is not an accessibility matter, use the contact page, or request technical service for an active fault.