This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
P1 Task: review all the gdb-lite code for a11y compliance, and make all necessary fixes to become a11y compliant.
There are 6 java files in the "gdb" module where a11y problems can exist: 1. gdb/breakpoints/ActionsPanel.java cnd/gdb/src/org/netbeans/modules/cnd/debugger/gdb/breakpoints/ActionsPanel.java 2. gdb/breakpoints/FunctionBreakpointPanel.java cnd/gdb/src/org/netbeans/modules/cnd/debugger/gdb/breakpoints/FunctionBreakpointPanel.java 3. gdb/breakpoints/LineBreakpointPanel.java cnd/gdb/src/org/netbeans/modules/cnd/debugger/gdb/breakpoints/LineBreakpointPanel.java 4. gdb/GdbMemoryWindow.java cnd/gdb/src/org/netbeans/modules/cnd/debugger/gdb/GdbMemoryWindow.java 5. gdb/proxy/GdbConsoleWindow.java cnd/gdb/src/org/netbeans/modules/cnd/debugger/gdb/proxy/GdbConsoleWindow.java The first one ("gdb/breakpoints/ActionsPanel.java") is already reviewed and all a11y problems are fixed.
Another file which needs to be a11y verified is gdb/profiles/GdbProfile.java. It displays the Debugging node in project properties. Its currently just a single text field so its not likely to be noncompliant, but should still be checked.
File gdb/breakpoints/ActionsPanel.java is reviewed and all discovered a11y issues are fixed. The Netbeans accessibility module also does not report any a11y problems there. ------------------------------------------------------------------------- File gdb/breakpoints/FunctionBreakpointPanel.java is reviewed and all discovered a11y issues are fixed. The Netbeans accessibility module also does not report any a11y problems there. ------------------------------------------------------------------------- File gdb/breakpoints/LineBreakpointPanel.java is reviewed and all discovered a11y issues are fixed. The Netbeans accessibility module also does not report any a11y problems there. ------------------------------------------------------------------------- File gdb/GdbMemoryWindow.java has several a11y problems. Here is a report provided by the Netbeans accessibility module: Output from UIAccessibilityTester for window with title : Gdb Memory Results of Accessibility test, window with title "Gdb Memory" Doesn't implement Accessible : - none. No Accessible name : - none. No Accessible description : - none. Label with LABEL_FOR not set : - none. Components with no LABEL_FOR pointing to it : Class: org.openide.explorer.view.TreeTable { N/A | N/A } [0,0] Components with no mnemonic : - none. Components with wrong mnemonic (mnemonic isn't ASCII , label doesn't contain mn emonic): - none. Components not reachable with tab traversal : Class: org.openide.explorer.view.TreeTable { N/A | N/A } [0,0] -------------------------------------------------------------------------
File gdb/proxy/GdbConsoleWindow.java has several a11y problems. Here is a report provided by the Netbeans accessibility module: Output from UIAccessibilityTester for window with title : Debugger Console Results of Accessibility test, window with title "Debugger Console" Doesn't implement Accessible : - none. No Accessible name : - none. No Accessible description : - none. Label with LABEL_FOR not set : - none. Components with no LABEL_FOR pointing to it : Class: org.openide.explorer.view.TreeTable { N/A | N/A } [0,0] Components with no mnemonic : - none. Components with wrong mnemonic (mnemonic isn't ASCII , label doesn't contain mn emonic): - none. Components not reachable with tab traversal : Class: org.openide.explorer.view.TreeTable { N/A | N/A } [0,0] -------------------------------------------------------------------------
File gdb/profiles/GdbProfile.java creates the Debugging node in project properties: Debugging | Tool | gdb [...] (the word "gdb" is the default name of debugger, and user should be able to change it with and without mouse) I run the Netbeans accessibility test over this page, and it found several a11y issues. None of them is related to the Debugging node itself, but I cannot find a way to change the value of the Tool property without mouse. If I select this entry and try to type in a new value, it opens a "Quick Search" textfield, which is absolutely useless here, because it cannot find anything. Context menu (Shift+F10) also does not work - it just beeps. I can open context menu using right mouse button, but cannot open it without mouse. Here is a report provided by the Netbeans accessibility module: <TITLE>Output from UIAccessibilityTester for window with title : Project Propert ies - Args1 </TITLE> Results of Accessibility test, window with title "Project Properties - Args1" Doesn't implement Accessible : - none. No Accessible name : Class: org.openide.explorer.view.BeanTreeView { | } [14,71] Class: org.openide.explorer.view.TreeView$ExplorerTree { | } [14,71] No Accessible description : Class: javax.swing.JButton { Manage Configurations... | } [213,38] Class: javax.swing.JComboBox { Configuration: | } [85,40] Class: org.openide.explorer.view.BeanTreeView { | } [14,71] Class: org.openide.explorer.view.TreeView$ExplorerTree { | } [14,71] Label with LABEL_FOR not set : - none. Components with no LABEL_FOR pointing to it : Class: org.openide.explorer.propertysheet.SheetTable { Properties table | T able of editable properties representing the current object } [246,71] Class: org.openide.explorer.view.TreeView$ExplorerTree { | } [14,71] Components with no mnemonic : - none. Components with wrong mnemonic (mnemonic isn't ASCII , label doesn't contain mn emonic): Class: javax.swing.JLabel { Configuration: | } [12,42] Components not reachable with tab traversal : - none. -------------------------------------------------------------------------
File gdb/proxy/GdbConsoleWindow.java is reviewed and all discovered a11y issues are fixed. The Netbeans accessibility module also does not report any a11y problems there. -------------------------------------------------------------------------
File gdb/GdbMemoryWindow.java is reviewed and all discovered a11y issues are fixed. The Netbeans accessibility module also does not report any a11y problems there. -------------------------------------------------------------------------
All known a11y issues are fixed.