WCAG 2 Level A Compliance Checklist

Creating a WCAG 2 Level A Compliance Checklist using eAuditor Audits & Inspections involves checking that your website meets the minimum accessibility standards as set by the Web Content Accessibility Guidelines (WCAG). These guidelines ensure that web content is accessible to people with disabilities. Here’s a WCAG 2 A Checklist  standards that you can integrate into eAuditor Audits & Inspections for auditing websites.

WCAG 2 Level A Compliance Checklist

General Information

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

Section 1: Perceivable

1. Text Alternatives for Non-Text Content (Guideline 1.1)
   • Alt text for images: All images have appropriate and descriptive alt attributes.
   • Text for complex images: Complex images (e.g., graphs) have accompanying text descriptions.
   • Form elements: All form controls, buttons, and inputs have descriptive labels or alt text.
   • Audio and video: Audio-only and video-only content provides a text transcript or description.
2. Time-Based Media Alternatives (Guideline 1.2)
   • Audio or video: Captions are provided for pre-recorded audio or video.
   • Live audio-only content: A text-based alternative is available for live audio-only streams.
3. Adaptable Content (Guideline 1.3)
   • Structure Content properly: Use of Headings (h1, h2, etc.), lists, and paragraphs in a logical sequence.
   • Not basing Instructions solely on shape, size, or visual location: Avoid or Clarify Instructions such as “click the red button”.
   • Present Content in different ways: Content does not lose meaning at the styling removal (e.g., CSS off).
4. Distinguishable Content (Guideline 1.4)
   • Color is not the sole means of conveying information: Critical information is not based only on color (e.g., links are underlined, not just a different color).
   • Text contrast: Text has a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.
   • Text resizing: Users can resize text up to 200% without loss of content or functionality.
   • Images of text: Images of text are avoided unless absolutely necessary.

Section 2: Operable

1. Keyboard Accessibility (Guideline 2.1)
   • Keyboard navigation: All functionality is available via keyboard (without requiring a mouse).
   • No keyboard traps: Users can navigate into and out of any content or components using the keyboard alone.
2. Enough Time (Guideline 2.2)
   • Adjustable time limits: Time limits for reading or interaction can be adjusted, extended, or turned off.
   • Content not time-sensitive: Content that disappears or auto-updates can be controlled by the user (e.g., sliders, rotating banners).
3. Seizure Prevention (Guideline 2.3)
   • No flashing content: Web pages do not include flashing content that flashes more than three times per second, unless it meets specific criteria.
4. Navigable (Guideline 2.4)
   • Skip to content link: There is a “skip to content” link or mechanism to bypass repetitive content.
   • Descriptive page titles: Each page has a clear, descriptive title that identifies its topic or purpose.
   • Focus indicators: All interactive elements (e.g., links, buttons) provide a visual indication when they are in focus.
   • Link purpose: The purpose of each link is clear from its text (or surrounding text) without relying solely on context.

Section 3: Understandable

1. Readable Content (Guideline 3.1)
   • Language of the page is defined: The language for the content is clearly defined using the appropriate language attribute (lang).
   • Readable language: The content is readable and understandable, using simple language where possible.
2. Predictable Interface (Guideline 3.2)
   • Consistent navigation: Navigation mechanisms are used consistently across the website.
   • Avoid unexpected changes: Components do not trigger unexpected changes (e.g., automatic redirects or page reloads).
3. Input Assistance (Guideline 3.3)
   • Error identification: Identify Errors are clearly and describe in text (e.g., form validation errors).
   • Labels for form fields: Form inputs have descriptive labels, and any required fields are clearly marked.
   • Instructions: Instructions are provided for complex interactions (e.g., filling out forms or following steps).

Section 4: Robust

1. Compatible with Assistive Technology (Guideline 4.1)
   • Valid HTML: The website uses valid and well-formed HTML, with elements properly nested.
   • Name, role, value: All user interface components (e.g., forms, buttons, inputs) provide sufficient information to assistive technologies (screen readers).

Section 5: Additional Notes

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

Conclusion

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

Using eAuditor Audits & Inspections for WCAG Audits with WCAG 2 Level A Compliance Checklist

1. Create a New Template: Start a new WCAG 2 Level A Compliance template or use existing WCAG 2 Level A Compliance Checklist in eAuditor Audits & Inspections and break it down into the sections listed above.
2. Add Checkboxes and Text Inputs: For each item, use checkboxes to verify compliance or input fields to record observations and recommendations.
3. Utilize Media Features: You can attach screenshots of non-compliant elements or areas needing improvements.
4. Track Compliance: Use eAuditor Audits & Inspection’s reporting features to monitor compliance over time, share reports, and assign follow-up tasks for remediation.

This checklist is designed for WCAG 2.0 Level A, which is the most basic level of web accessibility. It can be expanded to include WCAG 2.0 AA and AAA criteria as needed.