Accessibility Statement

Accessibility Statement for Insulgard.com

This is an accessibility statement from Insulgard Security Products.

Conformance status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. Insulgard.com is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

Feedback

We welcome your feedback on the accessibility of Insulgard.com. Please let us know if you encounter accessibility barriers on Insulgard.com:

  • Phone: 800-624-6315
  • E-mail: [email protected]
  • Postal Address: 1291 Rickett Rd Brighton, MI 48116

We try to respond to feedback within 3 business days.

Technical specifications

Accessibility of Insulgard.com relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML
  • CSS
  • JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Limitations and alternatives

Despite our best efforts to ensure accessibility of Insulgard.com , there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below.

Known limitations for Insulgard.com:

  1. Redundant Graphics and Links: On the shop page and product details pages, in sections where images of products are paired with text links, there is redundancy because the image description and link text are the same. There are also 2 images – 1 is the magnified image on hover and the other is the thumbnail visible when not hovering. We are working to reduce the redundancy of links by grouping the image anchor and the product title anchor into one link, as well as providing a better description for the image in the alt attribute. If there is limited value in the description of products, we will use a blank alt attribute instead. Please contact Insulgard for assistance.
  2. Invisible Links Gain Keyboard Focus: On the Home page, the accessibility tree includes two “FAQ” links under the “Capabilities” heading, but these links do not appear anywhere on the page. When a screen reader’s focus is on “FAQ” link the visual focus indicator lands on the “Learn More About Our Capabilities” link instead. Low-vision users who also use a screen reader cannot visually locate the focused element, and screen-reader users encounter interactive elements that do not exist visually. Some users cannot see or locate focused elements breaking orientation and making navigation unreliable. We are working to remove the hidden “FAQ” links from the accessibility tree or ensure they are visually present and correctly associated with visual content. Please contact Insulgard for assistance.
  3. SVG in Header Requires Alt Text: The phone number link in the header includes a phone icon that provides clarity regarding the purpose of the link. The icon has aria-hidden applied to it, which prevents screen-reader users from accessing the context/purpose of the linked digits that are presented as the link’s accessible name. We are working to remove aria-hidden from the icon and add meaningful alternative text to the image to ensure all users have the benefit of the context/purpose conveyed by the icon, and screen-reader users are not making assumptions regarding the linked numerals. Please contact Insulgard for assistance.
  4. Content Outside of Main Region: On the shop page, the “Filter” section sits on the left side of the page visually but the accessibility tree presents the heading and controls in the Filter section outside of the <main> region, after the product grid and pagination. The visual order and the reading order do not match, which may make the page structure confusing and unpredictable for screen-reader and keyboard-only users. We are working to place the “Filter” section in the accessibility tree before the product grid and pagination – making sure the visual order and the reading order match. Please contact Insulgard for assistance.
  5. Language Picker Lacks Semantics: The “English” button in the header that triggers different language options to be revealed gains focus with the keyboard but presents no role to screen readers – coded as role=”none.” The label “English” does not convey the intended purpose of the component, as a language selector/picker. And the state of “collapsed” is not conveyed. We are working to ensure the language selector has correct roles and states (e.g., button and `aria-expanded=”false”). Please contact Insulgard for assistance.
  6. Learn More Links Need More Context: On the Home page, the “Learn More” link text is used for links going to different destinations. Screen-reader users are unable to identify a links purpose, in the context of the page, without additional reading/navigation, and may be overwhelmed or confused by the number of “Learn More” links on the page. We are working to revise the link text to be more specific to reflect what the link text is associated with. Please contact Insulgard for assistance.
  7. Headings Needed to Provide Context to Sections: On the Home page, when screen-reader users navigate into the tablist using TAB, they only hear the first tab item label “Blocks” which does not give enough context. Sighted users see the heading, “Security Solutions” above the tabs, which screen-reader users will only encounter if they choose to read the page with UP/DOWN ARROW. Users can still operate the tabs, but they may not understand what the tabset relates to without the heading context. This can create a small, but noticeable, clarity gap for screen-reader users. We are working to label the tabpanel using aria-labelledby or a group role to strengthen the relationship. Please contact Insulgard for assistance.
  8. Scrollable Element Is Not Keyboard Accessible: Automated accessibility testing identified scrollable sections that can’t be operated by keyboard. We are working to update the image gallery modals on product detail pages to be keyboard accessible. Please contact Insulgard for assistance.
  9. Container Element is Empty: Accessibility scans detected empty tablist containers. We are working to update the list items in the tablist container to include role=”tab.” Please contact Insulgard for assistance.
  10. Visible Label and Accessible Name Do Not Match: The scan identified elements with programmatic labels that do not match the visible labels on the page. Of the 10% of the pages manually confirmed, this included product cards in “Product” and “Featured Products” sections of various pages and was identified as a false positive in all instances manually verified. We are working to manually confirm every instance and ensure the labels are the same. Please contact Insulgard for assistance.
  11. Image Missing a Text Alternative: The scan has identified images on product detail pages occasionally missing text alternatives. We are working to provide alt text to meaningful images to ensure users on slow internet, or who use screen readers, understand what images are supposed to be displayed. Please contact Insulgard for assistance.
  12. Link Missing a Text Alternative: The scan identified links without meaningful link text, including links that rely on image file names, and FAQ links that are in the reading and focus order, but that serve no purpose. We are working to update links to display only usable links in reading/focus order and ensure they have meaningful names that inform users where they will be taken if they activate each link. Please contact Insulgard for assistance.
  13. Color Contrast Does Not Meet Minimum Requirement: Elements on some pages, like Product Line pages, have been identified as having a color contrast ratio of about 2.5:1, for large text of headings that should have a contrast ratio of 3:1 and regular text that should have a contrast ratio of 4.5:1. We are working to update color combinations to ensure text meets minimum requirements at all font sizes. Please contact Insulgard for assistance.
  14. Hidden Element Has Focusable Content: An element on pages like “Our Team” have aria-hidden applied to an element on the page that has an interactive role and is intended to be interacted with. If an element is hidden, it cannot be interacted with without a mouse. We are working to review use of aria-hidden and remove if it is unnecessary or blocking in any way. Please contact Insulgard for assistance.

Assessment approach

Insulgard Security Products assessed the accessibility of Insulgard.com by the following approaches:

  • Self-evaluation

This statement was created on 2 June 2026 using the W3C Accessibility Statement Generator Tool.