NB69A11YandI18Ntesting

Revision as of 14:57, 20 April 2010 by Juhrik (Talk | contribs)

NetBeans 6.9 Accessibility and Internationalization Testing plan

Quality engineers will explicitly write issues filed during testing to this table :

Area QE Owner(s) A11Y I18N
Maven/ Web Services Client/ Partner Services Jaroslav Pospisil
PHP Filip Zamboj
Debugger Marian Mirilovic NOT TESTED NOT TESTED
C-dev Jara Uhrik P2: 184532, 184549, 184556

P3: 184542, 182544, 182547

NOT TESTED
Editor/ Java/ Refactoring Peter Pis
OSGi Tomas Musil
DB Michael Nazarov
Java EE Martin Schovanek/Michal Mocnak
JavaScript Petr Blaha
Web, JSP, HTML, CSS Jindra Sedek
XML, Installler/AU Michael Nazarov
Mobility Andrei Chistiakov NOT TESTED NOT TESTED
Java FX Alexandr Scherbatiy/Lukas Hasik
CnD Alexander Pepin
C/V, Platform Ivan Sidorkin
Server Plugins Davis Nguyen
Summary: All Issues, P2 issues, P3 issues, P4 issues

Accessibility

According to the NB 69 Quality Plan the NetBeans Quality Engineering will provide testing of accessibility during Apr 19-21. We agreed that testing will be provided only for areas that changed UI a lot or hasn't been tested yet. If your area is not tested then please write "NOT TESTED" to the table.

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.

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 UI).

  • For all new features/UI 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 UI 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 6.9 Beta build or daily build.

Assessment

The 508 form will be submitted by May 3 at http://section508tool.sfbay/ and will contain link to this document.

Contact person

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

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