Built to be usable by everyone.

We believe accessible technology is better technology for everyone. Our goal is to deliver digital experiences that conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA — for our own website, and for the products we build with clients.

Accessibility is baked into our engineering practice. It is not a checklist we run at the end of a project; it is a requirement we design for from kickoff.

We target conformance with the following standards:

• Web Content Accessibility Guidelines (WCAG) 2.1 Level AA
• Section 508 of the U.S. Rehabilitation Act, for federal-facing work
• EN 301 549, for European public-sector work
• WAI-ARIA 1.2 best practices for interactive components

We work to ensure our site is perceivable, operable, understandable, and robust for assistive technologies. That includes:

• Semantic HTML and correct heading structure so screen readers can navigate efficiently
• Meaningful alt text for images that convey information
• Keyboard navigation for every interactive element, with visible focus styles
• Sufficient color contrast between text and background (4.5:1 for body text, 3:1 for large text and UI components)
• Support for prefers-reduced-motion to reduce or disable non-essential animation
• Responsive design that works at 200% zoom and on a range of viewport sizes
• Respect for user-set font sizes and system dark-mode preferences
• ARIA landmarks and labels where native HTML semantics are insufficient

Mudish Technologies aims for full WCAG 2.1 AA conformance. We test regularly with a combination of automated tools (axe-core, Lighthouse), manual keyboard-only testing, screen-reader testing (VoiceOver on macOS / iOS, NVDA on Windows), and color-contrast audits.

At present, we are partially conformant with WCAG 2.1 AA. “Partially conformant” means that parts of the content may not yet fully meet the standard. Specifically, the following areas are under active improvement:

• Some embedded third-party content (video players, chat widgets) may not meet our contrast or keyboard-navigation targets
• A small number of legacy decorative illustrations are missing fine-grained alt text
• Our motion-heavy hero sections are being audited against vestibular-disorder best practices; reduced-motion fallbacks are in progress

We track accessibility issues like any other engineering defect, triage them by impact, and fix them on a rolling basis.

We regularly test the site with the following combinations:

• VoiceOver on Safari (macOS) and Safari (iOS)
• NVDA on Firefox and Chrome (Windows)
• JAWS on Chrome (Windows)
• Keyboard-only navigation without a pointing device
• Zoom up to 200% and reflow at narrow viewport widths

Despite our best efforts, you may encounter barriers on this site. If you do, please let us know — we treat accessibility reports as high-priority bugs.

Third-party widgets (such as embedded media players, analytics overlays, or chatbots) are not fully under our control. Where a vendor widget does not meet our accessibility bar, we work with the vendor on a fix or replace the widget.

We welcome feedback on the accessibility of mudishtech.com. If you run into a barrier or need content in an alternative format, please contact us and we will work with you to provide the information you need.

• Email: accessibility@mudishtech.com
• Phone: available on request via accessibility@mudishtech.com
• Mail: Mudish Technologies, Inc., 23834 Grayhaven Place, Aldie, VA 20105, USA

We aim to respond to accessibility feedback within three business days, and to resolve reported issues as quickly as reasonably possible given severity.

If you contact us with an accessibility concern and are not satisfied with our response, you may escalate to the appropriate authority in your jurisdiction — for example, the U.S. Department of Justice (DOJ) for ADA matters, or your local equality/ombuds authority. We will continue to work with you to address your concerns in good faith regardless.

Accessibility is not a one-time project. We audit the site quarterly, train new engineers on accessible patterns during onboarding, and include an accessibility-review step in our design-and-build handoff for both our own site and client work. This page is updated when our conformance status, known issues, or escalation paths change.