Easy HTML Question 220 of 229

Why should a button be a real button element instead of a div?

Frontend Master · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: DATABASE INDEX

Without indexScan every row
With indexJump to keys
CostWrites slower

Simple meaning

A real button gets keyboard focus, Enter/Space activation, and the right role for free.

1

WHY — HTML instead of guessing?

Why interviewers care about HTML:

They are checking judgment

on HTML.

A good answer names

the situation, the default choice, and one exception - that reads as experience.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

2

STEPS — What happens step by step?

Before you speak the answer, walk the interviewer through these steps:

  1. 1
    A real button gets

    keyboard focus, Enter/Space activation, and the right role for free.

  2. 2
    A div needs tabindex,

    key handlers, and ARIA or it fails accessibility.

  3. 3
    I use button unless

    the design truly needs a custom control.

  4. 4
    Give an example

    One tiny concrete case you can say aloud.

  5. 5
    Common mistake

    What juniors usually get wrong.

  6. 6
    Close

    When you pick this over the alternative.

3

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line
“A div needs tabindex, key handlers, and ARIA or it fails accessibility.”
Break into beats
Adivneedstabindexkeyhandlers
Speaking order
2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

A real button gets keyboard focus, Enter/Space activation, and the right role for free. A div needs tabindex, key handlers, and ARIA or it fails accessibility.

Chat with us