WAI Guidelines Check

So let's check back with w3.org/TR/WAI-WEBCONTENT, the Web Content Accessibility Guidelines 1.0, where section 12, 13, 14 are most relevant to the functionality targetted at with the mksite.sh project, and hinted more strongly in the w3.org/TR/WAI-WEBCONTENT-TECHS pages, the Techniques for Web Content Accessibility Guidelines 1.0.

"12" Provide context and orientation information

• 12.1 Title each frame to facilitate frame identification and navigation. [Priority 1]
  HTML Techniques: Providing a frame title.
  mksite.sh: parse out <title> or the first of the <h1> <h2> ... <h6> as the $title meta variable. A sitefile can pick it up on its <title> presentation including a prefix that categorizes the web page into a larger context.
• 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. [Priority 2]
  Core Techniques: Text equivalents
  HTML Techniques: Describing frame relationships
  mksite.sh : The recognition of sect/subsect relations is taken out of the markup in the sitefile for graphical representtion. The used markups encourage clear relation designation of references pages. The sect/subsect relations will build a printer-friendly layout with pages on the same sect/subect level on one line. That creates clear parent/children and next/previous relations.
• 12.2 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2]
  HTML Techniques: Structural grouping
  HTML Techniques: Grouping form controls
  mksite.sh Largely content related to the author, e.g. using tables in the body. Otherwise we encourage to split long pages into more manageable parts and bind the via a sitefile.

"13" Provide clear navigation mechanisms

• 13.1 Clearly identify the target of each link. [Priority 2]
  HTML Techniques: Link text
• 13.2 Provide metadata to add semantic information to pages and sites. [Priority 2]
  Core Techniques: Navigation
  HTML Techniques: Metadata
  CSS Techniques: Providing contextual clues in HTML lists
  mksite.sh : We generate automatically metadata information in the html head and allow users to extend it and override the defaults - mksite.sh does generate some defaults. The html head meta tags are however only useful to special user agents or search bots.
• 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). [Priority 2]
  Core Techniques: Navigation
  mksite.sh : We generate a site map - all automically. Just name it as a link in your sitefile.
• 13.4 Use navigation mechanisms in a consistent manner. [Priority 2]
  Core Techniques: Navigation
  mksite.sh : We encourage to use a single sitefile with the navigation items for all assiated pages - including pages in subdirectories of the main website. If the website gets a bit too big then you can use the "mulitsectionlayout" that will split the navigation items in a consistent manner.

"14" Ensure that documents are clear and simple.

• 14.1 Use the clearest and simplest language appropriate for a site's content. [Priority 1]
  Core Techniques: Comprehension
• 14.3 Create a style of presentation that is consistent across pages. [Priority 3]
  Core Techniques: Navigation
  CSS Techniques: Decrease maintenance and increase consistency
  mksite.sh : We encourage to use a single sitefile as the only maintenance object for the layout of a website. The sitefile sect/subsect scanning provides consistency over the associated pages. The site file contains the CSS block for all pages giving the a consistent style across.