Issue date: 25/09/2026 • Standard: WCAG 2.1/AA • Technical document for compliance audit
This register contains the technical details of accessibility violations found during the evaluation. It is intended for internal use for planning corrective actions and documentation required by the European EAA regulation (EU Directive 2019/882), the EN 301 549 technical standard and AgID Guidelines.
Blocking • Immediate action
Serious
Moderate
Minor • Planning
Severity is not defined by WCAG, which does not provide for it: it is the band assigned by the automated tools to each finding, reported here as an operational indication of priority.
| Severity | Count | Percentage | Impact |
|---|---|---|---|
| Critical | 10 | 32.3% | Completely blocks access for some users |
| High | 18 | 58.1% | Prevents important functionality |
| Medium | 3 | 9.7% | Hinders use without blocking it |
| Low | 0 | 0.0% | Improves user experience |
| Total | 31 | 100.0% |
The P.O.U.R. principles (Perceivable, Operable, Understandable, Robust) constitute the four fundamental pillars of WCAG. The following analysis groups violations according to these principles.
Criteria 1.x - Content presentable in different ways
Criteria 2.x - Accessible interface and navigation
Criteria 3.x - Clear information and operations
Criteria 4.x - Compatibility with assistive technologies
List of success criteria WCAG 2.1 level AA that are not satisfied. Each criterion is linked to official W3C documentation.
| Criterion | Name | Level | Principle | Occurrences | Reference |
|---|---|---|---|---|---|
| 1.4.3 | Contrast (Minimum) | AA | Perceivable | 1424 | W3C Documentation |
| 4.1.2 | Name, Role, Value | A | Robust | 1032 | W3C Documentation |
| 2.4.4 | Link Purpose (In Context) | A | Operable | 836 | W3C Documentation |
| 1.3.1 | Info and Relationships | A | Perceivable | 216 | W3C Documentation |
| 2.4.7 | Focus Visible | AA | Operable | 216 | W3C Documentation |
| 1.1.1 | Non-text Content | A | Perceivable | 55 | W3C Documentation |
| 2.5.3 | Label in Name | A | Operable | 4 | W3C Documentation |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Perceivable | 1 | W3C Documentation |
| 1.2.2 | Captions (Prerecorded) | A | Perceivable | 1 | W3C Documentation |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Perceivable | 1 | W3C Documentation |
| 1.2.5 | Audio Description (Prerecorded) | AA | Perceivable | 1 | W3C Documentation |
| 1.4.10 | Reflow | AA | Perceivable | 1 | W3C Documentation |
| 1.4.11 | Non-text Contrast | AA | Perceivable | 1 | W3C Documentation |
| 1.4.13 | Content on Hover or Focus | AA | Perceivable | 1 | W3C Documentation |
| 2.2.2 | Pause, Stop, Hide | A | Operable | 1 | W3C Documentation |
| 3.1.2 | Language of Parts | AA | Understandable | 1 | W3C Documentation |
Below is the complete register of violations found, sorted by descending severity. Each entry includes the element identification, violated WCAG criterion and correction guidance.
Element has contrast ratio lower than minimum.
The test target doesn't have an accessible name, or it's empty ('').
The complete visible text content of the test target neither matches or is contained within its accessible name.
The image doesn't have an accessible name.
Use semantic HTML elements (headings, lists, tables with th) so that the visual structure is also exposed in the code.
The test target parent doesn't have the required context role.
Use semantic HTML elements (headings, lists, tables with th) so that the visual structure is also exposed in the code.
The test target owns elements that doesn't have the correct role.
Expose the name, role and value of every component: use native elements or complete ARIA roles with the required attributes and states.
The test target accessible name doesn't exist or it's empty ('').
Increase the contrast between text and background to at least 4.5:1 (3:1 for large text).
Increase the contrast between text and background to at least 4.5:1 (3:1 for large text).
Increase the contrast between text and background to at least 4.5:1 (3:1 for large text).
Make link text describe the destination, even out of context; avoid "click here" and icon-only links without an accessible name.
Expose the name, role and value of every component: use native elements or complete ARIA roles with the required attributes and states.
Keep the keyboard focus indicator always visible: do not remove the outline without replacing it with an equivalent style.
Add descriptive alternative text to non-decorative images; mark as decorative (empty alt) those that convey no information.
<li> elements are used semantically
<li> elements are used semanticallyUse semantic HTML elements (headings, lists, tables with th) so that the visual structure is also exposed in the code.
Use semantic HTML elements (headings, lists, tables with th) so that the visual structure is also exposed in the code.
Expose the name, role and value of every component: use native elements or complete ARIA roles with the required attributes and states.
Expose the name, role and value of every component: use native elements or complete ARIA roles with the required attributes and states.
Use semantic HTML elements (headings, lists, tables with th) so that the visual structure is also exposed in the code.
Expose the name, role and value of every component: use native elements or complete ARIA roles with the required attributes and states.
Expose the name, role and value of every component: use native elements or complete ARIA roles with the required attributes and states.
Expose the name, role and value of every component: use native elements or complete ARIA roles with the required attributes and states.
Expose the name, role and value of every component: use native elements or complete ARIA roles with the required attributes and states.
Expose the name, role and value of every component: use native elements or complete ARIA roles with the required attributes and states.
Expose the name, role and value of every component: use native elements or complete ARIA roles with the required attributes and states.
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. [Learn how to make links accessible](https://dequeuniversity.com/rules/axe/4.13/link-name).
<li>) are not contained within <ul>, <ol> or <menu> parent elements.
<li>) are not contained within <ul>, <ol> or <menu> parent elements.Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. [Learn more about proper list structure](https://dequeuniversity.com/rules/axe/4.13/listitem).
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. [Learn more about form element labels](https://dequeuniversity.com/rules/axe/4.13/label).
The following findings do not demonstrate the violation of a WCAG 2.1 level A or AA success criterion: they are automated tool notices that require manual verification. They are excluded from the violation count and from the conformance outcome.
Element has contrast ratio lower than minimum.
The aria-label property is neither inherited nor supported by the role generic.
percent, em, names for font sizes
percent, em, names for font sizesThis test target has a font-size css property using an absolute unit value with the important flag.
Text alternative needs manual verification.
Check if the element has some visible focus indication
Check if each ancestor or the text node is not clipped by overflow.
Check that text error messages provided, identify the cause of the error or how to fix the error.
The link contains an image that has an alt attribute that should be manually verified.
Check that content that has the visual appearance of a list (with or without bullets) is marked as an unordered list.
The links with the same accessible name have different content. Verify is the content is equivalent.
The links with the same accessible name have different content. Verify is the content is equivalent.
Please verify that the element's title attribute describes correctly the link.
Check either there is no non-repeated content after repeated content or there exists an element for which all the following are true: - the element has semantic role inheriting from landmark; and - the first perceivable content (in tree order in the flat tree) which is an inclusive descendant of the element is non-repeated content after repeated content; and - the element is included in the accessibility tree.
Check either there is no non-repeated content after repeated content or there exists an element for which all the following are true: - the element is non-repeated content after repeated content; and - the element has a semantic role of heading; and - the element is visible; and - the element is included in the accessibility tree.
For each block of repeated content in each test target, which is before (in the flat tree) at least one node of non-repeated content after repeated content, check that all the following are true: - there exists an instrument to make all nodes in this block not visible; and - there exists an instrument to remove all nodes in this block from the accessibility tree.
The page has one or more instrument(s) to move focus. Check if any of these instrument(s) is being used before a block of repeated content, and the focus is moved to just before a block of non-repeated content.
Can't collect data from the test target.
Can't collect data from the test target.
Can't collect data from the test target.
Can't collect data from the test target.
Can't collect data from the test target.
Can't collect data from the test target.
Can't collect data from the test target.
No test targets found.QW-ACT-R55
No test targets found.QW-ACT-R56
No test targets found.QW-ACT-R51
No test targets found.QW-ACT-R55
No test targets found.QW-ACT-R63
Please verify that headers are used to divide the page correctly.
The first focusable control is a visible link to some content in the Web Page. Verify if it links to the main content.
The form field has incorrect positioned label.
fieldset and legend elements
fieldset and legend elementsThe fieldset element is neither inside nor referencing a form element.
Element didn't keep focus.
Suggested order of intervention for the unmet criteria. It contains no duration estimates: these depend on the site architecture and on the resources of the assessed entity.
Complete technical information about the accessibility evaluation conducted.
| Field | Value |
|---|---|
| Audit ID | eaa_1790330462437 |
| Conducting entity | Principi S.r.l. |
| Technical manager | Andrea Vadacchino |
| Assessment date | 25/09/2026 |
| Reference standard | WCAG 2.1 level AA - EN 301 549 v3.2.1 |
| Methodology | Multi-scanner automated analysis |
| Pages in the sample | 52 |
| Compliance rate | 66% |
| Tool | Developer | Type |
|---|---|---|
| Axe-core | Deque Systems | Analysis of WCAG violations, identifying the problematic elements |
| Lighthouse | Evaluation of accessibility best practices | |
| Pa11y | Team Pa11y | Validation of accessibility standards, focusing on HTML5 and ARIA |
| Playwright | Microsoft | Checks in the browser (keyboard, focus, text spacing, labels). Five checks, tested on test pages, prove that their own criterion is not met (1.4.10, 1.4.12, 2.1.2, 2.4.7, 2.5.3), never that it is met; the other findings are warnings to be verified |
| QualWeb | Universidade de Lisboa | W3C ACT rules and WCAG techniques |
Evaluated organization: Gruppo Turi srl
Website: https://www.cucineturi.com/
Validation method: Multi-scanner automated analysis + result normalization
Accuracy level: Limited to the WCAG criteria automatically verifiable
Assignment of responsibilities for managing and resolving violations.
| Audit performed by | Client |
|---|---|
|
Organization: Principi S.r.l. Technician: Andrea Vadacchino Audit date: 25/09/2026 |
Organization: Gruppo Turi srl Email: info@gruppoturi.it Phone: +39 080 5897111 |
Document revision history with details of changes made.
| Date | Responsible | Type | Version | Description |
|---|---|---|---|---|
| 20/07/2026 | Principi S.r.l. | First release | 1.0 | Outcome not available |
| 25/09/2026 | Principi S.r.l. | Update | 2.0 | Revision based on new accessibility scan |
| 25/09/2026 | Principi S.r.l. | Reissue | 2.2 | New issue of the documents of the same scan, with the rendering rules in force |
The integer part of the number counts the scans of the site (X.0 = X-th scan); the decimal part counts the reissues of the documents of the same scan (X.1, X.2…).