aicente Logoaicente

Accessibility Statement

Last updated: May 2025

aicente is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply relevant accessibility standards.

1. Our Commitment

We strive to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines explain how to make web content more accessible to people with disabilities, including those with visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

2. Measures We Take

Keyboard Navigation

All interactive elements on our platform are accessible via keyboard navigation. Users can tab through links, buttons, and form fields without requiring a mouse.

Screen Reader Support

We use semantic HTML, ARIA labels, and descriptive alt text for images to ensure compatibility with screen readers such as NVDA, JAWS, and VoiceOver.

Color Contrast

Text and interactive elements maintain a minimum contrast ratio of 4.5:1 against their backgrounds to ensure readability for users with low vision or color blindness.

Resizable Text

Our platform supports browser-level text resizing up to 200% without loss of content or functionality.

3. Known Limitations

While we strive for full accessibility, some third-party content or embedded tools may not yet meet all accessibility standards. We are actively working with our partners to address these gaps and improve the overall experience.

4. Feedback & Contact

We welcome feedback on the accessibility of aicente. If you experience any barriers or have suggestions for improvement, please contact us:

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

5. Formal Complaints

If you are not satisfied with our response, you have the right to contact your local equality or human rights body for further assistance.

6. Technical Specifications

aicente relies on the following technologies for conformance with WCAG 2.1 AA: HTML5, CSS3, WAI-ARIA 1.1, and JavaScript. We test our platform with the following assistive technologies and browser combinations:

  • NVDA with Firefox on Windows
  • JAWS with Chrome on Windows
  • VoiceOver with Safari on macOS and iOS
  • TalkBack with Chrome on Android
  • Keyboard-only navigation on all major browsers

We use automated accessibility testing tools — including axe-core and Lighthouse — as part of our development workflow, supplemented by manual audits conducted quarterly by members of our engineering team.

7. Accessibility Roadmap

We are actively working to improve accessibility across our platform. Current priorities on our accessibility roadmap include:

  • Enhanced focus management for modal dialogs and dynamic content updates across all aicente tools
  • Improved ARIA live region announcements for real-time data updates in Action Dispatcher and fleet tracking views
  • Accessible drag-and-drop support for the Action CRM pipeline and Action Proposal section editor
  • Full keyboard support for the Action Sign document editor and field placement interface
  • Audio description alternatives for video content in Action Studio
  • Improved color contrast in low-emphasis UI elements across dark-mode dashboards

8. Scope of This Statement

This accessibility statement applies to the aicente web platform at aicente.com, including all product subpages and authenticated dashboards: Action CRM, Action Sign, Action Proposal, Action Invoicing, Action Calendar, Action Mail, Action Studio, Action Limo, Action Dispatcher, Action Delivery, Action Docs, Action Link, and Action Teams. Mobile applications are governed by separate accessibility documentation. Third-party services embedded in or linked from aicente — such as payment processors, mapping services, or external data providers — are subject to their own accessibility policies.

This statement was last reviewed and updated in May 2025. We review and update this statement at least annually, or whenever significant changes are made to the platform.

Accessibility at aicente

Every person deserves equal access to online tools. At aicente, we design for all users — including people who use screen readers, keyboard navigation, or other assistive tools.

Our Standard

We follow the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. This means our pages work with keyboards, have good color contrast, include text alternatives for images, and give users enough time to read and act on content.

Screen Reader and Keyboard Support

We test with screen readers on Windows, Mac, and mobile devices. Every page works with keyboard-only navigation. Focus is always visible. Users can skip repeated menus and jump straight to the main content.

Color and Contrast

All text meets a minimum contrast ratio of 4.5 to 1. We never use color alone to show important information. Error messages always include a written description, not just a red highlight.

Forms and Error Messages

All form fields have clear labels. Error messages are specific and easy to understand. We show what went wrong and how to fix it. Required fields are clearly marked.

Report an Issue

Found a barrier on our site? Email admin@aicente.com with the page address and a brief note about what happened. We reply within 2 business days and aim to fix critical issues within 30 days.

Assistive Technology Compatibility

aicente is tested for compatibility with JAWS and NVDA on Windows, VoiceOver on macOS and iOS, and TalkBack on Android. Interactive components including modals, dropdowns, date pickers, and data tables use ARIA roles and live regions to communicate state changes to assistive technologies. Form validation errors are announced to screen reader users immediately on submission without requiring a page reload.

Motion and Animation

aicente respects the operating system's reduced motion preference. When a user has enabled the "Reduce Motion" setting on their device, animations and transitions throughout the platform are minimized or removed entirely. This applies to page transitions, loading spinners, hover effects, and all animated UI elements across the dashboard and product tools.

Third-Party Content

Some aicente pages embed or link to third-party services — payment processors, mapping providers, and external data sources. These services operate under their own accessibility policies and may not meet the same standards as aicente. Where third-party components fall below WCAG 2.1 AA standards, we provide accessible alternatives where technically feasible. We prioritize partners with strong accessibility commitments in our vendor selection process.

Ongoing Commitment

Accessibility is a continuous process, not a one-time fix. aicente runs automated accessibility scans on every code deployment, conducts manual testing with screen readers on a quarterly basis, and incorporates user feedback from the accessibility support channel into product planning. We include accessibility criteria in the acceptance requirements for every new feature before it is released to production.