WCAG 2 Level AA Compliance Checklist

Creating a WCAG 2 Level AA Compliance Checklist in eAuditor Audits & Inspections involves building on the basic accessibility guidelines established in WCAG 2 Level A, ensuring a higher level of web accessibility. Level AA covers more inclusive accessibility requirements, improving the user experience for people with a wider range of disabilities. Below is a WCAG 2 Level AA checklist that can be used within eAuditor Audits & Inspections.

WCAG 2 Level AA Compliance Checklist

General Information

• Website/Project Name:
• URL:
• Date of Inspection:
• Inspector Name:
• WCAG Version: WCAG 2 Level AA

Section 1: Perceivable

1. Text Alternatives (Guideline 1.1)
   • All non-text content (e.g., images, audio, video) has appropriate text alternatives (alt text, captions, transcripts).
2. Time-Based Media (Guideline 1.2)
   • Captions for live audio content: Live audio and video streams have captions or alternative text where feasible.
   • Audio description for pre-recorded video: Audio descriptions are available for all pre-recorded video content.
   • Transcripts for pre-recorded content: Text transcripts are available for pre-recorded multimedia content.
3. Adaptable Content (Guideline 1.3)
   • Logical structure: Present Information and relationships (e.g., headings, paragraphs, lists)  in a logical and understandable order.
   • Color, shape, and position: Instructions or elements do not rely solely on sensory characteristics like shape, color, or location.
   • Forms and labels: Form fields and interactive elements have clear labels or instructions for proper use.
4. Distinguishable Content (Guideline 1.4)
   • Contrast ratio for text and images: Text and images of text have a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.
   • Contrast ratio for UI elements: Non-text content (like icons, form controls) have a contrast ratio of at least 3:1 against their background.
   • Resize text: Resize Content up to 200% without loss of functionality or content.
   • Text and background colors: Presentation of Text is not over complex backgrounds or images that would affect readability.
   • No use of images for text: Avoid Images of text, except when necessary (e.g., logos).

Section 2: Operable

1. Keyboard Accessibility (Guideline 2.1)
   • All functionality, including complex interactions (e.g., drop-down menus), can be operated via the keyboard.
   • There are no keyboard traps (i.e., users can navigate freely without being stuck in a component).
2. Enough Time (Guideline 2.2)
   • Adjustable time limits: Time limits can be turned off, adjusted, or extended for content interactions.
   • Pause, stop, or hide moving content: Users can pause or stop any moving or scrolling content (e.g., banners, auto-updating content).
3. Seizure Prevention (Guideline 2.3)
   • No flashing content: Flashing content does not flash more than three times per second, or it is below the general threshold for causing seizures.
4. Navigable (Guideline 2.4)
   • Multiple ways to navigate: There is more than one way to locate a web page within a set of pages (e.g., search functionality, site maps).
   • Descriptive link text: Link text clearly describes the link’s purpose, even when read out of context.
   • Focus visible: There is a visible indication when interactive elements, such as buttons or form fields, are in focus (e.g., by keyboard).

Section 3: Understandable

1. Readable Content (Guideline 3.1)
   • Language of the page: Clearly identify the primary language of the web page using a lang attribute.
   • Language of parts: If there is a language switch within the page (e.g., a foreign quote), identify the switch with a corresponding lang attribute.
2. Predictable Interface (Guideline 3.2)
   • Consistent navigation: Present Navigation links consistently across the site.
   • Consistent identification: Identify Interactive elements that perform the same function consistently (e.g., buttons, links).
   • Avoid unexpected changes: Components that trigger changes (e.g., dropdowns) do not result in unexpected context changes (e.g., unexpected page navigation).
3. Input Assistance (Guideline 3.3)
   • Error suggestions: Upon detection of input errors, provide users with suggestions on how to correct the error.
   • Error prevention for forms: Before submitting important data (e.g., financial transactions), allow users to review, correct, and confirm their input.

Section 4: Robust

1. Compatibility with Assistive Technology (Guideline 4.1)
   • Valid and well-formed HTML: The website uses valid, properly nested HTML elements.
   • Name, role, and value of UI components: UI elements (e.g., buttons, inputs) provide clear roles, names, and values to assistive technologies (e.g., screen readers).
   • Accessible scripting: Interactive components created via JavaScript or other scripts work properly with assistive technologies.

Section 5: Additional Notes

• Observations:
• Recommendations:
• Follow-Up Actions Required:

Conclusion

• Inspector Signature:
• Date of Follow-Up Inspection:

Using eAuditor Audits & Inspections for WCAG 2 Level AA Audits

1. Create a New Template:
   • Open eAuditor Audits & Inspections and create a new template for your WCAG audit.
2. Add Sections:
   • Use the above sections and criteria to structure your checklist. eAuditor Audits & Inspections allows adding checkboxes for “compliance” and “non-compliance,” as well as text fields for further comments or observations.
3. Use the Media Feature:
   • You can use eAuditor Audits & Inspection’s photo feature to attach screenshots of non-compliant elements on the website for easy identification.
4. Monitor and Track:
   • Use the audit results to monitor and track progress, share reports with stakeholders, and assign follow-up actions to resolve any compliance issues.

This checklist for WCAG 2 Level AA is designed to ensure your website provides a higher level of accessibility, covering a wider range of users with different disabilities. You can also integrate WCAG 2.1 guidelines if you want to extend the checklist further for modern web standards.