top of page

Accessibility Statement for Endowance Solutions

This is an accessibility statement from Endowance Solutions.

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. Endowance Solutions 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 Endowance Solutions. Please let us know if you encounter accessibility barriers on Endowance Solutions:

  • Phone: +1 (279) 201-9924

  • E-mail: info@endowance.com

  • Visitor Address: 1919 Apalachee Dr

  • Postal Address: 96151

We try to respond to feedback within 3 Business Days.

Compatibility with browsers and assistive technology

Endowance Solutions is designed to be compatible with the following assistive technologies:

  • Chrome Browser

  • Safari Browser

  • Edge Browser

Technical specifications

Accessibility of Endowance Solutions 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

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

Limitations and alternatives

Despite our best efforts to ensure accessibility of Endowance Solutions , 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 Endowance Solutions:

  1. Header Labeling: Elements that visually appear as titles but are coded with no header. because Site upgrade issue.. We are conducting an audit of all text field types.. Please report the issue via email..

  2. Inconsistent Hx Levels: Title levels should not be skipped and should be built with consistent hierarchy. For example: you cannot have "h4" titles and "h2" titles without having "h3" titles. because Site design for aesthetics. We are auditing the choices to omit a intermediary H level.. Please report the issue via email..

  3. Pop-up and screen reader compatibility: Active popups should include an "aria-modal" attribute that equals to "true", and a "role" attribute that equals to "dialog", so screen-reader users know how to navigate within it. because 3rd party supplied content issue.. We are working with the supplier to improve this issue.. Please report the issue via email..

  4. CSS Manipulations 1: Elements that are hidden using CSS manipulations (opacity, height, text-indent, off-canvas, etc.) should be wrapped inside an element with an "aria-hidden" attribute that equals to "false", or include it directly, and have it dynamically changed to "true" when they become visible. because Website host design does not include work around for this.. We are looking at how to avoid this issue by using an alternative design.. Please report the issue via email..

  5. CSS Manipulations 2: Elements that are hidden using CSS manipulations (opacity, height, text-indent, off-canvas, etc.) should include a "tabindex" attribute that is below 0, and have it dynamically changed to 0 when they become visible. because Website host design does not include work around for this.. We are looking at how to avoid this issue by using an alternative design.. Please report the issue via email..

  6. Background Images Relevant: Background images that are not just for decoration purposes and should have the same treatment as standard images and include a "role" attribute that equals to "img" and an alternative text description in an "arialabel" attribute. because We have improperly labeled background images. We are working on relabeling.. Please report the issue via email..

Assessment approach

Endowance Solutions assessed the accessibility of Endowance Solutions by the following approaches:

  • Self-evaluation

  • External evaluation

Date

This statement was created on 18 December 2023 using the W3C Accessibility Statement Generator Tool.

bottom of page