Clean & Accessible HTML

We write semantic, accessible, standards-compliant HTML by default. Accessibility is a baseline requirement, not an enhancement.

Semantics First

• PREFER semantic elements (header, nav, main, section, article, footer)
• AVOID generic div/span usage when a semantic element exists
• Use correct heading hierarchy (h1 → h6) without skipping levels

Accessibility

• ALWAYS ensure interactive elements are keyboard accessible
• PREFER native HTML elements over ARIA whenever possible
• DO NOT use ARIA to fix bad HTML semantics
• Provide accessible names for all interactive controls
  • Labels for inputs
  • aria-label or visible text where required