icon-logo

Statement for Rifaximin Pathway Deployment

References:

Web Content Accessibility guidelines

WCAG 2 at a Glance

Below, we provide our accessibility conformance report covering the deployment and use of the Rifaximin Pathway application, designed for use within the clinical coding departments of NHS provider organisations. To be noted, the product is not an information service (used in conjunction with a website, intranet, or extranet) for general consumption; it is not a mobile application. The product has been designed as a cloud-based system, for ease of deployment

This report does not include reference to the browsers used to access the product; individual browsers will contain design features that support accessibility, such as contrast, screen sizing, and various plug-ins to meet Regulations.

The Accessibility Regulations came into force for public sector bodies on 23 September 2018. They state you must make websites or mobile app more accessible by making it ‘perceivable, operable, understandable and robust’. Developers need to include and update an accessibility statement on their website. Whilst ACCORD™ is not a product targeted for use by Public Sector Bodies for onward transmission of information via a website or mobile app, the product falls under the Regulations, and making a website or mobile app accessible means making sure it can be used by as many people as possible. Intranet and extranet websites are covered by the accessibility regulations. These are internal websites which disabled employees working in or with the public sector may use.

This includes those with:

  • impaired vision
  • motor difficulties
  • cognitive impairments or learning disabilities
  • deafness or impaired hearing

The accessibility regulations build on existing obligations to people who have a disability under the Equality Act 2010 (or the Disability Discrimination Act 1995 in Northern Ireland).

Websites or mobile apps will meet the newer legal requirements if they:

  • meet the international WCAG 2.1 AA accessibility standard – although there may be valid legal reasons for not meeting accessibility standards
  • publish an accessibility statement that explains how accessible the website or mobile app is

This accessibility statement is made on the understanding that the product’s target audience is finite, comprised of a limited number of individuals per NHS Trust. The product is not generally available via the World Wide Web. No patients, no general public, or wider NHS staff members would require access. The product represents a discrete offering serving a specialist information need, which wherever possible has been designed to meet the WCAG 2.1 standards.

WCAG 2.1 was initiated with the goal to improve accessibility guidance for three major groups:

  1. Users with cognitive or learning disabilities;
  2. Users with low vision;
  3. Users with disabilities on mobile devices.

Of note, the Working Group considers that WCAG 2.1 incrementally advances web content accessibility guidance for all these areas but underscores that not all user needs are met by these guidelines.

Level of compliance for the Rifaximin Pathway product

The table below highlights where the Rifaximin Pathway application conforms to the standard. Each individual success criterion is listed for levels, A, AA and AAA, and compliance is stated against each one.

Overall accessibility is assessed as partially compliant.

Due to its focus, the product does not include multi-media, video or audio recordings. Where included as individual success criterion, all reference to multi-media has been regarded as not applicable for this accessibility statement.

Additionally, as referenced within the WCAG 2.1 standard, many of the success criteria are based upon websites containing multiple pages, requiring accessibility features to support all users in navigation. Also, reference is made to mobile access and use of apps. Rifaximin Pathway is not used as part of a public sector, public-facing website, nor is it an application for use via a smartphone. The tool is not licensed to be used as part of an intranet or extranet information service. It is a tool for providing specialist feedback on clinical coding data sets. It provides reports that are used by NHS accredited auditors, only, to assess own in-house data content.

Where not fully compliant, the table highlights which parts do not currently meet accessibility standards and why based upon the above rationale. The terms used in the conformance level information are defined as follows:

  • Supported: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supported: Some functionality of the product does not meet the criterion.
  • Does Not Support: The majority of product functionality does not meet the criterion.
  • Not Applicable: The criterion is not relevant to the product.

 

Criteria

Conformance

Remarks

 

 

 

1.1.1 Non-text Content (Level A)

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for stated situations.

Not applicable

The application does not contain any content that is not a sequence of characters.

 

 

 

1.2.1 Audio-only and Video-only (Pre-recorded) (Level A)

Not Applicable

The application does not include prerecorded audio-only or prerecorded video-only content.

 

 

 

1.2.2 Captions (Pre-recorded)

(Level A)

Not Applicable

The application does not include pre-recorded synchronised media content.

 

 

 

1.2.3 Audio Description or Media Alternative (Pre-recorded)

(Level A)

Not applicable

The application does not include pre-recorded video content.

 

 

 

Success Criterion 1.2.4 Captions (Live)

(Level AA)

Captions are provided for all live audio content in synchronized media.

Not applicable

No live audio content.

 

 

 

Success Criterion 1.2.5 Audio Description (Pre-recorded

(Level AA)

Audio description is provided for all pre-recorded video content in synchronized media.

Not applicable

No audio provided; no pre-recorded video content.

 

 

 

Success Criterion 1.2.6 Sign Language (Prerecorded)

(Level AAA)

Sign language interpretation is provided for all pre-recorded audio content in synchronized media.

Not applicable

No pre-recorded audio content in synchronized media.

 

 

 

Success Criterion 1.2.7 Extended Audio Description (Pre-recorded)

(Level AAA)

Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media.

Not applicable

No audio, no video.

 

 

 

Success Criterion 1.2.8 Media Alternative (Pre-recorded)

(Level AAA)

An alternative for time-based media is provided for all prerecorded synchronized media and for all pre-recorded video-only media.

Not applicable

No pre-recorded media.

 

 

 

Success Criterion 1.2.9 Audio-only (Live)

(Level AAA)

An alternative for time-based media that presents equivalent information for live audio-only content is provided.

Not applicable

No audio.

 

 

 

Success Criterion 1.3.1 Info and Relationships

(Level A)

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Supported.

 

 

 

 

Success Criterion 1.3.2 Meaningful Sequence

(Level A)

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

Supported

The application presents a correct and logical reading sequence for all content.

 

 

 

Success Criterion 1.3.3 Sensory Characteristics

(Level A)

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.

Supported

The application does not rely solely on shape, colour, size, location, orientation, or sound to convey instructions.

 

 

 

Success Criterion 1.3.4 Orientation

(Level AA)

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.

Supported

Content does not restrict its view and operation to a single display orientation.

 

 

 

Success Criterion 1.3.5 Identify Input Purpose

(Level AA)

The purpose of each input field collecting information about the user can be programmatically determined when:

·         The input field serves a purpose identified in the Input Purposes for User Interface Components section; and

·         The content is implemented using technologies with support for identifying the expected meaning for form input data.

Supported

 

 

 

 

Success Criterion 1.3.6 Identify Purpose

(Level AAA)

In content implemented using markup languages, the purpose of User Interface Components, icons, and regions can be programmatically determined.

Partially supported

Techniques provide programmatic access to sections of the web page. Landmark roles programmatically identify sections of a page, which help assistive technology (AT) users orientate themselves to a page and help them navigate easily to various sections of a page.

 

 

 

Success Criterion 1.4.1 Use of Colour

(Level A)

Colour is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Supported

Colour is not used as the only visual means of conveying information.

 

 

 

Success Criterion 1.4.2 Audio Control

(Level A)

If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.

Not applicable

No audio used.

 

 

 

Success Criterion 1.4.3 Contrast (Minimum)

(Level AA)

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1

Supported

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1.

 

 

 

Success Criterion 1.4.4 Resize text

(Level AA)

Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

Supported

Text can be resized without assistive technology up to 200 percent without loss of content or functionality.

 

 

 

Success Criterion 1.4.5 Images of Text

(Level AA)

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text.

Supported

Text is used to convey information rather than images of text.

 

 

 

Success Criterion 1.4.6 Contrast (Enhanced)

(Level AAA)

The visual presentation of text and images of text has a contrast ratio of at least 7:1

Not supported

 

 

 

 

Success Criterion 1.4.7 Low or No Background Audio

(Level AAA)

For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping.

Not applicable

No audio.

 

 

 

Success Criterion 1.4.8 Visual Presentation

(Level AAA)

Partially supported

Foreground and background colours cannot be selected by the user.

Line spacing (leading) is not at least space-and-a-half within paragraphs, and paragraph spacing is not at least 1.5 times larger than the line spacing.

 

 

 

Success Criterion 1.4.9 Images of Text (No Exception)

(Level AAA)

Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed.

Supported

 

 

 

 

Success Criterion 1.4.10 Reflow

(Level AA)

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions

Not supported

Microsoft Excel spreadsheet review requires two-dimensional scrolling.

 

 

 

Success Criterion 1.4.11 Non-text Contrast

(Level AA)

Partially supported

The visual presentation has a contrast ratio of at least 3:1 for certain screen features only. No graphics included.

 

 

 

Success Criterion 1.4.12 Text Spacing

(Level AA)

Partially supported

In content implemented using markup languages, some loss of content or functionality occurs by changing style property.

 

 

 

Success Criterion 1.4.13 Content on Hover or Focus

(Level AA)

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden.

Partially supported

No mechanism available to dismiss the additional content without moving pointer hover or keyboard focus.

 

 

 

Success Criterion 2.1.1 Keyboard

(Level A)

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints.

Supported

 

 

 

 

Success Criterion 2.1.2 No Keyboard Trap

(Level A)

If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

Partially supported

The user is not advised of the method for moving focus away.

 

 

 

Success Criterion 2.1.3 Keyboard

(Level AAA)

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

Supported

 

 

 

 

Success Criterion 2.1.4 Character Key Shortcuts

(Level A)

Keyboard shortcuts implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters.

Not applicable

 

 

 

 

Success Criterion 2.2.1 Timing Adjustable

(Level A)

Time limit is set by the content.

Not applicable

 

 

 

 

Success Criterion 2.2.2 Pause, Stop, Hide

(Level A)

For implemented moving, blinking, scrolling, or auto-updating information.

Not applicable

 

 

 

 

Success Criterion 2.2.3 No Timing

(Level AAA)

Timing is not an essential part of the event or activity presented by the content.

Supported

 

 

 

 

Success Criterion 2.2.4 Interruptions

(Level AAA)

Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.

Not applicable

 

 

 

 

Success Criterion 2.2.5 Re-authenticating

(Level AAA)

When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.

Supported

 

 

 

 

Success Criterion 2.2.6 Timeouts §

 (Level AAA)

Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.

Not applicable

Data preserved within Excel™ format for use.

 

 

 

Success Criterion 2.3.1 Three Flashes or Below Threshold

(Level A)

Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

Supported

No on-screen flashes.

 

 

 

Success Criterion 2.3.2 Three Flashes

(Level AAA)

Web pages do not contain anything that flashes more than three times in any one second period.

Supported

No on-screen flashes.

 

 

 

Success Criterion 2.3.3 Animation from Interactions

(Level AAA)

Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.

Supported

No animation in content implemented.

 

 

 

Success Criterion 2.4.1 Bypass Blocks

(Level A)

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

Not applicable

No content repeated on multiple web pages.

 

 

 

Success Criterion 2.4.2 Page Titled

(Level A)

Web pages have titles that describe topic or purpose.

Supported

 

 

 

 

Success Criterion 2.4.3 Focus Order

(Level A)

If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

Supported

 

 

 

 

Success Criterion 2.4.4 Link Purpose (In Context)

(Level A)

The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

Supported

 

 

 

 

Success Criterion 2.4.5 Multiple Ways

(Level AA)

More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.

Supported

 

 

 

 

Success Criterion 2.4.6 Headings and Labels

(Level AA)

Headings and labels describe topic or purpose.

Supported

 

 

 

 

Success Criterion 2.4.7 Focus Visible

(Level AA)

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

Supported

 

 

 

 

Success Criterion 2.4.8 Location

(Level AAA)

Information about the user’s location within a set of Web pages is available.

Supported

 

 

 

 

Success Criterion 2.4.9 Link Purpose (Link Only)

(Level AAA)

A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.

Supported

 

 

 

 

Success Criterion 2.5.1 Pointer Gestures

(Level A)

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

Supported

 

 

 

 

Success Criterion 2.5.2 Pointer Cancellation

(Level A)

Functionality that can be operated using a single pointer.

Not applicable

 

 

 

 

Success Criterion 2.5.3 Label in Name

(Level A)

For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

Not applicable

 

 

 

 

Success Criterion 2.5.4 Motion

(Level A)

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.

Not applicable

 

 

 

 

Success Criterion 2.5.5 Target Size

(Level AAA)

The size of the target for pointer inputs is at least 44 by 44 CSS pixels.

Supported

 

 

 

 

Success Criterion 2.5.6 Concurrent Input Mechanisms

(Level AAA)

Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings.

Not applicable

 

 

 

 

Success Criterion 3.1.1 Language of Page

(Level A)

The default human language of each Web page can be programmatically determined.

Supported

 

 

 

 

Success Criterion 3.1.2 Language of Parts

(Level AA)

The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

Supported

 

 

 

 

Success Criterion 3.1.3 Unusual Words

(Level AAA)

A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon.

Not applicable

 

 

 

 

Success Criterion 3.1.4 Abbreviations

(Level AAA)

A mechanism for identifying the expanded form or meaning of abbreviations is available.

Not applicable

Not required.

 

 

 

Success Criterion 3.1.5 Reading Level

(Level AAA)

When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.

Not applicable

Not required.

 

 

 

Success Criterion 3.1.6 Pronunciation

(Level AAA)

A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.

Not applicable

Not required.

 

 

 

Success Criterion 3.2.1 On Focus

(Level A)

When any user interface component receives focus, it does not initiate a change of context.

Supported

 

 

 

 

Success Criterion 3.2.2 On Input

(Level A)

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behaviour before using the component.

Not applicable

 

 

 

 

Success Criterion 3.2.3 Consistent Navigation

(Level AA)

Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

Not applicable

Multiple web pages do not apply to the product; navigation is however consistent.

 

 

 

Success Criterion 3.2.4 Consistent Identification

(Level AA)

Components that have the same functionality within a set of Web pages are identified consistently.

Supported

 

 

 

 

Success Criterion 3.2.5 Change on Request

(Level AAA)

Changes of context are initiated only by user request or a mechanism is available to turn off such changes.

Not applicable

 

 

 

 

Success Criterion 3.3.1 Error Identification

(Level A)

If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

Not applicable

 

 

 

 

Success Criterion 3.3.2 Labels or Instructions

(Level A)

Labels or instructions are provided when content requires user input.

Supported

 

 

 

 

Success Criterion 3.3.3 Error Suggestion

(Level AA)

If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

Not applicable

 

 

 

 

Success Criterion 3.3.4 Error Prevention (Legal, Financial, Data)

(Level AA)

For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses.

Not applicable

 

 

 

 

Success Criterion 3.3.5 Help

(Level AAA)

Context-sensitive help is available.

Not applicable

Not required.

 

 

 

Success Criterion 3.3.6 Error Prevention (All)

(Level AAA)

For Web pages that require the user to submit information

Not applicable

No user information submitted to web pages.

 

 

 

Success Criterion 4.1.1 Parsing

(Level A)

In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

Supported

 

 

 

 

Success Criterion 4.1.2 Name, Role, Value

(Level A)

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

Not applicable

No states, properties, and values can be set by the user.

 

 

 

Success Criterion 4.1.3 Status Messages

(Level AA)

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

Not supported

 

 

 

 

5. Conformance

This section lists requirements for conformance to WCAG 2.1. It also gives information about how to make conformance claims, which are optional.

This report assesses the deployment of ACCORD™ to be partially compliant with WCAG 2.1. No claims on compliance are made.

 

 

 

 

 

Individuals that are unable to access the Rifaximin Pathway application are able to get alternatives to content that is not accessible to them by contacting the in-house clinical coding department.

Should any user wish to contact IGspectrum Private Limited to report accessibility problems and or make a complaint about any responses received in connection with accessibility, they should please contact the company using support@igspectrum.com

 

Legal Disclaimer

This accessibility compliance statement represents the current view of Igspectrum Private Limited regarding information about the subject product, Rifaximin Pathway, as outlined.

Igspectrum does not guarantee that any information in this statement will remain accurate, but Igspectrum works continuously to monitor the accessibility of its products and provide updates from time to time.

Any modification or customisation to Rifaximin Pathway may entail elements of this statement to become inapplicable. This statement is provided “as is” and for informational purposes only.