liveBook · Manning

Accessibility

As explained in Acing the Frontend Interview

Accessibility is the property of a user interface or document being usable by people with diverse abilities and assistive technologies.

Accessibility makes interfaces and documents usable across diverse abilities and assistive technologies. In frontend interviews, demonstrate it through semantic HTML, meaningful document hierarchy, accessible interactions, and appropriate ARIA rather than treating it as a styling afterthought. section 2.1 section 2.5

Show accessibility awareness by explaining:

  • Why elements such as <header>, <main>, <nav>, <article>, <section>, headings, and <footer> communicate structure more clearly than generic containers. section 2.1 section 2.5
  • How semantic markup supports accessibility, SEO, maintainability, and cross-browser compatibility. section 2.1
  • How standard HTML APIs, ARIA attributes, and properly designed forms support accessible interactions and validation. section 2.5

Interview scenario: article component

When implementing a React article page, structure the content with <main>, <article>, <header>, headings, <section>, paragraphs, and <footer>. Explain that these choices describe purpose and hierarchy, not merely visual presentation, then discuss how the same reasoning applies to forms and interactive controls. section 2.1

Listing 2.2 The BlogPost <main> element defined using semantic elements
<main>
  <article>
    <header>
      <h1>{post.title}</h1>
      <h2>{post.subtitle}</h2>
    </header>
    {post.sections.map((section, index) => (
    <section key="{index}">
      <h3>{section.title}</h3>
      {section.subsections.map((subsection, subIndex) => (
      <div key="{subIndex}">
        <h4>{subsection.title}</h4>
        <p>{subsection.content}</p>
      </div>
        ))}
    </section>
    ))}
  </article>
</main>

Inspect a semantic BlogPost structure with <main>, <article>, headings, nested sections, and paragraphs. section 2.1

How Acing the Frontend Interview covers it

How deep it goes
Connects semantic markup to accessibility, SEO, maintainability, and compatibility, then stops short of detailed assistive-technology testing.
Examples
Demonstrates accessibility through a React article page and discussions of semantic elements, forms, HTML APIs, and ARIA attributes.
What it assumes
Assumes frontend and HTML fundamentals while reinforcing semantic elements, document structure, forms, and standard HTML APIs.
What you can do after
Apply semantic HTML and appropriate ARIA while explaining accessibility trade-offs in React interviews and frontend implementation tasks.
How it connects
Connects accessibility with semantic HTML, document hierarchy, ARIA, forms, validation, SEO, maintainability, and cross-browser compatibility.

Also explained in

Compare how 9 books explain accessibility →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Acing the Frontend Interview. The section links point to the parts of the book it draws on.