-
Hello. First, thank you for your hard work on this project. I'm interested in using this package to test an open-source library. However, the project's license seems so complex that I feel like I'd have to hire a few lawyers, so I thought I'd ask directly. I maintain Ariakit.org, where we're developing a CSS package to help developers style their websites. That's a CSS-only package that automatically adjusts the colors you provide to avoid mid-tones and determines foreground colors dynamically—not just black or white—using CSS relative color syntax. We're planning to use this APCA package (or a similar one) solely for automated testing of our generated CSS. It won't be distributed as part of our project. It's strictly for development purposes. Since it's a CSS-only package, we're a bit limited in what we can do, so we can't guarantee the output will be compliant. It's fine if we can't even mention APCA. My goal is simply to have automated tests to ensure that most use cases meet at least Lc 75. Are we allowed to use this project? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Yes of course, and we encourage experimentation right now. The restrictions are on public release of tools that use the APCA algorithm, until we release the final "certified" version. Love to see what you come up with! |
Beta Was this translation helpful? Give feedback.
Yes of course, and we encourage experimentation right now. The restrictions are on public release of tools that use the APCA algorithm, until we release the final "certified" version.
Love to see what you come up with!