can you add a valid test using `components` as well?

these, and the options extraction, should be done at the top level of `create` to avoid having to do so every time the node is visited.

```suggestion context.report({ node, message: 'Ambiguous text within anchor. Screenreader users rely on link text for context; the words "{{wordsList}}" are ambiguous and do not provide enough context.', data: { wordsList: words.join('", "'), }, ```

how are you able to use type annotations in js files ?

```suggestion if (child.type === 'Literal' || child.type === 'JSXText) { return str + child.value; } return str; ``` switch statements should be avoided :-)

we can allow passing this list as an option as well , and fallback to this as default ?

this error message won't contain the right words if the config specifies its own words

adding a new rule to a config is a breaking change, so we can't do that here. ```suggestion 'jsx-a11y/anchor-ambiguous-text': 'off', // TODO: error ```

just checking that the text content matches any of the ambiguous text might not be enough, as the author might have already catered for this by adding an aria-label which explains things more clearly.

why only additional? what if someone doesn't want the default words?

```suggestion "jsx-a11y/img-redundant-alt": [2, { "words": ["click this"], ```

do we need to take care of JSXElement here ? ``` <a ...> Click <span> here </span> </a> ```