As per https://github.com/yzen/validator.js/wiki/Sketches
Here we can write down ideas about possible structure of the validator configuration file:

Any ideas on what validator.js represents - application, service, web-service, library could we put here.
As well as any ideas on what is an input and what is a useful and usable output of this "tool".
High-level descriptions of this "tool" should go here:

Any ideas on what technology should be used in order to accommodate Design Scope in the best way should go here. The core technology, 3rd pary or open source libraries which could potentially help us to solve the problem should go here.
As well as any high level descriptions of how things should be implemented.

There are several aspects of wa11y that need to be configured and at different stages.

DESCRIPTION INCOMPLETE

Stages of configuration:

At the stage of calling the configure options

if there are global options configured they should be merged with wa11y global options.

What happens at this stage:

LOGGER

• Configure verbosity
• Configure format

COMMON TEST OBJECT OPTIONS

• Configure source file types: css, html, html img, html nav, etc.

At the stage of calling creating an individual test object

If there are options they should be merged on top of: rule specific options, global options for test objects

Leave any ideas on what should we do in order to release validator.js here:
(Any general sequence of steps, tasks, checks or researches etc could be put here so that we would be aware of the designing/developing path we are taking.)

Looks like only wa11y: wa11y.merge runs
[master branch -> Windows, have not checked Node]

Any ideas or thoughts on what we are trying to solve and deliver as a solution should be written here. What is the subgoals and subproblems this project is going to resolve or avoid.

Here we can discuss a possible structure of the output report: