How do I test for WCAG 1.3.5 compliance?

To test Identify Input Purpose: use automated tools like AltorLab's scanner for initial detection, then manually verify with keyboard navigation and screen reader testing. Check the specific failure modes described in the WCAG documentation.

🔵 Level AA

WCAG 1.3.5: Identify Input Purpose

Name: AI Room Redesign
Price: 9 USD

Success Criterion 1.3.5 — Level AA

Quick Answer

The purpose of common input fields must be programmatically determinable.

Why It Matters

Password managers and autofill tools require autocomplete attributes to function correctly.

How to Audit

Run an automated accessibility scan to detect common Identify Input Purpose failures. Then manually verify with: keyboard-only navigation, a screen reader (VoiceOver on Mac, NVDA on Windows), and browser developer tools. Automated tools catch approximately 40% of Identify Input Purpose issues — manual testing is essential.

How to Fix

Add autocomplete attributes: name, email, tel, street-address, postal-code, cc-number, etc.

Frequently Asked Questions

What is WCAG 1.3.5 Identify Input Purpose?

The purpose of common input fields must be programmatically determinable.

Is WCAG 1.3.5 required for ADA compliance?

WCAG 2.1 Level AA is the standard referenced in most ADA website lawsuits and DOJ guidance. All Level AA criteria including this one are relevant to legal compliance.

How do I fix WCAG 1.3.5 violations?

Add autocomplete attributes: name, email, tel, street-address, postal-code, cc-number, etc.

Disclaimer: This guide is for informational purposes only and does not constitute legal advice. Consult a qualified ADA/accessibility attorney for your specific compliance situation.

Scan Your Site for WCAG 1.3.5 Issues

Get a free automated accessibility report including all WCAG 2.1 AA violations.

Run Free Accessibility Scan