You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an aria-current="page" is added to a span, as can now happen with WordPress + Yoast SEO, the AMP validator invalidates the page with a The attribute 'aria-current' may not appear in tag 'span' error message.
On a WordPress install, using Yoast SEO, a page that has pagination will cause this error. Can also be reproduced by adding the aria-current attribute to any element I think.
Which AMP version is affected?
Tested as of 2017-11-17
The text was updated successfully, but these errors were encountered:
What's the issue?
If an aria-current="page" is added to a span, as can now happen with WordPress + Yoast SEO, the AMP validator invalidates the page with a
The attribute 'aria-current' may not appear in tag 'span'
error message.[EDIT]: I looked up https://github.com/ampproject/amphtml/blob/master/validator/validator-main.protoascii and it appears that aria-current is simply not whitelisted.
How do we reproduce the issue?
On a WordPress install, using Yoast SEO, a page that has pagination will cause this error. Can also be reproduced by adding the aria-current attribute to any element I think.
Which AMP version is affected?
Tested as of 2017-11-17
The text was updated successfully, but these errors were encountered: