autocomplete attribute must be used correctly

Rule ID: autocomplete-valid
Ruleset: axe-core 4.9
User Impact: Serious
Guidelines: WCAG 2.1 (AA), WCAG 2.2 (AA), EN 301 549
 

Accessibility testing for dev teams - No experience required

Find and fix up to 80% of accessibility issues with axe DevTools Pro. Get started with your free trial today. No credit card needed.

Compliance Data & Impact

User Impact

Serious
▼
Minor
Critical

Disabilities Affected

  • Attention Deficit
  • Blind
  • Low Vision
  • Deafblind
  • Mobility
  • Cognitive

Standard(s)

  • WCAG 2.1 (AA)
  • WCAG 2.2 (AA)
  • EN 301 549

WCAG Success Criteria [WCAG 2.1 (AA)]

  • 1.3.5: MUST: Identify Input Purpose

WCAG Success Criteria [WCAG 2.2 (AA)]

  • 1.3.5: MUST: Identify Input Purpose

    How to Fix the Problem

    1. Identify any form elements that accept an individual's personal data.
    2. For each form element that accepts an individual's personal data:
      • Check to see if the personal data is one of the 53 types identified in WCAG 2.1 Section 7 Input Purposes for User Interface Components opens in a new window.
      • Confirm that the autocomplete attribute is set with the appropriate value to identify the purpose of that UI component.

    Why it Matters

    Failure to provide autocomplete values in form fields results in inaccessible content. Screen readers do not read identified autocomplete form fields if the appropriate autocomplete attribute values are missing. Users cannot correctly navigate forms when screen readers cannot provide adequate information to the user regarding form field interaction requirements.

    Rule Description

    The purpose for each common input field that collects an individual's personal data is programmatically defined based on the list of 53 Input Purposes for User Interface Components. The autocomplete attribute values must be valid and correctly applied for screen readers to function correctly.

    The Algorithm (in simple terms)

    The purpose of each input field collecting information about the user can be programmatically determined when:

    • The input field serves a purpose identified in the Input Purposes for User Interface Components section; and
    • The content is implemented using technologies with support for identifying the expected meaning for form input data.

    Resources

    Deque University Course Pages (subscription required)

    No related course information available.

    Contribute to axe-core on GitHub

    Other Resources

    You may also want to check out these other resources.

    Refer to the complete list of axe 4.9 rules.

    Was this information helpful?

    You have already given your feedback, thank you..

    Your response was as follows:

    Was this information helpful?
    Date/Time feedback was submitted: