Accessibility Statement for Päikky Guardian Service

1. Application does not completely meet criteria

• Perceivable: Mobile application works only in portrait mode

  Non-accessible content and its failings

  Mobile application does not work in landscape position yet, even though the app has been fully rewritten. Only hindrance at this point is the login screen and others built on the same template, for example change password view.

  Accessibility criteria not met

  • 1.3.4 Orientation

• Perceivable: Survey text input errors show only as red, after submitting

  Non-accessible content and its failings

  After trying to submit answers to a survey, an error dialog appears, and on acknowledge, shifts to the first spot in the survey that needs correcting, but fields with errors are simply colored red, and no other indication shows the user which fields are, in fact, erroneous.
  
  We hope to have this fixed within the next couple of months at the latest.

  Accessibility criteria not met

  • 1.4.1 Use of Color

• Perceivable & Operable & Understandable & Robust: Login-related views have minor issues

  Non-accessible content and its failings

  There are many places with white text against a colored background where the contrast is too low.
  
  User is automatically sent to "change password" view after logging in with an expired password. There is no other way to reach this view.
  
  If a user enters non-numbers in the username field of the login screen, these are removed automatically and the user is not notified.
  
  Dropdown list doesn't have proper label / role specified.
  
  We plan to have all these fixed as soon as possible.

  Accessibility criteria not met

  • 1.4.3 Contrast (minimum)
  • 2.4.5 Multiple Ways
  • 3.3.1 Error Identification
  • 4.1.2 Name, role, value

• Perceivable: Some minor text cut-offs when text size is at 200%

  Non-accessible content and its failings

  In calendar view, month and week balance views, planning view, surveys and login views there are minor problems with text getting cut off when text size is at 200%. In none of these cases does the cut-off text cause the view to be unusable. The worst case is in user-entered dates in surveys. These show up slightly cut-off in text fields, but when editing, the datepicker is fully visible and there is no question what the selected date is.

  Accessibility criteria not met

  • 1.4.4 Resize text

• Perceivable: Resizing text doesn't affect application content on iOS (mobile application)

  Non-accessible content and its failings

  Mobile application uses webview technology, which on iOS doesn't seem to pass along the text size settings from the operating system. Therefore, resizing the text on iOS has no affect on text size within the application.

  Accessibility criteria not met

  • 1.4.4 Resize text

• Operable: Time picker not working with screen reader

  Non-accessible content and its failings

  Issues are related to a library we are using.
  
  Not exactly a keyboard issue, but using screenreader, the current implementation of time picker we are using is essentially completely unusable.

  Accessibility criteria not met

  • 2.1.1 Keyboard

• Operable: Calendar widget previous/next month buttons not fully working with screen reader in iOS

  Non-accessible content and its failings

  Not exactly a keyboard issue, but using screenreader, previous/next month navigation with the calendar widget often jumps back/ahead 2 months at a time.

  Accessibility criteria not met

  • 2.1.1 Keyboard

• Operable: Message list updated occasionally

  Non-accessible content and its failings

  The message list updates at certain intervals, which may disturb a user who is just then reading a message thread or looking at the message list.

  Accessibility criteria not met

  • 2.2.2 Pause, Stop, Hide

• Operable: Pages do not have titles

  Non-accessible content and its failings

  Although this is largely a single-page-app, it would be more accessible if the various views had unique titles.

  Accessibility criteria not met

  • 2.4.2 Page Titled

• Operable: Focus order is not always logical

  Non-accessible content and its failings

  Focus is not always logical when using SR. e.g. Focus does not start at the top of the page when navigating to a new page.

  Accessibility criteria not met

  • 2.4.3 Focus order

• Operable: Date picker components have names which are not the same as the labels for these values

  Non-accessible content and its failings

  There are date pickers in several views: Planning, edit default plans, surveys. These date pickers' names are e.g. "Choose time", while the label could be simply "Arrives" or "Leaves".

  Accessibility criteria not met

  • 2.5.3 Label in Name

• Understandable: Outermost HTML element's "lang" attribute is "en", regardless of the page's actual content

  Non-accessible content and its failings

  Inner HTML element's "lang" attribute tells the content's language, but that of the external HTML element cannot be trusted.

  Accessibility criteria not met

  • 3.1.1 Language of Page

• Robust: Some failings in status messages

  Non-accessible content and its failings

  Screen reader does not register the status of loading indicator. Same is true of some errors.

  Accessibility criteria not met

  • 4.1.3 Status Messages