Accessibility/Testing: Difference between revisions

no edit summary
No edit summary
 
Line 5: Line 5:
*[[MozillaQualityAssurance:Home_Page:Firefox_3.0_TestPlan:UIAccessibility|Firefox 3.0 Accessibility Test Plan]]
*[[MozillaQualityAssurance:Home_Page:Firefox_3.0_TestPlan:UIAccessibility|Firefox 3.0 Accessibility Test Plan]]


==Bugs of Note==
I'd like this area to evolve into a scratchpad of sorts where people can nominate bugs of particular importance to them based on their platform or disability.  It may turn out to be superfluous, but this will provide Mozilla developers and module owners a quick snapshot of high-priority accessibility-related bugs.  Everyone's priorities are different, and I'm hoping to capture a good cross-section of the accessibility community.
===All Platforms===
*{{bug|395096}}: No Quick Way to Focus Remember Password Prompt
*{{bug|392802}}: File Listings Very Hard to Read
*{{bug|393398}}: Add Bookmark Interface Inaccessible
===Windows Only===
===Linux Only===
{{Bug|332662}}: popup menu could not be grabbed by GOK.
{{bug|332663}}: Submenus are Not Accessible Via GOK when Activated for the First Time


==Environments==
==Environments==
Line 36: Line 23:
You can help make Firefox 3 accessible to the broadest range of users possible by adding an environment to the above list.  If you can help with testing of products for those with mobility related disabilities or additional screen magnifiers, please [mailto:tkeenan@mozilla.com contact us].
You can help make Firefox 3 accessible to the broadest range of users possible by adding an environment to the above list.  If you can help with testing of products for those with mobility related disabilities or additional screen magnifiers, please [mailto:tkeenan@mozilla.com contact us].
==Looking Ahead==
==Looking Ahead==
Beta 1 of Firefox 3 will likely be released in early October.  By that time it's important that we are able to test in as many environments as possible.
Beta 1 of Firefox 3 will likely be released in early November.  By that time it's important that we are able to test in as many environments as possible.
The beta will be feature complete, so most of the UI should be landed by then.  That will be when we'll need diligent testers to help us out by using the beta in their daily browsing, as well as running the forthcoming BFTs and Litmus test cases.
The beta will be feature complete, so most of the UI should be landed by then.  That will be when we'll need diligent testers to help us out by using the beta in their daily browsing, as well as running the forthcoming BFTs and Litmus test cases.
<P> Final work is being done on the Accessibility Test Plan, and that will be our blueprint to test the UI of Firefox 3.  Testing page rendering is more complex, which is why we'd like you to use the beta as your primary browser.  That will be the best way to help us catch rendering bugs on specific websites.
<P> Final work is being done on the Accessibility Test Plan, and that will be our blueprint to test the UI of Firefox 3.  Testing page rendering is more complex, which is why we'd like you to use the beta as your primary browser.  That will be the best way to help us catch rendering bugs on specific websites.
40

edits