Accessibility

Our commitment to an inclusive experience for every user.

Last reviewed: March 2026

Our Commitment

Hubity 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.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across all user-facing surfaces, including the main application, public marketing pages, and email communications.

Standards We Follow

WCAG 2.1 Level AA

Our target conformance level for all new features and existing surfaces. We evaluate against all Level A and Level AA success criteria.

Section 508

Hubity is designed to meet the requirements of Section 508 of the Rehabilitation Act for U.S. federal accessibility standards.

EN 301 549

We align with the European accessibility standard for ICT products and services where applicable.

ADA Compliance

We design and develop our platform to be compatible with assistive technologies in accordance with the Americans with Disabilities Act.

What We Do

Keyboard navigation

All interactive elements are reachable via keyboard with visible focus indicators. Tab order follows a logical reading sequence.

Screen reader support

ARIA labels, roles, and live regions provide full compatibility with assistive technologies including VoiceOver, NVDA, and JAWS.

Semantic HTML

Proper heading hierarchy, landmark regions, and form labels are used throughout the application for clear document structure.

Color contrast

All text and UI elements meet WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text) in both light and dark themes.

Skip navigation

A skip-to-content link is provided for keyboard users to bypass repetitive navigation elements.

Responsive design

The platform is fully usable on mobile, tablet, and desktop with touch, pointer, and keyboard input support.

Focus management

When modals, panels, or dialogs open, focus is moved to the new content and trapped appropriately. Closing returns focus to the trigger element.

Motion preferences

Animations and transitions respect the prefers-reduced-motion media query. Users who prefer reduced motion see simplified transitions.

Text resizing

The interface supports browser text zoom up to 200% without loss of content or functionality.

Error identification

Form validation errors are clearly identified with text descriptions, not color alone, and are associated with their respective fields.

Testing

We test accessibility through a combination of automated tools and manual review:

Automated scanning

Continuous integration checks catch common accessibility regressions before code reaches production.

Manual testing

Interactive features are tested with keyboard-only navigation and screen readers (VoiceOver on macOS/iOS, NVDA on Windows).

Color analysis

Contrast ratios are verified for all color combinations used in the interface, including dynamic theme switching.

Known Limitations

We are continuously working to improve accessibility. Some areas where we are actively making progress:

Third-party content

Some embedded content from third-party services may not fully conform to our accessibility standards. We work with vendors to improve this.

Complex charts

Interactive chart components provide basic accessibility through ARIA labels but may have limited screen reader narration for detailed data points.

Real-time features

Live-updating content like the status page and meeting transcription includes ARIA live regions, but rapid updates may occasionally be verbose for screen reader users.

Feedback

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

Email: [email protected]

We aim to respond to accessibility feedback within two business days and to resolve reported barriers as quickly as possible.

Accessibility

Our commitment to an inclusive experience for every user.

Last reviewed: March 2026

Our Commitment

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across all user-facing surfaces, including the main application, public marketing pages, and email communications.

Standards We Follow

WCAG 2.1 Level AA

Our target conformance level for all new features and existing surfaces. We evaluate against all Level A and Level AA success criteria.

Section 508

Hubity is designed to meet the requirements of Section 508 of the Rehabilitation Act for U.S. federal accessibility standards.

EN 301 549

We align with the European accessibility standard for ICT products and services where applicable.

ADA Compliance

We design and develop our platform to be compatible with assistive technologies in accordance with the Americans with Disabilities Act.

What We Do

Keyboard navigation

All interactive elements are reachable via keyboard with visible focus indicators. Tab order follows a logical reading sequence.

Screen reader support

ARIA labels, roles, and live regions provide full compatibility with assistive technologies including VoiceOver, NVDA, and JAWS.

Semantic HTML

Proper heading hierarchy, landmark regions, and form labels are used throughout the application for clear document structure.

Color contrast

All text and UI elements meet WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text) in both light and dark themes.

Skip navigation

A skip-to-content link is provided for keyboard users to bypass repetitive navigation elements.

Responsive design

The platform is fully usable on mobile, tablet, and desktop with touch, pointer, and keyboard input support.

Focus management

When modals, panels, or dialogs open, focus is moved to the new content and trapped appropriately. Closing returns focus to the trigger element.

Motion preferences

Animations and transitions respect the prefers-reduced-motion media query. Users who prefer reduced motion see simplified transitions.

Text resizing

The interface supports browser text zoom up to 200% without loss of content or functionality.

Error identification

Form validation errors are clearly identified with text descriptions, not color alone, and are associated with their respective fields.

Testing

We test accessibility through a combination of automated tools and manual review:

Automated scanning

Continuous integration checks catch common accessibility regressions before code reaches production.

Manual testing

Interactive features are tested with keyboard-only navigation and screen readers (VoiceOver on macOS/iOS, NVDA on Windows).

Color analysis

Contrast ratios are verified for all color combinations used in the interface, including dynamic theme switching.

Known Limitations

We are continuously working to improve accessibility. Some areas where we are actively making progress:

Third-party content

Some embedded content from third-party services may not fully conform to our accessibility standards. We work with vendors to improve this.

Complex charts

Interactive chart components provide basic accessibility through ARIA labels but may have limited screen reader narration for detailed data points.

Real-time features

Live-updating content like the status page and meeting transcription includes ARIA live regions, but rapid updates may occasionally be verbose for screen reader users.

Feedback

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

Email: [email protected]

We aim to respond to accessibility feedback within two business days and to resolve reported barriers as quickly as possible.

Accessibility

Our Commitment

Standards We Follow

What We Do

Testing

Known Limitations

Feedback

Besser arbeiten, gemeinsam.

Accessibility

Our Commitment

Standards We Follow

What We Do

Testing

Known Limitations

Feedback

Besser arbeiten, gemeinsam.