Skip to content

false positives depending on which viewport comes first #300

Description

@a11ya11y

There are some odd false positives that appear to result when the "small" (320x450) viewport comes first in the config file.

Here are Oranga Tamariki's 3 sites with the false positives, which are contrast errors with the spans of text in the main menu at the "medium" viewport -- otherwise there should be no issues on these sites:

organisation,url,sector
org,https://www.hcn.govt.nz/,sector
org,https://www.orangatamariki.govt.nz/,sector
org,https://www.strengtheningfamilies.govt.nz/,sector

There's a bit of fading in/out with the menu items as one moves between viewports--I'm not sure if this is contributing.

On my local machine, if I test the sites with the "medium" (1280x800) viewport first in the config file, then the false positives disappear. Otherwise, I get pretty consistent false positives for strengtheningfamilies.govt.nz.

The same thing is happening on www.corrections.govt.nz. If I run a scan with the "small" viewport first in the config file, false positives on the "medium" viewport show up. If I reverse the order in the config, and have "medium" first, the false positives disappear.

On its own, setting a 3s delay after page load or between page loads or between viewports hasn't seemed to prevent the false positives as long as the "small" viewport comes first in the config file.

It could be worth noting that CWAC is using a rather older version of Chrome. It's worth testing with a recent version.

Possibly related to #297

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions