Hi Justin,
Much better now, thanks. One more thing I just noticed, not a big
deal, but technically the cells in the first column should be marked
as th and not td as they are row headers.
HTH,
Everett
Follow me on Twitter
http://twitter.com/ezufelt
View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt
On 2010-02-12, at 1:47 PM, Justin Obara wrote:
Hi Everett,
Thanks for the quick reply. I think I have got that all fixed up in
the browser support chart.
If you have time to look at it again, please let me know if it isn't
working.
Thanks
Justin
On 2010-02-12, at 1:02 PM, E.J. Zufelt wrote:
Hi Justin,
On 2010-02-12, at 12:48 PM, Justin Obara wrote:
Hi Everett,
Thanks for spotting this.
Basically those are generated by a macro that transforms (/) into
an image of a check mark. It does't seem that I have control over
adding the alt text.
The presence of the image is to indicate that we do test on that
platform.
Here are some alternatives I could do.
1) copy the image and reference it as other wiki images, which
should allow me to add alt text.
2) use some other text or asci symbol
* I think that the order of preference would be the order you have
listed above. I can't think of a commonly used alternative at the
moment.
Thanks,
Everett
3) something else...
Any preference or recommendations.
Thanks
Justin
On 2010-02-12, at 12:25 PM, E.J. Zufelt wrote:
Good morning,
I took a look at the page with the table containing the browser
support matrix. I notice that the images have a null alt
attribute.
E.g. <img class="emoticon" src="
/images/icons/emoticons/check.gif"
height="16" width="16" align="absmiddle" alt="" border="0"/>
Thanks,
Everett
Follow me on Twitter
http://twitter.com/ezufelt
View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt
On 2010-02-12, at 12:03 PM, Sambhavi Chandrashekar 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
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
