angular/protractor-accessibility-plugin

Issues

• getOuterHtml() has been deprecated, and that issue was fixed in this repo, but the change was not published to NPM.

  #35 opened 6 years ago by guillermosnipe
  1

• Update this to support axe-core v3.x

  #36 opened 6 years ago by dylanb
  1

• Accessibility Testing Results

  #16 opened 5 years ago by angela-choo
  1

• Update axe-webdriverjs to 0.5.0

  #25 opened 8 years ago by evilaliv3
  9

• Page must have means to bypass repeated blocks

  #34 opened 6 years ago by jgf5013
  0

• NPM Version crashes on Chome a11y audit failure

  #31 opened 7 years ago by drewterry
  1

• exclude does not work for axe

  #33 opened 7 years ago by IConstructor
  0

• Chrome a11y dev tools fail with auditRulesToRun configuration

  #27 opened 8 years ago by jamsea
  2

• Running accessibility audit on all pages instead of the last page

  #29 opened 8 years ago by 10kresources
  2

• Tests fail with "Angular could not be found on the page" error

  #28 opened 8 years ago by sachams
  1

• Disable rules for aXe

  #14 opened 8 years ago by angela-choo
  7

• Incompatibility with protractor 4.0.10

  #12 opened 8 years ago by evilaliv3
  7

• Selenium WebElement#getOuterHtml() API is deprecated

  #23 opened 8 years ago by evilaliv3
  2

• Protractor suites and Accessibility-pluging

  #4 opened 9 years ago by FJLopezGarcia
  19

• Update to protractor 5.x

  #22 opened 8 years ago by giggio
  2

• some rules issues we found

  #20 opened 8 years ago by lleitep3
  0

• aXe audits for end-to-end tests

  #17 opened 8 years ago by angela-choo
  2

• Protractor & Tenon configuration steps

  #19 opened 8 years ago by FJLopezGarcia
  0

• Consider reloading page before running audits

  #7 opened 8 years ago by juliemr
  0

• CI for PRs needed

  #1 opened 9 years ago by sjelin
  0

• Running on a per test basis

  #11 opened 8 years ago by eyphka
  0

• Looking for maintainers?

  #10 opened 8 years ago by contolini
  2

• "Anonymous AMD module used" error.

  #8 opened 8 years ago by ssjjcc
  0

• Getting Protractor to correctly interpret Pass/Fail results from the protractor-accessibility-plugin

  #3 opened 9 years ago by JeffHall
  2