component-driven / component-driven/cypress-axe

Axe-core trademark use

Open
#174 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
641
Forks
90
Avg merge
6h 8m
Merged PRs (30d)
1

Description

Thanks for using axe-core! Could you please ensure that you are adhering to the trademark policy? Axe-core is a trademark of Deque Systems. Here are some common tips that should help:
Ensure that the language surrounding your reference to axe-core does not imply in any way that you own it or have any formal partnership with Deque without prior written permission.
Include the following attribution notice: “Axe-core® is a trademark of Deque Systems, Inc. in the US and other countries.” Adding this to your readme is a common approach.
Axe-core® is capitalized at the beginning of a sentence. When used within a sentence, axe-core® is lowercase. Don’t stress attempting to include the ® symbol everywhere you say axe-core. If you include it in a prominent place, in addition to the attribution notice above, you should be good.
Do not mistake the broader axe® brand name for the axe-core® open source project.
Don’t stress renaming your entire project. If you adhere to the above tips, you should be covered in most cases.
Please comply with this request in 30 days time and let us know when to expect to see the changes live.

Regards,
The team at Deque

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking the repository README for references to axe-core and compare the surrounding language with the linked trademark policy. Done means adding the requested attribution notice and adjusting capitalization or partnership wording where needed, then confirming the README does not imply ownership or affiliation.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.