testaro 8.4.5 → 8.4.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +47 -39
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -283,6 +283,8 @@ Another navigation example is:
283
283
 
284
284
  In this case, Testaro waits until the page title contains the string “travel” (case-insensitively).
285
285
 
286
+ The `launch` navigation command allows you to specify a “lowMotion” property as `true`. If you do, then the browser creates tabs with the `reduce-motion` option set to `reduce` instead of `no-preference`. This makes the browser act as if the user has chosen a [motion-reduction option in the settings of the operating system or browser](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion#user_preferences). However, there are often motions on web pages that this option fails to suppress, such as those on the [Inditex](https://www.inditex.com/itxcomweb/en/home) and [Rescuing Leftover Cuisine](https://www.rescuingleftovercuisine.org) home pages. Carousel motion is also not suppressed.
287
+
286
288
  ##### Alterations
287
289
 
288
290
  An example of an **alteration** is:
@@ -360,9 +362,53 @@ An example of a **Testaro-defined** test is:
360
362
 
361
363
  In this case, Testaro runs the `motion` test with the specified parameters.
362
364
 
365
+ ###### Continuum
366
+
367
+ The `continuum` packaged test makes use of the files in the `continuum` directory. The test inserts the contents of all three files into the page as scripts and then uses them to perform the tests of the Continuum package.
368
+
369
+ Level Access on 22 August 2022 granted authorization for the copying of the `AccessEngine.community.js` file insofar as necessary for allowing Continuum community edition tests to be included in Testaro.
370
+
371
+ ###### IBM Equal Access
372
+
373
+ The `ibm` packaged test requires the `aceconfig.js` file.
374
+
375
+ If you choose to invoke this packaged test with the `withNewContent` property specified, you will choose whether the tested content is the content of the existing page or is retrieved anew with the document URL. Typically, both methods succeed and deliver similar results. However, sometimes one method succeeds and the other fails, or one method reports more violations than the other does. In those cases, most often the success, or the larger violation count, arises from the existing page (`withNewContent: false`).
376
+
377
+ ###### HTML CodeSniffer
378
+
379
+ The `htmlcs` packaged test makes use of the`htmlcs/HTMLCS.js` file. That file was created, and can be recreated if necessary, as follows:
380
+
381
+ 1. Clone the (HTML CodeSniffer package)[https://github.com/squizlabs/HTML_CodeSniffer].
382
+ 1. Make that package’s directory the active directory.
383
+ 1. Install the HTML CodeSniffer dependencies by executing `npm install`.
384
+ 1. Build the HTML CodeSniffer auditor by executing `grunt build`.
385
+ 1. Copy the `build/HTMLCS.js` and `build/licence.txt` files into the `htmlcs` directory of Testaro.
386
+ 1. Edit the Testaro copy of `htmlcs/HTMLCS.js` to produce the changes shown below.
387
+
388
+ The changes in `htmlcs/HTMLCS.js` are:
389
+
390
+ ```diff
391
+ 479a480
392
+ > '4_1_2_attribute': 'attribute',
393
+ 6482a6484
394
+ > var messageStrings = new Set();
395
+ 6496d6497
396
+ < console.log('done');
397
+ 6499d6499
398
+ < console.log('done');
399
+ 6500a6501
400
+ > return Array.from(messageStrings);
401
+ 6531c6532,6534
402
+ < console.log('[HTMLCS] ' + typeName + '|' + msg.code + '|' + nodeName + '|' + elementId + '|' + msg.msg + '|' + html);
403
+ ---
404
+ > messageStrings.add(
405
+ > typeName + '|' + msg.code + '|' + nodeName + '|' + elementId + '|' + msg.msg + '|' + html
406
+ > );
407
+ ```
408
+
363
409
  ###### Tenon
364
410
 
365
- Most packaged tests require only one command, but the `tenon` test requires two commands:
411
+ Most packaged tests require only one command, but the `tenon` packaged test requires two commands:
366
412
  - A command of type `tenonRequest`.
367
413
  - A command of type `test` with `tenon` as the value of `which`.
368
414
 
@@ -402,44 +448,6 @@ Tenon recommends giving it a public URL rather than giving it the content of a p
402
448
 
403
449
  If a `tenon` test is included in a job, environment variables named `TENON_USER` and `TENON_PASSWORD` must exist, with your Tenon username and password, respectively, as their values. You can obtain those from [Tenon](https://tenon.io/documentation/overview).
404
450
 
405
- ###### Continuum
406
-
407
- The `continuum` test makes use of the files in the `continuum` directory. The test inserts the contents of all three files into the page as scripts and then uses them to perform the tests of the Continuum package.
408
-
409
- Level Access on 22 August 2022 granted authorization for the copying of the `AccessEngine.community.js` file insofar as necessary for allowing Continuum community edition tests to be included in Testaro.
410
-
411
- ###### HTML CodeSniffer
412
-
413
- The `htmlcs` test makes use of the`htmlcs/HTMLCS.js` file. That file was created, and can be recreated if necessary, as follows:
414
-
415
- 1. Clone the (HTML CodeSniffer package)[https://github.com/squizlabs/HTML_CodeSniffer].
416
- 1. Make that package’s directory the active directory.
417
- 1. Install the HTML CodeSniffer dependencies by executing `npm install`.
418
- 1. Build the HTML CodeSniffer auditor by executing `grunt build`.
419
- 1. Copy the `build/HTMLCS.js` and `build/licence.txt` files into the `htmlcs` directory of Testaro.
420
- 1. Edit the Testaro copy of `htmlcs/HTMLCS.js` to produce the changes shown below.
421
-
422
- The changes in `htmlcs/HTMLCS.js` are:
423
-
424
- ```diff
425
- 479a480
426
- > '4_1_2_attribute': 'attribute',
427
- 6482a6484
428
- > var messageStrings = new Set();
429
- 6496d6497
430
- < console.log('done');
431
- 6499d6499
432
- < console.log('done');
433
- 6500a6501
434
- > return Array.from(messageStrings);
435
- 6531c6532,6534
436
- < console.log('[HTMLCS] ' + typeName + '|' + msg.code + '|' + nodeName + '|' + elementId + '|' + msg.msg + '|' + html);
437
- ---
438
- > messageStrings.add(
439
- > typeName + '|' + msg.code + '|' + nodeName + '|' + elementId + '|' + msg.msg + '|' + html
440
- > );
441
- ```
442
-
443
451
  ###### WAVE
444
452
 
445
453
  If a `wave` test is included in the job, an environment variable named `WAVE_KEY` must exist, with your WAVE API key as its value. You can get it from [WebAIM](https://wave.webaim.org/api/).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "testaro",
3
- "version": "8.4.5",
3
+ "version": "8.4.7",
4
4
  "description": "Automation of accessibility testing",
5
5
  "main": "index.js",
6
6
  "scripts": {