Hi James and Justin, Your suggestions make complete sense. I am adding the changes for Voiceover testing within the tests. I am adding a section on 'Using the iPhone with VoiceOver' in the Getting Started page.
Thanks. Sam On Fri, Feb 12, 2010 at 3:38 PM, Justin Obara <[email protected]>wrote: > Hi James, > > I think it makes sense to reuse where possible. > > Since we want to make sure that users making use of VoiceOver are able to > have the same experience as those not, I think it best to have them sit side > by side, so that we make sure that they are always in sync. Also this would > reduce the repetition throughout the wiki. > > I think you should probably have a section for instructions on how to > launch the application. That would include instructions on how to have save > it as a home screen app or to launch in safari, and the appropriate url. > (you may have this already). > > Then the rest of the code should be fairly similar, with some deviations > for expected results for the VoiceOver and possibly some procedural > difference as well. For example we want to attempt to follow the same flow > that a voiceover user would. so for example you would want someone to just > activate VoiceOver and then double click everything... they should be using > the VoiceOver navigation semantics. Actually this could probably be included > in an instructions section for running this plan with VoiceOver. > > Does that make sense? > > I'm sort of in a flurry with this engage release so if I've been totally > incoherent please let me know. > > > Thanks > Justin > > > On 2010-02-12, at 3:26 PM, James William Yoon wrote: > > Hi Sam, > > I took a read through the the QA test plans for VoiceOver you wrote. It > seems to me that, with one or two exceptions, all the tests are > identical--even with the one or two exceptions, the difference is often just > an extra line in the procedure indicating that the test should be run > directly in Safari. > > I wonder if it would make better sense simply to layer the differences > between the procedure and expected results of the VO tests on top of the > existing non-VO tests, and highlight those differences (e.g., in bold make a > note that says "For VO: ..."). > > For instance, > > Test 1: Home page load > Procedure: > 1. Load the application and tap on "English" at the language selection > screen. (*For VO: Load the web app by opening the page in Safari."*) > 2. *For VO: Have VoiveOver read through the page.* > Expected results: > ... (the same for both non-VO and VO) > > Justin, do you have any thoughts or suggestions? (Justin was the one who > wrote the other Fluid QA test plans) > > Cheers, > James > > On Fri, Feb 12, 2010 at 12:03 PM, Sambhavi Chandrashekar < > [email protected]> wrote: > >> Hi Alison & James, >> >> Please take a look at the first three items under Fluid Engage 0.3 at >> http://wiki.fluidproject.org/display/fluid/Testing+Fluid+Components where >> I have replicated and modified (at the end of each section) tests for use of >> Engage with VoiceOver. Let me have your feedback whether I could continue >> similarly for the rest. >> >> Alison, thank you so much for your assistance. Are you available for a >> quick chat any time today? >> >> Sam >> >> >> On Thu, Feb 11, 2010 at 2:39 PM, Alison Benjamin < >> [email protected]> wrote: >> >>> Please let me know if I can be of any assistance with this. >>> >>> Thanks, >>> Alison >>> >>> On Feb 11, 2010, at 12:14 PM, Sambhavi Chandrashekar wrote: >>> >>> Thank you, James. I will look into that and check with what I have. Will >>> email you for assistance with integration. >>> >>> Sam >>> >>> On Thu, Feb 11, 2010 at 12:10 PM, James William Yoon < >>> [email protected]> wrote: >>> >>>> Hi Sam, >>>> >>>> Tona and I have completed writing our first draft of the QA test plans, >>>> found under "Fluid Engage 0.3" on the right side here: >>>> http://wiki.fluidproject.org/display/fluid/Testing+Fluid+Components >>>> >>>> Let us know where you're at with yours, and how we can assist you in >>>> integrating the accessibility test plans into there. (QA testing begins on >>>> Tuesday) >>>> >>>> Cheers, >>>> James >>>> >>>> >>>> On Thu, Feb 4, 2010 at 1:50 PM, Sambhavi Chandrashekar < >>>> [email protected]> wrote: >>>> >>>>> Hi James, >>>>> >>>>> I will join you both on Wednesday next (Feb 10th). Will mail you on Wed >>>>> morning about what I get done up to that point. We can then discuss how to >>>>> align/integrate the tests with/into the main QA plan. >>>>> >>>>> Sam >>>>> >>>>> On Thu, Feb 4, 2010 at 11:56 AM, James William Yoon < >>>>> [email protected]> wrote: >>>>> >>>>>> I'm glad you brought this up. I had just pinged Justin about this >>>>>> minutes ago. Tona and I are more than happy to lend our assistance in >>>>>> writing the QA test plans. We'll work on this early next week. >>>>>> >>>>>> Anyone else wanting to help us write the test plans and/or gain some >>>>>> experience writing them is welcome to join us! >>>>>> >>>>>> Cheers, >>>>>> James >>>>>> >>>>>> >>>>>> On Thu, Feb 4, 2010 at 11:25 AM, Colin Clark >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> Hi James and Tona, >>>>>>> >>>>>>> I'm wondering if you might be able to lend a hand with preparations >>>>>>> for Engage 0.3 quality assurance testing. Justin is pretty heads-down >>>>>>> with >>>>>>> development tasks, so I don't think he's going to have a chance to >>>>>>> create >>>>>>> all of the test plans we need to have in place before we start the QA >>>>>>> phase >>>>>>> on February 16. >>>>>>> >>>>>>> I'm wondering if you two are willing to help create these test plans, >>>>>>> with some advice and moral support from Justin and crew as needed? >>>>>>> Ideally, >>>>>>> we'll try to get these finished by late next week so we have time to >>>>>>> refine >>>>>>> them before QA actually starts. >>>>>>> >>>>>>> Sam is working on a screenreader-specific QA test plan as well, so >>>>>>> it'd be worth syncing up everyone on this as well. >>>>>>> >>>>>>> Let me know what you think, >>>>>>> >>>>>>> Colin >>>>>>> >>>>>>> --- >>>>>>> Colin Clark >>>>>>> Technical Lead, Fluid Project >>>>>>> http://fluidproject.org >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________________ >>>>>> fluid-work mailing list - [email protected] >>>>>> To unsubscribe, change settings or access archives, >>>>>> see http://fluidproject.org/mailman/listinfo/fluid-work >>>>>> >>>>>> >>>>> >>>> >>> _______________________________________________________ >>> fluid-work mailing list - [email protected] >>> To unsubscribe, change settings or access archives, >>> see http://fluidproject.org/mailman/listinfo/fluid-work >>> >>> >>> >> > _______________________________________________________ > fluid-work mailing list - [email protected] > To unsubscribe, change settings or access archives, > see http://fluidproject.org/mailman/listinfo/fluid-work > > >
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
