Proserva Inc. takes the following measures to ensure accessibility of Proserva:
• Appoint an accessibility officer and/or ombudsperson.
• Employ formal accessibility quality assurance methods.
‍

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. Proserva 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.
‍

Although our goal is WCAG 2.1 Level AA conformance, we have also applied some Level AAA Success Criteria: Images of text are only used for decorative purposes. Re-authentication after a session expires does not cause loss of data.
‍

We welcome your feedback on the accessibility of Proserva. Please let us know if you encounter accessibility barriers on Proserva:support@proserva.co. We try to respond to feedback within 2 business days.
‍

Proserva is designed to be compatible with the following assistive technologies:Proserva is not compatible with:
• Browsers older than 3 major versions.
‍

Accessibility of Proserva 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
• WAI-ARIA
• CSS
• JavaScript

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

Despite our best efforts to ensure accessibility of Proserva , 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 Proserva:
‍
1. User generated content: Uploaded images may not have text alternatives. Uploaded videos may not have captions or audio descriptions. because We cannot ensure the quality of contributions. We design our application to be compatible not only with screen readers to convey alt text (e.g., JAWS, NVDA, VoiceOver), but also with AI-powered image recognition technologies—such as JAWS Picture Smart AI, Android TalkBack with Gemini Nano, Microsoft’s “Describe Image” in Windows 11, Microsoft Seeing AI, Be My AI, and wearables like OrCam MyEye—to provide dynamic, real-time image descriptions when alt text is unavailable.. Please use the ‘send a message’ button in the chat bubble in the bottom right of the screen if you encounter an issue.
‍
2. Charts, dashboards, and data visualizations: Charts may not include full text alternatives. Tooltip details may not be reachable by keyboard or announced by screen readers. because Interactive visualizations rely on canvas or SVG with custom scripting.. Provide data tables for every chart, add ARIA labels and descriptions, ensure keyboard focus for tooltips, and document visualization patterns in our design system.. Use the “Export data” or “View table” options where available. If a chart is inaccessible, request the underlying data as a CSV or accessible table.
‍
3. Keyboard-only navigation: Some controls, sortable columns, and menus may not be reachable in a logical order. Certain components may require a mouse to operate. because Legacy components and custom widgets need additional keyboard bindings.. Add skip links, standardize tab order, ensure all actions have keyboard equivalents, and test with NVDA and VoiceOver.. If you cannot activate a control by keyboard, contact support@proserva.co and we will provide a workaround.
‍
4. Drag-and-drop features (reordering modules, assigning items): Actions may require dragging with a pointer and may not offer keyboard alternatives. because Reorder controls were built with pointer events first.. Add “Move up” and “Move down” buttons, provide menus with “Send to position” options, and announce changes to screen readers. Ask an admin to apply the desired order, or request that we perform the change for you.
‍
5. External or embedded third-party content (for example: videos, documents, iframes): We cannot guarantee accessibility of content hosted on external platforms. because Third-party providers control markup, player controls, and accessibility features.. Prefer providers with accessible players, document known gaps, and offer fallbacks.. Request an alternative format if an embedded item is not accessible.
‍

Proserva Inc. assessed the accessibility of Proserva by the following approaches:
‍
• Self-evaluation: Automated testing uses specialized software tools to quickly scan a website for common accessibility issues based on standards like WCAG 2.1 or 2.2. Tools such as Axe DevTools and Lighthouse can efficiently identify problems such as missing alt text, poor color contrast, or missing form labels. This approach is fast, cost-effective, and useful for detecting a large number of technical barriers early in development.
‍
• Automated Testing: Manual evaluation involves trained accessibility specialists who inspect and test web pages using both the keyboard and assistive technologies like screen readers (NVDA and VoiceOver). This process helps identify issues automation misses, such as incorrect heading structures, confusing link text, or improper use of ARIA attributes.
‍

Other related evidence for Proserva is available at:
•  VPAT (Voluntary Product Accessibility Template)
• Automated testing tools report (axe DevTools)