Skip to content
Archade
Loading page…
··
© Archade
Home
LArchade Legal
A
ArchadeLegal
Documents
OverviewTerms of ServicePrivacy PolicyContent License & Contributor AgreementContent & AttributionDataset LicenseDataset Opt-OutHow We Use Public DataAI & Automated ProcessingData Usage & EthicsDMCA & TakedownCookie PolicyIntellectual PropertyEntity ClaimsHiring & Jobs PolicyPayments & SubscriptionsMarketplace TermsCommunity GuidelinesReporting & TakedownsGDPR Rights
Accessibility Statement
Security Practices
Active Policy v1.0

Accessibility Statement

How Archade on the web and in the iOS and Android apps works with assistive technology, and how to report a barrier.

Effective Date: January 14, 2026 · Updated: October 20, 2026 (mobile apps)

Archade Inc. ("Archade") is committed to ensuring digital accessibility for people of all abilities. We are continuously improving the user experience for everyone and applying relevant accessibility standards.


1. Conformance Status

We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Archade takes the following measures to ensure accessibility:

  • Integrating accessibility into our internal design and engineering practices.
  • Assigning clear accessibility targets and responsibilities.
  • Employing formal quality assurance methods, including automated testing.

Reasonable Efforts: While we aim for comprehensive compliance, we acknowledge that full conformance across every page of a rapidly evolving platform is an ongoing process.


2. Accessibility Features

The Archade platform is built with the following assistive technologies in mind:

  • Semantic HTML: Proper heading structures and landmarks for screen reader navigation.
  • Keyboard Operability: Interactive elements are navigable without a mouse.
  • Visual Standards: Enforcement of sufficient color contrast ratios.
  • Media Alternatives: Text equivalents (Alt Text) for images and indexable assets.
  • Responsive Design: Usable across desktop, tablet, and mobile magnification levels.

3. Archade Mobile (iOS and Android)

This section covers the Archade apps for iPhone and Android. They follow the same commitment as the website: WCAG 2.1 Level AA, applied to native apps the way Apple's and Google's accessibility guidelines describe.

3.1 What the apps support

  • Screen readers: Every control is built to be reached and named by VoiceOver (iOS) and TalkBack (Android). Buttons drawn as icons carry a spoken label, toggles such as Follow and Save announce their state, and progress and errors (for example after applying to a job or publishing a project) are announced.
  • Larger text: Text follows your Dynamic Type (iOS) or font size (Android) setting, up to twice the default size for body text. Large display titles grow up to 1.3× so a single heading does not fill the screen; when text is shortened on screen, the full text is still read aloud.
  • Reduce Motion: With Reduce Motion (iOS) or Remove animations (Android) on, motion such as cover transitions, parallax and pull-to-refresh drawing is replaced by short cross-fades. Confirmation haptics are kept.
  • Colour and contrast: Both light and dark themes are drawn from one set of colour tokens whose text and control pairs are checked against WCAG contrast ratios on every change. States such as selection and errors are designed not to rely on colour alone.
  • Touch and alternatives to gestures: Icon buttons and other small controls have a touch area of at least 44 × 44 points. Actions offered by swiping, such as shortlisting or declining an applicant, are also available as buttons or as screen-reader actions.

3.2 How we check

Before each public release, the apps are audited on an iPhone and an Android reference device with VoiceOver, TalkBack, the largest text sizes, Reduce Motion and high-contrast settings, across the core journeys: first open, applying to a job, publishing a project, reviewing applicants and returning to the feed. A release does not go out with an open finding that blocks or seriously impairs one of those journeys.

3.3 Mobile-specific limitations

  • Some areas open the Archade website in an in-app browser rather than a native screen (for example catalogue management, institution administration, datasets and API keys, award review and billing). They follow the website's accessibility, described in this statement.
  • The image and 3D limitations in Section 4 apply to the apps as well.

4. Known Limitations

Despite our best efforts, users may encounter barriers in specific areas of the platform. We are working to resolve the following known limitations:

4.1 User-Generated Content (UGC)

  • Images & PDF Portfolios: Content uploaded by users may lack sufficient alt text or structural tags. We provide tools to encourage accessible uploads but cannot guarantee the compliance of third-party content.
  • Videos: User-uploaded videos may not always include captions or transcripts.

4.2 Advanced Visualizations

  • 3D Viewers & BIM Explorers: Interaction with complex 3D models and interactive canvases (e.g., WebGL viewers) may be difficult or impossible using standard screen readers. We are actively monitoring industry standards for 3D accessibility.

4.3 Third-Party Integrations

  • External components (e.g., map widgets, payment iframes) are subject to the provider's accessibility standards and may not fully align with our core platform.

5. Feedback & Remediation Process

We welcome your feedback on the accessibility of Archade. If you encounter barriers:

  • Email: legal@archade.app
  • From the apps: write to the same address, naming the screen, your device and the setting you use (for example VoiceOver or larger text).
  • Response Time: We aim to respond to accessibility reports within 5 business days.

Alternative Access: If a specific feature is inaccessible, our support team will make reasonable efforts to provide the information or service through an alternative method.


6. Technology Environment

Accessibility of Archade relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript
  • The iOS and Android accessibility APIs (UIAccessibility, Android Accessibility Framework), for the mobile apps

Owner: Product + Design Systems .....

© 2026 Archade Inc.PrivacyTerms
Last updated February 1, 2026