Revision as of 10:50, 21 January 2011 by Juhrik (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

NetBeans 7.0 Accessibility Testing plan


Results Table

Quality engineers will explicitly insert proper lines and write issues filed during testing to this table :

Area QE Owner(s) Build(s) tested Testing results
Debugger Jiří Kovalský #201011250001 DONE

P2: 192474 192475
P3: 192471 192472

DB Tomas #20101125 DONE

P3: 192467 192541

Editor Jaromír Uhřík #201011260001 DONE
P2: 192538

P3: 192539
P4: 192535

Maven Tomas #20101125 DONE

P3: 192664 192669 192680

Java WEB & EE Filip #201010151251 DONE
P2: 192692

P3: 192689 192691
P4: 192676 192677 192683 192688 192690 192693 192694 192695 192696 192697 192698 192700 192702 192684

Summary: All Issues(29), P2 issues(4), P3 issues(10), P4 issues(15)


According to the NB 7.0 Quality Plan the NetBeans Quality Engineering will provide testing of accessibility during Nov 15. We agreed that testing will be provided only for newly created GUI.
Notice: since there was different schedule for week of Nov 15 the testing has been moved to the week of Nov 22

Each QE engineer is required to write "NOT TESTED" to the table in case that the area hasn't been equipped by new GUI. If the testing of the area is completed then "DONE" is required in the proper cell.

A11Y-testing tool

To install the tester tool please follow the page at http://wiki.netbeans.org/A11YShortly

How to evaluate A11Y-tester output

It is not enough to execute A11Y-tester and file issues according to its output. While testing A11Y by A11Y-tester module there is human evaluation needed. The tool returns 2 types of results for each accessibility category of conflicts:

  • 1/String "-none" in the output means that there is no conflict in appropriate category of conflicts.
  • 2/The output of the tool tells us where could be potentially A11Y-issue but those suspicions need to be checked and the conclusion decision should be made whether it is issue or not according to common sense.

Notice: Please do NOT execute testing on Mac OS X because the tool is not fully compatible with that platform.

Testing process

We will use distributed process of testing NetBeans accessibility. It means that everybody from NetBeans Quality Engineering should execute A11Y testing in his/her responsible area (according to changes made in GUI).

  • For all new features/GUI there should be executed "first round" of a11y-testing right after the feature is integrated. This testing is executed in the same range as "regular round".
  • The "regular round" is usually executed at the same time for all team members according to the testing schedules. Quality engineer executes tests for all dialogs and GUI components from the area of responsibility and evaluates the output. Issues are reported to issuezilla and the issue priority is set according to the Bug priority guidelines document. Add keyword "A11Y" into the keyword field of reported issue. We used to have issue summary prefix 'A11Y' but please don't use this convention and sign the a11y-issues just with the 'A11Y' keyword. The output from A11Y-tester is usually added to the issue description.
  • Provide testing with the latest 7.0 builds or daily build.


Originally the 508 form needed to be submitted by Jan 17 at http://section508tool.us.oracle.com/ According to the slip of the release the submit date is moved to the end of week of Jan 24.

According to the http://globaldc.oracle.com/perl/twiki/view/AccessibilityProgram/VpatWriters#Creating%20a%20VPAT the VPAT is typically done by the Product Manager, QA Team, or Release Manager. The 'input' to the process is actual accessibility test results.

Link to this document will be added to the assessment.

Contact person

If you have questions related to accessibility feel free to contact Jaromir.Uhrik@Oracle.Com

Completed Dates

Testing has been performed in Nov 25 - Dec 01, 2010.

508 assessment submitted in TBD, 2010.

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo