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
SimpleTOC is not to blame, weird characters need to be encoded in URL's for sure, but have you considered filtering them out entirely. A manual inserted ID without encoded smileys satisfies the accessibility check.
Nothing critically that cannot be worked around, but maybe a potential improvement.
Bjarne
The text was updated successfully, but these errors were encountered:
SimpleTOC encodes "special characters" in the header, for instance 😉, when creating an ID for that header, as expected.
That triggers a false "broken link" accessibility check error. Reported here:
equalizedigital/accessibility-checker#483
Screenshot:
SimpleTOC is not to blame, weird characters need to be encoded in URL's for sure, but have you considered filtering them out entirely. A manual inserted ID without encoded smileys satisfies the accessibility check.
Nothing critically that cannot be worked around, but maybe a potential improvement.
Bjarne
The text was updated successfully, but these errors were encountered: