Accessibility | Guardimesh

Our Commitment

Illya LLC is committed to ensuring that the Guardimesh platform is accessible to all users, including people with disabilities. We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA across all of our web properties, including the public website and the authenticated web console.

Accessibility is a continuous effort, not a one-time project. We integrate accessibility considerations into every stage of our design and development process, and we treat accessibility defects with the same severity as functional defects.

Standards

Our target conformance level is WCAG 2.1 Level AA, as published by the World Wide Web Consortium (W3C). This standard is widely recognized as the benchmark for web accessibility and meets or exceeds the requirements of:

The Americans with Disabilities Act (ADA) Title III
Section 508 of the Rehabilitation Act
The California Unruh Civil Rights Act (Cal. Civ. Code sections 51-53)
The European Accessibility Act (EAA)

Accessibility Features

The Guardimesh platform includes the following accessibility features:

Skip navigation: A “Skip to main content” link is available as the first focusable element on every page, allowing keyboard users to bypass repetitive navigation.
Semantic HTML and landmarks: All pages use proper semantic HTML elements (<header>, <nav>, <main>, <footer>) and ARIA landmark roles to enable assistive technology navigation.
Keyboard navigation: All interactive elements are fully operable using only a keyboard. Focus indicators are visible on all focusable elements.
Screen reader support: Content is structured with proper heading hierarchy, ARIA attributes, and live regions to ensure screen readers can accurately convey page content and dynamic updates.
High color contrast: All text meets or exceeds the WCAG AA minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text.
Reduced motion: Animations and transitions are automatically disabled for users who have enabled the “reduce motion” preference in their operating system settings.
High contrast mode: The interface remains fully usable in Windows High Contrast Mode and other forced-color environments.
Accessible forms: All form inputs have associated labels, validation errors are linked to their inputs via ARIA attributes, and error messages are announced to screen readers immediately.
Responsive design: Content reflows without loss of information or functionality at up to 200% zoom and at viewport widths as narrow as 320 CSS pixels.

Technologies

We use accessibility-focused technologies and tooling throughout our development process:

Headless UI (public website) and PatternFly 6 (web console) provide accessible, pre-built interactive components with built-in keyboard navigation, focus management, and ARIA support.
ESLint with jsx-a11y enforces accessibility rules at code time, catching missing alternative text, invalid ARIA attributes, and inaccessible interactive patterns before code is merged.
axe-core integration testing validates rendered pages against WCAG success criteria in our automated test suite.

Testing

We employ a multi-layered testing approach to maintain accessibility conformance:

Automated linting: Static analysis with eslint-plugin-jsx-a11y runs on every code change, catching common accessibility issues such as missing labels, empty headings, and incorrect ARIA usage.
Automated integration testing: axe-core scans rendered pages for WCAG violations as part of our test suite.
Manual keyboard testing: Interactive features are verified to be fully operable using keyboard-only navigation.
Screen reader testing: Features are verified with screen readers (VoiceOver, NVDA, Orca) to ensure content is accurately announced.
Color contrast verification: Custom colors are verified against WCAG contrast requirements before use.

Known Limitations

While we work to ensure comprehensive accessibility, certain limitations exist:

Third-party payment forms: Our payment processing is handled by Stripe. While Stripe maintains its own accessibility standards, we do not have direct control over the accessibility of their embedded payment forms.
Continuous improvement: We regularly audit our platform and address newly identified barriers. If you encounter an issue not listed here, please contact us so we can prioritize a fix.

Feedback

We welcome feedback on the accessibility of the Guardimesh platform. If you encounter an accessibility barrier or have suggestions for improvement, please contact us:

Email: support@illya.us
Subject line: Include “Accessibility” for faster routing
Response time: We aim to respond to accessibility feedback within 5 business days

When reporting an accessibility issue, please include the URL of the page, a description of the barrier you encountered, and the assistive technology you were using (if applicable). This helps us reproduce and resolve the issue quickly.

Enforcement

If you are not satisfied with our response to your accessibility concern, you may contact the appropriate enforcement body in your jurisdiction. In the United States, the Department of Justice Civil Rights Division handles complaints under the Americans with Disabilities Act. In California, the Department of Fair Employment and Housing handles complaints under the Unruh Civil Rights Act.

Our Commitment

Standards

The Americans with Disabilities Act (ADA) Title III
Section 508 of the Rehabilitation Act
The California Unruh Civil Rights Act (Cal. Civ. Code sections 51-53)
The European Accessibility Act (EAA)

Accessibility Features

The Guardimesh platform includes the following accessibility features:

Skip navigation: A “Skip to main content” link is available as the first focusable element on every page, allowing keyboard users to bypass repetitive navigation.
Semantic HTML and landmarks: All pages use proper semantic HTML elements (<header>, <nav>, <main>, <footer>) and ARIA landmark roles to enable assistive technology navigation.
Keyboard navigation: All interactive elements are fully operable using only a keyboard. Focus indicators are visible on all focusable elements.
Screen reader support: Content is structured with proper heading hierarchy, ARIA attributes, and live regions to ensure screen readers can accurately convey page content and dynamic updates.
High color contrast: All text meets or exceeds the WCAG AA minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text.
Reduced motion: Animations and transitions are automatically disabled for users who have enabled the “reduce motion” preference in their operating system settings.
High contrast mode: The interface remains fully usable in Windows High Contrast Mode and other forced-color environments.
Accessible forms: All form inputs have associated labels, validation errors are linked to their inputs via ARIA attributes, and error messages are announced to screen readers immediately.
Responsive design: Content reflows without loss of information or functionality at up to 200% zoom and at viewport widths as narrow as 320 CSS pixels.

Technologies

We use accessibility-focused technologies and tooling throughout our development process:

Headless UI (public website) and PatternFly 6 (web console) provide accessible, pre-built interactive components with built-in keyboard navigation, focus management, and ARIA support.
ESLint with jsx-a11y enforces accessibility rules at code time, catching missing alternative text, invalid ARIA attributes, and inaccessible interactive patterns before code is merged.
axe-core integration testing validates rendered pages against WCAG success criteria in our automated test suite.

Testing

We employ a multi-layered testing approach to maintain accessibility conformance:

Automated linting: Static analysis with eslint-plugin-jsx-a11y runs on every code change, catching common accessibility issues such as missing labels, empty headings, and incorrect ARIA usage.
Automated integration testing: axe-core scans rendered pages for WCAG violations as part of our test suite.
Manual keyboard testing: Interactive features are verified to be fully operable using keyboard-only navigation.
Screen reader testing: Features are verified with screen readers (VoiceOver, NVDA, Orca) to ensure content is accurately announced.
Color contrast verification: Custom colors are verified against WCAG contrast requirements before use.

Known Limitations

While we work to ensure comprehensive accessibility, certain limitations exist:

Third-party payment forms: Our payment processing is handled by Stripe. While Stripe maintains its own accessibility standards, we do not have direct control over the accessibility of their embedded payment forms.
Continuous improvement: We regularly audit our platform and address newly identified barriers. If you encounter an issue not listed here, please contact us so we can prioritize a fix.

Feedback

We welcome feedback on the accessibility of the Guardimesh platform. If you encounter an accessibility barrier or have suggestions for improvement, please contact us:

Email: support@illya.us
Subject line: Include “Accessibility” for faster routing
Response time: We aim to respond to accessibility feedback within 5 business days

Accessibility Statement

Our Commitment

Standards

Accessibility Features

Technologies

Testing

Known Limitations

Feedback

Enforcement

Accessibility Statement

Our Commitment

Standards

Accessibility Features

Technologies

Testing

Known Limitations

Feedback

Enforcement