@mddsharpp Thanks a lot for testing.
The errors that are being reported are those which have been caught. Notice that the my are all shown as being “new accepted”. That means that the plugin is sanitizing them (that is, removing them). Because of the sanitization, the AMP validator reports that it is valid, because the plugin makes it valid. And that is working exactly as intended.
So it is expected that you evaluate those validation errors reported, and if they are truly all OK to be sanitized, then you can mark them as Accepted to clear their “new” state. This will Mark the errors as acknowledged and you won’t get complaints about them anymore. If the theme then looks right style-wise and there isn’t any critical JS being removed (e.g. for ads or analytics) then you’re done! In general any theme should behave in AMP by default as if JS is disabled in the browser, since all custom JS is removed. So if the theme gracefully degrades for noscript visitors, as good themes should, then the paired mode should get you a great AMP version out of the box.
