Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False positive on skip link not being the first link #663

Closed
rianrietveld opened this issue Dec 20, 2017 · 3 comments
Closed

False positive on skip link not being the first link #663

rianrietveld opened this issue Dec 20, 2017 · 3 comments

Comments

@rianrietveld
Copy link

rianrietveld commented Dec 20, 2017

For WordPress sites it's common to use a skip link like this:

<a class="skip-link screen-reader-text" href="#content">Skip to content</a>

This code triggers the warning "the page should have a skip link as first link" although the skip link is the first link on the page.

output error warning

Tested on several WP sites, see for an example: rianrietveld.com that uses the WordPress Twenty Sixteen theme.

<body class="home blog hfeed">
    <div id="page" class="site">
        <div class="site-inner">
            <a class="skip-link screen-reader-text" href="#content">Skip to content</a>

Using

  • Chrome 63.0.3239.84 (Official Build) (64-bit)
  • aXe-Coconut 3.1.1 with axe-devtools 3.1.1 and axe-core 3.0.0-alpha 6
@WilcoFiers
Copy link
Contributor

WilcoFiers commented Dec 21, 2017

Thanks Rian. My guess is that it's related to this bug: #647

We'll certainly look into it.

@rianrietveld
Copy link
Author

Thanks @WilcoFiers 👍

@WilcoFiers
Copy link
Contributor

I've tested it with the fix Zack provided. It should be fixed in the next update to Coconut.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants