Accessibility

Accessibility compliance

(How we meet the requirements)

We evaluated https://www.legaitaly.com/ compliance with the requirements of the European Accessibility Act (if necessary also its local application), the ADA, WCAG 2.2, Section 508 and is:

Perceivable

• No pre-recorded audio or video are without alternatives.
• No pre-recorded video is without subtitles.
• No synchronised media requiring them are without descriptions or alternative versions.
• No video that requires it is without audio description.
• The content is presented in an order that reflects the logical and semantic structure, allowing assistive technologies to interpret it correctly.
• The instructions provided for understanding and operating the content are not based solely on sensory characteristics of the components such as shape, colour, size, visual location, orientation or sound.
• Content adapts correctly to screen orientation, maintaining consistent display and operation.
• Where present, the purpose of input fields accepting specific data is correctly communicated to the aids and implemented accordingly.
• Information is presented using text, avoiding non-essential, non-customisable text images.
• Changing the spacing of texts, with regard to line height, spaces between paragraphs, letters or words, does not cause any loss of information or content.
• There are no cases where additional content activated by hover or focus disappears unexpectedly, cannot be closed without moving the pointer or focus, or does not remain visible.

Can be used

• There are no keyboard traps (you can freely navigate in and out of all components).
• There is no interference with hotkeys made from individual letters, numbers or symbols.
• There are no time limits imposed by the content or, if any, they are user controllable, adjustable, extendable or justified by functional or regulatory requirements.
• No flashing or flashing content at levels that may provoke epileptic seizures is used, staying within safe limits.
• Skiplinks are implemented to allow quick navigation to the main content, improving accessibility and user experience.
• The screens of the service flow have titles describing their subject matter or purpose.
• In screens of the service flow that can be navigated sequentially and where the sequence of navigation affects meaning and operation, the objects that can receive focus receive it in an order that preserves their meaning and operation.
• There are several ways to identify a content within the environment.
• Elements that can receive the focus of keyboard navigation are always at least partially visible in the viewport.
• All functions do not require complex gestures to be used.
• Features do not start immediately on touch, they can be cancelled before completing them, and you do not need to hold them down to make them work.
• For user interface components with labels that include text or text images, the name read by the aids contains the visually presented text.
• All functionalities are usable without relying solely on the movement of the device or the user
• All functions are usable without necessarily having to be dragged and dropped
• The clickable area of interactive elements is large enough to ensure easy interaction for users.

Understandable

• The language of each page is appropriately defined and used consistently throughout the service
• All language parts that require it can be determined programmatically.
• User interface components, when receiving the focus of keyboard navigation, do not generate unexpected context changes that could disorient the user
• User interface components, when activated by the user via keyboard or assistive technologies, do not generate unexpected contextual changes that may disorient the user
• The navigation mechanisms present are consistently positioned within the entire service flow
• Repeated elements of the interface are consistently defined to facilitate their identification
• In the environment, the mechanisms for requesting support or help are consistent.
• When an input error is automatically detected, the item in error is identified and the error is described in text.
• When an input error is identified and suggestions for correcting it are known, these suggestions are provided to the user, except in cases provided for in the regulations
• Systems are in place to prevent errors such as confirmation, cancellation or reversibility of sensitive actions.
• Where possible, requesting the same data several times is avoided.
• When present, complex authentication systems have accessible alternatives.
• We write content in clear and simple language.

Robust

• Standard development technologies interpretable by assistive technologies are used
• If present, status messages are made accessible so that assistive technologies can interpret them without requiring a shift of focus.

We tested https://www.legaitaly.com/ with the most common assistive technologies in a wide variety of operating system-browser configurations:

• Screen readers (such as NVDA and JAWS on Windows, VoiceOver on Mac and iOS) to confirm that all interactive elements are announced correctly and can be used.
• We also test screen magnification and high contrast modes.

We aim for compatibility with current versions of major assistive technologies. Our code follows the best practices outlined in WCAG 2.2 and EN 301 549 for robust implementation, which means it should remain accessible as technology evolves.

Standards: Based on the above, we apply the latest WCAG 2.2 AA and EN 301 549 criteria to ensure accessibility. Compliance with these standards creates a presumption of conformity with the requirements of the EAA, the ADA and other regulations based on the same technical standards.