JRNI Accessibility Standards & Compliance with the Web Content Accessibility Guidelines (WCAG) 2.1

1. JRNI Accessibility Overview

1.1 JRNI strives to provide an open, accessible, and compliant experience to all users.

1.2 To achieve this, to the extent possible, all JRNI end-user interfaces follow the internationally recognized best practices in Section 508 of the Rehabilitation Act and the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.

2. Approach to WCAG 2.1

2.1 WCAG 2.1 covers a wide range of recommendations for making web content more accessible to a wider range of people with disabilities. This includes those with visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

2.2 JRNI endeavors to adhere to the WCAG 2.1 (AA) standards, by following its four design principles and twelve supporting guidelines to make web content more accessible for people with disabilities.

3. JRNI Guidelines & Conformance to WCAG 2.1

3.1 JRNI’s open commitment to providing an accessible service is defined by the guidelines and standards set out by WCAG 2.1, as follows.

(i). Principle 1: PERCEIVABLE. Information and User Interface Components must be presented to users in ways that they can perceive (users can recognize and use the service with the senses available to them).


JRNI Comments/Method of Adherence

1.1. Text Alternatives (for any non-text content)

JRNI uses aria-label to provide labels for objects and uses alt attributes on img elements.

1.2. Time-based Media Alternative

JRNI uses live audio and video to facilitate phone and video appointments; however, no real-time captioning capability is provided.

1.3. Adaptable

JRNI adopts the following techniques to present content in different ways, thus making it more accessible for users:

  • ARIA landmarks used to identify regions of a page & aria-labeled by name regions and landmarks.
  • Use of role=heading to identify headings.
  • Using aria-labeled by to provide a name for user interface controls.
  • Grouping roles to identify related form controls.
  • Use of the region role to identify a region of the page.
  • Using semantic elements to mark-up structure and to mark emphasized or special text.
  • Separation of information and structure from presentation to enable different presentations.
  • Table mark-up to present tabular information.
  • Using caption elements to associate data table captions with data tables.
  • Using the summary attribute of the table element to give an overview of data tables.
  • Using the scope attribute to associate header cells and data cells in data tables
  • Using label elements to associate text labels with form controls.
  • Using the title attribute to identify form controls when the label element cannot be used.
  • Using OPTGROUP to group OPTION elements inside a SELECT.
  • Using h1-h6 to identify headings.
  • Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
  • The purpose of each input field collecting information about the user can be programmatically determined.

1.4. Distinguishable

To make it easier for users to see and hear content, JRNI uses:

  • Readable fonts.
  • Text in images of text is at least 14 points with a good contrast.
  • A highly visible mechanism for links or controls when they receive keyboard focus.
  • CSS letter-spacing to control spacing within a word.
  • Positioning of content based on structural mark-up.
  • Technology that has commonly available user agents that support Zoom (this technology is handled by the modern browser).
  • Vertical scrolling content at a width equivalent to 320 CSS pixels.
  • Horizontal scrolling content at a height equivalent to 256 CSS pixels.
  • The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s) for user interface components and graphical objects.
  • Line height (line spacing) to at least 1.5 times the font size.
  • Spacing following paragraphs to at least 2 times the font size.
  • Letter spacing (tracking) to at least 0.12 times the font size.
  • Word spacing to at least 0.16 times the font size.
  • Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, with the exception of additional contents controlled by user agents.

(ii). Principle 2: OPERABLE. User Interface components and navigation must be operable (the interface cannot require interaction that a user cannot perform. The user can find content regardless of how they choose to access it).


JRNI Comments/Method of Adherence

2.1. Keyboard Accessible

JRNI provides keyboard control for all functionality. Where core functions are triggered by mouse, JRNI provides alternative user interfaces to make these functions available via keyboard.

2.2. Enough Time

JRNI provides a 15-minute window for users to complete a booking. In our experience, this is more than enough time for all users to read and use the relevant content and complete the necessary functions to create a booking.

2.3. Seizures (design of content)

JRNI does not have any content designed in a way that is known to cause seizures; it has no flashing, blinking text or objects.

2.4. Navigable

The JRNI Studio interface is easily navigable and provides ways to help users navigate, find content, and determine where they are. This is done via the following approaches:

  • Limiting the number of links per page.
  • Providing mechanisms to navigate to different sections of the content of a Web page.
  • Making links visually distinct.
  • Use of meaningful links, heading, and labels.
2.5 Input ModalitiesJRNI makes it easier for users to operate functionality through various inputs beyond the keyboard. This is done via the following approaches:
  • All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture.
  • Actions can be easily canceled by gesturing away from interactable elements.
  • For user interface components with labels that include text or images of text, the name contains the text that is presented visually.
  • Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation.

(iii). Principle 3: UNDERSTANDABLE. Information and the operation of the user interface must be understandable.


JRNI Comments/Method of Adherence

3.1. Readable & Understandable

JRNI uses plain and clear English and is devoid of unusual words or jargon. Sentences are short, phrases logical, and all acronyms/ abbreviations are explained.

3.2. Predictable

The JRNI User Interface looks consistent and behaves in a predictable manner; e.g., no un-announced pop-up windows, disabling of the back button. The provided navigation is structured and arranged consistently.

3.3. Input assistance

The JRNI User Interface helps users avoid and correct mistakes. This is done via the use of clearly identified missing fields, and by providing examples of required content. It can also suggest corrections in the case of an input error and provide error ID and labels.

(iv). Principle 4: ROBUST. Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies (users must be able to access the content as technologies advance).


JRNI Comments/Method of Adherence

4.1. Compatible: Maximize compatibility with current and future agents including assistive technologies.

JRNI uses mark-up language written in HTML to support accessibility. ARIA is used to support the platforms accessibility, as well as support from most modern browsers.

User agent support continues to make access possible; this technology is ever expanding and growing.

In content implemented using markup languages, status messages can be programmatically determined through roles or properties such that they can be presented to the user by assistive technologies without receiving focus.

4. Testing

4.1 JRNI is tested periodically at a systems level by an accredited third party using WCAG-EM evaluation methodologies to ensure it operates correctly while using assistive technology. A compliance report is produced for each test run, where the scope of testing is detailed and issues identified are classified by severity as defined below:

(1) Blocker: A user is unable to complete a workflow

(2) Critical: A violation of a WCAG guideline

(3) Recommendation: The user experience can be optimized to work more effectively or logically with assistive technology

4.2 JRNI is committed to fixing all Blocker and Critical issues identified where a fix is viable.

5. Continuous Improvement

5.1 JRNI acknowledges that providing accessibility to all users is a work in progress. To ensure that no user is disadvantaged, JRNI endeavors to respond and react accordingly to all requests relating to assistance with accessibility by altering the necessary content/function as soon as possible, or by providing a replacement or alternative workaround within a reasonable timeframe.

5.2 Should customers find an area of limited accessibility, JRNI will endeavor to find a route to a solution, as per one of the methods below:

(a) Review of the request and, after internal viability discussion, addition to the product roadmap.
(i) If a request accepted into the product roadmap cannot be delivered in a suitable time frame, accelerated delivery may be provided for a mutually agreed fee.

(b) Workaround suggestion/resolution.

(c) Custom development of the bespoke accessibility request may be provided for a mutually agreed fee (if the request is not considered to be an out-of-the-box feature relevant to the roadmap).

5.3 JRNI is committed to developing new products in conformance with WCAG 2.1, and endeavors to integrate accessibility into every stage of product design, development, and testing.

6. Known Exceptions to the intended Level of Web Accessibility. (Non-Compliant Interfaces)

6.1 While JRNI strives to adhere to the accepted standards set out by WCAG 2.1, it is not always possible to do so in all areas of the JRNI platform. Areas of limited accessibility are documented in the Accessibility Risk Register.

7. Additional Standards

7.1 In the circumstance where compliance to additional standards (i.e., any standard not specified in 1.2) is required, JRNI will estimate the level of effort required to support these standards and provide a full cost to deliver this.

Revision: 2.5 (August 19, 2020)