Accessibility statement - research information system OuluCRIS

3. The website is not yet fully compliant with the requirements

• Perceivable: Shortcomings in alt text attributes

  Non-accessible content and its shortcomings

  Some alt text attributes are missing or they don’t correctly describe the element.

  Non-fulfilled accessibility requirements

  • 1.1.1 Non-text Content

• Perceivable: Only colours used to differentiate button icons when descriptive text is also required

  Non-accessible content and its shortcomings

  Only colours are used to differentiate some button icons, when a text describing the function of the button for screen readers is also required.

  Non-fulfilled accessibility requirements

  • 1.1.1 Non-text Content

• Perceivable: DOM sequence does not match the visual sequence

  Non-accessible content and its shortcomings

  Tab navigation goes through the profile menu even if it is closed.

  Non-fulfilled accessibility requirements

  • 1.3.2 Meaningful Sequence

• Perceivable: Heading levels are skipped and sequence is illogical

  Non-accessible content and its shortcomings

  Heading levels h1-h6 are not in correct order and on many pages headings may be skipped.

  Non-fulfilled accessibility requirements

  • 1.3.2 Meaningful Sequence

• Perceivable: Some texts and buttons do not fulfil minimum contrast requirements

  Non-accessible content and its shortcomings

  In some user interface elements (e.g. texts and buttons) the contrast ratio is below the minimum requirement level.

  Non-fulfilled accessibility requirements

  • 1.4.3 Contrast (Minimum)

• Perceivable: In the main menu some texts are cut off in the middle

  Non-accessible content and its shortcomings

  Long headings in the main menu are not fully displayed. The headings are cut off in the middle when the website is scaled.

  Non-fulfilled accessibility requirements

  • 1.4.12 Text Spacing

• Operable: All elements are not usable only with keyboard

  Non-accessible content and its shortcomings

  There are shortcomings e.g. in the search component and search listing.

  Non-fulfilled accessibility requirements

  • 2.1.1 Keyboard

• Operable: Shortcomings and illogicality when using the focus function

  Non-accessible content and its shortcomings

  There is illogicality in the order when using the focus function. The focus will not always move onto the correct target, or the user is forced to either go round or go back to reach the intended target.

  Non-fulfilled accessibility requirements

  • 2.4.3 Focus Order

• Operable: Link purpose is not clear

  Non-accessible content and its shortcomings

  In some publications there are links whose purpose is not clear. A link should tell the user where clicking the link leads to.

  Non-fulfilled accessibility requirements

  • 2.4.4 Link Purpose (In Context)

• Operable: Focus is not visible in some user interface elements

  Non-accessible content and its shortcomings

  When using the keyboard the user cannot always see where the focus is. Keyboard focus is missing in at least the following elements:
  
  1. Search button
  2. Advanced search button
  3. Radio buttons
  4. ”Show/hide” button on login page
  5. ”Pin publication” button
  6. Language selection button

  Non-fulfilled accessibility requirements

  • 2.4.7 Focus Visible

• Understandable: Missing language attribute in page description

  Non-accessible content and its shortcomings

  Since the language attribute has not been defined, screen readers are unable to recognize the language of the content.

  Non-fulfilled accessibility requirements

  • 3.1.1 Language of Page

• Understandable: Error messages cannot be detected by screen readers

  Non-accessible content and its shortcomings

  Error messages generated in form input cannot be detected by screen readers.

  Non-fulfilled accessibility requirements

  • 3.3.1 Error Identification

• Understandable: Missing information in grouped buttons

  Non-accessible content and its shortcomings

  Label elements are missing from some grouped buttons. Required label information is missing from some radio button groups.

  Non-fulfilled accessibility requirements

  • 3.3.2 Labels or Instructions

• Robust: Aria-label attribute not used to provide invisible labels

  Non-accessible content and its shortcomings

  All icons and buttons do not have attributes readable by screen readers.

  Non-fulfilled accessibility requirements

  • 4.1.2 Name, Role, Value

• Robust: All control objects have not been assigned a role

  Non-accessible content and its shortcomings

  Screen readers cannot detect whether an object is open or closed. In addition the state of ”yes” and ”no” buttons cannot be detected.

  Non-fulfilled accessibility requirements

  • 4.1.2 Name, Role, Value

• Robust: Accessible names for form fields missing

  Non-accessible content and its shortcomings

  Some form fields do not have attributes. Screen readers should be able to recognize field names by label attributes.

  Non-fulfilled accessibility requirements

  • 4.1.2 Name, Role, Value

• Robust: All messages are not displayed to screen readers

  Non-accessible content and its shortcomings

  All state-related messages within forms are not displayed to screen readers. For example the error message for an inadequately filled-in form field cannot be read by a screen reader.

  Non-fulfilled accessibility requirements

  • 4.1.3 Status Messages

• Robust: Screen reader does not display search results

  Non-accessible content and its shortcomings

  After a performed search, the screen reader does not display the search results to the user

  Non-fulfilled accessibility requirements

  • 4.1.3 Status Messages