End to End analysis of Guideline 2.1

Analysis of the table below:

It appears the Technology Independent Doc is getting pretty HTML specific with the "META Refresh" line. We don't have any techniques to stop the flashing and blinking.

  Guideline Technology Independent
Doc		 HTML Techniques CSS
Guideline 2.2
2.2: Allow users to control time limits on their reading or interaction unless specific real-time events or rules of competition make such control impossible.


 

    
Success Criteria 1: Content is designed so that time limits are not an essential part of interaction, or at least one of the following is true for each time limit: [I]
  • the user is allowed to deactivate the time limit or;
  • the user is allowed to adjust the time limit over a wide range which is at least ten times the length of the default setting or;
  • the user is warned before time expires, allowed to extend the time limit with a simple action (for example, "hit any key") and given at least 10 seconds to respond or;
  • the time limit is an important part of a real-time event (for example, an auction), and no alternative to the time limit is possible or;
  • the time limit is part of an activity where timing is essential (for example, competitive gaming or time-based testing) and time limits can not be extended further without invalidating the activity.

2.2.1

Task:

Ensure that users can control any time limits on their reading, interaction, or responses unless control is not possible due to nature of real time events or competition.

 

 

Content developers sometimes create pages that refresh or change without the user requesting the refresh. This automatic refresh can be very disorienting to some users. Instead, in order of preference, authors should:
  1. Configure the server to use the appropriate HTTP status code (301). Using HTTP headers is preferable because it reduces Internet traffic and download times, it may be applied to non-HTML documents, and it may be used by agents who requested only a HEAD request (e.g., link checkers). Also, status codes of the 30x type provide information such as "moved permanently" or "moved temporarily" that cannot be given with META refresh.
  2. Replace the page that would be redirected with a static page containing a normal link to the new page.
 

1.2 Task:

Avoid using meta http-equiv of "refresh; url=... "to automatically redirect users.

1.3 Meta refresh

Task:

Avoid using meta http-equiv of "refresh" to periodically refresh pages.

 

 		 N/A
Success Criteria 2: Level 2 : The user is allowed to turn off content that blinks for more than 3 seconds.    

1.13 Text style effects

Task:

@@

The following CSS2 properties can be used to style text:
  • Case: 'text-transform' (for uppercase, lowercase, and capitalization).
  • Shadow effects: 'text-shadow'
  • Underlines, overlinks, blinking: 'text-decoration'.

Note. If blinking content (e.g., a headline that appears and disappears at regular intervals) is used, provide a mechanism for stopping the blinking. In CSS, 'text-decoration: blink' will cause content to blink and will allow users to stop the effect by turning off style sheets or overriding the rule in a user style sheet. Do not use the BLINK and MARQUEE elements. These elements are not part of any W3C specification for HTML (i.e., they are non-standard elements).
Success Criteria 2:

Level 2 : The user is allowed to pause and/or permanently stop moving or time-based content.

 none    
Success Criteria 3: Level 3 : The content has been designed in a way that any time limits in the content would pass level 1, success criteria 1 for this guideline without exceptions.      
Success Criteria 3: Level 3 : Any non-emergency interruptions, such as the availability of updated content, can be postponed and/or suppressed by the user.      
Informative

 

Who Benefits from Guideline 2.2 (Informative)

  • People with reading disabilities, cognitive disabilities, and learning disabilities often need more time than most people to read and comprehend written text.
  • People with physical disabilities can access content that is updated often in cases where content might not be processed and read before being refreshed or when read out of order an assistive technology or voice browser.

Examples of Guideline 2.2 (Informative)

  • Examples of content that must meet the success criteria of this checkpoint:
    • automatic refresh,
    • redirection,
    • blinking or scrolling text,
    • dialog that disappears ater a short period,
    • shutdown or deactivation of resource if activity is not received in a set amount of time.
  • Example 1: blinking text.

    Client-side scripting is used to create blinking text. The content provides an option that allows the user to turn off the blinking.

  • Example 2: a news site that is updated regularly.

    A news site causes its front page to be updated every half hour. The front page contains minimal text and primarily consists of links to content. A user who does not wish the page to update selects a checkbox. The checkbox is in the "user preferences" portion of the site which is one of the first links on each page.

 		 The part above addresses this information