Status: Untriaged
Owner: [email protected]
Labels: Type-Bug Pri-2 OS-Windows Area-BrowserUI accessibility

New issue 9614 by [email protected]: Report bug or broken website dialog
http://code.google.com/p/chromium/issues/detail?id=9614

What steps will reproduce the problem?
1. Hit ALT + SHIFT + T to set the focus to the toolbar.
2. Use right arrow to move focus to the page menu.
3. Open page menu (with the document icon) by using down arrow.
4. Hit up arrow once to select 'Report bug or broken website'. Hit Enter to  
activate.
5. Tab through the fields, using a tool like Inspect32 to verify the MSAA  
information exposed.

What is the expected output? What do you see instead?

Issues:
1. Page URL edit box reported as role client, which is the default role,  
when none is provided by
the programmer. Expected behavior: get_accRole should return  
ROLE_SYSTEM_TEXT.
2. Description textarea reported as role client, which is the default role,  
when none is provided
by the programmer. Expected behavior: get_accRole should return  
ROLE_SYSTEM_TEXT.
3. The labels connected to the form fields are not programmatically  
connected to the
corresponding field. Expected behavior: get_accName for each form field  
will return the label
string.
4. The string value contained in the 'Bug type' combobox is reported as the  
name, not the value.
Expected behavior: get_accValue should return the value currently selected  
in the combobox.
5. The close (X) button in the top-right corner does not report any MSAA  
name. Expected
behavior: get_accName for the button should return 'Close'.
6. MSAA focus cannot get to the 'Send screen shot of current page' checkbox.



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to