Accessibility Statement

Last updated: February 2026

This is an accessibility statement from UAM Technologies Corp, the company behind eRealSign — an affordable, secure, and legally compliant electronic signature platform designed for businesses, insurance agencies, and professionals.

Conformance Status

The Web Content Accessibility Guidelines (WCAG) (opens in new tab) 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.

WCAG 2.1 Level AA Section 508

eRealSign is fully conformant with WCAG 2.1 Level AA. As of February 2026, all public-facing pages — including Home, About, API, Pricing, Contact, and Request Demo — achieve a Lighthouse Accessibility score of 100/100 on both desktop and mobile configurations. Validation was performed using Google Chrome DevTools (Lighthouse 13, axe-core 4.11), the IBM Equal Access Accessibility Checker, and manual testing. We are committed to maintaining this level of conformance through continuous monitoring and remediation.

Measures to Support Accessibility

UAM Technologies Corp takes the following measures to ensure the accessibility of eRealSign:

• Include accessibility as a core part of our product development lifecycle.
• Conduct ongoing, page-by-page accessibility audits using the approved WCAG 2.1 AA color palette and standards.
• Employ formal accessibility quality assurance methods, including automated and manual testing.
• Maintain an internal accessibility change log to track remediation progress across all pages.
• Ensure all interactive elements — buttons, forms, links, and document-signing workflows — support keyboard navigation and screen readers.
• Apply WCAG-compliant color contrast ratios across all user interface elements (minimum 4.5:1 for normal text, 3:1 for large text and UI components).

Accessibility Features of eRealSign

Our e-signature platform includes support for:

• Keyboard navigation — All core signing, document management, and form workflows can be operated via keyboard.
• Screen reader compatibility — Semantic HTML, ARIA landmarks, labels, and roles are used throughout the application.
• Skip navigation links — Provided on all pages to allow keyboard users to bypass repetitive navigation.
• Form labels and autocomplete — All form inputs include associated labels and correct autocomplete attributes for assistive technology.
• Color contrast — Text and UI elements meet or exceed WCAG 2.1 AA minimum contrast ratios.
• Responsive design — Pages adapt to various screen sizes, zoom levels, and text scaling preferences.

Compatibility with Browsers and Assistive Technology

eRealSign is designed to be compatible with the following assistive technologies:

• Windows: NVDA or JAWS screen readers with Google Chrome or Mozilla Firefox (latest two major versions).
• macOS / iOS: VoiceOver with Apple Safari.
• Android: TalkBack with Google Chrome.

eRealSign is not compatible with:

• Browsers older than three major versions.
• Mobile operating systems older than five years.
• Internet Explorer (any version).

Technical Specifications

Accessibility of eRealSign relies on the following technologies to work with your browser and any assistive technologies or plugins installed on your computer:

• HTML
• CSS
• JavaScript
• WAI-ARIA

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

Limitations and Alternatives

Despite our best efforts to ensure accessibility of eRealSign, 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.

Assessment Approach

UAM Technologies Corp assessed the accessibility of eRealSign by the following approaches:

• Automated auditing — Google Lighthouse (v13) with axe-core 4.11, achieving a 100/100 accessibility score on all public-facing pages (desktop and mobile) as of February 2026.
• IBM Equal Access Checker — IBM Accessibility Checker browser extension used for additional rule coverage and cross-validation beyond axe-core.
• Self-evaluation — Internal, page-by-page audits with results tracked in a detailed remediation log covering color contrast, heading order, button names, link distinguishability, and ARIA attributes.
• Manual testing — Keyboard-only navigation testing and screen reader verification across key user workflows (login, document upload, signing, and settings).
• Color contrast validation — All colors verified against WCAG 2.1 AA contrast requirements using an approved brand color palette with documented contrast ratios.

Feedback

We welcome your feedback on the accessibility of eRealSign. If you encounter accessibility barriers or have suggestions for improvement, please let us know:

We aim to respond to accessibility feedback within 5 business days.

Disclaimer

We are committed to making our website and application accessible to all users, including those with disabilities, and to providing an accessible experience that conforms to Section 508 Guidelines and the World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG), which defines levels of accessibility for consideration by website designers and developers. We strive to conduct accessibility reviews and maintain conformance in accordance with WCAG 2.1 Level AA.

While we seek to monitor and maintain acceptable compliance levels, we cannot anticipate every individualized accessibility need or overcome every technological limitation which, for example, may preclude fully accessible formats of documentation and graphical renderings or otherwise limit the platform's accessibility.

We do not maintain, and therefore cannot control or correct problems with, third-party content, software, tools, widgets, add-ins, or APIs, and shall not be liable for any inaccessibility with respect thereto. Should you encounter any difficulties with third-party content, you may notify us and/or direct your concerns to the respective third-party providers.

Date

This statement was created on July 1, 2025 and last revised on February 15, 2026, using the W3C Accessibility Statement Generator Tool (opens in new tab) as a structural reference.