Publishers of technology books, eBooks, and videos for creative people

Home > Articles > Web Design & Development > Usability

ppk on JavaScript: Context

  • Print
  • + Share This
JavaScript is used in the context of a Web page. This is obvious, but it has a few consequences that haven’t always been properly appreciated. Peter-Paul Koch discusses the standards-compliance CSS revolution that has changed Web development, starting with a quick summary of the CSS revolution and its impact on JavaScript.
This chapter is from the book

This chapter is from the book

JavaScript is used in the context of a Web page. This is obvious, but it has a few consequences that haven’t always been properly appreciated. JavaScript is embedded in an environment that also uses HTML and CSS, and in which usability and accessibility are essential elements. After all, a script must add something useful to a site, and the site must continue to work when JavaScript is disabled or entirely absent.

This chapter—in fact, my entire approach to JavaScript programming—is heavily influenced by the standards-compliance CSS revolution that has changed Web development. Therefore it’s fitting to start this chapter with a quick summary of the CSS revolution and its impact on JavaScript.

A: The CSS revolution

As we saw in 1C, in 1998 (when Netscape and Explorer 4 couldn’t agree about anything), a group of concerned Web developers united in the Web Standards Project (WaSP), to do something about the ludicrous proprietary elements of JavaScript and to promote the use of CSS for defining the presentation of Web sites. Their main message was “Follow the standards,” and they aimed this message at both browser vendors and Web developers.

At first, WaSP and its sympathizers concentrated on promoting CSS. There were various reasons for this, the most important being that using CSS in Web-site creation formed the clearest break with the past. JavaScript didn’t really enter the equation yet, both because CSS was enough of a challenge to occupy the best minds in Web-development land for years, and because back in 1998 the average JavaScript was badly written, badly thought out, and completely inaccessible.

Besides, it was relatively easy to get browser vendors to start working on their CSS implementation because it was a new technology that was not yet weighed down by millions of implementations on millions of sites. In contrast, JavaScript was hampered by the countless existing implementations of the browser-specific document.layers and document.all DOMs we briefly discussed in 1C. CSS offered the possibility of a clean slate.

One of the drawbacks of this focus on CSS was that, in the minds of some standards supporters, JavaScript became equated with “inaccessible.” You’ll still encounter this misconception every now and then, even though, as we’ll see later in this chapter, JavaScript and accessibility can co-exist in harmony, as long as you take some precautions.

Unobtrusive scripting

In 2002, Stuart Langridge coined the term “unobtrusive scripting,” which represented the first serious attempt to embed JavaScript in the new theory of CSS-based, standards-compliant Web sites.

An unobtrusive script should have all of the following traits:

  • It should be usable, i.e., it should confer a definite usability benefit on the site.
  • It should be accessible, i.e., if JavaScript doesn’t work, the page should remain readable and understandable, although the loss of some usability is inevitable.
  • It should be easy to implement; typically, a Web developer has only to include the script itself and add a JavaScript hook in the document, and the script works. We’ll discuss JavaScript hooks in 4B.
  • It should be separate; it resides in its own .js file instead of being scattered through the HTML.

In theory the first idea has been present since JavaScript’s birth, but it has usually been disregarded by programmers eager to show off JavaScript’s capabilities. Never mind if these capabilities don’t confer a usability benefit—they’re cool!

The other three ideas were new. Accessibility and JavaScript were generally held to be mutually exclusive, and most old-school JavaScript developers decided that their applications were too advanced to ever become accessible. That’s nonsense, of course, but it is powerful nonsense that has held JavaScript in thrall for far too many years. We’ll discuss JavaScript and accessibility in 2E.

Ease of implementation requires JavaScript hooks, and they became possible only with the advent of the W3C DOM. This was the sole idea that was new for technical rather than psychological reasons. See 4B for more information.

Separation, lastly, was an idea borrowed from the CSS revolution. If you should separate your HTML and CSS, it’s logical to separate your JavaScript from both of them, too. Before we can discuss the three kinds of separation, we first have to study what we’re going to separate.

The three layers

A Web page consists of three layers (and yes, these are the ones that need to be separated from each other):

  1. HTML structure.
  2. CSS presentation.
  3. JavaScript behavior.

Figure 2.1 The three layers of a Web page. The HTML structural layer is the required basis, and the CSS presentation and JavaScript behavior layers are built on top of it.

The HTML structural layer is the most basic part of the page. The HTML tags form the structure of the page and give meaning to its content. For instance, if a certain text is marked up with an <h1>, it’s a header and should be treated as such. Browsers (or, more generally, user agents—programs that interpret HTML) are expected to distinguish this header from the surrounding normal text, for instance by displaying it in bold and in a larger font, or by pronouncing it louder or slower. Once you’ve created structurally correct HTML, you can be reasonably certain that most user agents, hence most users, will recognize a header as a header.

The purpose of the CSS presentation layer is to define how your HTML should be presented. CSS allows you to specify colors, fonts, leading, and other typographical elements, as well as the general layout of the page, for instance, “The navigation block goes next to the content block.”

The JavaScript behavior layer adds interactivity to an HTML/CSS page. As soon as you want something to happen when the user mouses over an HTML element, you need JavaScript to implement the effect.

Every Web page needs an HTML structural layer—without HTML, there is no Web page. However, the CSS and JavaScript layers are optional. Old, obscure, or unusual browsers may not support CSS and/or JavaScript, in which case one or both layers may go missing—the presentation or behavior instructions are never executed.

Figure 2.2 If a browser can’t handle JavaScript, obviously the behavior layer won’t work. Will your site survive that experience?

The consequence of this state of affairs is obvious. Any site must be able to survive the demise of the behavior layer (or the presentation layer, but that’s a much rarer occurrence). In other words, a site may not totally rely on JavaScript, but must remain accessible when JavaScript doesn’t work. We’ll get back to this in 2E.

Separation of concerns

Another point raised by the division of client-side code into three layers is the separation of concerns. In general, it’s best to manage each of the three layers separately. At the most basic level, this is done by making sure of the following:

  • The HTML is structural, not too complex, and makes sense without CSS and JavaScript.
  • The CSS presentation layer and the JavaScript behavior layer reside in separate .css and .js files.

Separating concerns makes for easy maintenance. When you use separate CSS and JavaScript files, it’s easy to link to these files from all pages in your site. This has obvious maintenance advantages: if you open the .css file and change, say, the font size from 12px to 0.8em, this change will immediately be propagated to all HTML pages that link to that .css file.

Besides, separation allows you to change the entire CSS presentation layer to give your site a new design, without having to recode either the HTML structural or the JavaScript behavior layer.

The three separations

As you see, separating concerns makes your site’s code cleaner and easier to maintain. In the next section we’ll discuss the gory details of the three separations:

  • Separation of presentation and structure (CSS and HTML);
  • Separation of behavior and structure (JavaScript and HTML);
  • Separation of behavior and presentation (JavaScript and CSS).

All three influence the way we should write JavaScript.

  • + Share This
  • 🔖 Save To Your Account

Peachpit Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Peachpit and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Peachpit products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email ask@peachpit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.peachpit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020