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: .
MAUVE++ is easy to use. At https://mauve.isti.cnr.it, you can indicate the way what to evaluate (single page or multi page validation) and enter the corresponding web address.
In order to indicate the level of accessibility detected MAUVE++ provides two metrics.
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:
Depends on the validation type (single or multi page, Mauve++ will report the results in 3 different way:
In the traditional Static Web Page validation, the engine downloads the HTML and the CSS of the page, then it parses and validate the corresponding DOM
Using the Server Side Rendering Validation, the engine do not parse the static web page code, indeed it exploits Puppeteer library to load the HTML (and CSS) code within a headless version of the Chrome browser. In this way, we simulate the loading phase as if the page were open in the user's browser.
This can be useful in case of Single Page Applications, but more in generally we can assume that with all the pages the validation will be more complete.
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.
MAUVE++ is not perfect. If you are having difficulties using MAUVE++ or have feedback or recommendations, please send us feedback.