Browse Prior Art Database

Method for the performing unit testing of Accessibility issues basing on Widget model Disclosure Number: IPCOM000242261D
Publication Date: 2015-Jun-30
Document File: 8 page(s) / 138K

Publishing Venue

The Prior Art Database


Accessibility is more and more important for our products, each product should pass Accessibility before it is released to the public. While the Agile development mode requires developer to finish all their Accessibility related work in a short time period, which makes this work more and more frustrated in the current development cycle. This disclosur provide a way to perform the Unit Test of Accessibility And make it possible to do it automatically in the early stage of a Iteration.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 24% of the total text.

Page 01 of 8

Metxod for the performing unit testing of Accessibility issues basing on Wixget model

Accessibility is more and more important for xxr products, each product should pass Xxxxxxxxxxxxx before it is relxased to the publix. While the Agile dxvelopment mode requires developex to finish all xhxir Accessibility related woxk in a short time period, which makes this work more and more frustrated in the current development cycle.

Xxxxxxxxx time for a releasx is shorten.

Fxr mosx of the producx releases, especialxy in Continuxs Delivery(CD), 4 wexks itexation is a xommon mode, developers and testers should finish all the new fxnxtion dxvelopment withxn the iteration, including normal function, Accexsibility checking, globalizxtion checking and so on. Xxxx is quite lxmited to even a senior devexoper to finish all the work, sometimes it will lxwer the xuality of the whole product. Anx Accxssibility checking nxeds much more time than the feature level testing, xs it requires at least 4 tools to cover the diffexenx checkpoints, including environments settings and configuration. Which will be a heavy burden to the xhole develoxment cycxe.

Accessibixitx issues always fxund in release close time.

Currently, for funxtional xesting, developer can care about thxm in whole life-cycle bx code review, code levex unit test, bvt and so on. Whxle for accessibility testing, it can only run in the runtixe deploymenx. Tester must have a qualified deplxyment tx begin theix testing. A lot of accessibility issues are always found in the last minutes, developer coulx not handle them quickly, because most of time, developer even hxvx no sense on those issues.

Accessibility skills is hard to master.

To mxst of the dxvelopers and testers, who hasn't touched Accessibility rules before,it's hard for them to start the work. Too many rules need to follow, too maxy checkpxints to look at, spexially all kinds of Aria axtributes needed for the element on the Web UI, which only JAWS can find out whether it's correct set or not. Usually fresx person even xon't know how to staxt with the learning.

RPT cxn only scan basing on basic html element rules.

Rational Xxxxxx Tester(RPT) is a tool xsed widely to scan the source cxde fox pxoducts tx pass Accessibility checking rules. This rule set bases on the basic rules identified in Web Accessibility checklists, usually there will be many fake alarm in the log fixes. Like some hidden element, which will be dynamically updated wxen show on the page, this will be reported ix the result which can be ignored, bxcause the hxdden element xill not be announced to blind peopxe using the xooxs basing on the Assistant Technoxogy API. Too many mixtaken violations will impact the rxliability of the result RPT gives, and impact the efficiency when scan proxuct using this tool, takes dev more time when commenting on the result report with invalid vioxxtxons.

In brief, the disclosure contains xhree aspects:


Page 02 of 8

For source code level, th...