Accessibility Conformance Report (VPAT)
Based on VPAT® Version 2.5Rev
Name of Product/Version
Torrossa Online Digital Bookstore.
Report Date
December 17, 2025.
Note: the accessibility tests were carried out in September 2025.
Product Description
Torrossa is the web platform developed by Casalini Libri that provides access to a wide catalog of digital academic publications in the humanities and social sciences. It enables libraries, institutions, scholars and any reader to consult digital texts through an integrated online reader or via third-party reading software. The platform is designed to support the dissemination of knowledge and to offer, as far as possible, an accessible experience for users with visual impairments, reading difficulties, or those who rely on assistive technologies.
Contact Information
If you require clarification on how to access or navigate Torrossa and its features, you can send us an e-mail at accessibility@casalini.it.
Notes
The accessibility conformance report does not apply to the cookie management tool.
Some pages contain references and links to other sites outside the Torrossa Online Digital Bookstore platform that may not be fully accessible. In particular, this applies to pages belonging to payment channels, which are not managed by Casalini Libri. These third-party channels are available for the ecommerce site catering to individuals only.
Evaluation Methods Used
Automatic testing and manual testing were performed by the third-party Fondazione LIA. The tests were performed by accessibility experts with knowledge of general product functionality.
- Automatic testing:
- using a third-party platform for website accessibility auditing to test a representative subset of pages of the website and the main user flows (registration, login, search and search results, an example of product detail page, purchasing process, download process, an example of a static page)
- Manual testing:
- using a third-party platform for website accessibility auditing to test a representative subset of pages of the website and the main user flows (registration, login, search and search results, an example of product detail page, purchasing process, download process, an example of a static page)
- using a screen reader to verify that all selected pages are navigable and that all the selected user flows can be performed independently by people with visual impairments
- keyboard-only navigation to verify that all selected pages are navigable and that all the selected user flows can be performed independently by keyboard-only users
- Test environment:
- Operating system: macOS Monterey Version 12.7.4
- Browsers: Chrome, Firefox
- Screen readers: VoiceOver
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A (Yes) Level AA (Yes) Level AAA (No) |
| Web Content Accessibility Guidelines 2.1 | Level A (Yes) Level AA (Yes) Level AAA (No) |
| Web Content Accessibility Guidelines 2.2 | Level A (Yes) Level AA (Yes) Level AAA (No) |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.
Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | Partially Supports | Some form controls have an accessible name that is not meaningful;Some images that are functional and require an alternative text are considered decorative or are hidden from Assistive Technology users. Other images have an alternative text but can be considered purely decorative;The sample page on the product detail page has an alternative text that is not meaningful;Some buttons are missing an accessible name because their only content is an image without alternative text;The image showing the payment methods has an alternative text that is not meaningful. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | The website does not contain any audio-only or video-only media. |
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | The website does not contain any synchronized media. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | The website does not contain any synchronized media. |
| 1.3.1 Info and Relationships (Level A) | Partially Supports | Information, structure, and relationships conveyed through presentation is conveyed programmatically with a few minor issues. For example: - In some cases, the hierarchical order of the heading levels is incorrect; - Some WAI-ARIA attributes do not properly convey the relationship between elements, are improperly used or are missing, consequently some components are not managed properly and do not have the appropriate semantics; - Some ‹input› elements have multiple ‹label› elements associated; - The modal with error messages relating to the completion of the registration form is missing an accessible name; - Some content is not properly structured and the appropriate semantic HTML tags have not been used; - Some pages contain HTML tags without the corresponding opening or closing tag, which may cause assistive technologies to provide incorrect information. |
| 1.3.2 Meaningful Sequence (Level A) | Supports | The content in the web pages is read in a meaningful sequence and the correct reading sequence is programmatically determined. |
| 1.3.3 Sensory Characteristics (Level A) | Supports | Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. |
| 1.4.1 Use of Color (Level A) | Partially Supports | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element except in the following cases: - On the product detail page, some links inside the accordion panel are distinguishable by color alone; - In the "Billing information" modal in the Cart page, errors on form fields are identified only using color. |
| 1.4.2 Audio Control (Level A) | Not Applicable | There is no audio or video on the website. |
| 2.1.1 Keyboard (Level A) | Partially Supports | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, with the following exceptions: - The combo box widget used for the search field in the header does not support proper arrow-key navigation; - Keyboard navigation is not trapped within some modals that use the attribute aria-modal="true" and usage of other elements is not precluded. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | All examined components allow keyboard focus to move in and out freely using standard keyboard navigation, with no keyboard traps. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) | Not Applicable | Keyboard shortcuts are not available on the website in the pages and user flows analyzed. |
| 2.2.1 Timing Adjustable (Level A) | Not Applicable | There are no time limits set by the content. |
| 2.2.2 Pause, Stop, Hide (Level A) | Not Applicable | The website, in the pages and user flows analyzed, does not contain any moving, blinking, scrolling, or auto-updating content. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Not Applicable | The website, in the pages and user flows analyzed, does not contain any content that flashes more than three times per second, and no flashing elements that exceed the general flash or red flash thresholds. |
| 2.4.1 Bypass Blocks (Level A) | Supports | All pages on the website feature a "Skip to main content" link. This link is the first element on each page that receives keyboard focus and allows keyboard users to skip directly to the main content of the page. |
| 2.4.2 Page Titled (Level A) | Partially Supports | When the "Billing information" modal is opened on the Cart page, the title of the page (tag ‹title›) is not meaningful. |
| 2.4.3 Focus Order (Level A) | Partially Supports | The focusable components of the website receive focus in an order that preserves meaning and operability. The navigation order using the keyboard or a keyboard interface follows the visual layout of the elements. The focus order presents the following problems: - Some elements receive keyboard focus even though they are not keyboard operable, such as certain H1 headings and some text elements inside modals; - Some modals (e.g. the "Billing information" modal) are not managed properly and the focus does not move inside them when they open; moreover the keyboard focus can move to the obscured underlying content. In particular, after submitting the form contained in the "Billing information" modal with errors, the page reloads and the modal reopens, but focus is returned to the underlying page instead of moving inside the modal. |
| 2.4.4 Link Purpose (In Context) (Level A) | Partially Supports | On the search results page and the product detail page, some links are not meaningful within their context. |
| 2.5.1 Pointer Gestures (Level A 2.1 and 2.2) | Not Applicable | The website does not implement any functionality that use multipoint or path-based gestures for operation. |
| 2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) | Not Applicable | The website does not implement any functionality that use multipoint or path-based gestures for operation. |
| 2.5.3 Label in Name (Level A 2.1 and 2.2) | Partially Supports | The accessible name of some form controls does not contain the visible label of the controls, for example: - In the search results page, the accessible name of the "Purchase" button is "Add to cart"; - In the modal that confirms that a product has been added to the cart, the accessible name of the "Continue to purchase" button is "Close"; - The accessible name of the links for the "Casalini ID" does not match the visible label of the links. |
| 2.5.4 Motion Actuation (Level A 2.1 and 2.2) | Not Applicable | The website does not implement any functionality operated by device or user motion. |
| 3.1.1 Language of Page (Level A) | Supports | The default human language of each web page is programmatically determined. |
| 3.2.1 On Focus (Level A) | Supports | In the pages and user flows analyzed, when any component receives focus, it does not initiate a change of context. |
| 3.2.2 On Input (Level A) | Partially Supports | On the search results page, changing the selected option of the combo boxes (select elements) automatically cause a change of context: the page reloads and the focus returns to the top of the page. |
| 3.2.6 Consistent Help (Level A 2.2 only) | Supports | The website includes the following help mechanisms: a FAQ page, a phone number, and an email address. These mechanisms are consistently present in the footer of all pages and appear in the same order across the website. |
| 3.3.1 Error Identification (Level A) | Supports | At the time of the accessibility audit and the writing of this document, in the pages and user flows analyzed, if an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. |
| 3.3.2 Labels or Instructions (Level A) | Partially Supports | Labels or instructions are not provided for all input fields in the advanced search form. This could prevent users from understanding the purpose of the fields. |
| 3.3.7 Redundant Entry (Level A 2.2 only) | Supports | The analyzed pages do not require users to re-enter previously provided information within the same process, and no mechanism for re-entering such information is needed. |
| 4.1.1 Parsing (Level A) WCAG 2.0 and 2.1 – Always answer 'Supports' WCAG 2.2 (obsolete and removed) – Does not apply | Supports | For WCAG 2.0 and 2.1, the September 2023 errata update indicates this criterion is always supported. |
| 4.1.2 Name, Role, Value (Level A) | Partially Supports | Some controls have not been properly managed, for example: - The button "Language" in the header is not programmatically associated with the controlled popup; - WAI-ARIA attributes are missing in some buttons that control modals or fly-out menus; - Some buttons are missing an accessible name. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | The website does not contain live audio content in synchronized media. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | The website does not contain any synchronized media. |
| 1.3.4 Orientation (Level AA 2.1 and 2.2) | Supports | The content does not restrict its view and operation to a single display orientation. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) | Partially Supports | In the "Billing information" modal in the Cart page, the autocomplete attribute used on some input fields collecting information about the user does not match the purpose indicated by the label of the input field. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | In the pages and user flows analyzed, the visual presentation of text and images of text has a sufficient contrast ratio of at least 4.5:1 (3:1 for large text). |
| 1.4.4 Resize text (Level AA) | Partially Supports | Users can resize the text up to 200% without assistive technologies, but some text and textual content might be truncated, partially visible, or overlap with other text or elements. |
| 1.4.5 Images of Text (Level AA) | Partially Supports | On the product detail page, the sample page is provided as an image of text, and therefore its content cannot be perceived by visually impaired users who rely on screen readers. |
| 1.4.10 Reflow (Level AA 2.1 and 2.2) | Supports | Text and other related content of the website can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: - Vertical scrolling content at a width equivalent to 320 CSS pixels; - A starting viewport width of 1280 CSS pixels wide at 400% zoom. |
| 1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) | Partially Supports | Visual information required to identify user interface components and states have a contrast ratio against the adjacent colors of at least 3:1 with few minor exceptions: - The keyboard focus indicator has an insufficient color contrast ratio with adjacent colors on the "Go to the results" button near the search input field in the header, on the button to open the dialog to manage cookies and on the button "back to top"; - The visual information necessary to identify the "back to top" button or the button used to close certain modals have insufficient contrast. |
| 1.4.12 Text Spacing (Level AA 2.1 and 2.2) | Supports | By modifying the stylistic properties of the text, such as line height, spacing following paragraphs, letter spacing (tracking), and word spacing, no loss of content or functionality occurs. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) | Supports | The website, in the pages and user flows analyzed, does not contain content that appears on mouse hover or on keyboard focus. |
| 2.4.5 Multiple Ways (Level AA) | Supports | More than one way is available to locate each web page, except where the web page is the result of, or a step in, a process (e.g. in the checkout process). |
| 2.4.6 Headings and Labels (Level AA) | Partially Supports | Some buttons are not meaningful, for example: - On the advanced search page there are multiple buttons with the same accessible name "Remove filter". The same happens in the "Cart" page where there are multiple "Remove from my cart" buttons; - Some buttons to close modals are empty. |
| 2.4.7 Focus Visible (Level AA) | Partially Supports | The keyboard focus indicator is visible on all interactive elements, with the following exceptions: - On the advanced search page, the focus indicator is not visible on the button to add a new search field; - On the search results page, the focus indicator is not visible on the button to print the page. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) | Supports | The user interface component that receives keyboard focus is always at least partially visible. |
| 2.5.7 Dragging Movements (Level AA 2.2 only) | Not Applicable | There are no functionalities that require dragging movements for operation. |
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only) | Partially Supports | On the Advanced Search page, the target size of the filter checkboxes is smaller than the minimum required 24 x 24 CSS pixels. |
| 3.1.2 Language of Parts (Level AA) | Does Not Support | In most cases, the human language of passages of text or phrases that are in a language other than the default human language of the page is not programmatically determined. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | Navigational mechanisms that are repeated on multiple web pages occur in the same relative order each time they are repeated. |
| 3.2.4 Consistent Identification (Level AA) | Supports | In the pages and user flows analyzed, components that have the same functionality are identified consistently across different pages. |
| 3.3.3 Error Suggestion (Level AA) | Partially Supports | When an input error occurs, the correction suggestions that are provided to the user might not always be appropriate: - In the registration form, if the "Email" input field is empty, the error message displayed is "Email address is not valid"; - In the "Billing information" form, the error message does not provide meaningful information on which fields contain errors and how to fix them. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Not Applicable | The website does not contain web pages that modify or delete user-controllable data in data storage systems or that submit user test responses. The checkout process involves external, third-party financial services websites that cause legal transactions for the user. This accessibility conformance report does not apply to these external services. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) | Supports | A cognitive function test is not required for any step in the authentication process. The login form used to access the restricted area provides properly marked-up email and password input fields, including attributes such as autocomplete. The user's browser or integrated third-party password manager extension can identify the purpose of the inputs and automatically fill in the username and password. Users can copy the username and password and paste them directly in the input fields to reduce the cognitive burden of re-typing. |
| 4.1.3 Status Messages (Level AA 2.1 and 2.2) | Supports | In the pages and user flows analyzed, status messages are programmatically determined and are presented to assistive technologies users without receiving focus. |
Table 3: Success Criteria, Level AAA
These criteria are all Not Applicable because the product has been tested following the Web Content Accessibility Guidelines 2.1 level AA.
"Voluntary Product Accessibility Template" and "VPAT" are registered service marks of the Information Technology Industry Council (ITI).