Last updated: October 14, 2026
Key takeaways
- We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across our website.
- We have built in keyboard navigation, strong color contrast, reduced-motion support, alt text and a skip link, among other measures.
- Some third-party components and older materials may not yet fully meet our target. We list known limitations below.
- If anything gets in your way, email [email protected]. We aim to reply within two business days.
1. Our commitment
SecuritySage believes that good cybersecurity guidance should be available to everyone, including people with disabilities and people using assistive technologies. Small business owners and their teams come from every background, and security advice only works if people can read, understand and act on it. We are committed to making https://www.securitysage.org (the “Site”), our free resources and our self-paced programs accessible and usable for as many people as possible.
This statement explains the standard we work toward, what we have done so far, where we know we still fall short, and how to contact us if you have difficulty using any part of the Site.
2. Our accessibility target
Our goal is for the Site to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning and neurological disabilities.
We consider the Site to be partially conformant with WCAG 2.2 Level AA. “Partially conformant” means that some parts of the content do not yet fully conform to the standard. We are working to close those gaps, as described in the known limitations below.
We also aim to write in plain English, explain technical terms when we use them, and keep pages focused, because clear language is an important part of accessibility. Our cybersecurity glossary explains common security terms in everyday language.
3. Measures we have taken
We have taken the following steps to support accessibility on the Site:
- Keyboard navigation: all menus, links, buttons, forms, the cart and checkout, the self-assessment quiz and interactive checklists can be reached and operated using a keyboard alone. Focus moves in a logical order, and a clearly visible focus indicator shows where you are on the page.
- Skip link: a “Skip to main content” link is the first item on every page, so keyboard and screen reader users can bypass repeated navigation.
- Color contrast: text and important interface elements are designed to meet or exceed WCAG AA contrast ratios. We do not rely on color alone to convey meaning, for example in quiz results or form errors.
- Reduced-motion support: if you have enabled a “reduce motion” setting in your operating system or browser, the Site respects it by minimizing or switching off animations and transitions.
- Alternative text: informative images include descriptive alt text, and decorative images are marked so that screen readers skip them.
- Structure and semantics: pages use meaningful headings in a logical order, landmark regions, lists and properly marked-up data tables, so assistive technologies can present content clearly. Longer pages include a table of contents.
- Forms: form fields on our contact and get started pages, newsletter signup and checkout have visible labels. Required fields are identified in text, and error messages explain how to fix the problem.
- Resizable text and responsive layout: the Site works when text is enlarged up to 200% and adapts to small screens without requiring horizontal scrolling for regular content.
- Target size: buttons and links are sized and spaced to be easy to activate, including on touch screens.
- Descriptive links: link text describes where the link goes, and links that open in a new tab are kept to a minimum.
- Accessible authentication: logging in does not require solving a puzzle or memorizing information beyond your own credentials, and password managers and pasting are supported.
- Testing: we check pages with automated accessibility tools, keyboard-only testing, browser zoom and screen reader spot checks when we publish or significantly change content.
4. Known limitations
Despite our efforts, some content may not yet be fully accessible. Known limitations include:
- Third-party components: some features are provided by third parties, such as the cookie consent banner and payment processor checkout pages (such as Stripe or PayPal). We choose providers that state a commitment to accessibility, but we do not fully control their interfaces.
- Downloadable documents: some downloadable program materials, such as templates, worksheets and PDF documents, may not yet be fully tagged for screen readers. Editable versions in common word processing formats are available on request.
- Program video and audio: some program media may not yet have complete captions or transcripts. We are adding them, and we will provide a transcript on request.
- Complex images: some images, such as diagrams sourced from open-licensed collections, may need longer descriptions than alt text can provide. Where a diagram is important to understanding, we describe the key points in the surrounding text.
- Older content: some older blog posts may have been published before our current accessibility checks and may contain minor issues, such as heading order. We review and fix older posts as we update them.
- User-submitted content: blog comments are written by visitors and may not always meet accessibility guidelines.
If you need any content in an alternative format, such as a plain-text version, larger print or an editable document, please ask. We will do our best to provide it at no extra cost.
5. Feedback and contact
We welcome your feedback. If you encounter an accessibility barrier on the Site, have trouble accessing a program, or have suggestions for how we can improve, please contact us:
- Email: [email protected] (subject line “Accessibility”)
- Online: Contact us
- Location: SecuritySage, Lakewood, Ohio 44107, USA
To help us respond quickly, please include:
- the web address (URL) of the page where you had difficulty;
- a short description of the problem;
- the device, browser and any assistive technology you were using, if you are comfortable sharing it; and
- how you would prefer us to contact you.
If the barrier is preventing you from buying or using a program you need, tell us and we will help you complete the purchase or access the content another way while we work on a fix.
6. Our response time
We aim to acknowledge accessibility feedback within two business days. We aim to provide a substantive response, including either a fix, an accessible alternative or a timeline for resolving the issue, within 10 business days. If an issue requires changes from a third-party provider, we will tell you what we are doing to resolve it and keep you updated.
7. Ongoing improvement
Accessibility is an ongoing effort, not a one-time project. We review the Site regularly, include accessibility checks when we add new pages, programs or features, and update this statement as we make improvements or identify new issues. Feedback from people who use the Site is one of the most valuable ways we learn what needs fixing, so thank you for taking the time to let us know.
8. Related policies
For information about how we handle personal information you share when contacting us, see our Privacy Policy. Other policies that apply to the Site include our Terms & Conditions and Cookie Policy.