A11y i18n

[exterkamp]

Provide the steps to reproduce

As of #7008 there are some gaps in a11y translation:

• title, and category description
  
• Manual Audits
  

[paulirish]

As of #7008 there are some gaps in a11y translation:

We could bring back https://github.com/GoogleChrome/lighthouse/pull/5726/files#diff-4bcfedf0736e1cd08b26fe659537ad90 to help avoid this.

[patrickhulce]

We could bring back https://github.com/GoogleChrome/lighthouse/pull/5726/files#diff-4bcfedf0736e1cd08b26fe659537ad90

Huzzah!! Yes please :D

[brendankenny]

We could bring back https://github.com/GoogleChrome/lighthouse/pull/5726/files#diff-4bcfedf0736e1cd08b26fe659537ad90 to help avoid this.

wait, is that to make it easier to spot when we've missed some strings when manually testing? Is it that different than just loading in russian and looking for english?

[patrickhulce]

@brendankenny you have to wait for the translations to come back though, that bit was us programmatically generating it so you could notice as you're going.

[paulirish]

I also want to comment in this thread right now.

[brendankenny]

We need the script to load in the en-XA to see that it's bad before we send it to be translated afaik.

Cool. But I do predict the exact same pace of people actually loading another locale to check if we've missed something :P

[exterkamp]

Well now I have to leave a comment.

[brendankenny]

more comments: can we turn this into an i18n phase 2 issue and close #5719? Or turn it into a en-XA and make a phase 2 issue elsewhere