WishEDA Inc. ("Trace," "we," "our," or "us") is committed to ensuring that Trace is accessible to as many people as possible, including users with visual, auditory, motor, and cognitive disabilities. This statement describes the steps we take, our current status, and how to reach us if you encounter a barrier.

Our Commitment

We believe powerful design tools should be usable by everyone. We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA — the internationally recognized standard for digital accessibility — across buildwithtrace.com and our related web properties (including our component, symbol, and footprint libraries, documentation, status page, and dashboard), and to provide reasonable accessibility in our desktop application. Accessibility is an ongoing commitment that we build into our design and development process rather than treating it as a one-time project.

Conformance Status

We are actively working toward WCAG 2.1 Level AA conformance and have not yet completed a full independent audit, so we currently describe our status as "partially conformant" — meaning some parts of the Service may not yet fully meet the standard. We assess accessibility through a combination of automated tooling, manual keyboard and screen-reader testing, and accessibility coding standards enforced in our development workflow. We update this statement as our conformance improves.

Measures We Take

To support accessibility, we: (a) use semantic HTML, landmark regions, and a logical heading structure so assistive technologies can navigate our pages; (b) provide a visible keyboard focus indicator and ensure interactive elements are operable without a mouse; (c) label icon-only controls and form fields, and expose status messages and streaming AI responses to screen readers using live regions; (d) provide text alternatives for meaningful images and describe technical visualizations such as schematic and footprint previews, including data tables for pin and pad information; (e) maintain color-contrast levels intended to meet WCAG AA and avoid relying on color alone to convey meaning; (f) honor the operating system "reduce motion" preference; and (g) maintain internal accessibility coding standards so that new features are built with accessibility in mind.

Known Limitations

Despite our efforts, some areas have known limitations that we are actively working to address: (a) AI-generated outputs and certain richly interactive or graphical views — including detailed schematic and PCB layout canvases — can be difficult to represent fully to assistive technologies, and we provide text-based alternatives (such as pin and pad tables) where practical; (b) some legacy pages, embedded third-party content, and documentation rendered by external platforms may not yet fully conform; and (c) our desktop application is built on the open-source KiCad framework and inherits some interface components whose accessibility we do not fully control. We prioritize fixes based on user impact.

Third-Party Content

Some parts of the Service rely on third-party platforms and components — for example, documentation hosting, embedded media, payment processing, and authentication providers. We select accessible providers where possible, but we do not control and cannot guarantee the accessibility of all third-party content.

Feedback and Requesting Assistance

We welcome your feedback on the accessibility of Trace. If you encounter a barrier, need information in an alternative format, or would like to request a reasonable accommodation, contact us at hello@buildwithtrace.com with "Accessibility" in the subject line. Please describe the issue, the page or feature involved, and the assistive technology, browser, or operating system you are using so we can reproduce and address it. We aim to acknowledge accessibility requests within five business days and to provide the requested information or functionality through an accessible means while we work on a permanent fix.

Ongoing Effort

Accessibility is an ongoing effort. We review this statement periodically and as we ship significant changes to the Service, and we revise the "Last updated" date accordingly.