bSmart Labs srl is committed to making its bSmart Books web application accessible, in accordance with the requirements of Appendix A of the technical standard UNI CEI EN 301 549:2021 (WCAG 2.1) and the international Web Content Accessibility Guidelines (WCAG) 2.2, at conformance level AA.

The following accessibility statement applies to the bSmart Books platform, including the integrated reader, and to the login page (opens in a new tab).

Compliance Status

Partially compliant

This web application is partially compliant with the requirements of the international WCAG 2.2 standard due to the cases of non-compliance listed below.

Non-accessible content

bSmart Books platform and login page

The content listed below is non-accessible for the following reasons:

  1. Non-compliance with the accessibility requirements defined by the international WCAG 2.2 standard for conformance level AA. Specifically:
    • some images do not have a meaningful alternative text that correctly describes their content to people with visual disabilities who use screen readers, or alternative text has been provided for decorative images; therefore, WCAG Success Criterion 1.1.1 Non-text Content is not met;
    • some buttons lack a label, which can make it difficult for users to understand the purpose and function of the button; therefore, WCAG Success Criteria 1.1.1 Non-text Content, 2.4.6 Headings and Labels, and 4.1.2 Name, Role, Value are not met. Specifically, when dialog windows are opened or shown, there are empty buttons that are not visible on screen but are detectable by Assistive Technologies. The function of these buttons may not be clear to end users;
    • on some pages, headings, which help communicate the organization of the content and provide a structure that users (especially those using Assistive Technologies) rely on to navigate the content, are missing or their hierarchical order is incorrect; therefore, WCAG Success Criterion 1.3.1 Info and Relationships is not met;
    • dialog windows lack an accessible name; therefore, WCAG Success Criterion 1.3.1 Info and Relationships is not met;
    • on the login page, the "Log in with publisher or other" panel is not managed correctly and its content is only visually hidden: when navigating the page with a screen reader, all the panel's content can be detected and navigated. Dialog windows, even when they obscure the underlying content, are not managed as modals, and it is possible to navigate the obscured page content. This can make the content sequence meaningless; therefore, WCAG Success Criterion 1.3.2 Meaningful Sequence is not met;
    • on the login page, some links are identifiable only by color; therefore, WCAG Success Criterion 1.4.1 Use of Color is not met;
    • in some places, the contrast between the text and the background is not adequate, which may make reading difficult, or the text color or background color are not specified; therefore, WCAG Success Criterion 1.4.3 Contrast (Minimum) is not met;
    • text magnification is limited or not fully adjustable, which could make it difficult to enlarge the text up to 200% to facilitate reading; therefore, WCAG Success Criterion 1.4.4 Resize text is not met;
    • some user interface components (e.g., buttons and input fields), as well as the visual information that identifies their state, do not have sufficient contrast with adjacent colors; therefore, WCAG Success Criterion 1.4.11 Non-text Contrast is not met;
    • dialog windows, even when they obscure the underlying page content, are not correctly managed as modals, so the keyboard focus can move to the underlying content, and the element receiving focus may be obscured, with no mechanism available to reveal it. Therefore, WCAG Success Criteria 2.1.1 Keyboard and 2.4.3 Focus Order are not met. When no mechanism (e.g., ESC key) is available to close the dialog window and show the element receiving focus, WCAG Success Criterion 2.4.11 Focus Not Obscured (Minimum) is also not met;
    • there are no mechanisms (e.g., skip links) to bypass blocks of content that are repeated on multiple pages; therefore, WCAG Success Criterion 2.4.1 Bypass Blocks is not met;
    • page titles may not be fully meaningful; therefore, WCAG Success Criterion 2.4.2 Page Titled is not met;
    • on the login page, some purely textual elements receive keyboard focus, which can create confusion between what is interactive and what is not for users navigating the content with a keyboard or an interface that simulates its behavior; therefore, WCAG Success Criterion 2.4.3 Focus Order is not met;
    • some user interface components (e.g., buttons) have an accessible name that does not include the visible on-screen label; therefore, WCAG Success Criterion 2.5.3 Label in Name is not met;
    • the size of some buttons does not meet the minimum requirements, which can make it difficult to activate them accurately without accidentally activating nearby interactive elements; therefore, WCAG Success Criterion 2.5.8 Target Size (Minimum) is not met;
    • some error messages in the login form may not be informative for users or may not provide instructions on how to resolve or correct the error; therefore, WCAG Success Criterion 3.3.3 Error Suggestion is not met;
    • some ARIA roles, states, or properties that define the semantics, behavior, and state of interactive elements (e.g., buttons and popups) are not used correctly or are missing; therefore, WCAG Success Criteria 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value are not met;
    • some status messages (e.g., error messages displayed under input fields in the login form) are not correctly conveyed to Assistive Technologies; therefore, WCAG Success Criterion 4.1.3 Status Messages is not met.

bSmart Books reader

The content listed below is non-accessible for the following reasons:

  1. Non-compliance with the accessibility requirements defined by the international WCAG 2.2 standard for conformance level AA. Specifically:
    • some buttons and user interface components (e.g., checkboxes and input fields) lack a label, which can make it difficult for users to understand the purpose and function of the button or component, and even when a label is present on screen, it may not be programmatically associated with the button or component; therefore, WCAG Success Criteria 1.1.1 Non-text Content, 2.4.6 Headings and Labels, and 4.1.2 Name, Role, Value are not met. Specifically, when dialog windows are opened or shown, there are empty buttons that are not visible on screen but are detectable by Assistive Technologies. The function of these buttons may not be clear to end users. The "Settings" panel and the popups for tools or options may also contain buttons without labels;
    • the accessible name of some input fields is not meaningful because it is derived from the placeholder and not from a programmatically associated label; therefore, WCAG Success Criteria 1.1.1 Non-text Content and 1.3.1 Info and Relationships are not met;
    • some images do not have a meaningful alternative text that correctly describes their function to people with visual disabilities, or informative images have been identified as decorative; therefore, WCAG Success Criterion 1.1.1 Non-text Content is not met;
    • in some dialog windows (or sidebars), the hierarchical order of heading levels is incorrect; therefore, WCAG Success Criterion 1.3.1 Info and Relationships is not met;
    • the dialog windows and the embedded application in the reader for digital books lack an accessible name; therefore, WCAG Success Criterion 1.3.1 Info and Relationships is not met;
    • some radio buttons in the option panels are identifiable only by color; therefore, WCAG Success Criterion 1.4.1 Use of Color is not met;
    • in some places, the contrast between the text and the background is not adequate, which may make reading difficult, or the text color or background color are not specified; therefore, WCAG Success Criterion 1.4.3 Contrast (Minimum) is not met;
    • text magnification is limited or not fully adjustable, which could make it difficult to enlarge the text up to 200% to facilitate reading. In some places, resizing text to 200% can cause a loss of information due to a reduction in readable text; therefore, WCAG Success Criterion 1.4.4 Resize text is not met;
    • some user interface components (e.g., buttons and input fields), as well as the visual information that identifies their state, do not have sufficient contrast with adjacent colors; therefore, WCAG Success Criterion 1.4.11 Non-text Contrast is not met;
    • some functionalities, such as adding a highlight, starting the reading of selected text, and adding an annotation, as well as expanding the "Annotate" and "Draw" option menus, are not operable using the keyboard, which can make them impossible or difficult to use for people who cannot use a pointer. The menu content is not navigable using the arrow keys; therefore, WCAG Success Criterion 2.1.1 Keyboard is not met;
    • dialog windows, even when they obscure the underlying page content, are not correctly managed as modals, so the keyboard focus can move to the underlying content. Furthermore, the focus does not automatically move inside them; therefore, WCAG Success Criteria 2.1.1 Keyboard and 2.4.3 Focus Order are not met;
    • there are no mechanisms (e.g., skip links) to bypass blocks of content in the reader's interface to directly reach the main content when navigating with a keyboard or an interface that simulates its behavior; therefore, WCAG Success Criterion 2.4.1 Bypass Blocks is not met;
    • the reader's web page title may not be fully meaningful; therefore, WCAG Success Criterion 2.4.2 Page Titled is not met;
    • the accessible name of some buttons is not meaningful and does not allow for understanding and distinguishing the button's function and purpose; therefore, WCAG Success Criterion 2.4.6 Headings and Labels is not met;
    • some input fields have an accessible name that does not include the visible on-screen label; therefore, WCAG Success Criterion 2.5.3 Label in Name is not met;
    • the size of some buttons does not meet the minimum requirements, which can make it difficult to activate them accurately without accidentally activating nearby interactive elements; therefore, WCAG Success Criterion 2.5.8 Target Size (Minimum) is not met;
    • for some input fields, for example in the "Bookmarks" panel, there are no labels or instructions to understand the function and purpose of the input field; therefore, WCAG Success Criterion 3.3.2 Labels or Instructions is not met;
    • some ARIA roles, states, or properties that define the semantics, behavior, and state of interactive elements (e.g., buttons and popups) are not used correctly or are missing; therefore, WCAG Success Criteria 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value are not met.

Preparation of the accessibility statement

This statement was prepared on October 14, 2025.

The information in this statement is based on an assessment carried out by the third party Fondazione LIA, which conducted an accessibility audit on the following areas:

  • login flow;
  • settings area;
  • library area;
  • content reader in its two reading modes (fixed layout and reflowable version).

Feedback mechanism and contact details of the provider

The process we have started is very important to us, and feedback from our users is essential: if you encounter any problems or have any reports or suggestions while using our sites, you can contact us by e-mail at: accessibilita@bsmart.it

Information about the web application

  • Date of publication of the web application: August 7, 2024
  • Usability tests have been conducted: yes

Information about the organisation

  1. Number of employees with disabilities hired by the provider: none.
  2. Number of workstations for employees with disabilities: none.