??? Frames: No, frames are not universally supported, especially on many portable devices.
Even when they are supported, you need to be careful because a frame is essentially like
having another browser instance in terms of memory (and in some cases it very literally
is another browser instance), and this can be a major factor in mobile devices.
??? Graphics: Graphics can be tricky in terms of accessibility because they tend to convey
more information than an alt attribute can. So, some of the meaning of the graphic can
easily be lost for those with disabilities, no matter how vigilant you are to help them.
??? Newer HTML specs: There are still many people out there using older browsers that may
not even support HTML 4.01, so to be safe you will probably want to code to HTML 3.0.
You will lose some capabilities obviously in doing so.
Probably the most important element here is the lack of client-side scripting. Without
client-side scripting, so many possibilities are not available to you as a developer. Most important
in the context of this book is the fact that you have virtually no choice but to have the
server deal with every single user interaction. You may be able to get away with some metarefreshes
in frames in some cases, or perhaps other tricks of the trade, but frames too are on
the list, so you might not even have that option!
You may be wondering, ???What is the problem with the server rendering entire pages????
Certainly there are benefits, and the inherent security of being in complete control of the runtime
state of the application (i.
Pages:
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