MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_01CE418B.A27836D0" This document is a Single File Web Page, also known as a Web Archive file. If you are seeing this message, your browser or editor doesn't support Web Archive files. Please download a browser that supports Web Archive, such as Windows® Internet Explorer®. ------=_NextPart_01CE418B.A27836D0 Content-Location: file:///C:/5D65A114/wcag2-aaa-worksheet.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" TEXT ALTERNATIVES

WCAG 2.0 Level = AAA Compliance Worksheet

 

This worksheet has been prepared in= the form of checklist to allow web site developers and testers to record the le= vel of compliance by Website or Web pages with the Success Criteria of the Web Content Accessibility Guidelines Version 2.0 (WCAG 2.0).

 

The worksheet is a complicated tabl= e and apologies for its lack of accessibility. Please feel free to improve, modify and use the table as you wish.

 

The table contains the all the WCAG= 2.0 normative Success Criteria, which are the requirements for complying with WCAG 2.0 at Level AAA. Next to each Success Criterion, are the Sufficient Techniques fr= om the informative "How to Meet WCAG 2.0" document that provide advi= ce on how to comply with that criterion.

 

The Checklist is presented as a Word document. The Success Criteria and Sufficient Techniques are presented in t= able rows so that the document can be easily modified by users to meet differing situations. For example, to convert the document into a Level A worksheet, = delete the Level AA and AAA Success Criteria and associated Sufficient Techniques.= Similarly, for each Success Criterion the rows containing Sufficient Techniques that do not apply can be deleted.

 

The first page of the document cont= ains a form which can be used to record basic information about the Website for us= e in preparing a formal Accessibility Conformance Statement.

 

Support= ing information:

·      =    "Web Content Accessibility Guidelines (WCAG 2.0)" W3C Recommendation 11 December 2008, available at http:/= /www.w3.org/TR/WCAG20/

·         "How to Meet WCAG 2.0" reference document, which contain suggested techniqu= es for each Success Criteria, available at http://www.w3.org/WAI/WCAG2= 0/quickref/ 

·         "Understanding WCAG 2.0", available at http://www.w3.org/TR/UN= DERSTANDING-WCAG20/

·         "Understanding Accessibility Support", available at http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformanc= e.html#uc-accessibility-support-head

·         Information about "Conformance Requirements" available at http://www.w3.org/TR= /WCAG20/#conformance-reqs

 

This document was created by Roger Hudson using the Web Content Accessibility Guidelines and other material prepared by the W3C. Please send feedback and any suggestions about errors and omissions to rhudson@usability.com.au<= /o:p>


Content:

 

WCAG 2.0 Accessibility Compliance.. 3

Accessibility Support documentation. 3

Principle 1: Perceivable - Information and user int= erface components must be presentable to users in ways they can perceive. = 4

Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. 4

Guideline 1.2 Time-based Media: Provide alternative= s for time-based media. 6

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

Guideline 1.4 Distinguishable: Make it easier for u= sers to see and hear content including separating foreground from background  <= !--[if supportFields]>= PAGEREF _Toc220806374 \h 13

Principle 2: Operable – User interface compon= ents and navigation must be operable. 21

Guideline 2.1 Keyboard Accessible: Make all functio= nality available from the keyboard. 21

Guideline 2.2 Enough Time: Provide users enough tim= e to read and use content. 22

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

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

Principle 3: Understandable – Information and= the operation of user interface must be understandable. 32

Guideline 3.1 Readable: Make content readable and understandable. 32

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

Guideline 3.3 Input Assistance: Help users avoid and correct mistakes. 38

Principle 4: Robust – Content must be robust = enough that it can interpreted reliably by a wide variety of user agents, including assistive technologies. 44

Guideline 4.1 Compatible: Maximise compatibility wi= th current and future user agents, including assistive technologies  <= !--[if supportFields]>= PAGEREF _Toc220806385 \h 44

 

 


WCAG 2.0 Accessibil= ity Compliance

 

Website Name:<= /b>

URL:

Website Owner:=

Website author(s):

Scope of assessment <= span lang=3DEN-AU style=3D'font-family:"Arial","sans-serif"'>(if not entire site= ):

 

Tested by (name/organisation):

Test date:=

Compliance Level:

Accessibility Support documentation

(Only Accessibility Supported uses of Web Content technologies ca= n be used to comply with WCAG 2.0)

 

1. This = site relies on the following Accessibility Supported Technologies:

·         W3C Technologies (e.g. HTML, CSS):

·         Non-W3C Technologies (e.g. PDF, JavaScript):=

&nb= sp;

2. Accessibility Supported Technologies authorised by:

·         Name:

·         Organisation (e.g. owner, regulator):

 

3. Web C= ontent Technologies used, but not relied on:

&nb= sp;

&nb= sp;

&nb= sp;

4. Suppo= rted browsers/plugins:

(include versions & operating systems) =

&nb= sp;

&nb= sp;

&nb= sp;

5. Test Assistive Technologies (where appropriate):

(include version, operating systems, features supported and any k= nown limitations in the support of technology features)

 


Principle 1: Perceivable - Information and user interface components must be presentable= to users in ways they can perceive.

Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

1= .1.1 Non-text content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below.

·    <= /span>Controls, Input: then it has a name that describe= s its purpose.

·    <= /span>Time-Based Media: then text alternatives at least = provide descriptive identification of the non-text content.

·    <= /span>Test: then text alternatives at least provide descr= iptive identification of the non-text content.

·    <= /span>Sensory: then text alternatives at least provide descr= iptive identification of the non-text content.

·    <= /span>CAPTCHA: then text alternatives that identify and desc= ribe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes are provided to accommodate different disabilities.

·    Decoration, Formatting, Invisible: then it is implemented in a way that it can be ignored by assistive technology.

S= ituation A: If short desc= ription can serve the same purpose and present the same information

G94: Prov= iding short text alternative for non-text content using a short text alternative technique listed below:

 

 

 

H36: Alt attributes on images used as= submit buttons

 

 

 

H2:<= /span> Combining  image and text links for the same resource

 

 

 

H37: Alt attributes on img elements <= /span>

 

 

 

H35: Text alternatives on applet elem= ents

 

 

 

H53: Using the body of the object ele= ment

 

 

 

H24: Text alternatives for the area e= lements of image maps

 

 

 

H86: Text alterns for ASCII art, emot= icons, and leetspeak

 

 

 

H30: Link text that describes the pur= pose of a link for anchor elements

 

 

 

G196:<= /a> Text alternative on one item with= in a group of images that describes all items in the group

 

 

 

S= ituation B: I= f a short description can not serve the same purpose and present the same information as the non-text content (e.g. a chart or diagram):

G95: Provide short text alternatives = (see above) AND one of the following techniques for long description: <= /span>

 

 

 

G92: Long description for non-text con= tent using longdesc (H45) or  bod= y of the object element (H53)

 

 

 

G74: Long description in text near the non-text content

 

 

 

G73: Long description in another loca= tion with a link to it that is immediately adjacent to the non-text content

 

 

 


Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content (= page 2)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

See above

See above

1= .1.1 Non-text content (cont): = All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below (details on previous page).

·    <= /span>Controls, Input:

·    <= /span>Time-Based Media:

·    <= /span>Test:

·    <= /span>Sensory:

·    <= /span>CAPTCHA:

·    <= /span>Decoration, Formatting, Invisible= :

 

S= ituation C: If non-text c= ontent is a control or accepts user input:

G82: Provide a short text alternative= using a short text alternative technique (see above)

 

 

 

H44: Label elements to associate text= labels with form controls

 

 

 

H65: Title attribute to identify form controls when the label element cannot be used

 

 

 

S= ituation D: If non-text c= ontent is time-based media (including live video and audio); a test or exercise = that would be invalid if presented in text; or primarily intended  to create a specific sensory experience:

Prov= ide a descriptive label using a short text alternative technique (see above)

 

 

 

G68: Label that describes the purpose= of live audio-only and live video-only content using a short text alternative

 

 

 

G100:<= /a> Provide the accepted name or a descriptive name of the non-text content using a short text alternative <= /span>

 

 

 

S= ituation E: If non-text c= ontent is a CAPTCHA:

G143:<= /a> Text alternative that describes = the purpose of the CAPTCHA AND

G144:<= /a> Ensure the Web Page contains ano= ther CAPTCHA with the same purpose using a different modality

 

 

 

S= ituation F: If the non-te= xt content should be ignored by assistive technology:

H67: Null alt text and no title attri= bute on img elements for images that AT should ignore

 

 

 

C9:<= /span> Using CSS to include decorative = images

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 


Guideline 1.2 Time-based Media: Provide alternat= ives for time-based media

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

1.2.1 Audio only and Video only: For prerecorded audio-only and video-only media, the following are true, exce= pt when the audio or video is a media alternative for text and is clearly labelled as such:

&midd= ot;    <= /span>Prerecorded Audio-only: An alternative for time-based me= dia is provided that presents equivalent information for prerecorded audio conte= nt.

·    <= /span>Prerecorded Video-only: Either an alternative for time-b= ased media or an audio track is provided that presents equivalent information = for prerecorded video content.

G= 158: Providing a transcript for prerecorded audio only

 

 

 

G= 159:  Providing a transcript for prerecorded video o= nly

 

 

 

G166:<= /a> Providing audio that describes the important video content and describing it as such

 

 

 

BLANK<= /span>

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

A

Yes __

No __

1.2.2 Captions (prerecorded): Cap= tions are provided for all prerecorded audio content in synchronized media, exc= ept when media is a media alternative for text and is clearly labelled as suc= h.

G9= 3: Providing open (always visi= ble) captions

 

 

 

G8= 7:  Providing closed captions USING availab= le media format that has a video player that supports closed captioning

 

 

 

G8= 7:  Providing closed captions USING any of = the technology specific techniques below

SM11:<= /a> Captions through synchronized te= xt in SMIL 1.0  =

SM12:<= /a> Captions through synchronized te= xt in SMIL 2.0

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 


Guideline 1.2 Time-based Media: Provide alternatives for time-based media (page 2)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

1.2.3 Audio Description or Media Alternative (Prerecorded): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when media is a media alternative for text and is clearly labeled as such.

G6= 9: Providing an alternative for time-based media using one of

G58: Placing a link to the alternative for time-based media immediately next to the non-text content= , OR

Link to alternative with H53: Use the body of the object element  

 

 

 

G7= 8: Providing a second user-selectable audio track with audio description

 

 

 

G173:<= /a> Providing a version of a movie w= ith audio descriptions using one of:

SM6: Providing audio description in SMIL 1.0

SM7: Providing audio description in SMIL 2.0

 

 

 

G8:= Provide movie with extended audio description<= /span> using one of: =

SM1: Adding extended audio description in SMIL 1.0

SM2: Adding extended audio description in SMIL 2.0

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

AA

Yes __

No __

1= .2.4 Captions (Live): Captions are provided for all live audio content in synchronized media.=

G9= : Captions for live synchronized m= edia AND

G93: Provide open (always visible) ca= ptions

 

 

 

G9:= Captions for live synchronized m= edia AND

G87: Provide closed captions using re= adily available media format with video player that supports closed captioning =

 

 

 

G9:= Captions for live synchronized m= edia AND

G87: Provide closed captions using on= e of the following:

SM11:<= /a> Captions through synchronized text in SMIL 1.0 

SM12:<= /a> Captions through synchronized text in SMIL 2.0

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 


Guideline 1.2 Time-based Media: Provide alternatives for time-based media (page 3)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AA

Yes __

No __

1.2.5 Audio Description (Prerecorded): Audio description is provi= ded for all prerecorded video content in synchronized media.

G7= 8: Providing a second user-selectable audio track with audio description

 

 

 

G173:<= /a> Providing a version of a movie w= ith audio descriptions using one of:

SM6: Providing audio description in SMIL 1.0

SM7: Providing audio description in SMIL 2.0

 

 

 

G8:= Provide movie with extended audio description<= /span> using one of: =

SM1: Adding extended audio description in SMIL 1.0

SM2: Adding extended audio description in SMIL 2.0

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

AAA

Yes __

No __

1.2.6 Sign Language (Prerecorded)= : Sign language interpretation is = provided for all prerecorded audio content in synchronized media.

G5= 4: Including a sign language interp= reter in the video stream

 

 

 

G8= 1: Providing a synchronized video o= f the sign language interpreter that can be displayed in a different viewport or overlaid on the image by the player using one of:

= S= M13: Providing sign language interpre= tation through synchronized video streams in SMIL 1.0

= S= M14: Providing sign language interpre= tation through synchronized video streams in SMIL 2.0

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

AAA

Yes __

No __

1.2.7 Extended Audio Descript= ion (Prerecorded): Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of= a video, extended audio description is provided.

G8:= Provide movie with extended audio description<= /span> using one of: =

SM1: Adding extended audio description in SMIL 1.0

SM2: Adding extended audio description in SMIL 2.0

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

&= nbsp;

 


Guideline 1.2 Time-based Media: Provide alternatives for time-based media (page 4)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AAA

Yes __

No __

1.2.8 Media Alternative (Prerecorded): An alternative for time-ba= sed media is provided for all prerecorded synchronized media and for all prerecorded video-only media.

S= ituation A: If the conten= t is prerecorded synchronized media:

G6= 9: Providing an alternative for time-based media using one of

G58: Placing a link to the alternative for time-based media immediately next to the non-text content= , OR

Link to alternative with H53: Use the body of the object element

 

 

 

S= ituation B: If the conten= t is prerecorded video-only:

G= 159:  Providing a transcript for prerecorded video o= nly

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

&= nbsp;

 

 

AAA

Yes __

No __

1.2.9 Live audio-only: A t= ext alternative that presents equivalent information for live audio-only cont= ent is provided.

G= 151:  Providing a link to a text transc= ript of a prepared statement or script if the script is followed

 

 

 

G= 150: Providing text alternatives for live audio-on= ly content

 

 

 

G= 157: Incorporating a live audio captioning service into a Web page=

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

&= nbsp;

 

 

 


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

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

1.3.1 Info and Relationships:= Information, structure, and relationships conveyed through presentation c= an be programmatically determined or are available in text.

S= ituation A: The technology provides semantic structure to make information and relationships conveyed through presentation programmatically determinable:

G= 115: Using semantic elements to markup structure AND H4= 9: Using semantic markup to mark emphasized or special text

 

 

 

G117:<= /a> Using text to convey information that is conveyed by variations in presentation of text=

 

 

 

G= 140: Separating information and structure from presentation so that Web pages can be presented different = ways without losing information

 

 

 

Make info and relationships conveyed through presentation programmatically determinable using the following:

G138:<= /a> Using semantic marku= p when color cues are used

 

 

 

H5= 1: Using table markup to prese= nt tabular information

 

 

 

H39: Using caption elemen= ts to associate data table captions with data tables

 

 

 

H7= 3: Using the summary attribute of the table element to give an overvie= w of data tables.

 

 

 

H6= 3: Using the scope attribute to associate header cells and data cells in data tables

 

 

 

H4= 3: Using id and headers attrib= utes to associate data cells with header cells

 

 

 

H4= 4: Using label elements to associate text labels with form controls

 

 

 

H6= 5: Using the title attribute to identify form controls when the label element cannot be used

 

 

 


Guideline 1.3 Adaptable: Create content that can be presented in different ways without losing information or structure (page 2)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

See above

See above

1.3.1 Info and Relationships:= (Cont)

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available = in text.<= /span>

H7= 1: Provid= ing a description for groups of form controls using fieldset and legend element= s

 

 

 

H8= 5: Using = OPTGROUP to group OPTION elements inside a SELECT

 

 

 

H4= 8: Using ol, ul and dl for lists

 

 

 

H4= 2: Using h1-h6 to identify headings

 

 

 

= SCR21: Using functions of the Document Object Model (DOM) to add content to a page

 

 

 

S= ituation B: The technolog= y in use does NOT provide the semantic structure to make the information and relationships conveyed through presentation programmatically determinable= :

G117:<= /a> Using text to convey information that is conveyed by variations in presentation of text=

 

 

 

Making information and relationships conveyed through presentation programmatica= lly determinable or available in text using the following techniques:<= /p>

T1: = Using standard text formatting conventions for paragraphs

 

 

 

T2: = Using standard text formatting conventions for lists 

 

 

 

T3: = Using standard text formatting conventions for headings 

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 

 

 


Guideline 1.3 Adaptable: Create content that can be presented in different ways without losing information or structure (page 3)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

1.3.2 Meaningful Sequence:= When the sequence in which conte= nt is presented affects its meaning, a correct reading sequence can be programmatically determined.

G5= 7: Ordering the con= tent in a meaningful sequence for all the content in the Web page

 

 

 

Mark= ing sequences in the content as meaningful using one of the following techniq= ues AND G57: for those sequences

H3= 4: Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) to m= ix text direction inline (HTML)

H5= 6: Using the dir attribute on an inline element to resolve problems with nested directional runs (HTML)

C6:= Positioning content based on structural markup (CSS)

C8:= Using CSS letter-spacing to control spacing within a word (CSS)

 

 

 

C27: Making the DOM order match the v= isual order

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

A

Yes __

No __

1.3.3 Sensory Characteristics: Instructions provided for unders= tanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

G9= 6: Providing textual identification of items that otherwise rely only on sensory information t= o be understood

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 

 


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

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

1.4= .1 Use of Color: Color is not used as the o= nly visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

S= ituation A: If the color = of particular words, backgrounds, or other content is used to indicate information:

G1= 4: Ensuring that information conveyed by colour differences is also available in text

 

 

 

G= 122: Including a text cue whenever colour cues are used

 

 

 

G182:<= /a> Ensuring that additional visual = cues are available when text color differences are used to convey information=

 

 

 

G183:<= /a> Using a contrast ratio of 3:1 wi= th surrounding text and providing additional visual cues on focus for links = or controls where color alone is used to identify them

 

 

 

S= ituation B: If color is u= sed within an image to convey information:

G= 111: Using colour and pattern

 

 

 

G1= 4: Ensuring that information conveyed by colour differences is also available in text

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

A

Yes __

No __

1.4.2 Audio Control: <= span lang=3DEN-AU style=3D'font-size:11.0pt'>If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio vol= ume independently from the overall system volume level.

G6= 0: Playing a sound = that turns off automatically within three seconds =

 

 

 

G170:<= /a> Providing a control = near the beginning of the Web page that turns off sounds that play automatically

 

 

 

G171:<= /a> Playing sounds only = on user request

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 = Guideline 1.4 Distinguishable: Make it easier for users to see and hear content (page 2)<= o:p>

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AA

Yes __

No __

1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least = 4.5:1, except for the following:

·        Large print

·        Incidental text or images <= /p>

·     &nbs= p;  Logotypes

S= ituation A: text is less = than 18 point if not bold and less than 14 point if bold

G1= 8: Ensuring that a contrast ra= tio of at least 4.5:1 exists between text (and images of text) and background behind the text

 

 

 

G148:<= /a> Not specifying background color,= not specifying text color, and not using technology features that change those defaults

 

 

 

G174:<= /a> Provide control with= a sufficient contrast ratio that allows users to switch to a presentation t= hat uses sufficient contrast

 

 

 

Situation B: text is as least 18 point if not bold and at least 14 point= if bold

G= 145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text

 

 

 

G148:<= /a> Not specifying background color,= not specifying text color, and not using technology features that change those defaults

 

 

 

G174:<= /a> Provide control with= a sufficient contrast ratio that allows users to switch to a presentation t= hat uses sufficient contrast

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 


Guideline 1.4 Distinguishable: Make it easier for users to see and hear content (page= 3)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AA

Yes __

No __

1.4.4 Resize text:= Except for captions and images of text, text = can be resized without assistive technology up to 200 percent without loss of content or functionality.

G= 142: Using a technology that has commonly-available user agents that support zoom.

 

 

 

Ensu= ring that text containers resize when the text resizes AND using measurements = that are relative to other measurements in the content by using one or more of= the following techniques:

 

 

 

C2= 8: Specifying the size of text cont= ainers using em units

 

 

 

Tech= niques for relative measurements

C12: Using percent for font sizes 

C13: Using named font sizes 

C14: Using em units for font sizes  =

 

 

 

Tech= niques for text container resizing

SCR34= : Calculating size and position in a way that scales with text size 

G146:<= /a> Using liquid layout

 

 

 

G178:<= /a> Providing controls o= n the Web page that allow users to incrementally change the size of all text on= the page up to 200 percent

 

 

 

G179:<= /a> Ensuring that there = is no loss of content or functionality when the text resizes and text container= s do not resize

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 


Guideline 1.4 Distinguishable: Make it easier for users to see and hear content (page= 4)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AA

Yes __

No __

1.4.5 Images of text:<= /b> If the technologies being used can achieve the visual presentation, text is used to convey information rather than image= s of text except for the following:

·    Cu= stomizable: The image of text = can be visually customized to the user's requirements;

·    <= /span>Essential: A particular presentation of text is essential to the information being conveyed.

C2= 2: Using CSS to control visual pres= entation of text

 

 

 

 

C3= 0: Using CSS to replace text with i= mages of text and providing user interface controls to switch

 

 

 

G= 140: Separating information and structure from presentation so that Web pages can be presented different = ways without losing information

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

AAA

Yes __

No __

1.4.6 Contrast (Enhanced): The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following:

·    Large print

·    Incidental text or images <= /p>

·    <= /span>Logotypes

S= ituation A: text is less = than 18 point if not bold and less than 14 point if bold

G1= 7: Ensure a contrast ratio of = at least 7:1 exists between text (and images of text) and background behind = the text

 

 

 

G148:<= /a> Not specifying background color,= not specifying text color, and not using technology features that change those defaults

 

 

 

G174:<= /a> Provide control with= a sufficient contrast ratio that allows users to switch to a presentation t= hat uses sufficient contrast

 

 

 

Situation B: text is as least 18 point if not bold and at least 14 point= if bold

G1= 8: Ensuring that a contrast ra= tio of at least 4.5:1 exists between text (and images of text) and background behind the text=

 

 

 

G148:<= /a> Not specifying background color,= not specifying text color, and not using technology features that change those defaults

 

 

 

G174:<= /a> Provide control with= a sufficient contrast ratio that allows users to switch to a presentation t= hat uses sufficient contrast

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 


Guideline 1.4 Distinguishable: Make it easier for users to see and hear content (page= 5)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AAA

Yes __

No __

1.4.7 Low or No Background Audio:= For audio content that (1) contai= ns primarily speech in the foreground, (2) is not an audio CAPTCHA or audio login, and= (3) is not vocalisation intended to be primarily musical expression such as signing or rapping, at least one of the following is true:

·    <= span lang=3DEN-AU style=3D'font-size:11.0pt;mso-bidi-font-style:italic'>No Bac= kground: The audio does not contain background sounds.

·    <= span lang=3DEN-AU style=3D'font-size:11.0pt;mso-bidi-font-style:italic'>Turn O= ff: The ba= ckground sounds can be turned off.

·    <= /span>20 dB: The background soun= ds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last only one or two seconds.

G5= 6: Mixing audio fil= es so that non-speech sounds are at least 20 decibels lower than the speech aud= io content

 

 

 

 

BLAN= K

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 


Guideline 1.4 Distinguishable: Make it easier for users to see and hear content (page= 6)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AAA

Yes __

No __

1.4.8 Visual Presentation:= For the visual presentation of b= locks of text, a mechanism is available to achieve the following:

1.      foregr= ound and background colors can be selected by the user

2.      width = is no more than 80 characters or glyphs (40 if CJK)

3.      text i= s not justified (aligned to both the left and the right margins)

4.      line s= pacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing

5.=       text can be resized without assistive technol= ogy up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window

Instructions: Since this is a multi-part success criterion, you must satisfy on= e of the numbered items for each of the requirements below.<= /p>

First Requirement: Techniques to ensure foreground and background colors can be selected by the user

1.     &nbs= p; C23: Specify text and bg colors of se= condary content in CSS while not specifying text and bg colors of main content  OR

 

 

 

2.     &nbs= p; C2= 5: Specify borders and layout in CS= S to delineate areas of page while not specifying text and text-bg colors  OR

 

 

 

3.     &nbs= p; G= 156: Using a technology that has commonly-available user agents that can change the foreground and bg of blocks of text OR

 

 

 

4.     &nbs= p; G148:<= /a> Not specifying bg color, not spe= cifying text color, and not using technology features that change those defaults = OR

 

 

 

5.     &nbs= p; G= 175: Providing a multi color selectio= n tool on the page for foreground and background colors

 

 

 

S= econd Requirement: Tec= hniques to ensure width is no more than 80 characters or glyphs (40 if CJK)<= /o:p>

1.     &nbs= p; H8= 7: Not interfering with the user ag= ent's reflow of text as the viewing window is narrowed OR

 

 

 

2.     &nbs= p; C2= 0: Use relative measurements to set= column widths so that lines average 80 characters or less when browser is resized  <= /p>

 

 

 

T= hird Requirement: Tec= hniques to ensure text is not justified (aligned to both the left and the right margins)

1.     &nbs= p; C1= 9: Specify alignment either to left= OR right in CSS OR

 

 

 

2.=       G= 172: Provide mechanism to remove full justification OR

 

 

 

3.=      &nbs= p; G= 169: Align text on only one side

 

 

 


Guideline 1.4 Distinguishable: Make it easier for users to see and hear content (page= 7)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

As above

As above

1.4.8 Visual Presentation: (Cont)=

 For the visual presentation of bl= ocks of text, a mechanism is available to achieve the following:

See Above

F= ourth Requirement: Tec= hniques to ensure line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the l= ine spacing.

G= 188: Providing a button on the page to increase line spaces and paragraph spaces OR

 

 

 

C2= 1: Specifying line spacing in CSS <= o:p>

 

 

 

F= ifth Requirement: Tec= hniques to ensure text can be resized without assistive technology up to 200 perc= ent in a way that does not require the user to scroll horizontally to read a = line of text on a full-screen window

Not interfering with the user agent's reflow of text as the viewing window is narrowed (General, Future Link) OR

 

 

 

G146:<= /a> Using liquid layout AND using measurements that are relative to ot= her measurements in the content by using one or more of the following techniq= ues:

C12: Using percent for font sizes OR

C13: Using named font sizes OR=  

C14: Using em units for font sizes OR  

C24: Using percentage values in CSS f= or container sizes OR

SCR34= : Calculating size and position in a way that scales with text size = OR

 

 

 

C2= 6: Provide options within the conte= nt to switch to a layout that does not require the user to scroll horizontally = to read a line of text

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 

 


Guideline 1.4 Distinguishable: Make it easier for users to see and hear content (page= 8)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AA

Yes __

No __

1.4.9 Images of Text (No Exception): Images of text are only used for pure decoration or where a particular presentation of text is essenti= al to the information being conveyed.

C2= 2: Using CSS to control visual pres= entation of text

 

 

 

C3= 0: Using CSS to replace text with i= mages of text and providing user interface controls to switch

 

 

 

G= 140: Separating information and = structure from presentation so that Web pages can be presented different ways witho= ut losing information

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 

 


Principle 2: Oper= able – User interface components and navigation must be operable.

Guideline 2.1 Keyboard Accessible: Make all functionality available from the keyboard.<= span style=3D'mso-bookmark:_Toc220806376'>

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoint= s.

Ensu= ring keyboard control by using the following;

H91: Using HTML form controls and lin= ks

 

 

 

G9= 0: Providing keyboard-triggered eve= nt handlers using one of the following techniques:

 

 

 

= SCR20: Use both keyboard and other device-specific functions

 

 

 

= SCR35: Making actions keyboard accessib= le by using the onclick event of anchors and buttons 

 

 

 

S= CR2: Using redundant keyboard and mou= se event handlers

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

A

Yes __

No __

2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component using a keyboard interface, then focus can be moved away using only a keyboard, and= , if it requires more than unmodified arrow or= tab keys, the user is advised of method for moving focus away.

G2= 1: Ensuri= ng that users are not trapped in content

 

 

 

&= nbsp;

BLANK<= o:p>

 

 

 

 

 

 

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

AAA

Yes __

No __

2.1.3 Keyboard (No Exception)= : All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

No additional techniques exist for this Success Criterion.

Foll= ow te= chniques for Success Criterion 2.1.1 . If that is not possible because there i= s a requirement for analog, time-dependent input, then it is not possible to = meet this Level AAA Success Criterion.

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 


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

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

2= .2.1 Timing Adjustable: For each time limit that is set by the conten= t, at least one of the following is true:

·         Turn off: The user is allowed to turn off the time limit before encountering it; OR=

·         Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; = OR

·         Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at lea= st ten times; OR

·         Real-time Exception: the time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; OR=

·         Essential Exception: The time limit is essential and extending it would invalidate the activit= y; OR

·         20 Hour Exception: The time limit is longer than 20 hours

S= ituation A: If there are = session time limits:

G= 133: Provid= ing a checkbox on the first page of a multipart form that allows users to ask f= or longer session time limit or no session time limit

 

 

 

G198:<= /a> Providing a way for the user to = turn the time limit off

 

 

 

S= ituation B: If a time lim= it is controlled by a script on the page:

G198:<= /a> Providing a way for the user to turn the time limit off=

 

 

 

G180:<= /a> Providing the user w= ith a means to set the time limit to 10 times the default time limit<= span lang=3DEN-AU style=3D'font-size:10.0pt'>

 

 

 

= SCR16: Provid= ing a script that warns the user a time limit is about to expire AND S= CR1:  Allowing the user to extend the default time limit.

 

 

 

S= ituation C: If there are = time limits on reading:

G4:= Allowing the content to be paused and restart= ed from where it was stopped

 

 

 

G198:<= /a> Providing a way for the user to = turn the time limit off

 

 

 

SCR33= : Using script to scroll content, = and providing a mechanism to pause it

 

 

 

SCR36= : Providing a mechanism to allow u= sers to display moving, scrolling, or auto-updating text in a static window or ar= ea  <= /span>

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 


Guideline 2.2 Enough Time: Provide users enough time to read and use content (page 2)=

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-upda= ting information, all of the following are true:

·         Mo= ving, blinking, scrolling: For any moving, blinking or scrolling informa= tion that (1) starts automatically, (2) lasts more than five seconds, and (3) = is presented in parallel with other content, there is a mechanism to pause, stop, or hide it unless the movement, is part of an essential activity; A= ND

·         Au= to-updating: For any auto-updat= ing information that (1) starts automatically, (2) lasts more than five secon= ds, and (3) is presented in parallel with other content, there is a mechanism= for the user to pause, stop, or hide it or to control the frequency of the up= date unless it is part of an essential activity.

G4:= Allowing the content to be paused and restart= ed from where it was stopped

 

 

 

SCR33= : Using script to scroll content, = and providing a mechanism to pause it

 

 

 

G1= 1: Creating content that blinks for less than 3 seconds

 

 

 

G= 187: Using a technology to include bl= inking content that can be turned off via the user agent

 

 

 

G= 152: Setting animated= gif images to stop blinking after n cycles (within 5 seconds)

 

 

 

= SCR22: Using scripts to control blinkin= g and stop it in five seconds or less

 

 

 

G= 186: Using a control in the Web page = that stops moving, blinking, or auto-updating content

 

 

 

G= 191: Providing a link, button, or oth= er mechanism that reloads the page without any blinking content

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

AAA

Yes __

No __

2.2.3 No Timing: Timing is not an essential part = of the event or activity presented by the content, except for non-interactive synchronized media and real-time events

G5:=  Allowing users to complete an act= ivity without any time limit

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 <= /h3>

Guideline 2.2 Enough Time: Provide users enough time to read and use content (page 3)=

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AAA

Yes __

No __

2.2.4 Interruptions: Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.

G7= 5: Providing a mech= anism to postpone any updating of content

 

 

 

G76: Providing a mechanism to request= an update of the content instead of updating automatically

 

 

 

= SCR14: Using scripts to= make nonessential alerts optional

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

A

Yes __

No __

2.2.5 Re-authenticating: When an authenticated session ex= pires, the user can continue the activity without loss of data after re-authenticating.

Prov= iding options to continue without loss of data using one of the following techniques:

G= 105: Saving data so that it can be used after a user re-authenticates

 

 

 

G181:<= /a>Encodi= ng user data as hidden or encrypted data in a re-authorization page

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 

 

 =


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

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

2.3.1 Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or = the flash is below the general flash and red flash thresholds.

G1= 9: Ensuring that no component of the content fla= shes more than three times in any 1-second period

 

 

 

G176:<= /a> Keeping the flashing= area small enough

 

 

 

G1= 5: Ensuring that content does not violate the general flash threshold or red flash threshold

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 

AAA

Yes __

No __

2.3.2 Three Flashes: <= /b>Web pages do not contain anything that flashes more than three times in any one second period.

G1= 9: Ensuring that no component of the content fla= shes more than three times in any 1-second period

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 

 


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

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

Crea= ting links to skip blocks of repeated material using one of the following techniques:

G1:= Adding a link at the top of each page that goes directly to the main content area

 

 

 

G= 123: Adding a link at the beginn= ing of a block of repeated content to go to the end of the block <= /span>

 

 

 

G= 124: Add links at the top of the page to each area= of content

 

 

 

Groupi= ng blocks of repeated material in a way that can be skipped, using one of the follo= wing techniques:

H6= 9: Providing heading elements at the beginning of each section of content

 

 

 

H5= 0: Using structural elements to group links

 

 

 

H7= 0: Using frame elements to group blocks of repea= ted material AND H6= 4: Using the title attribute of the frame / iframe elements

 

 

 

SCR28= : Using expandable and collapsible menu to by p= ass block of content

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

AAA

Yes __

No __

2.4.2 Page Titled: Web pages have titles that describe topic or purpose.

G88: Providing descriptive titles for= Web pages AND associating a title with a Web page using one of the following technique:

H2= 5: Providing a title using the title element

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 


Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and deter= mine where they are (page 2)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

2= .4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus= in an order that preserves meaning and operability.

 

G5= 9: Placin= g the interactive elements in an order that follows sequences and relationships within the content

 

 

 

Givi= ng focus to elements in an order that follows sequences and relationships within t= he content using one of the following techniques:

H4:= Creati= ng a logical tab order through links, form controls, and objects=

 

 

 

C27: Making the DOM order match the v= isual order

 

 

 

Chan= ging a Web page dynamically using one of the following techniques:

= SCR26:  Inserting dynamic content into t= he Document Object Model immediately following its trigger element

 

 

 

SCR37= : Creating Custom Dialogs in a Device Independent Way=

 

 

 

= SCR27: Reordering page sections using t= he Document Object Model

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 


Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and deter= mine where they are (page 3)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

2= .4.4 Link Purpose (In Context): The purpose of each link can be determined fr= om the link text alone, or from the link text together with its programmatic= ally determined link context, except where the purpose of the link would be ambiguous to users in general.

 G9= 1: Provid= ing link text that describes the purpose of a link

H30: Link text describe purpose of a = link for anchor elements

H24: Text alternatives for the area e= lements of image maps

 

 

 

Allo= wing the user to choose short or long link text using one of the technology specif= ic techniques below:

G189:<= /a> Providing a control near the beginning of the Web page that changes the l= ink text

 

 

 

= SCR30: Using scripts to change the link text

 

 

 

G5= 3: Identifying the purpose of a link using link text combined with the text of the enclosing sentence

 

 

 

Prov= iding a supplemental description of the purpose of a link using one of the follow= ing techniques:

H3= 3: Supplementing link text with the title attribute

 

 

 

C7:= Using CSS to hide a portion of the li= nk text

 

 

 

Iden= tifying purpose of a link using link text combined with programmatically determin= ed link context using one of the following techniques:

H77: Identifying the purpose of a link using link text combined with its enclo= sing list item 

 

 

 

H78: Identifying the purpose of a link using link text combined with its enclo= sing paragraph

 

 

 

H79: Identify purpose of a link using link text combined with its enclosing table cell = and associated table headings  <= o:p>

 

 

 

H80: Identifying the purpose of a link using link text combined with the prece= ding heading element  =

 

 

 

H81: Identify purpose of a link in a nested list using link text combined with= the parent list item

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and deter= mine where they are (page 4)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AA

Yes __

No __

2.4.5 Multiple ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of= , or a step in, a process.

Using two or more for the following techniques

G= 125: Providing links to navigate= to related Web pages

 

 

 

G6= 4: Providing a Table of Contents

 

 

 

G6= 3: Providing a site map

 

 

 

G161:<= /a> Providing a search function to help users find content

 

 

 

G= 126: Providing a list of links to all other Web pages

 

 

 

G185:<= /a> Linking to all the pages on the site from the home page

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

AA

Yes __

No __

2.4.6 Headings and Labels: Headings and labels describe topic or purpose= . <= o:p>

G= 130: Providing descriptive headings

 

 

 

G= 131: Providing descriptive labels

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 

 


Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and deter= mine where they are (page 4)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AA

Yes __

No __

2.4.7 Focus Visible: <= span lang=3DEN-AU style=3D'font-size:11.0pt'>Any keyboard operable user interf= ace has a mode of operation where the keyboard focus indicator is visible.=

G= 149: Using user inter= face components that are highlighted by the user agent when they receive focus=

 

 

 

C1= 5: Using CSS to cha= nge the presentation of a user interface component when it receives focus

 

 

 

G165:<= /a> Using the default fo= cus indicator for the platform so that high visibility default focus indicato= rs will carry over

 

 

 

G195:<= /a> Using an author-supp= lied, highly visible focus indicator

 

 

 

SCR31= : Using script to chan= ge the background color or border of the element with focus

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

AAA

Yes __

No __

2.4.8 Location: Information about the user's loc= ation within a set of Web pages is available.

G6= 5: Providing a brea= dcrumb trail

 

 

 

G6= 3: Providing a site= map

 

 

 

G1= 28: Indicating curre= nt location within navigation bars

 

 

 

G= 127:  Identifying a Web page's relationship to a lar= ger collection of Web pages USING  <= /span>H5= 9: Using the link element and navigation tools

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 


Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and deter= mine where they are (page 5)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AAA

Yes __

No __

2= .4.9 Link Purpose (Link Only): A mechanism is available to allow the purpose= of each link to be identified from link text alone, except where the purpose= of the link would be ambiguous to users in general.

G9= 1: Provid= ing link text that describes the purpose of a link using one of the following

 

 

 

H30: Link text describe purpose of a = link for anchor elements

 

 

 

H24: Text alternatives for the area e= lements of image maps

 

 

 

Allo= wing the user to choose short or long link text using one of the technology specif= ic techniques below:

G189:<= /a> Providing a control near the beginning of the Web page that changes the l= ink text

 

 

 

 

 

 

= SCR30: Using scripts to change the link text

 

 

 

 

 

 

Prov= iding a supplemental description of the purpose of a link using following;=

 

 

 

C7:= Using CSS to hide a portion of the li= nk text

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

AAA

Yes __

No __

2.4.10 Section Headings: Section headings are used to org= anize the content.

G= 141; Organi= zing a page using headings

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 

 


Principle 3: Un= derstandable – Information and the operation of user interface must be understanda= ble.

Guideline 3.1 Readable: Make content rea= dable and understandable.

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

3= .1.1 Language of page: The default human language of each Web page c= an be programmatically determined.

H5= 7: Using language attributes on the html element

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 

AA

Yes __

No __

3= .1.2 Language of parts: The human language of each passage or phrase = in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases th= at have become part of the vernacular of the immediately surrounding text.

H5= 8: Using language attributes to identify changes in the human language=

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 


Guideline 3.1 Readable: Make content readable and understandable (page 2)<= /span>

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AAA

Yes __

No __

3= .1.3 Unusual words:  <= span lang=3DEN-AU style=3D'font-size:11.0pt;mso-bidi-font-weight:bold'>A mecha= nism is available for identifying specific definitions of words or phrases used i= n an unusual or restricted way, including idioms and jargon.

S= ituation A: If the word o= r phrase has a unique meaning within the Web page:

G101:<= /a> Providing the definition of a wo= rd or phrase for the FIRST occurrence in a Web page using one of = the following techniques:

 

 

 

G5= 5: Linking to definitions

>  H4= 0: Using definition lists

>H6= 0: Using the link element to link to a glossary

 

 

 

G112:<= /a> Using inline definitions

>  H5= 4: Using the dfn element to identify the defining instance of a word<= span lang=3DEN-AU>

 

 

 

G101:<= /a> Providing the definition of a wo= rd or phrase for EACH occurrence in a Web page using one of the following techniques:

 

 

 

G5= 5: Linking to definitions

>  H4= 0: Using definition lists

>  H6= 0: Using the link element to link to a glossary

 

 

 

G62: Providing a glossary

 

 

 

G7= 0: Providing a function to search an online dictionary=

 

 

 

Situation B: If the word or phrase means different things within the same page:

G101:<= /a> Providing the definition of a wo= rd or phrase for EACH occurrence in a Web page using one of the following techniques:

 

 

 

G5= 5: Linking to definitions

>  H4= 0: Using definition lists

>  H6= 0: Using the link element to link to a glossary

 

 

 

G112:<= /a> Using inline definitions

>  H5= 4: Using the dfn element to identify the defining instance of a word<= /i>

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 


Guideline 3.1 Readable: Make content readable and understandable (page 3)<= /span>

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AAA

Yes __

No __

3= .1.4 Abbreviations: A mechanism for identifying the expanded form or meaning of abbreviations is available.

S= ituation A: If the abbrev= iation has only one meaning within the Web page:

G102:<= /a> Provide the expansion or explana= tion for the FIRST occurrence in a Web page using one of the following techniques:

 

 

 

G9= 7: Providing the abbreviation immediately following the expanded form

 

 

 

G5= 5: Linking to definitions

 

 

 

H2= 8: Providing definitions for abbreviations by using the abbr and acronym elements

 

 

 

G102:<= /a> Provide the expansion or explana= tion for ALL occurrences in a Web page using one of the following technique= s:

 

 

 

G5= 5: Linking to definitions

 

 

 

H6= 0: Using the link element to link to a glossary

 

 

 

G62: Providing a glossary

 

 

 

G7= 0: Providing a function to search an online dictionary=

 

 

 

H2= 8: Providing definitions for abbreviations by using the abbr and acronym elements

 

 

 

Situation B: If the abbreviation means different things within the same page:

G102:<= /a> Provide the expansion or explana= tion for the FIRST occurrence in a Web page using one of the following techniques:

 

 

 

G5= 5: Linking to definitions

 

 

 

H2= 8: Providing definitions for abbreviations by using the abbr and acronym elements

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 


Guideline 3.1 Readable: Make content readable and understandable (page 5)<= /span>

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AAA

Yes __

No __

3.1.5 Reading Level: When text requires reading abili= ty more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available.

G8= 6: Providing a text summary th= at requires reading ability less advanced than the upper secondary education level

 

 

 

G= 103: Providing visual illustrations, pictures, and symbols to help explain ideas, events, and processes

 

 

 

G7= 9: Providing a spoken version = of the text

 

 

 

G153:<= /a> Making the text easier to read <= o:p>

 

 

 

G160:<= /a> Providing sign language versions= of information, ideas, and processes that must be understood in order to use= the content

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

AAA

Yes __

No __

3.1.6 Pronunciation: A mechanism is available for ide= ntifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.

G= 120: Providing the pronunciation imme= diately following the word

 

 

 

G= 121: Linking to pronunciations

 

 

 

G6= 2: Providing a glos= sary that includes pronunciation information for words that have a unique pronunciation in the content and have meaning that depends on pronunciati= on

 

 

 

Prov= ide pronunciation information using= a technology-specific technique below:

H6= 2: Using the ruby element (HTML) (X= HTML 1.1)

 

 

 

G163:<= /a> Using standard diacritical marks= that can be turned off

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 


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

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

3.2.1 On Focus: When any component receives focu= s, it does not initiate a change of context.

G= 107: Using "activate" rathe= r than "focus" as a trigger for changes of context

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

A

Yes __

No __

3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unle= ss the user has been advised of the behavior before using the component.<= o:p>

G8= 0: Providing a submit button to ini= tiate a change of context using a technology-specific technique listed below

 

 

 

H3= 2: Providing submit buttons

 

 

 

H8= 4: Using a button with a select element to perform an action

 

 

 

G1= 3: Describing what = will happen before a change to a form control is made

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

AA

Yes __

No __

3.2.3 Consistent Navigation:<= /span> Navigational mechanisms that are repeated on multiple pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

G6= 1: Presenting repeated components in the same relative order each time they appear

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 


Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways (pag= e 2)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AA

Yes __

No __

3.2.4 Consistent Identificati= on: Components that have the same functionality wi= thin a set of Web pages are identified consistently.

G197:<= /a> Using labels, names, and text alternatives consistently for content that has the same functionality = AND for providing labels, names and text alternatives following;

 

 

 

sufficient techniques for Success Criterion 1.1.1

 

 

 

sufficient techniques for Success Criterion 4.1.2

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AAA

Yes __

No __

3= .2.5 Change of request: Changes of context are initiated only by user request or a mechanism is available to turn off such changes.

Situation A: If the Web page allows automatic updates:

G76: Providing a mechanism to request= update of the content instead of updating automatically

 

 

 

Situation B: If automatic redirects are possible:

S= VR1: Implementing aut= omatic redirects on the server side instead of on the client side.

 

 

 

G= 110: Use an instant client-side redirect using the following

 

 

 

H76: Using meta refresh to create an instant client-side redirect

 

 

 

S= ituation C: If the Web pa= ge uses pop-up windows:

Incl= uding pop-up windows using one of the following techniques:

H83: Using the target att= ribute to open a new window on user request and indicating this in link text

 

 

 

SCR24= : Use enhancement to o= pen new windows on request

 

 

 

Sit= uation D: If using an onchange event on a = select element:

SCR19= : Using an onchange ev= ent on a select element without causing a change of context

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

Guideline 3.3 Input Assistance: Help users avoid and correct mistakes

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is descri= bed to the user in text.

Situation A: If a form contains f= ields for which information from the user is mandatory.<= /b>

G8= 3: Providing text descriptions to i= dentify required fields that were not completed

 

 

 

= SCR18: Providing client= -side validation and alert

 

 

 

Situation B: If information provi= ded by the user is required to be in a specific data format or of certain values= .

G84: Providing a text des= cription when the user provides information that is not in the list of allowed val= ues

 

 

 

G8= 5: Providing a text description whe= n user input falls outside the required format or values

 

 

 

= SCR18: Providing client-side validation= and alert

 

 

 

SCR32= : Providing client-side validation and adding error text via the DOM

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 


Guideline 3.3 Input Assistance: Help users avoid and correct mistakes (page 2)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

3.3.2 Labels or Instructions: Labels or instructions are provi= ded when content requires user input.

G= 131: Providing descri= ptive labels AND one of the follow= ing:

 

 

 

G8= 9: Providing expected data format and example

 

 

 

G184:<= /a> Providing text instr= uctions at the beginning of a form or set of fields that describes the necessary input

 

 

 

G162:<= /a> Positioning labels to maximize predictability of relationships

 

 

 

G8= 3: Providing text descriptions to identify requir= ed fields that were not completed

 

 

 

H4= 4:Using label elements to associate= text labels with form controls

 

 

 

H7= 1: Providing a description for grou= ps of form controls using fieldset and legend elements

 

 

 

H6= 5:Using the title attribute to iden= tify form controls when the label element cannot be used

 

 

 

G167: Using an adjacent bu= tton to label the purpose of a field

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 


Guideline 3.3 Input Assistance: Help users avoid and correct mistakes (page 3)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AA

Yes __

No __

3.3.3 Error Suggestion: If an input error is automatical= ly detected and suggestions for correction are known, then the suggestions are provid= ed to the user, unless it would jeopardize the security or purpose of the content.

Situation A: If a mandatory field contains no information:<= span lang=3DEN-AU style=3D'font-size:11.0pt'>

G8= 3: Providing text descriptions to identify required fields that were not completed

 

 

 

Situation B: If information for a= field is required to be in a specific data format:

G8= 5: Providing a text description whe= n user input falls outside the required format or values

 

 

 

G177:<= /a> Providing suggested correction text=

 

 

 

= SCR18: Providing client= -side validation and alert

 

 

 

SCR32= : Providing client-side validation and adding error text via the DOM

 

 

 

Situation C: Information provided= by the user is required to be one of a limited set of values:

G8= 4: Providing a text description when the user provides information that is not in the list of allowed values

 

 

 

G177:<= /a> Providing suggested correction text=

 

 

 

= SCR18: Providing client= -side validation and alert

 

 

 

SCR32= : Providing client-side validation and adding error text via the DOM =

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 


Guideline 3.3 Input Assistance: Help users avoid and correct mistakes (page 4)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AA

Yes __

No __

3.3.4 Error Prevention (Legal, Fi= nancial, Data): For Web p= ages that cause legal commitments or financial transactions for the user to oc= cur, that modify or delete user-controllable data in data storage systems, or = that submit user test responses, at least one of the following is true: <= /o:p>

·     <= span lang=3DEN-AU style=3D'font-size:11.0pt;mso-bidi-font-style:italic'>Revers= ible: Submi= ssions are reversible.

·     <= span lang=3DEN-AU style=3D'font-size:11.0pt;mso-bidi-font-style:italic'>Checke= d: Data = entered by the user is checked for input errors and the user is provided an opportunity to correct them.

·     Confirmed: A mechanism is ava= ilable for reviewing, confirming, and correcting information before finalizing t= he submission.

Situation A: If an application ca= uses a legal transaction to occur, such as making a purchase or submitting an in= come tax return:

G164:<= /a> Providing a stated p= eriod of time after submission of the form when the order can be updated or cancel= led by the user

 

 

 

G9= 8: Providing the ab= ility for the user to review and correct answers before submitting <= /span>

 

 

 

G= 155: Providing a chec= kbox in addition to a submit button

 

 

 

Situation B: If an action causes information to be deleted:

G9= 9: Providing the ab= ility to recover deleted information

 

 

 

G168:<= /a> Requesting confirmat= ion to continue with selected action

 

 

 

G= 155: Providing a chec= kbox in addition to a submit button

 

 

 

Situation C: If the Web page incl= udes a testing application:

G9= 8: Providing the ab= ility for the user to review and correct answers before submitting <= /span>

 

 

 

G168:<= /a> Requesting confirmat= ion to continue with selected action

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 


Guideline 3.3 Input Assistance: Help users avoid and correct mistakes (page 5)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AAA

Yes __

No __

3.3.5 Help: Context-sensitive help is available.

Situation A: If a form requires t= ext input:

G7= 1: Providing a help link on every W= eb page

 

 

 

G193:<= /a> Providing help by an assistant in the Web page

 

 

 

G194:<= /a> Providing spell chec= king and suggestions for text input

 

 

 

G184:<= /a> Providing text instr= uctions at the beginning of a form or set of fields that describes the necessary input

 

 

 

Situation B: If a form requires t= ext input in an expected data format:

G8= 9: Providing expect= ed data format and example

 

 

 

G184:<= /a> Providing text instr= uctions at the beginning of a form or set of fields that describes the necessary input

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 

 

 


Guideline 3.3 Input Assistance: Help users avoid and correct mistakes (page 6)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

AAA

Yes __

No __

3.3.6 Error Prevention (All): For Web pages that require the us= er to submit information, at least one of the following is true:

·     <= span lang=3DEN-AU style=3D'font-size:11.0pt;mso-bidi-font-style:italic'>Revers= ible: Submi= ssions are reversible.

·     <= span lang=3DEN-AU style=3D'font-size:11.0pt;mso-bidi-font-style:italic'>Checke= d: Data = entered by the user is checked for input errors and the user is provided an opportunity to correct them.

·     Confirmed: A mechanism is ava= ilable for reviewing, confirming, and correcting information before finalizing t= he submission.

INSTRUCTION: Following the sufficient technique= s for Success Criterion 3.3.4 (below) for all forms that require the user to su= bmit information.

Situation A: If an application ca= uses a legal transaction to occur, such as making a purchase or submitting an in= come tax return:

G164:<= /a> Providing a stated p= eriod of time after submission of the form when the order can be updated or cancel= led by the user

 

 

 

G9= 8: Providing the ab= ility for the user to review and correct answers before submitting <= /span>

 

 

 

G= 155: Providing a chec= kbox in addition to a submit button

 

 

 

Situation B: If an action causes information to be deleted:

G9= 9: Providing the ab= ility to recover deleted information

 

 

 

G168:<= /a> Requesting confirmat= ion to continue with selected action

 

 

 

G= 155: Providing a chec= kbox in addition to a submit button

 

 

 

Situation C: If the Web page incl= udes a testing application:

G9= 8: Providing the ab= ility for the user to review and correct answers before submitting

 

 

 

G168:<= /a> Requesting confirmat= ion to continue with selected action

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 


Principle 4: Ro= bust – Content must be robust enough that it can interpreted reliably by a wide variety of user agents, including assistive technologies.

Guideline 4.1 Compatible: Maximise compati= bility with current and future user agents, including assistive technologies

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

4.1.1 Parsing: In content implemented using markup languages, elements have complete start and end tags, elements are nested according = to their specifications, elements do not contain duplicate attributes, and a= ny IDs are unique, except where the specifications allow these features..

G= 134: Validating Web pages <= /o:p>

 

 

 

G192:<= /a> Fully conforming to specifications

 

 

 

H88: Using HTML according to specs

 

 

 

Ensu= ring that Web pages can be parsed by using one of the following techniques:

H74: Ensuring that opening and closin= g tags are used according to specification

 

 

 

H7= 5: Ensuring that Web pages are well= -formed

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

 

 

 

 


Guideline 4.1 Compatible: Maximise compatibility with current and future user agents, including assistive technologies (page 2)

Level

Comply

Success Crite= rion = (normative)

Sufficient Techniques (informative)

Yes

Part

No=

A

Yes __

No __

4.1.2 Name, Role, Value: For all user user-interface components (includ= ing but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agen= ts, including assistive technologies.

Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.

Situation A: If using a standard user interface component in a markup language:=

G108:<= /a> Using markup features to expose = the name and role, allow user-settable properties to be directly set, and provide notification of changes using technology-specific techniques below:<= /o:p>

 

 

 

H91: Using HTML form controls and lin= ks

 

 

 

H44: Label elements to associate text= labels with form controls

 

 

 

H6= 4: Using the title attribute of the frame / iframe elements

 

 

 

H65: Title attribute to identify form controls when the label element cannot be used

 

 

 

H88: Using HTML according to specs

 

 

 

= SCR21: Using functions of the Document Object Model (DOM) to add content to a page

 

 

 

S= ituation B: If using scri= pt or code to re-purpose a standard user interface component in a markup langua= ge:

Expo= sing the names and roles, allowing user-settable properties to be directly set, and providing notification of changes using the following technique:

= SCR21: Using functions of the Document Object Model (DOM) to add content to a page

 

 

 

S= ituation C: If using a st= andard interface component in programming technology:

G= 135: Using the accessibility API feat= ures of a technology to expose names and roles, to allow user-settable properties= to be directly set, and to provide notification of changes=

 

 

 

S= ituation D: If creating u= ser interface component in a programming language:

G1= 0: Creating components using a tech= nology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow properties t= o be directly set, and provide notification of changes

 

 

 

Comments or o= ther techniques used to meet Success Criterion:

 

------=_NextPart_01CE418B.A27836D0 Content-Location: file:///C:/5D65A114/wcag2-aaa-worksheet_files/themedata.thmx Content-Transfer-Encoding: base64 Content-Type: application/vnd.ms-officetheme UEsDBBQABgAIAAAAIQDp3g+//wAAABwCAAATAAAAW0NvbnRlbnRfVHlwZXNdLnhtbKyRy07DMBBF 90j8g+UtSpyyQAgl6YLHjseifMDImSQWydiyp1X790zSVEKoIBZsLNkz954743K9Hwe1w5icp0qv 8kIrJOsbR12l3zdP2a1WiYEaGDxhpQ+Y9Lq+vCg3h4BJiZpSpXvmcGdMsj2OkHIfkKTS+jgCyzV2 JoD9gA7NdVHcGOuJkTjjyUPX5QO2sB1YPe7l+Zgk4pC0uj82TqxKQwiDs8CS1Oyo+UbJFkIuyrkn 9S6kK4mhzVnCVPkZsOheZTXRNajeIPILjBLDsAyJX89nIBkt5r87nons29ZZbLzdjrKOfDZezE7B /xRg9T/oE9PMf1t/AgAA//8DAFBLAwQUAAYACAAAACEApdan58AAAAA2AQAACwAAAF9yZWxzLy5y ZWxzhI/PasMwDIfvhb2D0X1R0sMYJXYvpZBDL6N9AOEof2giG9sb69tPxwYKuwiEpO/3qT3+rov5 4ZTnIBaaqgbD4kM/y2jhdj2/f4LJhaSnJQhbeHCGo3vbtV+8UNGjPM0xG6VItjCVEg+I2U+8Uq5C ZNHJENJKRds0YiR/p5FxX9cfmJ4Z4DZM0/UWUtc3YK6PqMn/s8MwzJ5PwX+vLOVFBG43lExp5GKh qC/jU72QqGWq1B7Qtbj51v0BAAD//wMAUEsDBBQABgAIAAAAIQBreZYWgwAAAIoAAAAcAAAAdGhl bWUvdGhlbWUvdGhlbWVNYW5hZ2VyLnhtbAzMTQrDIBBA4X2hd5DZN2O7KEVissuuu/YAQ5waQceg 0p/b1+XjgzfO3xTVm0sNWSycBw2KZc0uiLfwfCynG6jaSBzFLGzhxxXm6XgYybSNE99JyHNRfSPV kIWttd0g1rUr1SHvLN1euSRqPYtHV+jT9yniResrJgoCOP0BAAD//wMAUEsDBBQABgAIAAAAIQAw 3UMpqAYAAKQbAAAWAAAAdGhlbWUvdGhlbWUvdGhlbWUxLnhtbOxZT2/bNhS/D9h3IHRvYyd2Ggd1 itixmy1NG8Ruhx5piZbYUKJA0kl9G9rjgAHDumGHFdhth2FbgRbYpfs02TpsHdCvsEdSksVYXpI2 2IqtPiQS+eP7/x4fqavX7scMHRIhKU/aXv1yzUMk8XlAk7Dt3R72L615SCqcBJjxhLS9KZHetY33 37uK11VEYoJgfSLXcduLlErXl5akD8NYXuYpSWBuzEWMFbyKcCkQ+AjoxmxpuVZbXYoxTTyU4BjI 3hqPqU/QUJP0NnLiPQaviZJ6wGdioEkTZ4XBBgd1jZBT2WUCHWLW9oBPwI+G5L7yEMNSwUTbq5mf t7RxdQmvZ4uYWrC2tK5vftm6bEFwsGx4inBUMK33G60rWwV9A2BqHtfr9bq9ekHPALDvg6ZWljLN Rn+t3slplkD2cZ52t9asNVx8if7KnMytTqfTbGWyWKIGZB8bc/i12mpjc9nBG5DFN+fwjc5mt7vq 4A3I4lfn8P0rrdWGizegiNHkYA6tHdrvZ9QLyJiz7Ur4GsDXahl8hoJoKKJLsxjzRC2KtRjf46IP AA1kWNEEqWlKxtiHKO7ieCQo1gzwOsGlGTvky7khzQtJX9BUtb0PUwwZMaP36vn3r54/RccPnh0/ +On44cPjBz9aQs6qbZyE5VUvv/3sz8cfoz+efvPy0RfVeFnG//rDJ7/8/Hk1ENJnJs6LL5/89uzJ i68+/f27RxXwTYFHZfiQxkSim+QI7fMYFDNWcSUnI3G+FcMI0/KKzSSUOMGaSwX9nooc9M0pZpl3 HDk6xLXgHQHlowp4fXLPEXgQiYmiFZx3otgB7nLOOlxUWmFH8yqZeThJwmrmYlLG7WN8WMW7ixPH v71JCnUzD0tH8W5EHDH3GE4UDklCFNJz/ICQCu3uUurYdZf6gks+VuguRR1MK00ypCMnmmaLtmkM fplW6Qz+dmyzewd1OKvSeoscukjICswqhB8S5pjxOp4oHFeRHOKYlQ1+A6uoSsjBVPhlXE8q8HRI GEe9gEhZteaWAH1LTt/BULEq3b7LprGLFIoeVNG8gTkvI7f4QTfCcVqFHdAkKmM/kAcQohjtcVUF 3+Vuhuh38ANOFrr7DiWOu0+vBrdp6Ig0CxA9MxEVvrxOuBO/gykbY2JKDRR1p1bHNPm7ws0oVG7L 4eIKN5TKF18/rpD7bS3Zm7B7VeXM9olCvQh3sjx3uQjo21+dt/Ak2SOQEPNb1Lvi/K44e//54rwo ny++JM+qMBRo3YvYRtu03fHCrntMGRuoKSM3pGm8Jew9QR8G9Tpz4iTFKSyN4FFnMjBwcKHAZg0S XH1EVTSIcApNe93TREKZkQ4lSrmEw6IZrqSt8dD4K3vUbOpDiK0cEqtdHtjhFT2cnzUKMkaq0Bxo c0YrmsBZma1cyYiCbq/DrK6FOjO3uhHNFEWHW6GyNrE5lIPJC9VgsLAmNDUIWiGw8iqc+TVrOOxg RgJtd+uj3C3GCxfpIhnhgGQ+0nrP+6hunJTHypwiWg8bDPrgeIrVStxamuwbcDuLk8rsGgvY5d57 Ey/lETzzElA7mY4sKScnS9BR22s1l5se8nHa9sZwTobHOAWvS91HYhbCZZOvhA37U5PZZPnMm61c MTcJ6nD1Ye0+p7BTB1Ih1RaWkQ0NM5WFAEs0Jyv/chPMelEKVFSjs0mxsgbB8K9JAXZ0XUvGY+Kr srNLI9p29jUrpXyiiBhEwREasYnYx+B+HaqgT0AlXHeYiqBf4G5OW9tMucU5S7ryjZjB2XHM0ghn 5VanaJ7JFm4KUiGDeSuJB7pVym6UO78qJuUvSJVyGP/PVNH7Cdw+rATaAz5cDQuMdKa0PS5UxKEK pRH1+wIaB1M7IFrgfhemIajggtr8F+RQ/7c5Z2mYtIZDpNqnIRIU9iMVCUL2oCyZ6DuFWD3buyxJ lhEyEVUSV6ZW7BE5JGyoa+Cq3ts9FEGom2qSlQGDOxl/7nuWQaNQNznlfHMqWbH32hz4pzsfm8yg lFuHTUOT278QsWgPZruqXW+W53tvWRE9MWuzGnlWALPSVtDK0v41RTjnVmsr1pzGy81cOPDivMYw WDREKdwhIf0H9j8qfGa/dugNdcj3obYi+HihiUHYQFRfso0H0gXSDo6gcbKDNpg0KWvarHXSVss3 6wvudAu+J4ytJTuLv89p7KI5c9k5uXiRxs4s7Njaji00NXj2ZIrC0Dg/yBjHmM9k5S9ZfHQPHL0F 3wwmTEkTTPCdSmDooQcmDyD5LUezdOMvAAAA//8DAFBLAwQUAAYACAAAACEADdGQn7YAAAAbAQAA JwAAAHRoZW1lL3RoZW1lL19yZWxzL3RoZW1lTWFuYWdlci54bWwucmVsc4SPTQrCMBSE94J3CG9v 07oQkSbdiNCt1AOE5DUNNj8kUeztDa4sCC6HYb6ZabuXnckTYzLeMWiqGgg66ZVxmsFtuOyOQFIW TonZO2SwYIKObzftFWeRSyhNJiRSKC4xmHIOJ0qTnNCKVPmArjijj1bkIqOmQci70Ej3dX2g8ZsB fMUkvWIQe9UAGZZQmv+z/TgaiWcvHxZd/lFBc9mFBSiixszgI5uqTATKW7q6xN8AAAD//wMAUEsB Ai0AFAAGAAgAAAAhAOneD7//AAAAHAIAABMAAAAAAAAAAAAAAAAAAAAAAFtDb250ZW50X1R5cGVz XS54bWxQSwECLQAUAAYACAAAACEApdan58AAAAA2AQAACwAAAAAAAAAAAAAAAAAwAQAAX3JlbHMv LnJlbHNQSwECLQAUAAYACAAAACEAa3mWFoMAAACKAAAAHAAAAAAAAAAAAAAAAAAZAgAAdGhlbWUv dGhlbWUvdGhlbWVNYW5hZ2VyLnhtbFBLAQItABQABgAIAAAAIQAw3UMpqAYAAKQbAAAWAAAAAAAA AAAAAAAAANYCAAB0aGVtZS90aGVtZS90aGVtZTEueG1sUEsBAi0AFAAGAAgAAAAhAA3RkJ+2AAAA GwEAACcAAAAAAAAAAAAAAAAAsgkAAHRoZW1lL3RoZW1lL19yZWxzL3RoZW1lTWFuYWdlci54bWwu cmVsc1BLBQYAAAAABQAFAF0BAACtCgAAAAA= ------=_NextPart_01CE418B.A27836D0 Content-Location: file:///C:/5D65A114/wcag2-aaa-worksheet_files/colorschememapping.xml Content-Transfer-Encoding: quoted-printable Content-Type: text/xml ------=_NextPart_01CE418B.A27836D0 Content-Location: file:///C:/5D65A114/wcag2-aaa-worksheet_files/header.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii"





WC= AG 2.0 Worksheet (AAA)    &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;   Page 1        &= nbsp;           &nbs= p;            &= nbsp;                   &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;

------=_NextPart_01CE418B.A27836D0 Content-Location: file:///C:/5D65A114/wcag2-aaa-worksheet_files/filelist.xml Content-Transfer-Encoding: quoted-printable Content-Type: text/xml; charset="utf-8" ------=_NextPart_01CE418B.A27836D0--