i18n: axe 3.3

[Elfo404]

Summary
Changes axe urls to 3.3

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[Elfo404]

I signed it! 😃

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[exterkamp]

Definitely blocked behind #9114 (as we don't want to round trip these changes to our translators without placeholders), but this looks fine to me. Revert all the files under locales/*.json, we update those with the translation updates.

Once #9114 lands you should be able to revert all locales/*.json files and then run yarn i18n to update the en-US and en-XL files and make sure everything is 100%.

I also think this overlaps heavily/totally with #9084. Which I think we'll prefer. @egsweeny @paulirish ?

[Elfo404]

@exterkamp oh, didn't know about #9084 , my bad!

I guess we can close this one then as it doesn't make much sense.

[exterkamp]

I guess we can close this one then as it doesn't make much sense.

Okay, SGTM. Sorry that #9084 was kinda hidden! Thanks for the PR, we definitely appreciate the effort and involvement!

[exterkamp]

@Elfo404 Found something that relates to this though. In web.dev, articles on Lighthouse a11y, they point to axe 3.2 at the bottom:

https://github.com/GoogleChrome/web.dev/blob/master/src/site/content/en/lighthouse-accessibility/accesskeys/index.md

They might want a bug/PR to update those links to 3.3 since thats what LH uses now. (I only did a brief check if this is on their radar already, so I'd ask before making a PR so that this kind of thing doesn't happen again over there jsyk)