Accessibility of the application “Academic Mobile UPNA”

Accessibility Statement

The Public University of Navarre (UPNA) is committed (RESOLUTION 214/2020 of 4 February of the Rector of the Public University of Navarre on Unit Responsible for Accessibility) to making its website accessible in accordance with Real Decree 1112/2018 of 7 September on the accessibility of public sector websites and mobile device applications.

This accessibility statement is applied to applications for mobile devices “Academic Mobile UPNA”

• For operating system: Android (v 4.0.1) and IOS (v 4.2.5)
• Of May 2022

Compliance status

This application for mobile devices is not yet in agreement with RD 1112/2018. Below are those parts not in agreement.

Non-accessible content

The contents gathered below are not accessible due to lack of agreement with RD 1112/2018.

Screens: 

• Do not provide an alternative to visual means for detecting actionable elements of the user interface (5.5.2 Detectability of actionable elements).
• In "Settings": vision and hearing-impaired individuals cannot determine through touch or sound the visual status of locking or switching controls without having to operate the control (criterion 5.6.1 Tactile or audible status).
• In "Schedules" and "Surveys": they do not provide people with no vision or limited vision with the means to access non-textual content through voice output to meet the needs of users who cannot use a screen reader (11.1.1.1.2 Non-text content (closed functionality)).
• In "Schedules" and "Surveys": they do not ensure that all users can access content and understand instructions for use, even when they cannot perceive the shape, colour, size, spatial location, orientation, or sound (11.1.3.3 Sensory characteristics).
• In "Schedules" and "Surveys": they do not ensure that users with low vision and limited cognitive ability, in situations where they are asked to provide information about themselves, can, if the purpose of each data entry field can be determined programmatically, customize or automatically complete instructions through assistive technologies, browsers, and mobile devices to make them more understandable for a specific user and potentially easier to complete the requested data (11.1.3.5.1 Identification of input purpose (open functionality)).
• In "Schedules" and "Registration Appointment": they do not ensure that sufficient contrast is provided between text and background to allow users with low vision to read text without contrast enhancement technology (11.1.4.3 Minimum contrast).
• They do not provide a mode of operation in which text is large enough to be usable by most users with limited vision who cannot use assistive technologies, because the functionality is closed in the mobile application (11.1.4.4.2 Text resize (closed functionality)).
• In "Login": they do not guarantee that individuals with no vision or limited vision receive information transmitted through non-text content, such as an image of text, accessible through voice output to meet the needs of users who cannot use a screen reader because the functionality is closed in the mobile application (11.1.4.5.2 Images of text (closed functionality)).
• They do not guarantee that users with low vision and limited cognitive ability can adjust text spacing to make it easier to read, adapting content to their needs (11.1.4.12 Text spacing).
• They do not guarantee that individuals with low vision who rely on magnification to view content can move the pointer to additional content to read it, as well as individuals with no vision and those who depend on the keyboard for operation can activate and dismiss new content without interrupting their work and without harming the user experience (11.1.4.13 Pointed or focused content).
• They do not guarantee individuals with no vision or limited vision that all functions of the mobile application can be performed without vision by providing at least one mode of operation that uses non-visual access through sound output (including voice, touch, or braille) to meet the needs of users who cannot use a screen reader, keyboard, or keyboard interface because the functionality is closed in the mobile application (11.2.1.1.2 Keyboard (closed functionality)).
• They do not guarantee that keyboard focus is not "trapped" within subsections of content, leaving users who only use the keyboard with no way to return to other content (11.2.1.2 No keyboard focus traps).
• They do not guarantee individuals with no vision or limited vision that direct personalised accesses of the mobile application can be performed without vision by providing at least one mode of operation that uses non-visual access through sound output (including voice, touch, or braille) to meet the needs of users who cannot use a screen reader, keyboard, or keyboard interface because the functionality is closed in the mobile application (Shortcuts (closed functionality)).
• They do not prevent accidental interactions by users unintentionally clicking on a component (11.2.5.2 Pointer cancellation).
• In "Login": they do not ensure, whenever possible, that users, especially those with limited cognitive ability, no vision, and limited vision, receive appropriate suggestions to correct errors made when entering data (11.3.3.3 Suggestions after errors).
• In "Login" and "Surveys": they not guarantee that users, especially those with limited cognitive ability, no vision, and limited vision, can avoid irreversible consequences that may occur when performing an action, such as sending irreversible financial transactions, deleting unrecoverable data, and purchasing items, by providing the ability to review and correct information or reverse actions to avoid errors that could have serious consequences (11.3.3.4 Error prevention (legal, financial, data)).
• They do not guarantee that individuals with no vision, limited vision, limited manipulation or force, as well as limited cognitive ability, can use the accessibility services offered by the platform where the mobile application is installed (11.5.2.3 Use of accessibility services).
• They do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, can use assistive technology, such as a screen reader, screen magnifier, or Braille display, by providing semantic information about objects in the user interface (11.5.2.5 Object information).
• They do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, can understand the organization of data tables and relationship information displayed visually through assistive technologies (11.5.2.6 Row, column, and header information).
• In "Surveys": they do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, can know the current value, and any set or range of allowed values associated with an object in the user interface through assistive technologies (11.5.2.7 Values).
• They do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, can know the relationship between one component (widget or object) and another, whether it be a label, a description, or instructions, content sections, controls, and groups of controls in the user interface through assistive technologies (11.5.2.8 Labelling relationships).
• In "Surveys" and "Settings": they do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, can know the hierarchical relationship (parent-child) that one component has as a container for another component, or that it is contained within it, allowing users of assistive technologies to understand how to navigate and interact with composite content and controls (11.5.2.9 Parent-child relationships).
• In "Login," "Surveys," and "Settings": they do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, can receive information on text content, style attributes, and, if the text is editable, assistive technologies also need the ability to interact with text content, focus interpolation, text selection, and text boundaries so that they can convey information to their users (11.5.2.10 Text).
• In "Login," "Surveys," and "Settings": they do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, know all the actions (such as selecting, copying, pasting, etc.) that each object in the user interface (component or widget) offers through assistive technologies, without the need for a contextual menu that requires additional steps (11.5.2.11 List of available actions).
• In "Login," "Surveys," and "Settings": they do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, receive information and have the necessary mechanisms to track focus, text insertion point, and selection attributes of elements that allow text editing through assistive technologies (11.5.2.13 Focus tracking and selection attributes).
• In "Logout", “Login”, "Surveys," and "Settings": they do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, can set up focus, text insertion point, and selection attributes of elements that allow text editing through assistive technologies (11.5.2.14 Focus and selection attributes modification).
• In "Login," "Surveys," and "Settings": they do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, are informed by assistive technologies when events occur that cause changes in the semantic information of user interface elements (11.5.2.15 Notification of changes).
• In "Login," "Surveys," and "Settings": they do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, are informed by assistive technologies when the states and properties of user interface elements are modified (11.5.2.16 State and property modifications).
• In "Login," "Surveys," and "Settings": they do not guarantee that individuals with no vision or limited vision, as well as those with limited manipulation or force, are informed by assistive technologies when the values and text of data input fields in the user interface are modified (11.5.2.17 Notification of changes).
• In "Login," "Surveys," and "Settings": they do not guarantee that users who need a high-contrast theme, preferred fonts, or a more visible focus cursor can define their preferences in one place, instead of having to modify the display settings for each mobile application.  Each mobile application must respect the colour, contrast, font type, font size, or focus cursor settings corresponding to the device platform configuration (11.7 User preference).

Web contents:

• The visual presentation of text and images does not have a minimum contrast ratio of 4.5:1 (9.1.4.3 Contrast (minimum)).
• The visual presentation of certain elements does not have a minimum contrast ratio of 3:1 with respect to adjacent colours (9.1.4.11 Non-text contrast).
• The default language of each page cannot be determined by software (9.3.1.1 Page language).
• The language of each passage or sentence in the content cannot be determined by software, except for proper names, technical terms, words in an undetermined language, and words or phrases that have become a natural part of the surrounding text (9.3.1.2 Language of parts).
• On level AA the five requirements of agreement of WCAG 2.1 Guidelines are not met (9.6 Agreement requirements of WCAG Guidelines (conditional)).

Preparation of this accessibility statement

This statement was written on the 1 December, 2022.

The method used to prepare the statement has been a self-evaluation carried out by the institution itself.

Latest revision of this statement: 20 November 2023.

Feedback and contact details

You can communicate issues regarding accessibility requirements (Article 10.2.a of Royal Decree 1112/2018 of 7 September), such as:

• Any possible noncompliance of this website.
• Other difficulties accessing the content.
• Queries or suggestions to improve the accessibility of the website.

Through the following channels:

• Email: accesibililidad.web@unavarra.es
• Telephone: ++948 169007

Such communications will be received and processed by the UPNA Communication Service and forwarded to the Web unit, as the Unit Responsible for Accessibility for the Public University of Navarre.

Application procedure

If, when a request, complaint or suggestion is made, it gets dismissed, one does not agree with the decision or it does not meet the requirements established on article 12.5, the interested person may start a claim process. Likewise, this person may also start a claim process in the case that they have not been answered within twenty working days.

This procedure will be carried out through the General Registry or On-line Office.