index.html
86.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>W3C mobileOK Basic Tests 1.0</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
p.pseudocode1 {
margin-left: 0.2in;
margin-right: 0.1in;
}
p.pseudocode2 {
margin-left: 0.4in;
margin-right: 0.1in;
}
p.pseudocode3 {
margin-left: 0.6in;
margin-right: 0.1in;
}
p.pseudocode4 {
margin-left: 0.8in;
margin-right: 0.1in;
}
p.pseudocode5 {
margin-left: 1.0in;
margin-right: 0.1in;
}
p.pseudocode6 {
margin-left: 1.2in;
margin-right: 0.1in;
}
.ednote {
border: 1px dashed black;
background-color: #FFcccc;
color: inherit;
}
.kw {
font-weight: bold;
border-bottom: 1px dashed black;
}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-REC.css"/></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"/></a></p>
<h1><a name="title" id="title"/>W3C mobileOK Basic Tests 1.0</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>W3C Recommendation 08 December 2008</h2><dl><dt>This version:</dt><dd>
<a href="http://www.w3.org/TR/2008/REC-mobileOK-basic10-tests-20081208/">http://www.w3.org/TR/2008/REC-mobileOK-basic10-tests-20081208/</a>
</dd><dt>Latest version:</dt><dd>
<a href="http://www.w3.org/TR/mobileOK-basic10-tests/">http://www.w3.org/TR/mobileOK-basic10-tests/</a>
</dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2008/PR-mobileOK-basic10-tests-20081103/">http://www.w3.org/TR/2008/PR-mobileOK-basic10-tests-20081103/</a>
</dd>
<dt>Editors:</dt><dd>Sean Owen, Google</dd><dd>Jo Rabin, dotMobi (and before at Segala)</dd></dl>
<p>Please refer to the <a href="http://www.w3.org/2008/12/mobileok-errata.html"><strong>errata</strong></a> for this document, which may include some normative corrections.</p>
<p>See also <a
href="http://www.w3.org/2003/03/Translations/byTechnology?technology=mobileOK-basic10-tests"><strong>translations</strong></a>.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2008 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>This document defines the tests that provide the basis for making a claim of W3C®
mobileOK™ Basic conformance and are based on W3C Mobile Web Best Practices <a href="#BestPractices">[Best Practices]</a>. The details of how to claim mobileOK conformance will be described separately. Providers of content which passes the tests have taken some steps to
provide a <a href="http://www.w3.org/TR/2003/WD-di-gloss-20030825/#def-functional-user-experience">functional user experience</a> for
users of <em>basic</em> mobile devices whose capabilities at least match those
of the <a href="http://www.w3.org/TR/mobile-bp/#ddc">Default Delivery Context</a> (DDC).</p><p>mobileOK Basic primarily assesses basic usability, efficiency and interoperability.
It does not address the important goal of assessing whether users of more advanced
devices enjoy a richer user experience than is possible using the DDC.</p></div><div>
<h2><a name="status" id="status"/>Status of this Document</h2>
<p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
<p>This document was developed by the <a href="http://www.w3.org/2005/MWI/BPWG/">Mobile Web Best Practices Working Group</a> as part of the <a href="http://www.w3.org/2005/MWI/Activity">Mobile Web Initiative</a>.</p>
<p>Please see the Working Group's <a href="http://www.w3.org/2008/06/mobileok-implementation-report">implementation report</a>. A complete <a href="diff.html">list of the editorial changes</a> since the previous version of this document is available.</p>
<p>Please send comments about this document to <a href="mailto:public-bpwg-comments@w3.org">public-bpwg-comments@w3.org</a> (with <a href="http://lists.w3.org/Archives/Public/public-bpwg-comments/">public archive</a>).</p>
<p>This document defines machine-verifiable tests, based on the W3C Mobile Web Best Practices [<a href="#BestPractices">Best Practices</a>]. Although content authors are not expected to use this document directly, participants of the Working Group expect tools that implement the tests defined in this document to greatly improve the authoring of content that addresses the browsing experience of users on a broad range of devices.</p>
<p>This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</p>
<p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/37584/status"> public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p>
</div>
<div class="toc">
<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#overview">Introduction</a><br/>
1.1 <a href="#scope">Scope</a><br/>
1.1.1 <a href="#relationship_to_best_practices">Relationship to Best Practices</a><br/>
1.1.2 <a href="#out_of_scope">Out of Scope</a><br/>
1.1.3 <a href="#beyond_mobileok">Beyond mobileOK</a><br/>
1.2 <a href="#applicability">Applicability</a><br/>
1.3 <a href="#claiming_mobileok_conformance">Claiming mobileOK conformance</a><br/>
2 <a href="#about_the_tests">Conformance</a><br/>
2.1 <a href="#Use_of_RFC2119">Use of Terms must, should etc.</a><br/>
2.2 <a href="#testing_validity">Validity of the Tests</a><br/>
2.3 <a href="#testing_outcomes">Testing Outcomes</a><br/>
2.4 <a href="#conduct_of_tests">Conduct of Tests</a><br/>
2.4.1 <a href="#order_of_tests">Order of Tests</a><br/>
2.4.2 <a href="#https">HTTPS</a><br/>
2.4.3 <a href="#http_request">HTTP Request</a><br/>
2.4.4 <a href="#http_response">HTTP Response</a><br/>
2.4.5 <a href="#meta_http_equiv">Meta http-equiv Elements</a><br/>
2.4.6 <a href="#handheld_css_style_rule_definition">CSS Style</a><br/>
2.4.7 <a href="#included_resources">Included Resources</a><br/>
2.4.8 <a href="#linked_resources">Linked Resources</a><br/>
2.4.9 <a href="#validity">Validity</a><br/>
2.4.10 <a href="#whitespace">White Space</a><br/>
3 <a href="#mobileok_basic_tests">mobileOK Basic Tests</a><br/>
3.1 <a href="#AUTO_REFRESH">
AUTO_REFRESH and REDIRECTION</a><br/>
3.2 <a href="#CACHING">
CACHING
</a><br/>
3.3 <a href="#CHARACTER_ENCODING_SUPPORT">
CHARACTER_ENCODING_SUPPORT
and CHARACTER_ENCODING_USE</a><br/>
3.4 <a href="#CONTENT_FORMAT_SUPPORT">
CONTENT_FORMAT_SUPPORT and
VALID_MARKUP</a><br/>
3.5 <a href="#DEFAULT_INPUT_MODE">
DEFAULT_INPUT_MODE
</a><br/>
3.6 <a href="#EXTERNAL_RESOURCES">
EXTERNAL_RESOURCES
</a><br/>
3.7 <a href="#GRAPHICS_FOR_SPACING">
GRAPHICS_FOR_SPACING
</a><br/>
3.8 <a href="#IMAGE_MAPS">
IMAGE_MAPS
</a><br/>
3.9 <a href="#IMAGES_SPECIFY_SIZE">
IMAGES_RESIZING and IMAGES_SPECIFY_SIZE</a><br/>
3.10 <a href="#LINK_TARGET_FORMAT">
LINK_TARGET_FORMAT
</a><br/>
3.11 <a href="#MEASURES">
MEASURES
</a><br/>
3.12 <a href="#MINIMIZE">
MINIMIZE
</a><br/>
3.13 <a href="#NO_FRAMES">
NO_FRAMES
</a><br/>
3.14 <a href="#NON_TEXT_ALTERNATIVES">
NON-TEXT_ALTERNATIVES
</a><br/>
3.15 <a href="#OBJECTS_OR_SCRIPT">
OBJECTS_OR_SCRIPT
</a><br/>
3.15.1 <a href="#ObjectElementProcessingRule">Object Element Processing Rule</a><br/>
3.16 <a href="#PAGE_SIZE_LIMIT">
PAGE_SIZE_LIMIT
</a><br/>
3.17 <a href="#PAGE_TITLE">
PAGE_TITLE
</a><br/>
3.18 <a href="#POP_UPS">
POP_UPS
</a><br/>
3.19 <a href="#PROVIDE_DEFAULTS">
PROVIDE_DEFAULTS
</a><br/>
3.20 <a href="#STYLE_SHEETS_SUPPORT">
STYLE_SHEETS_SUPPORT
</a><br/>
3.21 <a href="#STYLE_SHEETS_USE">
STYLE_SHEETS_USE
</a><br/>
3.22 <a href="#TABLES_ALTERNATIVES">
TABLES_ALTERNATIVES
</a><br/>
3.23 <a href="#TABLES_LAYOUT">
TABLES_LAYOUT
</a><br/>
3.24 <a href="#TABLES_NESTED">
TABLES_NESTED
</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#acknowledgments">Acknowledgments</a> (Non-Normative)<br/>
B <a href="#references">References</a> (Non-Normative)<br/>
C <a href="#bp_test_reference">Relationship between Best Practices and mobileOK Tests</a> (Non-Normative)<br/>
</p></div><hr/><div class="body"><div class="div1">
<h2><a name="overview" id="overview"/>1 Introduction</h2><p>mobileOK Basic is a scheme for assessing whether Web resources (Web content) can be
delivered in a manner that is conformant with Mobile Web Best Practices <a href="#BestPractices">[Best Practices]</a> to a simple and largely hypothetical mobile user agent,
the <a href="http://www.w3.org/TR/mobile-bp/#ddc">Default Delivery Context</a>.</p><p>This document describes W3C mobileOK Basic tests for delivered content, and describes
how to emulate the DDC when requesting that content.</p><p>The intention of mobileOK is to help catalyze development of Web content that
provides a <a href="http://www.w3.org/TR/di-gloss/#def-functional-user-experience">functional user experience</a> in a
mobile context. It is not a test for browsers, user agents or mobile devices, and is
not intended to imply anything about the way these should behave.</p><p>mobileOK does not imply endorsement or suitability of content. For example, it must
not be assumed that <span>a claim that a resource is mobileOK conformant implies
that it</span> is of higher informational value, is more reliable, more
trustworthy or is <span>more</span> appropriate for children <span>than any
other resource</span>.</p><div class="div2">
<h3><a name="scope" id="scope"/>1.1 Scope</h3><div class="div3">
<h4><a name="relationship_to_best_practices" id="relationship_to_best_practices"/>1.1.1 Relationship to Best Practices</h4><p>mobileOK Basic tests are based on a limited subset of the Mobile Web Best
Practices. Their outcome is machine-verifiable, hence claims of mobileOK
Basic conformance are easy to check.</p><p>Content passing the tests demonstrates that the content provider has taken
<em>basic</em> steps to provide a <a href="http://www.w3.org/TR/di-gloss/#def-functional-user-experience">functional experience</a> for
mobile users. </p><p>mobileOK Basic conformance should be considered only a first step towards
building a <a href="http://www.w3.org/TR/di-gloss/#def-harmonized-user-experience">harmonized experience</a> for
mobile users. Conformance merely demonstrates that a basic experience is
available, interoperable with a large number of mobile devices. mobileOK
Basic conformance says nothing about richer, more sophisticated, experiences
that may be available, nor does it say anything about whether other
guidelines for development of Web content (such as <a href="#WCAG">[WCAG 1.0]</a>)
have been followed.</p></div><div class="div3">
<h4><a name="out_of_scope" id="out_of_scope"/>1.1.2 Out of Scope</h4><p>Some Best Practices, like <a href="http://www.w3.org/TR/mobile-bp/#TESTING">TESTING</a>, are advisable
but do not meaningfully translate into concrete tests.</p><p>The tests assess whether the content <em>can</em> be provided in a way
that achieves basic usability, efficiency, and interoperability with mobile
devices. The tests should not be understood to assess thoroughly whether the
content has been well-designed for mobile devices.</p></div><div class="div3">
<h4><a name="beyond_mobileok" id="beyond_mobileok"/>1.1.3 Beyond mobileOK</h4><p>The Best Practices, and hence the tests, are not promoted as guidance for
achieving the optimal user experience. The capabilities of many devices
exceed those defined by the DDC. It will often be possible, and generally
desirable, to provide an experience designed to take advantage of the extra
capabilities. </p><p>Content providers should provide an experience that is mobileOK Basic conformant to
ensure a basic level of interoperability. Providers are encouraged to
provide enhanced experiences as well when these are appropriate to their
application and devices that are accessing them. </p></div></div><div class="div2">
<h3><a name="applicability" id="applicability"/>1.2 Applicability</h3><p>The tests apply to a URI. Passing the tests means that when accessed as described
in <a href="#http_request"><span class="specref">2.4.3 HTTP Request</span></a>, resolving a URI will result in
<span>mobileOK Basic</span> conformant content that is delivered in a
<span>mobileOK Basic</span> conformant manner.</p><p>That is, the tests do not apply solely to content or document instances. Many
Best Practices relate not just to the document (e.g. <a href="http://www.w3.org/TR/mobile-bp/#VALID_MARKUP">VALID_MARKUP</a>), but to how it is delivered to a
mobile device (e.g. <a href="http://www.w3.org/TR/mobile-bp/#CACHING">CACHING</a>).</p><p>mobileOK Basic says nothing about what may be delivered to non-mobile
devices.</p></div><div class="div2">
<h3><a name="claiming_mobileok_conformance" id="claiming_mobileok_conformance"/>1.3 Claiming mobileOK conformance</h3><p>A standard mechanism will be defined that allows content providers to claim that
a URI or group of URIs, such as a Web site, conforms to mobileOK Basic. It will be possible to make claims in a
machine-processable form. It will also be possible to notify end users of the
presence of the claim by means of a human-readable mark.</p><p>The details of the mechanism for claiming mobileOK conformance will be described
separately.</p></div></div><div class="div1">
<h2><a name="about_the_tests" id="about_the_tests"/>2 Conformance</h2><div class="div2">
<h3><a name="Use_of_RFC2119" id="Use_of_RFC2119"/>2.1 Use of Terms must, should etc.</h3><p>Where terms are used with the meanings defined in <a href="#RFC2119">[RFC 2119]</a> they
are highlighted in the text e.g. <strong>must</strong>.</p></div><div class="div2">
<h3><a name="testing_validity" id="testing_validity"/>2.2 Validity of the Tests</h3><p>mobileOK tests are only meaningful when the URI under test resolves to HTML
content delivered over HTTP.</p></div><div class="div2">
<h3><a name="testing_outcomes" id="testing_outcomes"/>2.3 Testing Outcomes</h3><p>Individual tests may result in <b>PASS</b> or <b>FAIL</b>. <b>PASS</b> is
required from all tests in order to claim mobileOK Basic conformance. In any test,
<b>PASS</b> is achieved if and only if there are no <b>FAIL</b>s. No
specific <b>PASS</b> outcome is defined for any test.</p><p>Tests may also generate a number of informative <b>warn</b>ings which do not
affect whether a test has <b>PASS</b>ed or not. A <b>warn</b>ing may
indicate that it could not be conclusively determined whether the content under
test conforms to a Best Practice (and thus does not <b>FAIL</b>), or may
indicate that the content under test is close to violating a Best Practice.</p></div><div class="div2">
<h3><a name="conduct_of_tests" id="conduct_of_tests"/>2.4 Conduct of Tests</h3><div class="div3">
<h4><a name="order_of_tests" id="order_of_tests"/>2.4.1 Order of Tests</h4><p>mobileOK Basic does not prescribe the order in which tests are to be carried
out as they may be executed independently. Some tests have been designed to
assess aspects of the content that are disallowed by other tests; this is
deliberate and is intended to allow testing environments to provide as much
information as possible.</p><p>For example the test for <a href="#STYLE_SHEETS_USE"><span class="specref">3.21
STYLE_SHEETS_USE
</span></a> points out that
style sheets should be used in preference to markup elements such as
<code>center</code>, even though the <code>center</code> element is also
disallowed by the test for <a href="#CONTENT_FORMAT_SUPPORT"><span class="specref">3.4
CONTENT_FORMAT_SUPPORT and
VALID_MARKUP</span></a>.</p><p>Creators of implementations of the tests described in this document are
encouraged to provide as much information as possible to users of their
implementations. Where possible they should not stop on <b>FAIL</b> and
specifically they <strong>should</strong>:</p><ul><li><p>Provide information about the cause of warning or failure (each
<b>warn</b> and <b>FAIL</b> is individually identified);</p></li><li><p>Continue individual tests as far as is possible;</p></li><li><p>Carry out as many tests as is reasonable.</p></li></ul></div><div class="div3">
<h4><a name="https" id="https"/>2.4.2 HTTPS</h4><div class="note"><p class="prefix"><b>Note:</b></p><p>Arbitrary root certificates (including self-signed certificates) should
be regarded as trusted.</p></div><div class="exampleOuter"><p class="pseudocode1">When resolving a URI, if the URI has the scheme <code>https</code>:</p><p class="pseudocode2">If the certificate presented does not match the
requested URI, <span class="kw" id="https-1" title="https-1">FAIL</span></p><p class="pseudocode2">If the certificate has expired, or is not yet valid, <span class="kw" id="https-2" title="https-2">warn</span></p><p class="pseudocode2">If certificate validation otherwise fails, <span class="kw" id="https-3" title="https-3">FAIL</span></p></div></div><div class="div3">
<h4><a name="http_request" id="http_request"/>2.4.3 HTTP Request</h4><p>The following HTTP request headers inform the server that it should deliver
content that is compatible with the <a href="http://www.w3.org/TR/mobile-bp/#ddc">Default Delivery Context</a>.</p><ul><li><p>Use the HTTP <code>GET</code> method when making requests, except for
<a href="#LINK_TARGET_FORMAT"><span class="specref">3.10
LINK_TARGET_FORMAT
</span></a> where the <code>HEAD</code>
method may be used (See <a href="#linked_resources"><span class="specref">2.4.8 Linked Resources</span></a> for a
discussion of the <code>POST</code> method).</p></li><li><p>Include a <code>User-Agent</code> header which starts exactly as follows (indicating the Default Delivery Context, and which <strong>may</strong> be extended in accordance with <a href="#HTTP">[RFC 2616]</a> <a href="http://tools.ietf.org/html/rfc2616#section-14.43">Section 14.43, User-Agent Header</a>) :</p><div class="exampleInner"><pre>User-Agent: W3C-mobileOK/DDC-1.0 (see http://www.w3.org/2006/07/mobileok-ddc)</pre></div></li><li><p>Include an <code>Accept</code> header indicating that Internet media
types understood by the Default Delivery Context are accepted by
sending exactly this header:</p><div class="exampleInner"><pre>Accept: application/xhtml+xml,text/html;q=0.1,application/vnd.wap.xhtml+xml;q=0.1,text/css,image/jpeg,image/gif</pre></div></li><li><p>Include an <code>Accept-Charset</code> header indicating that only
UTF-8 is accepted by sending exactly this header:</p><div class="exampleInner"><pre>Accept-Charset: UTF-8</pre></div></li><li><p>Do not include cookie related headers.</p></li><li><p>Include authentication information if required (see <a href="#http_response"><span class="specref">2.4.4 HTTP Response</span></a>). Once authentication information has
been included in a request, subsequent requests for the same realm
<strong>must</strong> include authentication information as
described in <a href="http://tools.ietf.org/html/rfc2617#section-2">Section 2</a> and
under "domain" in <a href="http://tools.ietf.org/html/rfc2617#section-3.2.1">Section 3.2.1</a> of
<a href="#RFC2617">[RFC 2617]</a>.</p></li><li><p>Implementations <strong>must</strong> support URIs with both
<code>http</code> and <code>https</code> scheme components.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>As noted under <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a> and <a href="#linked_resources"><span class="specref">2.4.8 Linked Resources</span></a> the URIs that are relevant to
mobileOK are those that, when represented in an absolute form,
have either the <code>http</code> or the <code>https</code>
scheme. Requests <strong>should not</strong> be made for URIs
with schemes other than <code>http</code> and
<code>https</code>.</p></div></li></ul></div><div class="div3">
<h4><a name="http_response" id="http_response"/>2.4.4 HTTP Response</h4><div class="note"><p class="prefix"><b>Note:</b></p><p>Implementations <strong>must</strong> support basic and digest
authentication.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Below, note that a 404 or 5xx response for the resource under test does
not result in a <b>FAIL</b> in order to allow for the possibility of
testing an application's error page.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>If the test below results in a <b>FAIL</b>, do not proceed with further
tests. Otherwise, the mobileOK Basic Tests should be applied to the
content.</p></div><div class="exampleOuter"><p class="pseudocode1">If an HTTP request does not result in a valid HTTP
response (because of network-level error, DNS resolution error, or
non-HTTP response), <span class="kw" id="http_response-1" title="http_response-1">FAIL</span></p><p class="pseudocode1">If the HTTP status indicates redirection (status code
3xx):</p><p class="pseudocode2">Do not carry out tests on the response</p><p class="pseudocode2">If the response relates to a request for the resource
under test, or any of its Included Resources (see <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a>):</p><p class="pseudocode3">Include the size of the response in the "total size"
as described under <a href="#PAGE_SIZE_LIMIT"><span class="specref">3.16
PAGE_SIZE_LIMIT
</span></a></p><p class="pseudocode3">Include this response under the count as described under
<a href="#EXTERNAL_RESOURCES"><span class="specref">3.6
EXTERNAL_RESOURCES
</span></a></p><p class="pseudocode2">If there is no HTTP <code>Location</code> header, <span class="kw" id="http_response-4" title="http_response-4">FAIL</span>.</p><p class="pseudocode2">If the URI identified by the HTTP
<code>Location</code> header is a relative URI, create an absolute URI
by combining the value of the <code>Location</code> header with the
absolute URI of the request to which this is a response, <span class="kw" id="http_response-5" title="http_response-5">warn</span></p><p class="pseudocode2">If the resulting URI is not a URI with the scheme
<code>http</code> or <code>https</code>, <span class="kw" id="http_response-6" title="http_response-6">FAIL</span>.</p><p class="pseudocode2">Re-request the resource using the URI formulated
above.</p><p class="pseudocode1">If the HTTP status indicates that authentication is
required (e.g. status code 401):</p><p class="pseudocode2">If the response relates to a request for the resource
under test, or any of its Included Resources (see <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a>):</p><p class="pseudocode3">If authentication information was supplied in the HTTP
request (i.e. authentication failed) or if no authentication information is available, <span class="kw" id="http_response-7" title="http_response-7">FAIL</span></p><p class="pseudocode3">Carry out tests on the response</p><p class="pseudocode3">Include the size of the response in the "total size"
as described under <a href="#PAGE_SIZE_LIMIT"><span class="specref">3.16
PAGE_SIZE_LIMIT
</span></a></p><p class="pseudocode3">Include this response under the count as described under
<a href="#EXTERNAL_RESOURCES"><span class="specref">3.6
EXTERNAL_RESOURCES
</span></a></p><p class="pseudocode3">Re-request the resource using authentication
information</p><p class="pseudocode2">If the response relates to a request for a linked
resource (see <a href="#linked_resources"><span class="specref">2.4.8 Linked Resources</span></a>):</p><p class="pseudocode3">Continue with the test (see <a href="#LINK_TARGET_FORMAT"><span class="specref">3.10
LINK_TARGET_FORMAT
</span></a>, i.e. do not re-request the resource
with authentication information), <span class="kw" id="http_response-12" title="http_response-12">warn</span></p><p class="pseudocode1">If the HTTP status code is 404 or 5xx</p><p class="pseudocode2">If the response relates to a request for the resource
under test, continue with tests on the response and <span class="kw" id="http_response-8" title="http_response-8">warn</span></p><p class="pseudocode2">If the response relates to a request for a linked
resource (see <a href="#linked_resources"><span class="specref">2.4.8 Linked Resources</span></a>), continue with the
test (see <a href="#LINK_TARGET_FORMAT"><span class="specref">3.10
LINK_TARGET_FORMAT
</span></a>) and <span class="kw" id="http_response-9" title="http_response-9">warn</span></p><p class="pseudocode2">Otherwise (i.e. for Included Resources), <span class="kw" id="http_response-10" title="http_response-10">FAIL</span></p><p class="pseudocode1">If the HTTP status represents failure (4xx), other
than 404, a request for authentication (e.g. 401) or a 406 when carrying out the <a href="#ObjectElementProcessingRule"><span class="specref">3.15.1 Object Element Processing Rule</span></a>, <span class="kw" id="http_response-11" title="http_response-11">FAIL</span></p></div></div><div class="div3">
<h4><a name="meta_http_equiv" id="meta_http_equiv"/>2.4.5 Meta http-equiv Elements</h4><p>Documents can include <code>meta</code> elements with an
<code>http-equiv</code> attribute; these are sometimes considered
substitutes for HTTP response headers.</p><p>mobileOK Basic test implementations <b>must</b> ignore values specified in
such elements, aside from the following:</p><ul><li><p>The <code>Refresh</code> header as specified in <a href="#AUTO_REFRESH"><span class="specref">3.1
AUTO_REFRESH and REDIRECTION</span></a></p></li><li><p>The <code>Content-Type</code> header as specified in <a href="#CHARACTER_ENCODING_SUPPORT"><span class="specref">3.3
CHARACTER_ENCODING_SUPPORT
and CHARACTER_ENCODING_USE</span></a></p></li><li><p>The <code>Cache-Control</code> header as specified in <a href="#CACHING"><span class="specref">3.2
CACHING
</span></a></p></li><li><p>Check for consistency with HTTP headers, as follows:</p><div class="exampleOuter"><p class="pseudocode1">For each <code>meta</code> element with an
<code>http-equiv</code> attribute:</p><p class="pseudocode2">If a matching HTTP response header does not
exist, <span class="kw" id="meta_http_equiv-1" title="meta_http_equiv-1">warn</span></p><p class="pseudocode2">If a matching HTTP response header exists but
its value differs from the <code>content</code> attribute value,
<span class="kw" id="meta_http_equiv-2" title="meta_http_equiv-2">warn</span></p></div></li></ul></div><div class="div3">
<h4><a name="handheld_css_style_rule_definition" id="handheld_css_style_rule_definition"/>2.4.6 CSS Style</h4><p>Some tests refer to "CSS Style" information. Assemble the
CSS Style by using the contents of:</p><ul><li><p>the <code>style</code> attribute of any element (use of the
<code>style</code> attribute is deprecated in XHTML Basic 1.1
<a href="#XHTMLBasic11">[XHTML Basic 1.1]</a>)</p></li><li><p>
<code>style</code> elements whose <code>type</code> attribute is
"text/css", and whose <code>media</code> attribute
is either not present or is present and contains values
"all" or "handheld"
(case-insensitive).</p></li><li><p>resources linked via <code>link</code> elements and
<code>xml-stylesheet</code> processing instructions, where:</p><ul><li><p>the <code>rel</code> attribute contains
"stylesheet" but not
"alternate" (case-insensitive)</p></li><li><p>the <code>charset</code> attribute is either not present or
is present with value "UTF-8"
(case-insensitive)</p></li><li><p>the <code>type</code> attribute is either not present or is
present with value "text/css"</p></li><li><p>the <code>media</code> attribute is either not present or is
present and contains value "all" or
"handheld" (case-insensitive).</p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>In the case of <code>xml-stylesheet</code> processing
instructions, <em>attribute</em> in this section refers to
<em>pseudo-attribute</em>.</p></div></li><li><p>resources linked by CSS <code>@import</code> at-rules whose
presentation media list is either not present or is present
and contains the value "all" or
"handheld"</p></li></ul><p>In the course of assembling the CSS Style use only those CSS rulesets that
are not restricted as to their presentation media type or whose presentation media type
list contains "handheld" or
"all".</p></div><div class="div3">
<h4><a name="included_resources" id="included_resources"/>2.4.7 Included Resources</h4><p>Some tests refer to Included Resources, which are resources
external to the resource being tested and yet vital to rendering that
resource and whose URI has the "http" or
"https" scheme, when represented in an absolute form.
Examples include image and style sheet resources.</p><p>When retrieving resources, caching directives should be observed. Multiple
references to cached resources are counted only once in regard of page
weight (see <a href="#PAGE_SIZE_LIMIT"><span class="specref">3.16
PAGE_SIZE_LIMIT
</span></a>) and resource count (see
<a href="#EXTERNAL_RESOURCES"><span class="specref">3.6
EXTERNAL_RESOURCES
</span></a>).</p><p>Included Resources are defined as those that are referenced by the following:</p><ul><li><p>the <code>src</code> attribute of <code>img</code> elements</p></li><li><p>the <code>data</code> attribute of <code>object</code> elements (see
notes below)</p></li><li><p>the <code>href</code> attribute of <code>link</code> elements and
<code>xml-stylesheet</code> processing instructions as defined
in <a href="#handheld_css_style_rule_definition"><span class="specref">2.4.6 CSS Style</span></a>
</p></li><li><p>images included by <code>background-image</code> and
<code>list-style-image</code> properties in the CSS Style (see
<a href="#handheld_css_style_rule_definition"><span class="specref">2.4.6 CSS Style</span></a>)</p></li><li><p>
<code>@import</code> directives in the CSS Style - providing they
are unqualified as to presentation media type or qualified by
presentation media type "handheld" or
"all" (case-insensitive) as defined in <a href="#handheld_css_style_rule_definition"><span class="specref">2.4.6 CSS Style</span></a></p></li></ul><div class="note"><p class="prefix"><b>Note:</b></p><p>In some circumstances <code>object</code> elements may act as synonyms
for other elements such as <code>img</code> and <code>iframe</code>. In
these cases it is noted in the relevant section when to regard object
elements as equivalents for other elements.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Resources that are retrieved as references from <code>object</code> elements and whose <code>Content-Type</code> HTTP header is not set to "image/jpeg" or "image/gif" are not considered to be Included Resources as discussed under <a href="#ObjectElementProcessingRule"><span class="specref">3.15.1 Object Element Processing Rule</span></a> (i.e. objects that are "tasted" to determine their Internet content type but are then discarded are not Included Resources). Their treatment, as regards <a href="#PAGE_SIZE_LIMIT"><span class="specref">3.16
PAGE_SIZE_LIMIT
</span></a> and <a href="#EXTERNAL_RESOURCES"><span class="specref">3.6
EXTERNAL_RESOURCES
</span></a>, is described in the relevant section.
</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Resources referenced by descendants of an <code>object</code> element that itself refers to an Included Resource are not considered to be Included Resources as discussed under <a href="#ObjectElementProcessingRule"><span class="specref">3.15.1 Object Element Processing Rule</span></a> (i.e. any <code>img</code> or <code>object</code> element which occurs in the fall-back of an acceptable <code>object</code> element is not an Included Resource).</p></div></div><div class="div3">
<h4><a name="linked_resources" id="linked_resources"/>2.4.8 Linked Resources</h4><p>Linked Resources are resources linked to from the resource being tested
(other than the resource itself), but which are not vital to rendering that
resource whose URI begins with the "http" or
"https" scheme when represented in an absolute form.</p><p>Linked resources are defined as those that are referenced by:</p><ul><li><p>the <code>href</code> attribute of <code>a</code> (anchor)
elements.</p></li><li><p>the <code>action</code> attribute of <code>form</code> elements whose
<code>method</code> attribute is not present or is present with
value "get" (case-insensitive).</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Forms with <code>method</code> attribute "POST"
(case-insensitive) are permissible in documents under test, but
are not checked by mobileOK Basic (posting might cause side
effects such as the addition of unwanted records to a
database).</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>When submitting forms use default values where supplied,
otherwise supply empty values.</p></div></li></ul></div><div class="div3">
<h4><a name="validity" id="validity"/>2.4.9 Validity</h4><p>Several tests refer to the validity of aspects of a resource. This section
defines specifically what this means.</p><dl><dt class="label">
<span>CSS</span>
</dt><dd><p>A resource is considered a valid CSS resource if it conforms to
the grammar defined in <a href="#CSS">[CSS Level 1]</a>, <a href="http://www.w3.org/TR/REC-CSS1#appendix-b">Appendix B</a>. The presence of at-rules, properties or values or
combinations of properties and values that are not specified in
<a href="#CSS">[CSS Level 1]</a> does not constitute a validity failure
for CSS. See <a href="#STYLE_SHEETS_USE"><span class="specref">3.21
STYLE_SHEETS_USE
</span></a> for treatment of
such values. In addition, the <code>@media</code> at-rule and
the presentation media list for the <code>@import</code>
at-rule are taken into account when evaluating CSS.</p></dd><dt class="label">
<span>GIF</span>
</dt><dd><p>An image is a valid GIF image if it conforms to the grammar
defined in section 25 of the <a href="#GIF">[GIF]</a>
specification.</p></dd><dt class="label">
<span>JPEG</span>
</dt><dd><p>An image is a valid JPEG image if it follows the format defined
in Annex B of the <a href="#JPEG">[JPEG]</a> specification</p></dd><dt class="label">
<span>UTF-8</span>
</dt><dd><p>A resource is considered to be valid UTF-8 if its bytes represent
the valid UTF-8 encoding of some string, as defined in <a href="#UTF-8">[RFC 3629]</a>, <a href="http://tools.ietf.org/html/rfc3629#section-4">section 4</a>
</p></dd></dl></div><div class="div3">
<h4><a name="whitespace" id="whitespace"/>2.4.10 White Space</h4><p>Several tests refer to white space. White space has the same definition in
this document as in XML. For XML 1.0 <a href="#XML10">[XML 1.0]</a> it is defined in
<a href="http://www.w3.org/TR/REC-xml/#sec-common-syn">http://www.w3.org/TR/REC-xml/#sec-common-syn</a> as being:</p><p>
<code>S ::= (#x20 | #x9 | #xD | #xA)+</code> i.e. the characters SP, TAB, CR
and LF.</p></div></div></div><div class="div1">
<h2><a name="mobileok_basic_tests" id="mobileok_basic_tests"/>3 mobileOK Basic Tests</h2><p>This section describes tests for mobileOK Basic. Tests are organized alphabetically
by the Best Practice from which they derive. Where a test derives from more than one
Best Practice it is placed according to the one that occurs first in dictionary
order.</p><div class="div2">
<h3><a name="AUTO_REFRESH" id="AUTO_REFRESH"/>3.1
<a href="http://www.w3.org/TR/mobile-bp/#AUTO_REFRESH">AUTO_REFRESH</a> and <a href="http://www.w3.org/TR/mobile-bp/#REDIRECTION">REDIRECTION</a></h3><p>This test does not determine whether the user is able to opt out of refresh. </p><div class="exampleOuter"><p class="pseudocode1">If a <code>meta</code> element is present with
<code>http-equiv</code> attribute value of "refresh",</p><p class="pseudocode2">If the URI specified as part of the <code>content</code>
attribute is not the current resource's URI, <span class="kw" id="AUTO_REFRESH-1" title="AUTO_REFRESH-1">FAIL</span>
</p><p class="pseudocode2">Else, <span class="kw" id="AUTO_REFRESH-2" title="AUTO_REFRESH-2">warn</span>
</p><p class="pseudocode1">If a <code>Refresh</code> HTTP header is present,</p><p class="pseudocode2">If the URI specified in the header value is not the
current resource's URI, <span class="kw" id="AUTO_REFRESH-3" title="AUTO_REFRESH-3">FAIL</span>
</p><p class="pseudocode2">Else, <span class="kw" id="AUTO_REFRESH-4" title="AUTO_REFRESH-4">warn</span>
</p></div></div><div class="div2">
<h3><a name="CACHING" id="CACHING"/>3.2
<a href="http://www.w3.org/TR/mobile-bp/#CACHING">CACHING</a>
</h3><p>The purpose of the test is to alert providers to the fact that their content may
not be cached, if it would be beneficial to do so.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>Where both a <code>meta</code> element with <code>http-equiv</code> attribute
and the corresponding HTTP header are found, the value of the HTTP header
<strong>must</strong> be used - see also note under <a href="#meta_http_equiv"><span class="specref">2.4.5 Meta http-equiv Elements</span></a>.</p></div><div class="exampleOuter"><p class="pseudocode1">If the HTTP response contains neither an
<code>Expires</code> nor <code>Cache-Control</code> header</p><p class="pseudocode2">If no <code>meta http-equiv</code> element is present,
referring to those headers, <span class="kw" id="CACHING-1" title="CACHING-1">FAIL</span>
</p><p class="pseudocode2">Continue the test using the value from the <code>meta</code>
<code>content</code> attribute as though it were specified in the
appropriate header, <span class="kw" id="CACHING-2" title="CACHING-2">warn</span></p><p class="pseudocode1">If a <code>Cache-Control</code> HTTP header is present and
contains value "no-cache", or contains value
"max-age=0", <span class="kw" id="CACHING-3" title="CACHING-3">warn</span>
</p><p class="pseudocode1">If a <code>Pragma</code> HTTP header is present and
contains value "no-cache", <span class="kw" id="CACHING-4" title="CACHING-4">warn</span>
</p><p class="pseudocode1">If an <code>Expires</code> and <code>Date</code> HTTP
header are present, and the <code>Expires</code> header specifies a date
which is not later than what the <code>Date</code> header specifies, <span class="kw" id="CACHING-5" title="CACHING-5">warn</span>
</p><p class="pseudocode1">If any cache related header contains an invalid value, <span class="kw" id="CACHING-6" title="CACHING-6">warn</span>
</p><p class="pseudocode1">If the HTTP response contains a <code>Last-Modified</code>
header,</p><p class="pseudocode2">Request the same URI again, adding an
<code>If-Modified-Since</code> request header whose value matches that
of the <code>Last-Modified</code> response header</p><p class="pseudocode2">If the HTTP response contains a <code>Last-Modified</code>
header and its value is again the same, and the HTTP response status is not
304 (Not Modified), <span class="kw" id="CACHING-7" title="CACHING-7">warn</span>
</p><p class="pseudocode1">If the HTTP response contains an <code>ETag</code> header,</p><p class="pseudocode2">Request the same URI again, adding an
<code>If-None-Match</code> request header whose value matches that of the
<code>ETag</code> response header</p><p class="pseudocode2">If the HTTP response contains an <code>ETag</code> header
and its value is again the same, and the HTTP response status is not 304
(Not Modified), <span class="kw" id="CACHING-8" title="CACHING-8">warn</span>
</p></div></div><div class="div2">
<h3><a name="CHARACTER_ENCODING_SUPPORT" id="CHARACTER_ENCODING_SUPPORT"/>3.3
<a href="http://www.w3.org/TR/mobile-bp/#CHARACTER_ENCODING_SUPPORT">CHARACTER_ENCODING_SUPPORT</a>
and <a href="http://www.w3.org/TR/mobile-bp/#CHARACTER_ENCODING_USE">CHARACTER_ENCODING_USE</a></h3><p>The DDC is defined to support only UTF-8 encoding, and hence this test fails if a
resource is not encoded in UTF-8. The test does <em>not</em> require that
resource <em>always</em> be encoded in UTF-8; the test merely checks that
the resource <em>is available</em> in UTF-8 encoding, if requested.
Resources may be <span>represented using</span> other encodings where
appropriate. This test verifies that a DDC-like device which only accepts UTF-8
encoding may access the resource in UTF-8 encoding.</p><p>This test requires that character encoding is explicitly specified and recognizes
the following methods of specification:</p><ul><li><p>HTTP <code>Content-Type</code> header</p><div class="exampleInner"><pre>application/xhtml+xml<em>; charset=UTF-8</em></pre></div></li><li><p>XML declaration</p><div class="exampleInner"><pre><?xml version="1.0" <em>encoding="UTF-8"</em> ?></pre></div></li><li><p>
<code>meta</code> element that is the first child of the document's
<code>head</code> element, and whose <code>http-equiv</code>
attribute is "Content-Type", and whose
<code>content</code> attribute specifies a character encoding</p><div class="exampleInner"><pre>... <head> <meta http-equiv="Content-Type" content="application/xhtml+xml<em>; charset=UTF-8</em>"/> ... </pre></div></li></ul><div class="exampleOuter"><p class="pseudocode1">If the HTTP <code>Content-Type</code> header specifies a
character encoding other than UTF-8, <span class="kw" id="CHARACTER_ENCODING_SUPPORT-1" title="CHARACTER_ENCODING_SUPPORT-1">FAIL</span></p><p class="pseudocode1">If the HTTP <code>Content-Type</code> header does not
specify a character encoding:</p><p class="pseudocode2">If there is no XML declaration, or UTF-8 character
encoding is not specified in the XML declaration, <span class="kw" id="CHARACTER_ENCODING_SUPPORT-2" title="CHARACTER_ENCODING_SUPPORT-2">FAIL</span></p><p class="pseudocode2">If the HTTP <code>Content-Type</code> header specifies an
Internet media type starting with "text/":</p><p class="pseudocode3">If there is no <code>meta</code> element with
<code>http-equiv</code> attribute that specifies UTF-8 character
encoding, <span class="kw" id="CHARACTER_ENCODING_SUPPORT-3" title="CHARACTER_ENCODING_SUPPORT-3">FAIL</span></p><p class="pseudocode1">If character encoding is specified in more than one way,
and not all values are the same, <span class="kw" id="CHARACTER_ENCODING_SUPPORT-4" title="CHARACTER_ENCODING_SUPPORT-4">FAIL</span></p><p class="pseudocode1">If the document is not valid UTF-8 (see <a href="#validity"><span class="specref">2.4.9 Validity</span></a>), <span class="kw" id="CHARACTER_ENCODING_SUPPORT-5" title="CHARACTER_ENCODING_SUPPORT-5">FAIL</span></p><p class="pseudocode1">For each resource specified by <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a>:</p><p class="pseudocode2">Request the resource</p><p class="pseudocode2">If the HTTP <code>Content-Type</code> header value of the
response starts with "text/" but does not specify UTF-8
character encoding, <span class="kw" id="CHARACTER_ENCODING_SUPPORT-6" title="CHARACTER_ENCODING_SUPPORT-6">warn</span>
</p></div></div><div class="div2">
<h3><a name="CONTENT_FORMAT_SUPPORT" id="CONTENT_FORMAT_SUPPORT"/>3.4
<a href="http://www.w3.org/TR/mobile-bp/#CONTENT_FORMAT_SUPPORT">CONTENT_FORMAT_SUPPORT</a> and
<a href="http://www.w3.org/TR/mobile-bp/#VALID_MARKUP">VALID_MARKUP</a></h3><div class="note"><p class="prefix"><b>Note:</b></p><p>In the following, an <a name="htmldoc" id="htmldoc" title="html document">"html document"</a> is a document that has
"html" as its root element.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In the following, <a name="regardless" id="regardless" title="regardless of its stated DOCTYPE">"regardless of its
stated <code>DOCTYPE</code>"</a> means that when
assessing validity against the XHTML Basic 1.1 and XHTML MP 1.2 DTDs this
may be carried out by inserting a <code>DOCTYPE</code> if none is present,
or by replacing the given <code>DOCTYPE</code> with the appropriate
<code>DOCTYPE</code> for the DTD under test.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In the following, <a name="known" id="known" title="a known XHTML version">"a known
XHTML version"</a> means XHTML Basic 1.0, XHTML Basic 1.1, XHTML-MP
1.0, XHTML-MP 1.1 or XHTML-MP 1.2.</p></div><div class="exampleOuter"><p class="pseudocode1">If the document's Internet media type, as specified in the
HTTP response <code>Content-Type</code> header, is not
"application/xhtml+xml",
"application/vnd.wap.xhtml+xml", or
"text/html", <span class="kw" id="CONTENT_FORMAT_SUPPORT-1" title="CONTENT_FORMAT_SUPPORT-1">FAIL</span>
</p><p class="pseudocode1">If the document's Internet media type is
"text/html" or
"application/vnd.wap.xhtml+xml", <span class="kw" id="CONTENT_FORMAT_SUPPORT-2" title="CONTENT_FORMAT_SUPPORT-2">warn</span>
</p><p class="pseudocode1">If the document does not contain a <code>DOCTYPE</code>
declaration, <span class="kw" id="CONTENT_FORMAT_SUPPORT-3" title="CONTENT_FORMAT_SUPPORT-3">FAIL</span></p><p class="pseudocode1">If the document is not an <a title="html document" href="#htmldoc">HTML
document</a>, <span class="kw" id="CONTENT_FORMAT_SUPPORT-4" title="CONTENT_FORMAT_SUPPORT-4">FAIL</span>
</p><p class="pseudocode1">If the <code>DOCTYPE</code> is not an XML
<code>DOCTYPE</code>, <span class="kw" id="CONTENT_FORMAT_SUPPORT-12" title="CONTENT_FORMAT_SUPPORT-12">warn</span></p><p class="pseudocode1">If the document is an <a title="html document" href="#htmldoc">HTML
document</a> and it has an XML <code>DOCTYPE</code>:</p><p class="pseudocode2">If the document does not declare the html namespace on its
<code>html</code> root element, <span class="kw" id="CONTENT_FORMAT_SUPPORT-5" title="CONTENT_FORMAT_SUPPORT-5">FAIL</span></p><p class="pseudocode2">If the <code>DOCTYPE</code> refers to <a title="a known XHTML version" href="#known">a known XHTML version</a>, validate against that
<code>DOCTYPE</code> and if invalid, <span class="kw" id="CONTENT_FORMAT_SUPPORT-13" title="CONTENT_FORMAT_SUPPORT-13">warn</span></p><p class="pseudocode2">Otherwise (if the <code>DOCTYPE</code> is not known), <span class="kw" id="CONTENT_FORMAT_SUPPORT-14" title="CONTENT_FORMAT_SUPPORT-14">warn</span></p><p class="pseudocode1">If (<a title="regardless of its stated DOCTYPE" href="#regardless">regardless of its stated
DOCTYPE</a>) the document does not validate
against the XHTML Basic 1.1 DTD:</p><p class="pseudocode2">If (<a title="regardless of its stated DOCTYPE" href="#regardless">regardless of its stated
DOCTYPE</a>) it does not validate against the
XHTML-MP 1.2 DTD, <span class="kw" id="CONTENT_FORMAT_SUPPORT-6" title="CONTENT_FORMAT_SUPPORT-6">FAIL</span></p><p class="pseudocode1">For each Included Resource (see <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a>):</p><p class="pseudocode2">If the response specifies an Internet media type that is
not "text/css", "image/jpeg" or
"image/gif", <span class="kw" id="CONTENT_FORMAT_SUPPORT-7" title="CONTENT_FORMAT_SUPPORT-7">FAIL</span></p><p class="pseudocode2">If an image is required (see also <a href="#OBJECTS_OR_SCRIPT"><span class="specref">3.15
OBJECTS_OR_SCRIPT
</span></a>) and the response specifies an Internet media
type that is not "image/jpeg" or
"image/gif", <span class="kw" id="CONTENT_FORMAT_SUPPORT-8" title="CONTENT_FORMAT_SUPPORT-8">FAIL</span></p><p class="pseudocode2">If the Internet media type is
"image/gif" or "image/jpeg", and the
resource is not valid (see <a href="#validity"><span class="specref">2.4.9 Validity</span></a>), <span class="kw" id="CONTENT_FORMAT_SUPPORT-9" title="CONTENT_FORMAT_SUPPORT-9">FAIL</span>
</p><p class="pseudocode2">If a style sheet is required and the response specifies an
Internet media type that is not "text/css", <span class="kw" id="CONTENT_FORMAT_SUPPORT-10" title="CONTENT_FORMAT_SUPPORT-10">FAIL</span></p><p class="pseudocode2">If the Internet media type is "text/css"
and the content is not valid CSS (see <a href="#validity"><span class="specref">2.4.9 Validity</span></a>), <span class="kw" id="CONTENT_FORMAT_SUPPORT-11" title="CONTENT_FORMAT_SUPPORT-11">FAIL</span>
</p></div></div><div class="div2">
<h3><a name="DEFAULT_INPUT_MODE" id="DEFAULT_INPUT_MODE"/>3.5
<a href="http://www.w3.org/TR/mobile-bp/#DEFAULT_INPUT_MODE">DEFAULT_INPUT_MODE</a>
</h3><div class="note"><p class="prefix"><b>Note:</b></p><p>
<code>inputmode</code> is part of <a href="#XHTMLBasic11">[XHTML Basic 1.1]</a>.</p></div><div class="exampleOuter"><p class="pseudocode1">For each <code>input</code> element with attribute
<code>type</code> whose value is "text" or
"password" or whose <code>type</code> attribute is
missing:</p><p class="pseudocode2">If the element's <code>inputmode</code> attribute is
invalid according to <a href="http://www.w3.org/TR/2006/WD-xhtml-basic-20060705/#s_inputmode">Section 5.2 User Agent
Behavior</a> of XHTML Basic 1.1 <a href="#XHTMLBasic11">[XHTML Basic 1.1]</a>, <span class="kw" id="DEFAULT_INPUT_MODE-1" title="DEFAULT_INPUT_MODE-1">FAIL</span>
</p><p class="pseudocode2">If the element's <code>value</code> attribute is missing
or empty, and an <code>inputmode</code> attribute is not present, <span class="kw" id="DEFAULT_INPUT_MODE-2" title="DEFAULT_INPUT_MODE-2">warn</span>
</p><p class="pseudocode1">For each <code>textarea</code> element:</p><p class="pseudocode2">If the element's <code>inputmode</code> attribute is
invalid according to <a href="http://www.w3.org/TR/2006/WD-xhtml-basic-20060705/#s_inputmode">Section 5.2 User Agent
Behavior</a> of XHTML Basic 1.1 <a href="#XHTMLBasic11">[XHTML Basic 1.1]</a>, <span class="kw" id="DEFAULT_INPUT_MODE-3" title="DEFAULT_INPUT_MODE-3">FAIL</span>
</p><p class="pseudocode2">If the element is empty and an <code>inputmode</code>
attribute is not present, <span class="kw" id="DEFAULT_INPUT_MODE-4" title="DEFAULT_INPUT_MODE-4">warn</span>
</p></div></div><div class="div2">
<h3><a name="EXTERNAL_RESOURCES" id="EXTERNAL_RESOURCES"/>3.6
<a href="http://www.w3.org/TR/mobile-bp/#EXTERNAL_RESOURCES">EXTERNAL_RESOURCES</a>
</h3><div class="exampleOuter"><p class="pseudocode1">Retrieve the resource under test, and add the number of retrievals required to obtain the resource (see <a href="#http_response"><span class="specref">2.4.4 HTTP Response</span></a>) to a running total.</p><p class="pseudocode1">For each unique Included Resource, as defined in <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a>: </p><p class="pseudocode2">Request the referenced resource</p><p class="pseudocode2">Add the number of HTTP requests that are required to retrieve the resource (see <a href="#http_response"><span class="specref">2.4.4 HTTP Response</span></a>) to the running total. Include in the count only those objects retrieved under the <a href="#ObjectElementProcessingRule"><span class="specref">3.15.1 Object Element Processing Rule</span></a> whose <code>type</code> attribute is not specified, and those whose content type is either "image/jpeg" or "image/gif" irrespective of whether the <code>type</code> attribute is specified.</p><p class="pseudocode1">If the total exceeds 10, <span class="kw" id="EXTERNAL_RESOURCES-2" title="EXTERNAL_RESOURCES-2">warn</span>
</p><p class="pseudocode1">If this total exceeds 20, <span class="kw" id="EXTERNAL_RESOURCES-3" title="EXTERNAL_RESOURCES-3">FAIL</span>
</p></div></div><div class="div2">
<h3><a name="GRAPHICS_FOR_SPACING" id="GRAPHICS_FOR_SPACING"/>3.7
<a href="http://www.w3.org/TR/mobile-bp/#GRAPHICS_FOR_SPACING">GRAPHICS_FOR_SPACING</a>
</h3><p>The intent of this Best Practice is to avoid using transparent images for
spacing. However, small transparent images are often used in e-commerce sites
for user tracking purposes. The practice is common enough, and possibly vital
enough to the business interests of mobile sites, that it is undesirable to fail
sites that use such small transparent images. Therefore this machine-testable
test merely <b>warn</b>s about the presence of small (at most 2x2) transparent
images and <b>FAIL</b>s larger ones. It is believed that few if any sites
would use transparent images of any significant size for tracking.</p><div class="exampleOuter"><p class="pseudocode1">For each <code>img</code> element and
<code>object</code> element which is an Included Resource (see <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a>):</p><p class="pseudocode2">If all pixels are transparent,</p><p class="pseudocode3">If image height and width are both less than or equal to 2
pixels, <span class="kw" id="GRAPHICS_FOR_SPACING-1" title="GRAPHICS_FOR_SPACING-1">warn</span>
</p><p class="pseudocode3">If either dimension exceeds 2 pixels, <span class="kw" id="GRAPHICS_FOR_SPACING-2" title="GRAPHICS_FOR_SPACING-2">FAIL</span>
</p><p class="pseudocode1">If more than one image with all transparent pixels is
present, <span class="kw" id="GRAPHICS_FOR_SPACING-3" title="GRAPHICS_FOR_SPACING-3">warn</span>
</p></div></div><div class="div2">
<h3><a name="IMAGE_MAPS" id="IMAGE_MAPS"/>3.8
<a href="http://www.w3.org/TR/mobile-bp/#IMAGE_MAPS">IMAGE_MAPS</a>
</h3><div class="exampleOuter"><p class="pseudocode1">If an <code>input</code> element with <code>type</code>
attribute set to "image" is present, <span class="kw" id="IMAGE_MAPS-1" title="IMAGE_MAPS-1">FAIL</span></p><p class="pseudocode1">For each <code>img</code> element and <code>object
</code> element which is an Included Resource (see <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a>):</p><p class="pseudocode2">If a <code>usemap</code> attribute is present, <span class="kw" id="IMAGE_MAPS-2" title="IMAGE_MAPS-2">FAIL</span>
</p><p class="pseudocode2">If an <code>ismap</code> attribute is present, <span class="kw" id="IMAGE_MAPS-3" title="IMAGE_MAPS-3">FAIL</span>
</p></div></div><div class="div2">
<h3><a name="IMAGES_SPECIFY_SIZE" id="IMAGES_SPECIFY_SIZE"/>3.9
<a href="http://www.w3.org/TR/mobile-bp/#IMAGES_RESIZING">IMAGES_RESIZING</a> and <a href="http://www.w3.org/TR/mobile-bp/#IMAGES_SPECIFY_SIZE">IMAGES_SPECIFY_SIZE</a></h3><div class="note"><p class="prefix"><b>Note:</b></p><p>The <code>height</code> and <code>width</code> HTML attributes specify pixels
when they are used as a number. No unit is specified.</p></div><div class="exampleOuter"><p class="pseudocode1">For each <code>img</code> element and
<code>object</code> element which is an Included Resource (see <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a>):</p><p class="pseudocode3">If the <code>height</code> or <code>width</code> attribute
are missing, <span class="kw" id="IMAGES_SPECIFY_SIZE-1" title="IMAGES_SPECIFY_SIZE-1">FAIL</span>
</p><p class="pseudocode3">If the <code>height</code> or <code>width</code> attribute
do not specify a size in pixels, <span class="kw" id="IMAGES_SPECIFY_SIZE-2" title="IMAGES_SPECIFY_SIZE-2">FAIL</span>
</p><p class="pseudocode3">If the value specified by either the height or width
attribute is greater than the corresponding dimension of the image, <span class="kw" id="IMAGES_SPECIFY_SIZE-3" title="IMAGES_SPECIFY_SIZE-3">warn</span>
</p><p class="pseudocode3">If the value specified by either the height or width
attribute is less than the corresponding dimension of the image, <span class="kw" id="IMAGES_SPECIFY_SIZE-4" title="IMAGES_SPECIFY_SIZE-4">FAIL</span>
</p></div></div><div class="div2">
<h3><a name="LINK_TARGET_FORMAT" id="LINK_TARGET_FORMAT"/>3.10
<a href="http://www.w3.org/TR/mobile-bp/#LINK_TARGET_FORMAT">LINK_TARGET_FORMAT</a>
</h3><div class="note"><p class="prefix"><b>Note:</b></p><p>404 and 5xx HTTP status do not result in failure when conducting this
test.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>The document body of linked resources is not examined.</p></div><div class="exampleOuter"><p class="pseudocode1">For each linked resource, as defined in <a href="#linked_resources"><span class="specref">2.4.8 Linked Resources</span></a>:</p><p class="pseudocode2">Request the resource</p><p class="pseudocode2">If the <code>Content-Type</code> header value of the HTTP
response is not one of the Internet media types listed in the
<code>Accept</code> header in <a href="#http_request"><span class="specref">2.4.3 HTTP Request</span></a>, <span class="kw" id="LINK_TARGET_FORMAT-1" title="LINK_TARGET_FORMAT-1">warn</span>
</p><p class="pseudocode2">If the <code>Content-Type</code> header value of the HTTP
response does not specify a <code>charset</code> parameter, or does but it
is not consistent with the value of the <code>Accept-Charset</code> header
in <a href="#http_request"><span class="specref">2.4.3 HTTP Request</span></a>, <span class="kw" id="LINK_TARGET_FORMAT-2" title="LINK_TARGET_FORMAT-2">warn</span>
</p><p class="pseudocode1">For each document internal reference (links in the
document under test that refer to the document itself):</p><p class="pseudocode2">If there is no target for the reference or it is invalid
(e.g. '#'), <span class="kw" id="LINK_TARGET_FORMAT-3" title="LINK_TARGET_FORMAT-3">warn</span></p></div></div><div class="div2">
<h3><a name="MEASURES" id="MEASURES"/>3.11
<a href="http://www.w3.org/TR/mobile-bp/#MEASURES">MEASURES</a>
</h3><div class="note"><p class="prefix"><b>Note:</b></p><p>The intrinsic size of images must be specified as attributes of the
<code>img</code> element and not as CSS properties (see <a href="#IMAGES_SPECIFY_SIZE"><span class="specref">3.9
IMAGES_RESIZING and IMAGES_SPECIFY_SIZE</span></a>)</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Only CSS Level 1 properties are considered in this test.</p></div><div class="exampleOuter"><p class="pseudocode1">For each CSS Level 1 property in the CSS Style (see <a href="#handheld_css_style_rule_definition"><span class="specref">2.4.6 CSS Style</span></a>) whose value is a numeric
measure of length stated together with a unit:</p><p class="pseudocode2">If the value is non-zero and the unit is not
"em" or "ex" (and the value is not a
percentage), and the property is not a margin, border or padding box
property, <span class="kw" id="MEASURES-1" title="MEASURES-1">FAIL</span>
</p></div></div><div class="div2">
<h3><a name="MINIMIZE" id="MINIMIZE"/>3.12
<a href="http://www.w3.org/TR/mobile-bp/#MINIMIZE">MINIMIZE</a>
</h3><div class="note"><p class="prefix"><b>Note:</b></p><p>Extraneous white space characters in script and in CSS are not considered in
this test. Such an extension may be considered in a future revision of this
specification.</p></div><div class="exampleOuter"><p class="pseudocode1">Count number of white space characters (see <a href="#whitespace"><span class="specref">2.4.10 White Space</span></a>) in a sequence of more than one white space
character (not counting the first), which exist outside of a
<code>pre</code>, <code>style</code>, <code>script</code> element, or XML
comment.</p><p class="pseudocode1">Add to this count the number of characters comprising XML
comments. This total is the number of extraneous characters in the document.</p><p class="pseudocode1">Count total number of characters in document.</p><p class="pseudocode1">If the number of extraneous characters exceeds 10% of the
count of characters in the document, <span class="kw" id="MINIMIZE-1" title="MINIMIZE-1">warn</span>
</p><p class="pseudocode1">If the number of extraneous characters exceeds 25% of the
count of characters in the document, <span class="kw" id="MINIMIZE-2" title="MINIMIZE-2">FAIL</span>
</p></div></div><div class="div2">
<h3><a name="NO_FRAMES" id="NO_FRAMES"/>3.13
<a href="http://www.w3.org/TR/mobile-bp/#NO_FRAMES">NO_FRAMES</a>
</h3><div class="exampleOuter"><p class="pseudocode1">If the document contains a <code>frame</code>,
<code>frameset</code> or <code>iframe</code> element, <span class="kw" id="NO_FRAMES-1" title="NO_FRAMES-1">FAIL</span>
</p></div></div><div class="div2">
<h3><a name="NON_TEXT_ALTERNATIVES" id="NON_TEXT_ALTERNATIVES"/>3.14
<a href="http://www.w3.org/TR/mobile-bp/#NON-TEXT_ALTERNATIVES">NON-TEXT_ALTERNATIVES</a>
</h3><p>This test does not determine whether the alternative text is meaningful.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>An empty <code>alt</code> attribute is acceptable and signifies that there is
no meaningful textual alternative, for example for images that are purely
decorative.</p></div><div class="exampleOuter"><p class="pseudocode1">For each <code>img</code> element:</p><p class="pseudocode2">If an <code>alt</code> attribute is not present <span>or
contains only white space</span>, <span class="kw" id="NON_TEXT_ALTERNATIVES-1" title="NON_TEXT_ALTERNATIVES-1">FAIL</span>
</p></div></div><div class="div2">
<h3><a name="OBJECTS_OR_SCRIPT" id="OBJECTS_OR_SCRIPT"/>3.15
<a href="http://www.w3.org/TR/mobile-bp/#OBJECTS_OR_SCRIPT">OBJECTS_OR_SCRIPT</a>
</h3><p>This test does not determine whether the document is still usable without the
objects or scripts.</p><div class="exampleOuter"><p class="pseudocode1">If a <code>script</code> element is present, <span class="kw" id="OBJECTS_OR_SCRIPT-1" title="OBJECTS_OR_SCRIPT-1">warn</span>
</p><p class="pseudocode1">If any element has an "intrinsic event"
attribute (currently <code>onload</code>, <code>onunload</code>,
<code>onclick</code>, <code>ondblclick</code>, <code>onmousedown</code>,
<code>onmouseup</code>, <code>onmouseover</code>,
<code>onmousemove</code>, <code>onmouseout</code>, <code>onfocus</code>,
<code>onblur</code>, <code>onkeypress</code>, <code>onkeydown</code>,
<code>onkeyup</code>, <code>onsubmit</code>, <code>onreset</code>,
<code>onselect</code>, <code>onchange</code>), <span class="kw" id="OBJECTS_OR_SCRIPT-2" title="OBJECTS_OR_SCRIPT-2">warn</span>
</p><p class="pseudocode1">For each <code>a</code> and <code>link</code> element:</p><p class="pseudocode2">If the value of the <code>href</code> attribute begins
with the "javascript:" scheme, <span class="kw" id="OBJECTS_OR_SCRIPT-3" title="OBJECTS_OR_SCRIPT-3">FAIL</span>
</p><p class="pseudocode1">If an <code>applet</code> element is present, <span class="kw" id="OBJECTS_OR_SCRIPT-4" title="OBJECTS_OR_SCRIPT-4">FAIL</span>
</p><p class="pseudocode1">Set the context to the root element and apply the <a href="#ObjectElementProcessingRule">Object
Element Processing Rule</a></p></div><div class="div3">
<h4><a name="ObjectElementProcessingRule" id="ObjectElementProcessingRule"/>3.15.1 Object Element Processing Rule</h4><div class="exampleOuter"><p class="pseudocode1">For each <code>img</code> element that has no
<code>object</code> element ancestor (other than the context node) in this context:</p><p class="pseudocode2">Treat this image as an Included Resource (and carry out appropriate tests).</p><p class="pseudocode1">For each <code>object</code> element that has no <code>object</code> element ancestor (other than the context node) in this context:</p><p class="pseudocode2">If the <code>object</code> element is empty, <span class="kw" id="OBJECTS_OR_SCRIPT-5" title="OBJECTS_OR_SCRIPT-5">warn</span></p><p class="pseudocode2">If the content of the <code>object</code> element consists only of
white space, <span class="kw" id="OBJECTS_OR_SCRIPT-6" title="OBJECTS_OR_SCRIPT-6">FAIL</span></p><p class="pseudocode2">If there is no <code>type</code> attribute, <span class="kw" id="OBJECTS_OR_SCRIPT-8" title="OBJECTS_OR_SCRIPT-8">warn</span></p><p class="pseudocode2">If it is not already cached (see <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a>), retrieve the referenced resource (ignoring the <code>type</code> attribute)</p><p class="pseudocode3">If the Internet media type of the retrieved resource, as indicated by its <code>Content-Type</code> HTTP header does not match that stated in the <code>type</code> attribute, <span class="kw" id="OBJECTS_OR_SCRIPT-9" title="OBJECTS_OR_SCRIPT-9">warn</span></p><p class="pseudocode2">If the Internet media type indicated by the <code>Content-Type</code> HTTP Header of the retrieved resource is not "image/jpeg" or "image/gif", <span class="kw" id="OBJECTS_OR_SCRIPT-10" title="OBJECTS_OR_SCRIPT-10">warn</span></p><p class="pseudocode3">Reapply this rule using the current <code>object</code> element as the
context</p><p class="pseudocode2">Otherwise (the object is an acceptable image):</p><p class="pseudocode3">Treat this object as an Included Resource (and carry out appropriate tests), ignore <code>img</code> and <code>object</code> elements that are descendants of the current <code>object</code> element.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>A warning is issued when the Internet media type indicated by the <code>type</code> attribute is not compatible with the Default Delivery Context because some user agents do not take into account the <code>type</code> attribute of <code>object</code> elements and this may cause the user agent to retrieve large incompatible objects with consequences to performance and cost.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>An HTTP 406 status on retrieval of a resource referenced by an object
element does not constitute a FAIL.</p></div></div></div><div class="div2">
<h3><a name="PAGE_SIZE_LIMIT" id="PAGE_SIZE_LIMIT"/>3.16
<a href="http://www.w3.org/TR/mobile-bp/#PAGE_SIZE_LIMIT">PAGE_SIZE_LIMIT</a>
</h3><div class="exampleOuter"><p class="pseudocode1">Retrieve the document under test, if its size (excluding any redirections discussed under <a href="#http_response"><span class="specref">2.4.4 HTTP Response</span></a>) exceeds 10 kilobytes, <span class="kw" id="PAGE_SIZE_LIMIT-1" title="PAGE_SIZE_LIMIT-1">FAIL</span>
</p><p class="pseudocode1">Add to a running total (total size) the size of all the HTTP response bodies that are required to retrieve the document under test (<a href="#http_response"><span class="specref">2.4.4 HTTP Response</span></a>). </p><p class="pseudocode1">For each unique Included Resource, as defined in <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a>:</p><p class="pseudocode2">Add the size of all the response bodies that are required to retrieve the resource (see <a href="#http_response"><span class="specref">2.4.4 HTTP Response</span></a>) to the running total. Include in the total only those objects retrieved under the <a href="#ObjectElementProcessingRule"><span class="specref">3.15.1 Object Element Processing Rule</span></a> whose <code>type</code> attribute is not specified, and those whose Internet media type as indicated by the <code>Content-Type</code> HTTP header is either "image/jpeg" or "image/gif" irrespective of whether the <code>type</code> attribute is specified.</p><p class="pseudocode1">If the total exceeds 20 kilobytes, <span class="kw" id="PAGE_SIZE_LIMIT-2" title="PAGE_SIZE_LIMIT-2">FAIL</span>
</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>In the case of resources that are referenced more than once in the document under test, and where, as discussed under <a href="#included_resources"><span class="specref">2.4.7 Included Resources</span></a>, they are cached, it is the initial retrieval of that resource (as determined by the first reference in document order) that counts towards the total.</p></div><div class="note"><p class="prefix"><b>Note:</b></p><p>Where the <a href="#ObjectElementProcessingRule"><span class="specref">3.15.1 Object Element Processing Rule</span></a> yields a resource that is found to be cached, objects that must be assessed in the course of yielding the cached resource count towards the total.</p></div></div><div class="div2">
<h3><a name="PAGE_TITLE" id="PAGE_TITLE"/>3.17
<a href="http://www.w3.org/TR/mobile-bp/#PAGE_TITLE">PAGE_TITLE</a>
</h3><p>This test does not determine whether the title is meaningful.</p><div class="exampleOuter"><p class="pseudocode1">If a <code>title</code> element is not present in the
<code>head</code> element, or is empty, or contains only white space
(see <a href="#whitespace"><span class="specref">2.4.10 White Space</span></a>), <span class="kw" id="PAGE_TITLE-1" title="PAGE_TITLE-1">FAIL</span>
</p></div></div><div class="div2">
<h3><a name="POP_UPS" id="POP_UPS"/>3.18
<a href="http://www.w3.org/TR/mobile-bp/#POP_UPS">POP_UPS</a>
</h3><div class="exampleOuter"><p class="pseudocode1">For each <code>a</code>, <code>link</code>,
<code>form</code>, and <code>base</code> element:</p><p class="pseudocode2">If a <code>target</code> attribute is present,</p><p class="pseudocode3">If its value is not one of "_self",
"_parent", or "_top", <span class="kw" id="POP_UPS-1" title="POP_UPS-1">FAIL</span>
</p></div></div><div class="div2">
<h3><a name="PROVIDE_DEFAULTS" id="PROVIDE_DEFAULTS"/>3.19
<a href="http://www.w3.org/TR/mobile-bp/#PROVIDE_DEFAULTS">PROVIDE_DEFAULTS</a>
</h3><div class="exampleOuter"><p class="pseudocode1">For each radio button group within a <code>form</code>
element (<code>input</code> elements with <code>type</code>
"radio" that share the same <code>name</code> attribute
value):</p><p class="pseudocode2">Check that exactly one <code>input</code> element within
this group has its <code>checked</code> attribute set to
"checked", and if this is not the case, <span class="kw" id="PROVIDE_DEFAULTS-1" title="PROVIDE_DEFAULTS-1">warn</span>
</p><p class="pseudocode1">For each <code>select</code> element:</p><p class="pseudocode2">If there is no nested <code>option</code> element whose
<code>selected</code> attribute is set to "selected",
<span class="kw" id="PROVIDE_DEFAULTS-2" title="PROVIDE_DEFAULTS-2">warn</span>
</p><p class="pseudocode2">If there is more than one <code>option</code> element
whose <code>selected</code> attribute is set to
"selected", and the <code>multiple</code> attribute is not
set to "multiple", <span class="kw" id="PROVIDE_DEFAULTS-3" title="PROVIDE_DEFAULTS-3">warn</span>
</p></div></div><div class="div2">
<h3><a name="STYLE_SHEETS_SUPPORT" id="STYLE_SHEETS_SUPPORT"/>3.20
<a href="http://www.w3.org/TR/mobile-bp/#STYLE_SHEETS_SUPPORT">STYLE_SHEETS_SUPPORT</a>
</h3><div class="exampleOuter"><p class="pseudocode1">If the CSS Style (see <a href="#handheld_css_style_rule_definition"><span class="specref">2.4.6 CSS Style</span></a>) contains rules referencing
the <code>position</code>, <code>display</code> or <code>float</code>
properties, <span class="kw" id="STYLE_SHEETS_SUPPORT-1" title="STYLE_SHEETS_SUPPORT-1">warn</span>
</p></div></div><div class="div2">
<h3><a name="STYLE_SHEETS_USE" id="STYLE_SHEETS_USE"/>3.21
<a href="http://www.w3.org/TR/mobile-bp/#STYLE_SHEETS_USE">STYLE_SHEETS_USE</a>
</h3><p>This test looks for elements in the <a href="http://www.w3.org/TR/2006/WD-xhtml-modularization-20060705/abstract_modules.html#s_text">Text Extension module</a> defined
by <a href="#XHTMLModularization">[XHTML Modularization]</a>, some of which are not supported in
XHTML Basic <a href="#XHTMLBasic11">[XHTML Basic 1.1]</a>. It also looks for commonly-used
elements and attributes that were deprecated in HTML 4, and are not supported,
or are deprecated, in XHTML Basic.</p><div class="note"><p class="prefix"><b>Note:</b></p><p>This test does not require that any CSS Style is used, since in some cases,
no presentation information is required at all (for example, a simple page
of text).</p></div><div class="exampleOuter"><p class="pseudocode1">If the document contains any <code>basefont</code>,
<code>bdo</code>, <code>center</code>, <code>del</code>,
<code>dir</code>, <code>font</code>, <code>ins</code>, <code>menu</code>,
<code>s</code>, <code>strike</code> or <code>u</code> elements, <span class="kw" id="STYLE_SHEETS_USE-1" title="STYLE_SHEETS_USE-1">FAIL</span>
</p><p class="pseudocode1">If the document contains any <code>b</code>,
<code>big</code>, <code>i</code>, <code>small</code>, <code>sub</code>,
<code>sup</code> or <code>tt</code> elements, <span class="kw" id="STYLE_SHEETS_USE-2" title="STYLE_SHEETS_USE-2">warn</span>
</p><p class="pseudocode1">If any element has a <code>style</code> attribute, <span class="kw" id="STYLE_SHEETS_USE-3" title="STYLE_SHEETS_USE-3">warn</span>
</p><p class="pseudocode1">If all styles are restricted to presentation media types other than
"handheld" or "all" by means of <code>@media</code>
at-rules, <span class="kw" id="STYLE_SHEETS_USE-4" title="STYLE_SHEETS_USE-4">warn</span>
</p><p class="pseudocode1">If the CSS Style contains at-rules (other than the
<code>@media</code> at-rule, and the presentation media type list of the
<code>@import</code> at-rule), properties, or values that are not recognized
as being specified in CSS Level 1, or if the value of a recognized CSS Level 1 property is incompatible with the property, <span class="kw" id="STYLE_SHEETS_USE-5" title="STYLE_SHEETS_USE-5">warn</span>
</p></div></div><div class="div2">
<h3><a name="TABLES_ALTERNATIVES" id="TABLES_ALTERNATIVES"/>3.22
<a href="http://www.w3.org/TR/mobile-bp/#TABLES_ALTERNATIVES">TABLES_ALTERNATIVES</a>
</h3><div class="exampleOuter"><p class="pseudocode1">If a <code>table</code> element exists, <span class="kw" id="TABLES_ALTERNATIVES-1" title="TABLES_ALTERNATIVES-1">warn</span>
</p></div></div><div class="div2">
<h3><a name="TABLES_LAYOUT" id="TABLES_LAYOUT"/>3.23
<a href="http://www.w3.org/TR/mobile-bp/#TABLES_LAYOUT">TABLES_LAYOUT</a>
</h3><p>This test does not catch all cases where tables are used for layout purposes.</p><div class="exampleOuter"><p class="pseudocode1">For each <code>table</code> element:</p><p class="pseudocode2">If it contains at most one <code>tr</code> element, <span class="kw" id="TABLES_LAYOUT-1" title="TABLES_LAYOUT-1">FAIL</span>
</p><p class="pseudocode2">If no <code>tr</code> element contains more than one
<code>td</code> element, <span class="kw" id="TABLES_LAYOUT-2" title="TABLES_LAYOUT-2">FAIL</span>
</p><p class="pseudocode2">For each nested <code>td</code> element:</p><p class="pseudocode3">If the element contains only an image <span>(or
equivalent object) </span> whose actual dimensions are 2x2 or less,
<span class="kw" id="TABLES_LAYOUT-3" title="TABLES_LAYOUT-3">FAIL</span>
</p></div></div><div class="div2">
<h3><a name="TABLES_NESTED" id="TABLES_NESTED"/>3.24
<a href="http://www.w3.org/TR/mobile-bp/#TABLES_NESTED">TABLES_NESTED</a>
</h3><div class="exampleOuter"><p class="pseudocode1">For each <code>table</code> element:</p><p class="pseudocode2">If it contains a <code>table</code> element, <span class="kw" id="TABLES_NESTED-1" title="TABLES_NESTED-1">FAIL</span>
</p></div></div></div></div><div class="back"><div class="div1">
<h2><a name="acknowledgments" id="acknowledgments"/>A Acknowledgments (Non-Normative)</h2><p>The editors would like to thank members of the BPWG for contributions of various
kinds.</p><p>The editors acknowledge significant written contributions from:</p><ul><li>Dominique Hazaël-Massieux, W3C</li><li>Phil Archer, ICRA</li><li>François Daoust, W3C</li></ul></div><div class="div1">
<h2><a name="references" id="references"/>B References (Non-Normative)</h2>
<dl><dt class="label"><a name="BestPractices" id="BestPractices"/>Best Practices</dt><dd>Mobile Web Best
Practices 1.0, Jo Rabin, Charles McCathieNevile, W3C Recommendation, 29 July 2008 (See <a href="http://www.w3.org/TR/2008/REC-mobile-bp-20080729/">http://www.w3.org/TR/2008/REC-mobile-bp-20080729/</a>)</dd>
<dt class="label"><a name="CSS" id="CSS"/>CSS Level 1</dt><dd>Cascading Style Sheets, level 1, Håkon Wium Lie, Bert Bos, W3C Recommendation 17 Dec 1996, revised 11 Jan 1999 (See <a href="http://www.w3.org/TR/1999/REC-CSS1-19990111">http://www.w3.org/TR/1999/REC-CSS1-19990111/</a>)</dd><dt class="label"><a name="GIF" id="GIF"/>GIF</dt><dd>GRAPHICS INTERCHANGE FORMAT, Version
89a, CompuServe Incorporated, 1990 (See <a href="http://www.w3.org/Graphics/GIF/spec-gif89a.txt">http://www.w3.org/Graphics/GIF/spec-gif89a.txt</a>)</dd><dt class="label"><a name="JPEG" id="JPEG"/>JPEG</dt><dd>Recommendation T.81, 18 September 1992 (See <a href="http://www.w3.org/Graphics/JPEG/itu-t81.pdf">http://www.w3.org/Graphics/JPEG/itu-t81.pdf</a>)</dd><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd>Key words for use in RFCs to Indicate
Requirement Levels, S. Bradner, March 1997 (See <a href="http://tools.ietf.org/html/rfc2119.txt">http://tools.ietf.org/html/rfc2119.txt</a>)</dd><dt class="label"><a name="HTTP" id="HTTP"/>RFC 2616</dt><dd> Hypertext Transfer Protocol --
HTTP/1.1 Request for Comments: 2616, R. Fielding, J. Gettys, J. Mogul, H.
Frystyk, L. Masinter, P. Leach, T. Berners-Lee, June 1999 (See <a href="http://tools.ietf.org/html/rfc2616">http://tools.ietf.org/html/rfc2616</a>)</dd><dt class="label"><a name="RFC2617" id="RFC2617"/>RFC 2617</dt><dd>HTTP Authentication: Basic and Digest Access Authentication,
J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P. Leach, A. Luotonen, L.
Stewart, June 1999 (See <a href="http://tools.ietf.org/html/rfc2617">http://tools.ietf.org/html/rfc2617</a>)</dd><dt class="label"><a name="UTF-8" id="UTF-8"/>RFC 3629</dt><dd>UTF-8, a transformation format of ISO 10646, F. Yergau,
November 2003 (See <a href="http://tools.ietf.org/html/rfc3629">http://tools.ietf.org/html/rfc3629</a>)</dd><dt class="label"><a name="WCAG" id="WCAG"/>WCAG 1.0</dt><dd>Web Content Accessibility Guidelines 1.0,
W. Chisholm, G. Vanderheiden and I. Jacobs, eds., W3C Recommendation, 5 May 1999 (See <a href="http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/">http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/</a>)</dd>
<dt class="label"><a name="XHTMLBasic11" id="XHTMLBasic11"/>XHTML Basic 1.1</dt><dd>XHTML™ Basic 1.1, Mark Baker, Masayasu Ishikawa, Shinichi Matsui, Peter Stark, Ted Wugofski, Toshihiko Yamakami (eds), W3C Recommendation, 29 July 2008 (See <a href="http://www.w3.org/TR/2008/REC-xhtml-basic-20080729/">http://www.w3.org/TR/2008/REC-xhtml-basic-20080729/</a>)</dd>
<dt class="label"><a name="XHTMLModularization" id="XHTMLModularization"/>XHTML Modularization</dt><dd>XHTML™
Modularization 1.1, Daniel Austin, Subramanian Peruvemba, Shane McCarron, Masayasu Ishikawa, Mark Birbeck (eds), W3C Recommendation, 08 October 2008 (See <a href="http://www.w3.org/TR/2008/REC-xhtml-modularization-20081008/">http://www.w3.org/TR/2008/REC-xhtml-modularization-20081008/</a>)</dd>
<dt class="label"><a name="XML10" id="XML10"/>XML 1.0</dt><dd>Extensible Markup Language (XML) 1.0 (Fifth Edition), Tim
Bray, Jean Paoli, C. M. Sperberg-McQueen, Eve Maler, François Yergeau, W3C
Recommendation 26 November 2008 (See <a href="http://www.w3.org/TR/2008/REC-xml-20081126/">http://www.w3.org/TR/2008/REC-xml-20081126/</a>)</dd></dl></div><div class="div1">
<h2><a name="bp_test_reference" id="bp_test_reference"/>C Relationship between Best Practices and mobileOK Tests (Non-Normative)</h2><p>This appendix lists all Best Practices and indicates whether each has a corresponding
test in mobileOK Basic.</p><table><thead><tr><th>Best Practice</th><th>mobileOK Basic</th></tr></thead><tbody><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#ACCESS_KEYS">ACCESS_KEYS</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#AUTO_REFRESH">AUTO_REFRESH</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#AVOID_FREE_TEXT">AVOID_FREE_TEXT</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#BACKGROUND_IMAGE_READABILITY">BACKGROUND_IMAGE_READABILITY</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#BALANCE">BALANCE</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#CACHING">CACHING</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#CAPABILITIES">CAPABILITIES</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#CENTRAL_MEANING">CENTRAL_MEANING</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#CHARACTER_ENCODING_SUPPORT">CHARACTER_ENCODING_SUPPORT</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#CHARACTER_ENCODING_USE">CHARACTER_ENCODING_USE</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#CLARITY">CLARITY</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#COLOR_CONTRAST">COLOR_CONTRAST</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#CONTENT_FORMAT_PREFERRED">CONTENT_FORMAT_PREFERRED</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#CONTENT_FORMAT_SUPPORT">CONTENT_FORMAT_SUPPORT</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#CONTROL_LABELLING">CONTROL_LABELLING</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#CONTROL_POSITION">CONTROL_POSITION</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#COOKIES">COOKIES</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#DEFAULT_INPUT_MODE">DEFAULT_INPUT_MODE</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#DEFICIENCIES">DEFICIENCIES</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#ERROR_MESSAGES">ERROR_MESSAGES</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#EXTERNAL_RESOURCES">EXTERNAL_RESOURCES</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#FONTS">FONTS</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#GRAPHICS_FOR_SPACING">GRAPHICS_FOR_SPACING</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#IMAGE_MAPS">IMAGE_MAPS</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#IMAGES_RESIZING">IMAGES_RESIZING</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#IMAGES_SPECIFY_SIZE">IMAGES_SPECIFY_SIZE</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#LARGE_GRAPHICS">LARGE_GRAPHICS</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#LIMITED">LIMITED</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#LINK_TARGET_FORMAT">LINK_TARGET_FORMAT</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#LINK_TARGET_ID">LINK_TARGET_ID</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#MEASURES">MEASURES</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#MINIMIZE">MINIMIZE</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#MINIMIZE_KEYSTROKES">MINIMIZE_KEYSTROKES</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#NAVBAR">NAVBAR</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#NAVIGATION">NAVIGATION</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#NO_FRAMES">NO_FRAMES</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#NON-TEXT_ALTERNATIVES">NON-TEXT_ALTERNATIVES</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#OBJECTS_OR_SCRIPT">OBJECTS_OR_SCRIPT</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#PAGE_SIZE_LIMIT">PAGE_SIZE_LIMIT</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#PAGE_SIZE_USABLE">PAGE_SIZE_USABLE</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#PAGE_TITLE">PAGE_TITLE</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#POP_UPS">POP_UPS</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#PROVIDE_DEFAULTS">PROVIDE_DEFAULTS</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#REDIRECTION">REDIRECTION</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#SCROLLING">SCROLLING</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#STRUCTURE">STRUCTURE</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#STYLE_SHEETS_SIZE">STYLE_SHEETS_SIZE</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#STYLE_SHEETS_SUPPORT">STYLE_SHEETS_SUPPORT</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#STYLE_SHEETS_USE">STYLE_SHEETS_USE</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#SUITABLE">SUITABLE</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#TAB_ORDER">TAB_ORDER</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#TABLES_ALTERNATIVES">TABLES_ALTERNATIVES</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#TABLES_LAYOUT">TABLES_LAYOUT</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#TABLES_NESTED">TABLES_NESTED</a>
</td><td>X</td></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#TABLES_SUPPORT">TABLES_SUPPORT</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#TESTING">TESTING</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#THEMATIC_CONSISTENCY">THEMATIC_CONSISTENCY</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#URIS">URIS</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#USE_OF_COLOR">USE_OF_COLOR</a>
</td><td/></tr><tr><td>
<a href="http://www.w3.org/TR/mobile-bp/#VALID_MARKUP">VALID_MARKUP</a>
</td><td>X</td></tr></tbody></table></div></div></body></html>