Unit 6: Quality Control

What is one reason for validating your web pages?

• Valid HTML assures that all standards-compliant browsers will render the page reliably.

• Valid HTML loads many times faster than non-standard code.

• Valid HTML is the only form of code that by law may be published on the Internet.

• Valid HTML is the only form of HTML that standards-compliant browsers will display.

When validating a web page, it is usually a good idea to fix the first error, then save and retest because correcting one error tends to—

• take several days to process.

• make the validator process the page more quickly.

• ensure the validator will not freeze up as it will when multiple errors are corrected.

• have an influence on subsequent validation errors, possibly fixing other errors in a domino fashion.

The W3C HTML validator (and most validation services) allow you to—

• validate by entering the URL to your web page.

• validate by uploading an HTML file from your local drive.

• validate by pasting your HTML code directly into the validator.

• All of the above

If you have an HTML file that has not been posted on the Internet and only resides in your local drive, by what means will you validate it

• Validate by URL

• Validate by file upload

• Validate by direct input

• Either b or c

• All of the above

An HTML validator will not validate which of the following?

• HTML5

• HTML 4.01

• CSS

• XHTML

A text editor may make the validation process simpler if it has the following feature to help you scan through your code:

• Numbered code lines and columns

• Spelling and grammar checks

• Cup holders

• All of the above

Just like with HTML, a web page that has invalid CSS might look fine in your browser, but someone accessing the page in another browser might have an entirely different experience with the same content.

• True

• False

The W3C CSS validator (and most validation services) allow you to—

• validate by entering the URL to your style sheet (HTML with CSS or CSS only).

• validate by uploading a file from your local drive.

• validate by pasting your CSS code directly into the validator.

• All of the above

When your CSS validates, the Validator results window should provide you with‐

• a W3C favicon to signify that your page is standards-compliant.

• code for adding a W3C CSS logo to the bottom of your web page to signify that your page is standards-compliant.

• a certificate of standards-compliance, suitable for printing.

• None of the above

Some accessibility issues can't be automatically detected by a validator and require human judgment. In this case the web accessibility tools will—

• ignore issues that may require human judgment.

• prompt you to inspect issues that require human judgment.

• attempt to repair your code.

• prompt you to rewrite multiple lines of code.