Monthly Archives August 2014

Monthly Archives: August 2014

Heatmaps – tracking what visitors click on your website

Heatmaps – tracking what visitors click on your website

Tracking visitors with Google Analytics or Statcounter is one thing, but really understanding what catches their eye and what they click on? COME ON, you totally want to know.

WELL thanks to APPSUMO, we’ve got a free wordpress plugin to install. Heat maps with 1-click will show you instantly where people are clicking so you can improve your page to get them to do the things you want them to do.

Download WordPress Plugin

Click the download button to save to your computer.
Want us to install it for you? Email us your information.

Upload plugin

Upload to your WordPress website.

Activate plugin
Click Activate Plugin to activate the SumoMe plugin on your WordPress site.

Setup plugin

Continue to the SumoMe for WordPress settings page to complete setup.

Admin for SumoMe

Read More »

WCAG 2.0 Checklist

Special thanks again to WebAIM for developing this WCAG 2.0 Checklist for HTML documents

NOTE: The following is NOT the Web Content Accessibility Guidelines (WCAG) 2.0. It is, however, a simple checklist that presents our recommendations for implementing HTML-related principles and techniques for those seeking WCAG 2.0 conformance.

  • This checklist cannot be used to verify conformance with WCAG 2.0. You must reference official WCAG 2.0 documentation to determine any level of conformance or non-conformance.
  • This checklist should not be referenced in policies or in policy adoption. While this is a useful resource for technical implementation of WCAG for HTML content, it is not a useful policy checklist. Official WCAG 2.0 documentation provides much better mechanisms for implementing accessibility into policy or law.
  • WCAG 2.0 covers accessibility of all web content and is not technology specific. The language of this checklist has been targeted primarily for evaluation of HTML content. It is, therefore, fairly limited and subject to technology changes, whereas WCAG 2.0 is much less so.
  • This checklist contains WebAIM’s interpretation of WCAG guidelines and success criteria and our own recommended techniques for satisfying those success criteria. The first column of the table below links to the official WCAG 2.0 success criteria.

Web content is made available to the senses – sight, hearing, and/or touch

Guideline 1.1
Text Alternatives: Provide text alternatives for any non-text content

Success Criteria WebAIM’s Recommendations
1.1.1 Non-text Content
(Level A)
  • All images, form image buttons, and image map hot spots have appropriate, equivalent alternative text.
  • Images that do not convey content, are decorative, or contain content that is already conveyed in text are given null alt text (alt=””) or implemented as CSS backgrounds. All linked images have descriptive alternative text.
  • Equivalent alternatives to complex images are provided in context or on a separate (linked and/or referenced via longdesc) page.
  • Form buttons have a descriptive value.
  • Form inputs have associated text labels.
  • Embedded multimedia is identified via accessible text.
  • Frames are appropriately titled.

Guideline 1.2
Time-based Media: Provide alternatives for time-based media

NOTE: If the audio or video is designated as an alternative to web content (e.g., an audio or sign language version of a web page, for example), then the web content itself serves as the alternative.

Success Criteria WebAIM’s Recommendations
1.2.1 Prerecorded Audio-only and Video-only
(Level A)
  • A descriptive text transcript (including all relevant visual and auditory clues and indicators) is provided for non-live, web-based audio (audio podcasts, MP3 files, etc.).
  • A text or audio description is provided for non-live, web-based video-only (e.g., video that has no audio track).
1.2.2 Captions (Prerecorded)
(Level A)
  • Synchronized captions are provided for non-live, web-based video (YouTube videos, etc.)
1.2.3 Audio Description or Media Alternative (Prerecorded)
(Level A)
1.2.4 Captions (Live)
(Level AA)
  • Synchronized captions are provided for all live multimedia that contains audio (audio-only broadcasts, web casts, video conferences, Flash animations, etc.)
1.2.5 Audio Description (Prerecorded)
(Level AA)
  • Audio descriptions are provided for all video content
    NOTE: Only required if the video conveys content visually that is not available in the default audio track.
1.2.6 Sign Language (Prerecorded)
(Level AAA)
  • A sign language video is provided for all media content that contains audio.
1.2.7 Extended Audio Description (Prerecorded)
(Level AAA)
  • When an audio description track cannot be added to video due to audio timing (e.g., no pauses in the audio), an alternative version of the video with pauses that allow audio descriptions is provided.
1.2.8 Media Alternative (Prerecorded)
(Level AAA)
  • A descriptive text transcript is provided for all pre-recorded media that has a video track.
1.2.9 Audio-only (Live)
(Level AAA)
  • A descriptive text transcript (e.g., the script of the live audio) is provided for all live content that has audio.

Guideline 1.3
Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure

Success Criteria WebAIM’s Recommendations
1.3.1 Info and Relationships
(Level A)
  • Semantic markup is used to designate headings (<h1>), lists (<ul>, <ol>, and <dl>), emphasized or special text (<strong>, <code>, <abbr>, <blockquote>, for example), etc. Semantic markup is used appropriately.
  • Tables are used for tabular data. Where necessary, data cells are associated with their headers. Data table captions and summaries are used where appropriate.
  • Text labels are associated with form input elements. Related form elements are grouped with fieldset/legend.
1.3.2 Meaningful Sequence
(Level A)
1.3.3 Sensory Characteristics
(Level A)
  • Instructions do not rely upon shape, size, or visual location (e.g., “Click the square icon to continue” or “Instructions are in the right-hand column”).
  • Instructions do not rely upon sound (e.g., “A beeping sound indicates you may continue.”).

Guideline 1.4
Distinguishable: Make it easier for users to see and hear content including separating foreground from background

Success Criteria WebAIM’s Recommendations
1.4.1 Use of Color
(Level A)
  • Color is not used as the sole method of conveying content or distinguishing visual elements.
  • Color alone is not used to distinguish links from surrounding text unless the luminance contrast between the link and the surrounding text is at least 3:1 and an additional differentiation (e.g., it becomes underlined) is provided when the link is hovered over or receives focus.
1.4.2 Audio Control
(Level A)
  • A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays on a page for more than 3 seconds.
1.4.3 Contrast (Minimum)
(Level AA)
  • Text and images of text have a contrast ratio of at least 4.5:1.
  • Large text (over 18 point or 14 point bold) has a contrast ratio of at least 3:1
1.4.4 Resize text
(Level AA)
  • The page is readable and functional when the text size is doubled.
1.4.5 Images of Text
(Level AA)
  • If the same visual presentation can be made using text alone, an image is not used to present that text.
1.4.6 Contrast (Enhanced)
(Level AAA)
  • Text and images of text have a contrast ratio of at least 7:1.
  • Large text (over 18 point or 14 point bold) has a contrast ratio of at least 4.5:1
1.4.7 Low or No Background Audio
(Level AAA)
  • Audio of speech has no or very low background noise so the speech is easily distinguished.
1.4.8 Visual Presentation
(Level AAA)
  • Blocks of text over one sentence in length:
    • Are no more than 80 characters wide.
    • Are NOT fully justified (aligned to both the left and the right margins).
    • Have adequate line spacing (at least 1/2 the height of the text) and paragraph spacing (1.5 times line spacing).
    • Have a specified foreground and background color. These can be applied to specific elements or to the page as a whole using CSS (and thus inherited by all other elements).
    • Do NOT require horizontal scrolling when the text size is doubled.
1.4.9 Images of Text (No Exception)
(Level AAA)
  • Text is used within an image only for decoration (image does not convey content) OR when the information cannot be presented with text alone.

Interface forms, controls, and navigation are operable

Guideline 2.1
Keyboard Accessible: Make all functionality available from a keyboard

Success Criteria WebAIM’s Recommendations
2.1.1 Keyboard
(Level A)
  • All page functionality is available using the keyboard, unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing).
  • Page-specified shortcut keys and accesskeys (accesskey should typically be avoided) do not conflict with existing browser and screen reader shortcuts.
2.1.2 No Keyboard Trap
(Level A)
  • Keyboard focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements using only a keyboard.
2.1.3 Keyboard (No Exception)
(Level AAA)
  • All page functionality is available using the keyboard.

Guideline 2.2
Enough Time: Provide users enough time to read and use content

Success Criteria WebAIM’s Recommendations
2.2.1 Timing Adjustable
(Level A)
  • If a page or application has a time limit, the user is given options to turn off, adjust, or extend that time limit. This is not a requirement for real-time events (e.g., an auction), where the time limit is absolutely required, or if the time limit is longer than 20 hours.
2.2.2 Pause, Stop, Hide
(Level A)
  • Automatically moving, blinking, or scrolling content that lasts longer than 5 seconds can be paused, stopped, or hidden by the user. Moving, blinking, or scrolling can be used to draw attention to or highlight content as long as it lasts less than 5 seconds.
  • Automatically updating content (e.g., automatically redirecting or refreshing a page, a news ticker, AJAX updated field, a notification alert, etc.) can be paused, stopped, or hidden by the user or the user can manually control the timing of the updates.
2.2.3 No Timing
(Level AAA)
  • The content and functionality has no time limits or constraints.
2.2.4 Interruptions
(Level AAA)
  • Interruptions (alerts, page updates, etc.) can be postponed or suppressed by the user.
2.2.5 Re-authenticating
(Level AAA)
  • If an authentication session expires, the user can re-authenticate and continue the activity without losing any data from the current page.

Guideline 2.3
Seizures: Do not design content in a way that is known to cause seizures

Success Criteria WebAIM’s Recommendations
2.3.1 Three Flashes or Below Threshold
(Level A)
2.3.2 Three Flashes
(Level AAA)
  • No page content flashes more than 3 times per second.

Guideline 2.4
Navigable: Provide ways to help users navigate, find content, and determine where they are

Success Criteria WebAIM’s Recommendations
2.4.1 Bypass Blocks
(Level A)
  • A link is provided to skip navigation and other page elements that are repeated across web pages.
  • If a page has a proper heading structure, this may be considered a sufficient technique instead of a “Skip to main content” link. Note that navigating by headings is not yet supported in all browsers.
  • If a page uses frames and the frames are appropriately titled, this is a sufficient technique for bypassing individual frames.
2.4.2 Page Titled
(Level A)
  • The web page has a descriptive and informative page title.
2.4.3 Focus Order
(Level A)
  • The navigation order of links, form elements, etc. is logical and intuitive.
2.4.4 Link Purpose (In Context)
(Level A)
  • The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and its context (e.g., surrounding paragraph, list item, table cell, or table headers).
  • Links (or form image buttons) with the same text that go to different locations are readily distinguishable.
2.4.5 Multiple Ways
(Level AA)
  • Multiple ways are available to find other web pages on the site – at least two of: a list of related pages, table of contents, site map, site search, or list of all available web pages.
2.4.6 Headings and Labels
(Level AA)
  • Page headings and labels for form and interactive controls are informative. Avoid duplicating heading (e.g., “More Details”) or label text (e.g., “First Name”) unless the structure provides adequate differentiation between them.
2.4.7 Focus Visible
(Level AA)
  • It is visually apparent which page element has the current keyboard focus (i.e., as you tab through the page, you can see where you are).
2.4.8 Location
(Level AAA)
  • If a web page is part of a sequence of pages or within a complex site structure, an indication of the current page location is provided, for example, through breadcrumbs or specifying the current step in a sequence (e.g., “Step 2 of 5 – Shipping Address”).
2.4.9 Link Purpose (Link Only)
(Level AAA)
  • The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone.
  • There are no links (or form image buttons) with the same text that go to different locations.
2.4.10 Section Headings
(Level AAA)
  • Beyond providing an overall document structure, individual sections of content are designated using headings, where appropriate.

Content and interface are understandable

Guideline 3.1
Readable: Make text content readable and understandable

Success Criteria WebAIM’s Recommendations
3.1.1 Language of Page
(Level A)
  • The language of the page is identified using the HTML lang attribute (<html lang=”en”>, for example).
3.1.2 Language of Parts
(Level AA)
  • The language of page content that is in a different language is identified using the lang attribute (e.g., <blockquote lang=”es”>).
3.1.3 Unusual Words
(Level AAA)
  • Words that may be ambiguous, unknown, or used in a very specific way are defined through adjacent text, a definition list, a glossary, or other suitable method.
3.1.4 Abbreviations
(Level AAA)
  • Expansions for abbreviations are provided by expanding or explaining the definition the first time it is used, using the <abbr> element, or linking to a definition or glossary. NOTE: WCAG 2.0 gives no exception for regularly understood abbreviations (e.g., “HTML” on a web design site must always be expanded).
3.1.5 Reading Level
(Level AAA)
  • A more understandable alternative is provided for content that is more advanced than can be reasonably read by a person with roughly 9 years of primary education.
3.1.6 Pronunciation
(Level AAA)
  • If the pronunciation of a word is vital to understanding that word, its pronunciation is provided immediately following the word or via a link or glossary.

Guideline 3.2
Predictable: Make Web pages appear and operate in predictable ways

Success Criteria WebAIM’s Recommendations
3.2.1 On Focus
(Level A)
  • When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.
3.2.2 On Input
(Level A)
  • When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time.
3.2.3 Consistent Navigation
(Level AA)
  • Navigation links that are repeated on web pages do not change order when navigating through the site.
3.2.4 Consistent Identification
(Level AA)
  • Elements that have the same functionality across multiple web pages are consistently identified. For example, a search box at the top of the site should always be labeled the same way.
3.2.5 Change on Request
(Level AAA)
  • Substantial changes to the page, the spawning of pop-up windows, uncontrolled changes of keyboard focus, or any other change that could confuse or disorient the user must be initiated by the user. Alternatively, the user is provided an option to disable such changes.

Guideline 3.3
Input Assistance: Help users avoid and correct mistakes

Success Criteria WebAIM’s Recommendations
3.3.1 Error Identification
(Level A)
  • Required form elements or form elements that require a specific format, value, or length provide this information within the element’s label.
  • If utilized, form validation errors are presented in an efficient, intuitive, and accessible manner. The error is clearly identified, quick access to the problematic element is provided, and user is allowed to easily fix the error and resubmit the form.
3.3.2 Labels or Instructions
(Level A)
  • Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, properly positioned form labels, and/or fieldsets/legends.
3.3.3 Error Suggestion
(Level AA)
  • If an input error is detected (via client-side or server-side validation), provide suggestions for fixing the input in a timely and accessible manner.
3.3.4 Error Prevention (Legal, Financial, Data)
(Level AA)
  • If the user can change or delete legal, financial, or test data, the changes/deletions can be reversed, verified, or confirmed.
3.3.5 Help
(Level AAA)
  • Provide instructions and cues in context to help in form completion and submission.
3.3.6 Error Prevention (All)
(Level AAA)
  • If the user can submit information, the submission is reversible, verified, or confirmed.

Content can be used reliably by a wide variety of user agents, including assistive technologies

Guideline 4.1
Compatible: Maximize compatibility with current and future user agents, including assistive technologies

Success Criteria WebAIM’s Recommendations
4.1.1 Parsing
(Level A)
4.1.2 Name, Role, Value
(Level A)
  • Markup is used in a way that facilitates accessibility. This includes following the HTML/XHTML specifications and using forms, form labels, frame titles, etc. appropriately.

This checklist is provided as a resource to help implement Web Content Accessibility Guidelines (WCAG) 2.0 (W3C Recommendation 11 December 2008), which is Copyright © 2008 W3C®(MITERCIMKeio), All Rights Reserved. W3C liabilitytrademark and document userules apply.

Read More »

Website Checklist for Section 508 Compliancy

Special thanks to for publishing the first real extensive easy to navigate list of compliancy with simple Pass/Fail explanations. GREAT JOB! Original found here:

Part 1: HTML

The following standards are excerpted from Section 508 of the Rehabilitation Act, §1194.22. The pass/fail criteria in this document represent an interpretation of Section 508 web standards. This checklist is NOT official Section 508 documentation. For the full text of Section 508, please see theofficial government 508 web site.

(a) A text equivalent for every non-text element shall be provided (e.g., via “alt”, “longdesc”, or in element content). Every image, applet, embedded media, plug-in, etc. that conveys content has equivalentalternative text (alt,longdesc, or in the element context). A non-text element has no altor text description or the description is not equivalent, or is not described in the adjacent text.
The alternative text succinctly describes the content conveyed by the element, without being too verbose (for simple objects) or too vague (for complex objects). Alternative texts are verbose (“picture of…”, “image of…”, etc.), vague, misleading, inaccurate, or redundant to the context (e.g. the alt text is the same as adjacent text).
Complex graphics (graphs, charts, etc.) are accompanied by equivalent text, either through a description in the body of the page, a link to a description on a separate page, and/or thelongdesc attribute. [See Note 1] Complex graphics have no alternative text or the alternative does not fully convey the content of the graphic.
Images that have a function (images within links, image buttons, and image map areas) have alternative text which describes the associated function. Alternative texts for linked images, image buttons, or hot spots are not descriptive of the function.
Decorative graphics are CSS background images or have null/empty alt values (alt=""). Images with text alternatives in element content are given empty alt text to avoid redundancy. Decorative graphics have alternatives of “spacer”, “decorative graphic,” or other extraneous text. Graphics have alt text that is redundant with adjacent text.
Transcripts are provided for audio content. Audio does not have transcripts.
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. Video files and live audio broadcasts have synchronizedcaptions. Video files or live audio broadcasts do not have captions or captions are not synchronized.
Content presented through video, but not through audio is provided in an audio description track. Audio descriptions are not provided for visual-only content in multimedia.
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. Color is not used solely to convey important information. Color is the sole means of conveying information.
Sufficient contrast is provided. Contrast is poor.
(d) Documents shall be organized so they are readable without requiring an associated style sheet. Style sheets may be used for layout, but the document is still readable and understandable (even if less visually appealing) when the style sheet is turned off. The document is confusing or information is missing when the style sheet is turned off.
(e) Redundant text links shall be provided for each active region of a server-side image map. Client-side image maps are used instead of server-side image maps. Appropriate alternative text is provided for the image as well as each hot spot area. Server side image maps or inaccessible client-side image maps are present.
(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
(g) Row and column headers shall be identified for data tables. Data tables have column and/or row headers appropriately identified (using the <th>element). Data tables have no header rows or columns.
Tables used strictly for layout purposes do NOT use the <th>element. Tables used for layout have headers identified when there are no true headers.
(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. Data table cells are associated with the appropriate headers using the scope orid/headers attributes. Data table cells are not associated with column and/or row headers or they are associated incorrectly.
(i) Frames shall be titled with text that facilitates frame identification and navigation. Each frame is given a titlethat describes the frame’s purpose or content. Frames have no title or atitle that is not descriptive of the frame’s purpose or content.
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. No element on the page flashes at a rate of 2 to 55 cycles per second, thus reducing the risk of optically-induced seizures. One or more elements on the page flicker at a rate of 2 to 55 cycles per second, increasing the risk of optically-induced seizures.
(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. text-only version is created only when there is no other way to make the content accessible or when it offers significant advantages over the main version for certain disability types. A text-only version is provided when the main version is not accessible, but could be made fully accessible.
The text-only version provides equivalent content and is up-to-date with the main version. The text-only version is not equivalent to or up-to-date with the main version.
(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. Content and functionality provided by scripting is directly accessible to assistive technologies and the keyboard.<noscript> content does not constitute a suitable alternative to inaccessible scripting. Content and functionality provided by scripts only work with a mouse or cannot be accessed by assistive technologies.
(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l). [See Note 2] [See Note 3] A link is provided to a page where the plug-in can be downloaded. No link is provided to a page where the plug-in can be downloaded.
All applets, scripts and plug-ins (including PDF and PowerPointfiles, etc.) and the content within them are accessible to assistive technologies, or else an alternative means of accessing equivalent content is provided. Inaccessible plug-ins, scripts, and other applications are used without providing an accessible alternative.
(n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. <input><textarea>, and<select> elements have descriptive labels. There is no association between the form element and its label.
Scripting of form elements does not interfere with assistive technologies or keyboard. Scripting makes parts of the form unavailable to assistive technologies or keyboard users.
(o) A method shall be provided that permits users to skip repetitive navigation links. A link is provided to skip overnavigational menus or other lengthy lists of links. A good heading structure also facilitates navigation. There is no way to skip over repetitive lists of links.
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. The user has control over the timing of content changes. The user is required to react within limited time constraints.

Note 1: Until the longdesc attribute is better supported, it is best to use it in conjunction with a standard link to a longer description. Note 2: Standalone media players are usually more accessible than embedded media players. Note 3: A PDF file can be made accessible to screen reader users, but it may be best to include an accessible HTML version of a document instead of or in addition to PDF. Accessible alternatives must be provided for PowerPoint files.

Part 2: Scripts, Plug-ins, Java, etc.

The following standards are excerpted from Section 508 of the Rehabilitation Act, §1194.21. Full text of Section 508.

(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.
(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.
(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes.
(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology. When an image represents a program element, the information conveyed by the image must also be available in text.
(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application’s performance.
(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes.
(g) Applications shall not override user selected contrast and color selections and other individual display attributes.
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.
(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided.
(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.
(l) When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
Read More »