Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
maxLevel2
minLevel2
typeflat

Page titles

Required

  • The page <title> MUST Must be present and MUST contain text.

  • The page <title> MUST Must be updated when the web address URL changes.

  • The page <title> MUST Must be accurate and informative.

Non-required / best practice

  • If a page is the Should describe result of a user action or scripted change of context , the text of the <title> SHOULD describe the result or change of context to the user.if either occur

  • Should The <title> SHOULD be concise.

  • The page <title> SHOULD Should be unique, if possible.

  • Unique information SHOULD should come first in the <title>.title. Example: About us | Cornell Alumni

  • Should match H1 tagThe page <title> SHOULD match (or be very similar to) the top heading in the main content.

Language

Required

  • The primary language of the page MUST Must be identified accurately on in the <html> element.The primary language of the page MUST be identified tag with a valid value on the <html> element.
  • Inline language changes MUST be identified with a valid lang attribute.
  • language code. Example: <html lang="en">
  • Valid lang attribute must be used for inline language changes. Example: <p>And then I said in a German accent, <span lang="de">Bach ist ein Komponist.</span>.</p>The language code MUST be valid.

Headings

Required

  • Headings MUST Must be accurate and informative.

Non-required / best practice

  • Text that acts as If text looks like a heading visually , or is structurally SHOULD be designated as a true heading in the markup.

  • Text that does not act as a heading visually or structurally SHOULD NOT be marked as a heading.

  • Heading text SHOULD be concise and relatively brief.

  • a heading, use HTML heading tags. Example: <h2>The history of Cornell University</h2>

  • Do not use HTML heading tags for anything other than true headings

  • Should be concise

  • Should convey Headings SHOULD convey a clear and accurate structural outline of the sections of content of a web page .content

  • Should not Headings SHOULD NOT skip hierarchical levels .Example: Don't jump from <h2> to <h4>

  • Beginning of main content should The beginning of the main content SHOULD start with <h1>.

  • Should only have Most web pages SHOULD have only one <h1>.

Navigation

Required

  • Navigation patterns that are repeated on web pages MUST be presented in the same relative order each time they appear and MUST NOT change order when navigating through the site.
  • A skip link MUST be either visible at all times or visible on keyboard focus.
  • The reading order MUST be logical and intuitive.
  • The navigation order of focusable elements MUST be logical and intuitive.

...