Accessibility Statement

Our Commitment

SpaceNexus is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards to make our platform usable by the widest possible audience, regardless of ability or technology.

We believe that space industry intelligence should be accessible to all professionals, researchers, and enthusiasts. Accessibility is not an afterthought at SpaceNexus — it is a core part of how we design and build our platform.

Standards We Follow

SpaceNexus strives to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. These guidelines are published by the World Wide Web Consortium (W3C) and define how to make web content more accessible to people with disabilities. Conformance at Level AA addresses the most common barriers for users with visual, auditory, motor, and cognitive disabilities.

We also reference the following standards and best practices:

• WAI-ARIA (Accessible Rich Internet Applications) for dynamic content and interactive components
• Section 508 of the Rehabilitation Act (U.S. federal accessibility requirements)
• EN 301 549 (European accessibility standard for ICT products and services)
• ATAG 2.0 (Authoring Tool Accessibility Guidelines) for user-generated content features

Accessibility Measures

SpaceNexus takes the following measures to ensure accessibility:

• Include accessibility as part of our design system and internal development guidelines
• Provide ongoing accessibility training for our design and engineering teams
• Assign clear accessibility goals and responsibilities across teams
• Use semantic HTML throughout the platform for proper document structure
• Ensure sufficient color contrast ratios that meet or exceed WCAG AA thresholds
• Provide text alternatives for non-text content, including images, charts, and icons
• Support full keyboard navigation across all interactive elements
• Implement ARIA landmarks, labels, and live regions for screen reader compatibility
• Ensure forms include associated labels, clear error messages, and input instructions
• Maintain visible focus indicators for keyboard users
• Avoid content that flashes more than three times per second
• Design responsive layouts that work across a range of screen sizes and zoom levels up to 200%

Testing Approach

We evaluate the accessibility of SpaceNexus through a combination of automated and manual testing methods:

Automated Testing

• Axe-core automated accessibility scans integrated into our CI/CD pipeline
• Lighthouse accessibility audits run on every production build
• ESLint jsx-a11y plugin to catch common accessibility issues during development
• Automated color contrast checks across all theme variants

Manual Testing

• Keyboard-only navigation testing across all major user flows
• Screen reader testing with NVDA (Windows), VoiceOver (macOS/iOS), and TalkBack (Android)
• High contrast mode and forced colors testing
• Browser zoom testing at 200% and 400% magnification
• Testing with various assistive technologies including voice recognition software

Review Cadence

We perform comprehensive accessibility audits on a quarterly basis and conduct targeted reviews whenever significant new features or interface changes are introduced. Critical accessibility issues are treated with the same priority as security vulnerabilities.

Known Limitations

While we strive for full WCAG 2.1 AA conformance, we are aware of the following areas where we are actively working to improve accessibility:

• Interactive data visualizations: Some complex charts and orbital maps may not be fully accessible to screen readers. We provide data tables as alternative representations where possible and are working to expand this coverage.
• Real-time event feeds: Live update streams (such as launch telemetry and space weather alerts) may not always announce changes to assistive technologies in a timely manner. We are implementing ARIA live regions to address this.
• Third-party embedded content: Some externally embedded content (such as video players and social media widgets) may not fully meet our accessibility standards. We work with vendors to improve this and provide alternative access to the same information where feasible.
• PDF reports: Some downloadable PDF reports may have limited accessibility. We are working toward providing accessible HTML versions of all report content.

Assistive Technology Compatibility

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

• Screen readers: NVDA, JAWS, VoiceOver, TalkBack
• Screen magnification software
• Speech recognition software (e.g., Dragon NaturallySpeaking)
• Keyboard-only navigation
• Switch access devices
• Operating system accessibility features (high contrast, reduced motion, large text)

We support the current and previous two major versions of Chrome, Firefox, Safari, and Edge. The platform respects the prefers-reduced-motion and prefers-contrast media queries for users who have configured these preferences in their operating system.

Feedback and Contact

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

When reporting an accessibility issue, please include:

• The URL (web address) of the page where you encountered the issue
• A description of the problem and what you expected to happen
• The assistive technology you were using (if any), including its version
• Your browser and operating system

We aim to respond to accessibility feedback within two business days and to resolve reported issues within 30 days. If a fix requires more time, we will provide a timeline and, where possible, an interim workaround.

Enforcement Procedure

If you are not satisfied with our response to your accessibility concern, you may escalate the matter by contacting us at accessibility@spacenexus.us with the subject line "Accessibility Escalation." Our leadership team will review the issue and respond within five business days.