Accessibility Statement

Version 0.1.0 · Last reviewed: 2026-04-30

1. Introduction

Called 2 Work DBA Zia Code LLC is committed to making its job-board service usable by the widest possible audience, regardless of ability or assistive technology. We design and build to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, and we track related international standards including EN 301 549 (the EU harmonized accessibility standard) and Section 508 of the US Rehabilitation Act for federal procurement-style baselines.

This statement describes our current accessibility posture, the measures we take, the limitations we are aware of, and the ways you can contact us if something on the site does not work for you.

2. Conformance status

We aim to conform to WCAG 2.1 Level AA. This page documents the current status, known gaps, and how to request assistance or report issues. “Aim to conform” means we have designed and built to the standard and continue to measure ourselves against it; it does not mean that every page has been formally certified by an independent auditor (see Section 5).

3. Measures we take

The following measures are part of how we ship the service. The list is non-exhaustive and evolves as the product grows.

  • Semantic HTML. Pages are built from semantic landmarks (<main>, <nav>, <header>, <article>, <section>) so that assistive tech can navigate the page structure without guessing.
  • ARIA labeling. Where native semantics are insufficient (custom widgets, dynamic regions, modals), we label elements with aria-label, aria-labelledby, andaria-describedby rather than relying on visual context alone.
  • Keyboard navigation. Every interactive element is reachable and operable with the keyboard alone. Focus order follows the visual reading order, and focus indicators are visible on focused controls.
  • Skip-to-content link. A skip-to-content link is the first focusable item on every page, allowing keyboard and screen-reader users to jump past site chrome to #main-content directly.
  • Color and contrast. Text and meaningful UI elements target the WCAG AA contrast thresholds (4.5:1 for body text, 3:1 for large text and non-text UI). Color is never the sole carrier of meaning.
  • Modal focus management. Dialog-style overlays (for example, the cookie preference center) use role="dialog" with aria-modal, set initial focus into the dialog on open, and close on the Escape key — returning focus to the triggering control on close.
  • Reduced motion. We respect the operating-system prefers-reduced-motion setting and avoid or soften decorative animation for users who request it.
  • Alt text. Meaningful images have descriptive alt attributes. Purely decorative images use empty alt="" so screen readers can skip them.
  • Form labeling. Every form control has an associated <label> (oraria-label where a visible label is impractical), error messages are programmatically associated with their fields, and required fields are announced.

4. Compatibility

The site is designed to work with current evergreen browsers (Chrome, Firefox, Edge) and current Safari on macOS and iOS. With assistive technology, we target reasonable compatibility with VoiceOver (macOS / iOS), NVDA (Windows), and TalkBack (Android), as well as standard mobile screen-reader gestures.

Older browsers and outdated assistive-tech versions may show degraded styling or behavior. We recommend keeping both your browser and your assistive-technology software up to date for the best experience.

5. Known limitations

We want to be honest about where we are. Called 2 Work DBA Zia Code LLC is a small, community-funded project, and the following limitations apply today:

  • We do not currently have a paid third-party accessibility audit. An independent audit is on the v1.1 funded roadmap; until then, conformance is self-assessed against WCAG 2.1 Level AA.
  • User-generated content (job postings, profile copy, chat messages) may include images, links, or formatting outside our direct control. We provide tooling and guidance to encourage accessible authoring (for example, prompting for alt text on uploads), but we cannot guarantee the accessibility of every user-authored item.
  • Some third-party embeds (for example, Stripe Checkout for donations) are styled and operated by their vendors. We monitor vendor accessibility posture and select vendors with published WCAG conformance where possible, but we do not control their internal implementations.

6. Feedback channel

If you encounter an accessibility barrier, or if a workaround we offer is itself inaccessible, please tell us. Email [email protected] with a description of the problem, the page or feature where it occurred, and the assistive technology you were using if applicable.

We commit to acknowledging accessibility reports within five business days and providing a remediation timeline appropriate to the severity of the issue. Where a fix takes longer than the acknowledgment window, we will work with you on a temporary workaround so that the affected functionality is not blocked for you in the meantime.

7. Formal complaint pathways

For users in the European Union: once Called 2 Work DBA Zia Code LLC appoints an Article 27 representative and the EU geo-block is lifted (see the privacy policy for the current jurisdictional posture), the EU Web Accessibility Directive enforcement pathway in your member state will be available as a route of last resort if our internal feedback channel cannot resolve your issue. We will publish the specific competent-authority contact at that time.

For users in the United States: Called 2 Work DBA Zia Code LLC is operated by a small business that is not currently a public entity bound by Title II of the Americans with Disabilities Act, and is below the size threshold at which Title III public-accommodation obligations are routinely enforced against web operators. We nevertheless follow the spirit of the ADA and Section 504 of the Rehabilitation Act and will treat barrier reports seriously. Counsel will refine this section before publication.

8. Date last reviewed

This statement was last reviewed on 2026-04-30. We review the statement at least annually and whenever a significant feature ships that changes the accessibility posture of the service.