Mauve++ Updates

  • Version 2.1 - Release Date 2021-12-02

    Introduced the Project functionality to monitor the accessibility of multiple pages of a web site.
    Within a project, multiple audits can be created to evaluate the web pages. Audits can be executed just once or scheduled at fixed interval.
    Such new functionalities allow users to compare and improve the accessibility of a web site over the time.

Mauve++ Info

What is MAUVE++ and its functionality?

M.A.U.V.E. (Multiguideline Accessibility and Usability Validation Environment) is a system to evaluate accessibility of Web sites by checking their HTML and CSS code through guidelines, which are to be specified through an XML-compliant specification language called L.W.G.D (Language for Web Guideline Definition) that maintains the guidelines separated from the underlying logic. MAUVE++ aims to reduce the cost of validation, increase consistency in the identification of the problematic parts, and extend the set of features that can be assessed. It is not able to identify all the possible accessibility problems since in some cases human intervention is necessary for this purpose.Its main features are: .

  • Validation separated from guidelines’ definition.
  • Guidelines formalized through an XML language, capable of expressing all the past, present and (virtually) future accessibility guidelines.
  • Browser’s plugin for the validation of dynamically created/modified Web pages. Download MAUVE extension for Chrome Browser.
  • Possibility of analyzing the versions of a web-site specific for certain types of device (e.g. mobile versions, desktop version, etc.).
  • Potentially expandable as a system for continuous monitoring of accessibility of web sites’ sets.

MAUVE++ is easy to use. At, you can indicate the way what to evaluate (single page or multi page validation) and enter the corresponding web address.

How accessibility metrics are measured in MAUVE++.

In order to indicate the level of accessibility detected MAUVE++ provides two metrics.

  • Accessibility Percentage which indicates how much the website is accessible in terms of the number of checkpoint types successfully evaluated over the total number of evaluated checkpoints for which the tool has been able to make a decision (fail or pass) about the validation.
  • Evaluation Completeness, indicating the percentage of evaluated checkpoints type for which the tool has been able to make a decision (fail or pass) about the validation.

Guidelines and standards that MAUVE++ use.

MAUVE++(Multiguideline Accessibility and Usability Validation Environment) is a system to evaluate accessibility of websites by checking their HTML and CSS code through guidelines, it provides validation results for different types of stakeholders, and supports validation of W3C guidelines.

You can see the full list of techniques supported by MAUVE++ at supported Success Criterias.

At the moment MAUVE++ is able to validate the accessibility of web pages in relation to the following guidelines:

How does MAUVE++ handles the reports?

Depends on the validation type (single or multi page, Mauve++ will report the results in 3 different way:

  • a report in EARL
  • a PDF report with the results of the evaluation of the entire website, that the registered user receives by email
  • a web interface report of single web page validation, which has a separate view according to whether the user is a web developer or an end user without programming knowledge

Static Web Page validation VS Server Side Rendering Validation

In the traditional Static Web Page validation, the validation tool downloads the HTML and the CSS ofthe page, then it parses and validates the corresponding DOM

Using the Server Side Rendering Validation, the validation tool does not parse the static web page code, but it exploits the Puppeteer library to load the HTML (and CSS) code in a headless version of the Chrome browser. In this way, it simulates the loading phase as if the page were open in the user's browser and then performs the validation on the DOM of the resulting page obtained by also performing the scripts included in it.
This can be useful in case of Single Page Applications, but more in generally it can provide a more complete validation.
Of course, since the page will be loaded in a headless version of Chrome and then validated, the validation completion time will be longer than standard Static HTML validation.

Problems or feedback??

MAUVE++ is not perfect. If you are having difficulties using MAUVE++ or have feedback or recommendations, please send us feedback.