Accessibility Statement

AEGIS DATA SYSTEMS, LLC
Last updated: February 16, 2026

Our Commitment

AEGIS Data Systems is committed to ensuring digital accessibility for all users, including people with disabilities.
As a website development and application integration firm, accessibility is not an afterthought — it is a core design principle. We build websites to function as secure, structured command centers that connect the tools and applications businesses rely on. Accessibility is foundational to that mission.
We believe modern digital systems should be usable by everyone.

Standards we aim to follow

We strive to conform to the following accessibility standards and best practices:

  • WCAG 2.1 / 2.2 (Web Content Accessibility Guidelines) at Level AA
  • Section 508 of the U.S. Rehabilitation Act (where applicable)
  • WAI-ARIA (Accessible Rich Internet Applications) guidance for interactive components

Where clients require higher compliance levels (government, education, healthcare, enterprise), we design and test accordingly.

Accessibility features on this site

Depending on the page and content type, you may see features such as:

  • Semantic HTML structure (proper headings, landmarks, and labels)
  • Keyboard navigation support for menus, forms, and interactive elements
  • Color contrast designed for readability
  • Alternative text for key images and icons
  • Visible focus states for keyboard users
  • Responsive layouts that support zoom and reflow
  • Clear, human-readable content and error messaging

How We Build Accessible Websites

Accessibility is integrated into our development workflow — particularly within our Nexus Connect platform, where websites operate as structured application hubs.

Our accessibility approach includes:

  • Semantic HTML5 structure (clear heading hierarchy, landmarks, labels)
  • Keyboard-accessible navigation and forms
  • Proper focus states for interactive elements
  • Color contrast that meets WCAG AA standards
  • Scalable layouts that support zoom and reflow
  • ARIA attributes for dynamic components
  • Accessible form validation and error messaging
  • Alt text and descriptive media labeling
  • Structured content modeling for screen reader clarity

Accessibility is considered at the design, development, and deployment stages — not retrofitted after launch.

Third-Party Content & Integrations

Because AEGIS builds command-center websites that connect external platforms (CRM, ERP, payment systems, SaaS tools), some third-party integrations may introduce accessibility variables outside our direct control.

When integrating external systems, we:

  • Evaluate vendor accessibility documentation
  • Provide guidance to clients on platform limitations
  • Recommend accessible alternatives when feasiblearily introduce issues

Feedback and Support

If you have trouble accessing any part of this website, or if you want to report an accessibility issue, please contact us and include:

  • The page URL (or the page name)
  • What you were trying to do
  • Your browser/device details (optional but helpful)

Email: [email protected]
Phone: +1 (229) =1266-2180
Response Time: We aim to respond within 2 business days.

Alternative Formats

If you need information on this site provided in an alternative format (for example: accessible PDF, large print, or plain text), we will work with you to provide a suitable version.

Ongoing improvements

We regularly evaluate accessibility using a combination of:

  • Automated scanning tools
  • Manual testing (keyboard-only navigation, zoom/reflow checks, contrast checks)
  • Assistive technology spot checks (screen reader behavior where applicable)

We also incorporate accessibility practices into design, development, and content publishing workflows to reduce issues before they reach production.