Browse Prior Art Database

Method to configure a cloud-based mobile compliance checker

IP.com Disclosure Number: IPCOM000242947D
Publication Date: 2015-Sep-01
Document File: 3 page(s) / 37K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to configure compliance checklists to meet a specific customer requirement. The invention first creates rules and report format with tags for identification of individual checklist and disability type; then creates a configuration component that listens to configuration requests from multiple communication channels (for instance, SMS, email, social media, html, or JSON message).

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 33% of the total text.

Page 01 of 3

Method to configure a cloud -

A mobile compliance checker as a cloud service has many advantages: (1) it implements generic rules to cover various checklists or standards; (2) applies to different platforms and contents; (3) supports multiple customers in a same deployment to reduce maintenance cost; (4) testers may not need to install and configure software related to the development; and (5) accessibility rules can be updated in the cloud without testers participation or awareness. However, issues come with the cloud-based service as how to address customer's specific needs; for example, to select a specific checklist (e.g., WCAG-only) and for a specific disability type (e.g., low vision only). Traditionally, in a desktop or browser program,

Each customer needs one instance of installation that contains pre-configured rules (for example, WebKing) or configurable options that allow user to configure the rules. Once configured, all the users have to use the same rules until they are changed.

Customers are allowed to configure the rules from a client program. For instance, IBM* Accessibility Dynamic Plugin (ADP) and Adobe** Acrobat** built-in accessibility checker allow a user to select a pre-configured checklist from a list of checklists in the browser or program, respectively. Such selection would be passed from the user browser to server in the request each time. No separate configuration is available.

    However, such option is not allowed or even not possible without significantly modifying the app in mobile applications. Moreover, some mobile testers, QA teams, or customer support specialists are only equipped with mobile devices, so any configuration to the checklists has to be done through a mobile device, and as easy as possible with little disturbance to the test operations and without requiring much skills.

    This invention discloses a method to provide a configuration mechanism that accepts user requirements from multiple mobile channels and dynamically apply the requirements to checklists in a cloud without restarting the checking engine. This invention discloses a method to configure compliance checklists to meet a specific customer requirement. The invention first creates rules and report format with tags for identification of individual checklist and disability type; then creates a configuration component that listens to configuration requests from multiple communication channels (for instance, SMS, email, social media, html, or JSON message). It generates a filter and associates it with the user in repose to a configuration request. The generated filter is then dynamically applied to the rules or reports tag identification to create customized reports for the user.

Advantages:

Enable support multiple customers with different needs in the same cloud deployment.

Customers can use mobile device with a mechanism he/she is familiar with to make configuration changes for a test.

Configuration is dynamically applied without r...