#1 of 10Accessibility · WCAG 2.2 · SC 2.1.1
The “Place order” button can’t be reached with a keyboard
- Where
Checkout, step 3 (Payment), on every device.
- Evidence
The button is a
divwithonclick, no role and notabindex. With the Tab key, focus jumps from the “Phone” field straight to the footer, and a screen reader announces no button. Checked with NVDA in Chrome and VoiceOver in Safari.<div class="btn-order" onclick="placeOrder()">Place order</div>
- Why it matters
Anyone who doesn’t use a mouse can’t place an order. It’s a level A barrier in WCAG 2.2 and a clear compliance risk under the EAA (Law 232/2022 in Romania), on the very page that brings in the money.
- How to fix it
A native button, which takes focus and works with Enter and Space:
<button type="button" class="btn-order" onclick="placeOrder()">Place order</button>
- Effort
Small: about 2 hours of development and an hour of testing.
- How to check
You reach the button with Tab alone, Enter places the order, and a screen reader announces “Place order, button”.
A sample from a fictional shop. In your report, every finding also has screenshots.
