Geek Answers Handbook

Protractor - Availability Test Results - Results Analysis

I am using Accessibility Plugin + Protractor.

As indicated below, I see several accessibility errors after running some smoke tests, and I'm not sure if the availability check is actually performed on every web page during the E2E test.

Since I'm new to this, kindly let me know if there is a way to initiate an accessibility audit after going to a new webpage during the E2E tests.

e2e-tests $ fucking protractor: websiteSmokeTests --website = "https: // test site /"

Complete the protractor: SmokeTests site (protractor). Using selenium server at http: // localhost: 4444 / wd / hub [launcher] Starting 1 instances of WebDriver

Functionality of the website
  home page Home page - check invalid search return 0 Results - pass
    Check webmaster tools - BingSiteAuth and Google - go
    WebMaster Tools - Check Robots.txt - pass

website on feedback page | Check out the review page for the article - Give No-pass

Finished in 28.875 seconds 8 tests, 101 statements, 0 failure

: 0 ()     Chrome A11Y - , ARIA     Chrome A11Y - aria-owns , DOM     Chrome A11Y - ARIA     Chrome A11Y -     Chrome A11Y - ARIA      A11Y - ARIA

    2 elements failed:
    <div id="cookie-notice" class="notification" aria-describedby="cookieinfo">
    <div class="cont ... " id="close-cookie-notification" class="close-notification">Close</button>
    </div>
</div>
    <div id="decommissioned-site-notice" class="notification strong hidden" aria-describedby="decommissi ... -site-notification"

class= "-" >              

    https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules#ax_aria_04
Chrome A11Y - Elements with ARIA roles must use a valid, non-abstract ARIA role
Chrome A11Y - Controls and media elements should have labels
Chrome A11Y - An element ID must be unique in the DOM
Chrome A11Y - (WARNING) These elements are focusable but either invisible or obscured by another element (10 elements failed)
Chrome A11Y - The web page should have the content human language indicated in the markup
Chrome A11Y - Images should have an alt attribute
Chrome A11Y - (WARNING) The purpose of each link should be clear from the link text (3 elements failed)
Chrome A11Y - (WARNING) Text elements should have a reasonable contrast ratio (4 elements failed)
Chrome A11Y - role=main should only appear on significant elements
Chrome A11Y - Meaningful images should not be used in element backgrounds
Chrome A11Y - An element ID must not be present in more that one aria-owns attribute at any time
Chrome A11Y - ARIA attributes which refer to other elements by ID should refer to elements which exist in the DOM

    2 elements failed:
    <div id="cookie-notice" class="notification" aria-describedby="cookieinfo">
    <div class="cont ... " id="close-cookie-notification" class="close-notification">Close</button>
    </div>
</div>
    <div id="decommissioned-site-notice" class="notification strong hidden" aria-describedby="decommissi ... -site-notification"

class= "-" >              

    https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules#ax_aria_02

Chrome A11Y - This element has an unsupported ARIA attribute

    2 elements failed:
    <div id="cookie-notice" class="notification" aria-describedby="cookieinfo">
    <div class="cont ... " id="close-cookie-notification" class="close-notification">Close</button>
    </div>
</div>
    <div id="decommissioned-site-notice" class="notification strong hidden" aria-describedby="decommissi ... -site-notification"

class= "-" >              

    https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules#ax_aria_10
Chrome A11Y - Video elements should use <track> elements to provide captions [launcher] 0 instance(s) of WebDriver still running

[launcher] chrome # 1 4 [ ] : 4 spec (s) [launcher] 1

, .

.

+4
3

, . , .

: ngHint . .

+1

, , Accessibility ... .

0

I had the same problem, so I wrote a derivative of the plugin-availability-plugin: protractor-ax-report-plugin . It only generates reports using the ax mechanism, but can run for multiple pages in your test.

0
source

More articles:


All Articles