• Guideline 1.1 Text Alternatives:

  Provide text alternatives forany non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

• Success Criterion 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 (...). (Level A)

• Technique G94:

  Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content.

Hinweis: Zu diesem Erfolgskriterium gibt es zahlreiche weitere Techniques, die für unterschiedliche Arten von Grafiken die gleichen Anforderungen stellen wie die BITV-Test-Prüfschritte 1.1.1 und 1.1.2.

Siehe 1.1.1

• 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.

• Success Criterion 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 (...). (Level A)

• Technique H67:

  Using null alt text and no title attribute on img elements for images that AT should ignore

Prüfschritt 1.2.1 hat im BITV-Test aufgrund der geringeren Verbreitung von serverseitigen Imagemaps kaum praktische Relevanz. In den WCAG 2.0 gibt es zwar keine direkte Entsprechung, da serverseitige Imagemaps aber nicht tastaturbedienbar sind, wird ihre (alleinige) Verwendung schon durch Guideline 2.1 ausgeschlossen.

• Guideline 2.1 Keyboard Accessible:

  Make all functionality available from a keyboard.

• Success Criterion 1.2.5 Audio Description:

  Audio description is provided for all prerecorded video content in synchronized media. (Level AA)

• Success Criterion 1.2.2 Captions (Prerecorded):

  Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A)

• Success Criterion 1.2.4 Captions (Live):

  Captions are provided for all live audio content in synchronized media. (Level AA)

• Guideline 1.4 Distinguishable:

  Make it easier for users to see and hear content including separating foreground from background

• Success Criterion 1.4.1 Use of Color:

  Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A)

• Technique G18:

  Ensuring that a contrast ratio of at least 5:1 exists between text (and images of text) and background behind the text.

Hinweis: In der Technique G18 fehlt allerdings ein ausdrücklicher Hinweis, dass bei Grafiken mit transparentem Hintergrund beachtet werden muss, dass die Hintergrundfarbe variabel ist (je nach Benutzereinstellung).

• Failure F3:

  Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information.

Hinweis: Failure F3 zielt zwar hauptsächlich auf fehlende Alternativtexte bei via CSS eingebundenen Hintergrundgrafiken, behandelt aber in einer "Note" auch das Problem der verschwindenden Hintergrundgrafiken bei benutzerdefinierten Farben.

• Guideline 1.4 Distinguishable:

  Make it easier for users to see and hear content including separating foreground from background.

• Success Criterion 1.4.3 Contrast (Minimum):

  The visual presentation of text and images of text has a contrast ratio of at least 5:1, except for the following (...) (Level AA)

Hinweis: Es gibt allerdings nur für Schriftgrafiken eine Entsprechung. Im Unterschied zum BITV-Test sind andere Infografiken wie Symbole oder Diagramme ausgenommen. Immerhin raten aber einige (noch nicht geschriebene) Advisory Techniques dazu, für ausreichende Kontraste in Infografiken zu sorgen ("Making icons using simple line drawings that meet the contrast provisions for text", "Providing sufficient color contrast in graphs and charts").

Ein weiterer Unterschied: Kontraste werden nach einem anderen Algorithmus berechnet als im BITV-Test, zudem gelten anders als im BITV-Test für Grafiken und Texte die gleichen Anforderungen - siehe dazu Prüfschritt 2.3.1

• Guideline 1.4 Distinguishable:

  Make it easier for users to see and hear content including separating foreground from background.

• 1.4.3 Contrast (Minimum):

  The visual presentation of text and images of text has a contrast ratio of at least 5:1, except for the following: Large Print: (...); Incidental: (...); Logotypes: (...) (Level AA)

Hinweis: Kontraste werden nach einem anderen Algorithmus berechnet als im BITV-Test. Ausführlich siehe den Artikel Teil 3: Kontraste von Schrift.

• Success Criterion 1.4.5 Images of Text:

  If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following (...) (Level AA)

Hinweis: Anders als im BITV-Test werden Schriftgrafiken akzeptiert, wenn auf der Webseite ein Mechanismus angeboten wird, mit dem die Schriftart, die Größe sowie die Vorder- und Hintergrundfarbe der Grafiken durch den Benutzer angepasst werden können.

Keine Entsprechung.

Hinweis: Die Zielsetzung des Prüfschritts 3.1.2 findet sich aber in WCAG 2.0 Erfolgkriterium 2.4.6 wieder:

• Success Criterion 2.4.6 Headings and Labels:

  Headings and labels describe topic or purpose. (Level AA)

• Success Criterion 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 any IDs are unique, except where the specifications allow these features. (Level A)

• Technique G134:

  Validating Web pages

Keine Entsprechung, Layouttabellen sind grundsätzlich erlaubt.

Hinweis: Allerdings wird an mehreren Stellen dazu geraten, anstelle von Layouttabellen besser CSS zu verwenden, zum Beispiel: "Although WCAG 2 does not prohibit the use of layout tables, CSS-based layouts are recommended in order to retain the defined semantic meaning of the HTML table elements and to conform to the coding practice of separating presentation from content." (in F49)

Noch nicht geschrieben ist die geplante Advisory Technique "Using CSS rather than tables for page layout" zu Success Criterion 1.3.1 (Info and Relationships).

• Guideline 1.4 Distinguishable:

  Make it easier for users to see and hear content including separating foreground from background.

• Success Criterion 1.4.4 Resize text:

  Text (but not images of text) can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)

Hinweis: Etwas andere Anforderungen als im BITV-Test Prüfschritt 3.4.1 (200% statt 150% Vergrößerung, keine Festlegung der Browserfenstergröße bei der Prüfung). Ausführlich siehe den Artikel "Teil 5: Schriftgrößen und Skalierbarkeit".

Keine direkte Entsprechung. Allerdings wird auf Level AAA eine Layoutvariante gefordert, die bei niedriger Bildschirmauflösung gut nutzbar ist:

• 1.4.8 Visual Presentation

  For the visual presentation of blocks of text, a mechanism is available to achieve the following: 1. (...), 2. width is no more than 80 characters or glyphs (40 if CJK), (...) (Level AAA)

• Guideline 1.3 Adaptable:

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

• Success Criterion 1.3.1 Info and Relationships:

  Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

• Technique H42:

  Using h1-h6 to identify headings.

• Guideline 2.4 Navigable:

  Provide ways to help users navigate, find content and determine where they are

• Success Criterion 2.4.1 Bypass Blocks:

  A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)

• Technique H69:

  Providing heading elements at the beginning of each section of content

• Guideline 1.3 Adaptable:

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

• Success Criterion 1.3.1 Info and Relationships:

  Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

• Technique H48:

  Using ol, ul and dl for lists

• Guideline 2.4 Navigable:

  Provide ways to help users navigate, find content and determine where they are

• Success Criterion 2.4.1 Bypass Blocks:

  A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)

• Technique H50:

  Using structural elements to group links.

Hinweis: In H50 werden allerdings auch div- und map-Elemente zur Gruppierung von Links zugelassen.

• Guideline 1.3 Adaptable:

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

• Success Criterion 1.3.1 Info and Relationships:

  Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

• Technique G115:

  Using semantic elements to mark up structure.

• Guideline 3.1 Readable:

  Make text content readable and understandable.

• Success Criterion 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 that have become part of the vernacular of the immediately surrounding text. (Level AA)

• Technique H58:

  Using language attributes to identify changes in the human language

Hinweis: noch nicht geschrieben und verlinkt ist die Advisory Technique "Providing language markup on proper names to facilitate correct pronunciation by screen readers".

• Guideline 3.1 Readable:

  Make text content readable and understandable.

• Success Criterion 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 that have become part of the vernacular of the immediately surrounding text. (Level AA)

• Technique H58:

  Using language attributes to identify changes in the human language

• Guideline 3.1 Readable:

  Make text content readable and understandable.

• Success Criterion 3.1.1 Language of Page:

  The default human language of each Web page can be programmatically determined. (Level A)

• Technique H57:

  Using language attributes on the html element.

• Guideline 1.3 Adaptable:

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

• Success Criterion 1.3.1 Info and Relationships:

  Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

• Technique H51:

  Using table markup to present tabular information.

• Guideline 1.3 Adaptable:

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

• Success Criterion 1.3.1 Info and Relationships:

  Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

• Technique H43:

  Using id and headers attributes to associate data cells with header cells in data tables.

• Technique H63:

  Using the scope attribute to associate header cells and data cells in data tables.

• Success Criterion Guideline 1.3 Adaptable:

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

• Success Criterion 1.3.2 Meaningful Sequence:

  When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A)

• Technique G57:

  Ordering the content in a meaningful sequence.

• Failure F49:

  Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized

• Guideline 1.3 Adaptable:

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

• Success Criterion 1.3.1 Info and Relationships:

  Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

• Technique H39:

  Using caption elements to associate data table captions with data tables. (If a table is used for layout, the caption element is not used).

• Technique H73:

  Using the summary attribute of the table element to give an overview of data tables ("... if a layout table is used, then the summary attribute is not used or is null").

• Failure F46:

  Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables.

• Guideline 1.3 Adaptable:

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

• Success Criterion 1.3.2 Meaningful Sequence:

  When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A)

• Technique G57:

  Ordering the content in a meaningful sequence

• Technique C6:

  Positioning content based on structural markup

• Success Criterion 1.3.3 Sensory Characteristics:

  Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A)

• Technique G96:

  Providing textual identification of items that otherwise rely only on sensory information to be understood

Keine Entsprechung.

Hinweis: Techniken wie Javascript sind grundsätzlich zulässig, sofern sie aus Sicht der "Community" hinreichend "accessibility supported" sind.

• Guideline 2.2 Enough Time:

  Provide users enough time to read and use content

• Success Criterion 2.2.2 Pause, Stop, Hide:

  For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)
  Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential (...)

• Technique G4:

  Allowing the content to be paused and restarted from where it was paused.

• Technique G11:

  Creating content that blinks for less than 5 seconds.

Hinweis: Abschaltbarkeit durch den Benutzer ist im BITV-Test nicht als mögliche Lösung aufgenommen, denn "entsprechende Schaltflächen auf der Seite sind normalerweise ebenfalls nicht geeignet, weil sie nicht auffällig genug sind oder als Teil der Werbung verstanden werden."

Anderer Grenzwert für Beendigung der Bewegung ohne Zutun des Nutzers als im BITV-Test (5 Sekunden statt 10).

• Guideline 2.3 Seizures:

  Do not design content in a way that is known to cause seizures.

• Success Criterion 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. (Level A)

• Guideline 2.2 Enough Time:

  Provide users enough time to read and use content

• Success Criterion 2.2.2 Pause, Stop, Hide:

  For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)
  Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential (...)

• Technique G4:

  Allowing the content to be paused and restarted from where it was paused.

• Technique G11:

  Creating content that blinks for less than 5 seconds.

Hinweis: Anderer Grenzwert als im BITV-Test (5 Sekunden statt 10).

• Guideline 2.2 Enough Time:

  Provide users enough time to read and use content.

• 2.2.1 Timing Adjustable:

  For each time limit that is set by the content, at least one of the following is true: Turn off (...); or Adjust (...); or Extend (...); or Real-time Exception (...); or Essential Exception (...); or 20 Hour Exception (...) (Level A)

• Guideline 3.2 Predictable:

  Make Web pages appear and operate in predictable ways.

• Success Criterion 3.2.5 Change on Request:

  Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA)

• Technique G76:

  Providing a mechanism to request an update of the content instead of updating automatically.

Hinweis: Komplett abgedeckt wird der Prüfschritt 7.4.1 nur über Level AAA.

• Guideline 2.2 Enough Time:

  Provide users enough time to read and use content.

• 2.2.1 Timing Adjustable:

  For each time limit that is set by the content, at least one of the following is true: Turn off (...); or Adjust (...); or Extend (...); or Real-time Exception (...); or Essential Exception (...); or 20 Hour Exception (...) (Level A)

• Failure F40:

  Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit.

• Guideline 3.2 Predictable:

  Make Web pages appear and operate in predictable ways.

• 3.2.5 Change on Request:

  Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA)

• Technique G76:

  Providing a mechanism to request an update of the content instead of updating automatically.

• Technique H76:

  Using meta refresh to create an instant client-side redirect.

• Technique SVR1:

  Implementing automatic redirects on the server side instead of on the client side

Alternativen für programmierte Objekte sind auch nach den WCAG 2.0 vorgesehen, wenn die eingesetzte Technik nicht hinreichend "accessibility supported" ist (siehe Understanding Conforming Alternate Versions).

Ausführlich siehe den Artikel "Teil 9: Alternativ-Versionen".

• Guideline 2.1 Keyboard Accessible:

  Make all functionality available from a keyboard.

• 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 endpoints. (Level A)

• 2.1.2 No Keyboard Trap:

  If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys, the user is advised of the method for moving focus away. (Level A)

• Guideline 2.4 Navigable:

  Provide ways to help users navigate, find content and determine where they are.

• Success Criterion 2.4.7 Focus Visible:

  Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)

• Technique C15:

  Using CSS to change the presentation of a user interface component when it receives focus.

• Guideline 2.4 Navigable:

  Provide ways to help users navigate, find content and determine where they are.

• Success Criterion 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. (Level A)

• Guideline 3.2 Predictable:

  Make Web pages appear and operate in predictable ways

• 3.2.5 Change on Request:

  Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA)

• Technique H83:

  Using the target attribute to open a new window on user request and indicating this in link text.

Hinweis: Die Ankündigung von neuen Fenstern wird in den WCAG 2.0 nur auf Level AAA gefordert.

• 3.3.2 Labels or Instructions

  Labels or instructions are provided when content requires user input.

Noch nicht geschrieben ist die dazugehörige Technique "Positioning labels to maximize predictability of relationships".

Keine direkte Entsprechung.

Techniken oder Formate wie zum Beispiel PDF sind grundsätzlich zulässig, wenn sie aus Sicht der "Community" hinreichend "accessibility supported" sind. Sie müssen dann ebenso wie HTML-Seiten die relevanten Erfolgskriterien erfüllen.

Keine direkte Entsprechung, der Verzicht auf veraltete Elemente und Attribute wird aber implizit gefordert:

• Success Criterion 1.3.1 Info and Relationships:

  Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

• Technique G140:

  Separating information and structure from presentation to enable different presentations

• Technique H49:

  Using semantic markup to mark emphasized or special text

• Technique G138:

  Using semantic markup whenever color cues are used

Alternativ-Versionen sind unter bestimmten Umständen möglich, siehe Textversion für Blinde" ist aber auch nach WCAG 2.0 nicht zulässig.

Ausführlich siehe den Artikel "Teil 9: Alternativ-Versionen".

• Guideline 4.1 Compatible:

  Maximize compatibility with current and future user agents, including assistive technologies

• Success Criterion 4.1.2 Name, Role, Value:

  For all user user interface components (including 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 agents, including assistive technologies. (Level A)

• Technique H64:

  Using the title attribute of the frame and iframe elements

Hinweis: Während nach dem BITV-Test nicht nur das title-Attribut, sondern auch das name-Attribute für die aussagekräftige Benennung von Frames genutzt werden soll, verlangen die WCAG 2.0 nur einen aussagekräftigen title.

• Guideline 2.4 Navigable:

  Provide ways to help users navigate, find content and determine where they are.

• 2.4.1 Bypass Blocks:

  A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)

• Technique H70:

  Using frame elements to group blocks of repeated material.

Hinweis: Die Technique H70 verlangt zwar das gleiche wie der BITV-Prüfschritt 12.2.1 ("If the site uses framesets, organize the blocks of content into separate frames. Make certain that the repeated blocks of content appear in the same frame within the frameset of each Web page. In addition, each frame element must have a title attribute to describe the content of the frame. When frames are properly titled, users can use frame navigation to easily navigate between blocks of content."), ist allerdings ganz anders zugeordnet - denn im Success Criterion 2.4.1 geht es darum, wiederkehrende Blöcke überspringen zu können.

• Guideline 1.3 Adaptable:

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

• Success Criterion 1.3.1 Info and Relationships:

  Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

• Technique G115:

  Using semantic elements to mark up structure

• Technique H49:

  Using semantic markup to mark emphasized or special text

• Technique H82:

  Grouping form controls with FIELDSET and LEGEND

• Guideline 1.3 Adaptable:

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

• Success Criterion 1.3.1 Info and Relationships:

  Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

• Guideline 3.3 Input Assistance:

  Help users avoid and correct mistakes.

• Success Criterion 3.3.2 Labels or Instructions:

  Labels or instructions are provided when content requires user input. (Level A)

• Technique H44:

  Using label elements to associate text labels with form controls.

Hinweis: title-Attribute werden zur Beschriftung von Formularfeldern auch akzeptiert:

• Technique H65:

  Using the title attribute to identify form controls when the label element cannot be used.

• Guideline 2.4 Navigable:

  Provide ways to help users navigate, find content and determine where they are.

• Success Criterion 2.4.4 Link Purpose (In Context):

  The purpose of each link can be determined from the link text alone, or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)

• Technique G91:

  Providing link text that describes the purpose of a link

• Technique H33:

  Supplementing link text with the title attribute.

• Technique C7:

  Using CSS to hide a portion of the link text.

Hinweis: Neben den auch nach dem BITV-Test zulässigen Techniken (Ergänzung eines nicht ausreichend aussagekräftigen Linktexts durch ein title-Attribut oder durch via CSS verstecktem Text) erlauben die WCAG 2.0 noch weitere Möglichkeiten, da zum direkten Kontext eines Links unter anderem auch der umgebende Absatz (p-Element) oder eine direkt vorangestellte Überschrift (hx-Element) betrachtet werden.

Keine direkte Entsprechung, allerdings implizit gefordert durch das Level AA Erfolgskriterium "Link Purpose" und das Level AAA Erfolgskriterium "Change on Request" ("Changes of content" schließen unter anderem Wechsel des User Agents und neue Fenster ein).

• Guideline 2.4 Navigable:

  Provide ways to help users navigate, find content and determine where they are.

• Success Criterion 2.4.4 Link Purpose (In Context):

  The purpose of each link can be determined from the link text alone, or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)

• Guideline 3.2 Predictable:

  Make Web pages appear and operate in predictable ways

• Success Criterion 3.2.5 Change on Request:

  Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA)

• Success Criterion 2.4.2 Page Titled:

  Web pages have titles that describe topic or purpose. (Level A)

• Technique H25:

  Providing a title using the title element

• Advisory Technique G127:

  Identifying a Web page's relationship to a larger collection of Web pages

Hinweis: Die Nennung des Anbieters beziehungsweise des Gesamtangebots im Dokumenttitel wird ausdrücklich nur im Advisory Technique G127 verlangt.

• Guideline 2.4 Navigable:

  Provide ways to help users navigate, find content and determine where they are.

• Success Criterion 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. (Level AA)

• Technique G63:

  Providing a site map.

• Success Criterion 3.2.3 Consistent Navigation:

  Navigational mechanisms that are repeated on multiple Web 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. (Level AA)

• Success Criterion 3.2.4 Consistent Identification:

  Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)

Hinweis: Im BITV-Test wird explizit eine "an Konventionen orientierte Navigation" beschrieben und gefordert. Dies geschieht in den WCAG 2.0 nur implizit und weniger eindeutig.

• Guideline 2.4 Navigable:

  Provide ways to help users navigate, find content and determine where they are.

• Success Criterion 2.4.8 Location:

  Information about the user's location within a set of Web pages is available. (Level AAA)

Hinweis: Komplett abgedeckt wird der Prüfschritt 13.4.2 nur auf Level AAA. Wichtige Bedingungen einer klaren Orientierung im Webauftritt sind allerdings die konsistente Verwendung und die Aussagekraft von Navigationselementen:

• Success Criterion 2.4.6 Headings and Labels:

  Headings and labels describe topic or purpose. (Level AA)

• Success Criterion 3.2.4 Consistent Identification:

  Components that have the same functionality within a set of Web pages are identified consistently. (Level AA).

Die Verständlichkeit von Texten wird nur auf Level AAA geprüft.

• Guideline 3.1 Readable:

  Make text content readable and understandable.

• Success Criterion 3.1.3 Unusual Words:

  A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. (Level AAA)