W3C home > Mailing lists > Public > public-bpwg-pro@w3.org > June 2008

mobileOK Pro revision

From: Manrique Lopez <manrique.lopez@fundacionctic.org>
Date: Tue, 17 Jun 2008 12:17:02 +0200
To: public-bpwg-pro@w3.org
Message-Id: <1213697822.6225.19.camel@bespin>

Hello everybody,

Since F2F agenda has changed and I am not 100% sure if I will be able to
stay on wednesday afternoon, I send some MOK PRO questions to discuss
about:

3.1 Test Scope
Perhaps a better definition about what tests should be applied to one
page or multiple? (perhaps indicate it in each test?)
Which pages should I take for a "multiple pages" test?

4.1 Access Keys
We have "primary navigation links" in the "interpretation" but
"navigation links and form controls" in the "procedure". Should it be
the same text in both sections?

4.3 Avoid Free Text
Take care about too big "finite number".

4.4 Background Image Readability
Testing contrast for "each color", is it practical in an image with
degraded colors? (machine testable, isn't it?)

Perhaps it would be better adding reference to WCAG 2.0 tests instead of
Ishihara in the examples.

4.6 Device Capabilities
Imagine a page with videos that, for me, doesn't have any sense for
mobile context, and it doesn't serve them in the mobile page version.
According with the test, it would fail, wouldn't it?

Wouldn't it be better 'testing' if there is an alternative suitable for
mobile context?

4.8 Limited
Very similar to 4.19 in definition but not same text about link ID.

Reading the test, can I link to "not mobile web-sites"? It seems not

4.9 Clarity
Maybe we could take some 'info' or resources from WCAG2.0 instead of
letting it so open as it is now.
References: http://www.w3.org/TR/WCAG20/#understandable

When will you fail this test?

4.12 Control Labeling
How can a machine (easily) test that the label does not describe the
purpose of the form control?
Perhaps not so 100% machine testable

Open issues: Are empty labels "" acceptable, if the meaning of the field
is made clear in some other fashion? 
Perhaps for search boxes or date entry boxes?

4.13 Control Position
What's the difference between first and third test?

4.17 Fonts
Adding a "tagcloud" as example of information based on font size could
help. I.e.: http://www.flickr.com/photos/tags/

4.19 Link Target ID
In the note BPWG "title" could be added to link ID

4.21 Navbar
Second tests is same than 4.7

4.22 Navigation
I don't know if testing texts are clear enough

4.25 Page Size Usable
Instead of "screen size", could it be better "screen length" to avoid
confussion.
Which "size" is the base for "3 screen sizes"? (see 4.36 TESTING
proposal)

4.26 Page Title
I think that second test may conflicts with third example

4.27 Provide Defaults
Perhpas, we should add a condition about "if any free data entry is
present"...  and a link to Avoid Free text tests

4.28 Scrolling
I am not sure how this tests work when "texts" are the elements that
make horizontal scrolling appears. How could we "resize texts"?

4.36 Testing
Procedure: define some capabilities and some values for each one based
in DDR Vocab. Specially:
- Display Width (needed perhaps for Scrolling tests)
- Display Height (needed perhaps for Limited tests)

This information could be provided in a "mobileOK Pro Tests
report" (does POWDER or EARL provide this kind of feature?).Something
like: 
Capabilities tested:
- Display height: 90, 240, 320
...

So:
- If display dimensions aren't in the list of "capabilities
tested" [FAIL]
- If number of values for each display capability is less than three
[FAIL]
- If all the values can't be tested both in devices and emulators [FAIL]

Editor note. Perhaps other values could be added to improve other tests
and made them more "repeatable":
- Display Color Depth (needed perhaps for Device Capabilities testing)
- Stylesheet Support (needed perhaps for Style Sheet Support testing)
- Image Format Support (needed perhaps for Device Capabilities testing)
- Script Support (needed perhaps for Device Capabilities testing)

4.38 Use of color
It says: "Excluding hyperlinks, does the page include any other blue or
purple text? If yes, [FAIL]"
Then, I should put the links in blue or purple, shouldn't I?

Shouldn't it be better something like:
Excluding hyperlinks, does the page include any other text with same
color than hyperlinks? If yes, [FAIL]

Best regards,
-- 
José Manrique López de la Fuente <manrique.lopez@fundacionctic.org>
Área de Tecnología Fundación CTIC
Web: http://www.fundacionctic.org
Tel: (+34) 984 29 12 12
Parque Científico Tecnológico de Gijón
Edificio Centros Tecnológicos
Cabueñes s/n
33203 GIJÓN - ASTURIAS - ESPAÑA
#Antes de imprimir este e-mail piense bien si es necesario hacerlo: El
medioambiente es cosa de todos.
Received on Tuesday, 17 June 2008 10:17:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 17 June 2008 10:17:47 GMT