Acquia Monsido Accessibility Test Pages

This project contains test pages demonstrating various accessibility issues and solutions based on WCAG success criteria.

• 3.1.1 Language of Page (A) ▼
  The default human language of each web page can be programmatically determined.
  • 434 - Language declaration (examples) ▼
    • Failed 1
    • Failed 2
    • Failed 3
    • Failed 4
    • Passed
  • 451 - Programmatic language (examples) ▼
    • Failed 1
    • Failed 2
    • Failed 3
    • Failed 4
    • Passed 1
    • Passed 2
    • Inapplicable 1
• 3.1.2 Language of Parts (AA) ▼
  The human language of each passage or phrase in the content can be programmatically determined.
  • 472 - Language of parts detection (examples) ▼
    • Check
  • 454 - Language of parts (examples) ▼
    • Pass 1
    • Pass 1 shadow
    • Pass 2
    • Pass 2 shadow
    • Pass 3
    • Pass 3 shadow
    • Pass 4
    • Pass 4 shadow
    • Pass 5
    • Pass 5 shadow
    • Fail 1
    • Fail 1 shadow
    • Fail 2
    • Fail 2 shadow
    • Fail 3
    • Fail 3 shadow
    • Fail 4
    • Fail 4 shadow
    • Fail 5
    • Fail 5 shadow
    • Fail 6
    • Fail 6 shadow
    • Fail 7
    • Fail 7 shadow
    • Fail 8
    • Fail 8 shadow
    • Fail 9
    • Fail 9 shadow
    • Inapplicable 1
    • Inapplicable 1 shadow
    • Inapplicable 2
    • Inapplicable 2 shadow
    • Inapplicable 3
    • Inapplicable 3 shadow
    • Inapplicable 4
    • Inapplicable 4 shadow
    • Inapplicable 5
    • Inapplicable 5 shadow
• 3.1.4 Abbreviations (AAA) ▼
  A mechanism for identifying the expanded form or meaning of abbreviations is available.
  • 471 - Abbreviation expansion
• 3.2.6 Consistent Help (A) ▼
  Help mechanisms that are provided on multiple pages are presented in a consistent order.
  • 343 - Consistent help features
• 3.3.1 Error Identification (A) ▼
  If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.
  • 467 - Error identification
• 3.3.2 Labels or Instructions (A) ▼
  Labels or instructions are provided when content requires user input.
  • 473 - Form labels and instructions
• 3.3.3 Error Suggestion (AA) ▼
  If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user.
  • 468 - Error suggestions
• 3.3.4 Error Prevention (Legal, Financial, Data) (AA) ▼
  For web pages that cause legal commitments or financial transactions, that modify or delete user-controllable data, or that submit user test responses, at least one of: reversible, checked, or confirmed.
  • 469 - Error prevention mechanisms
• 3.3.5 Help (AAA) ▼
  Context-sensitive help is available.
  • 475 - Context-sensitive help
• 3.3.7 Accessible Authentication (AA) ▼
  For each step in an authentication process that relies on a cognitive function test, at least one other authentication method is available.
  • 340 - Alternative authentication methods
• 3.3.8 Accessible Authentication (Enhanced) (AAA) ▼
  For each step in an authentication process, an authentication method is available that does not rely on a cognitive function test.
  • 341 - Enhanced authentication accessibility
• 3.3.9 Redundant Entry (A) ▼
  Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated or available for the user to select.
  • 359 - Auto-population of repeated information

About This Project

This collection of accessibility test pages is designed to demonstrate both good and bad examples of implementing WCAG success criteria. Each page includes examples of common accessibility issues and their solutions.