search

mozilla-services / axe-selenium-python

aXe Selenium Integration python package
https://pypi.python.org/pypi/axe-selenium-python/
Mozilla Public License 2.0
58 stars 50 forks source link

Axe Selenium Python not able to capture violation even after making hidden element visible #171

Open HansMohan opened 4 years ago

HansMohan commented 4 years ago

Hi Team We are utilizing 'axe-selenium-python' package to capture violation of the website. It has been mentioned in the documentation that aXe would not be able to capture violation for hidden elements unless made visibly rendered.

After changing the style attribute for hidden elements, 'axe-selenium-python' package is not able to catch violation whereas axe chrome extension catch the violation for the same scenario.

Element source that is hidden on the website image

CSS style attributes corresponding to modal and fade class image

We change both manually or programatically through JS the style attribute display: block opacity:1

Once the elements goes visible on screen, 'axe chrome extension is able to capture vioaltion, see the below screen shot

image

Can it be please explained why axe-selenium python package is unable to capture the particular violation.

HansMohan commented 4 years ago

Hi Team,

We are stuck in our development procedure due to the issue mentioned.

Gentle reminder. Any help shall be very much appreciated.

kimberlythegeek commented 4 years ago

@HansMohan I apologize. I did take a look at this on Friday but had to go back to some of my other work.

My first guess is that axe-core needs to be updated. I was in the process of automating this with GitHub tools but was moved to a different team, so this project is unfortunately not my primary focus anymore.

I did download the latest version of axe-core and ran the tests locally, which passed. I will run it to see if it will catch an element similar to your example above.

Thanks for submitting this issue, and I appreciate your patience!

kimberlythegeek commented 4 years ago

marking as duplicate of #170

HansMohan commented 4 years ago

Thanks a lot @kimberlythegeek for taking up this issue. please let us know as you perform similar test for the element reported by us in your local with updated axe-core.

kimberlythegeek commented 4 years ago

an update on this: I've updated the axe-core version locally but I'm getting some import mismatch errors on the conftest.py file for some reason. I'm going to push my changes to see if the travis build returns the same results.

I'm also working to update the core tests to be a little more informative

HansMohan commented 4 years ago

Thanks @kimberlythegeek for the update. we look forward for the updated version of Axe-Core.. Keeping posting us. Thanks