Accessibility testing basics in Angular - Mini Project: Build & Apply

Accessibility Testing Basics with Angular

📖 Scenario: You are building a simple Angular component for a website's contact form. The form must be accessible to all users, including those using screen readers or keyboard navigation.

🎯 Goal: Create an accessible Angular component with a form that includes labels, ARIA attributes, and keyboard-friendly elements.

📋 What You'll Learn

Use semantic HTML elements inside the Angular template

Add aria-label attributes where needed

Ensure all form inputs have associated labels

Make the form keyboard navigable

Use Angular standalone component with @Component and standalone: true

💡 Why This Matters

🌍 Real World

Accessible forms are essential for websites to be usable by people with disabilities, including those using screen readers or keyboard navigation.

💼 Career

Web developers must ensure their applications meet accessibility standards to reach a wider audience and comply with legal requirements.

1

Create the Angular component skeleton

Create a standalone Angular component called ContactFormComponent with a template containing a <form> element and two input fields: one for name and one for email. Use semantic HTML tags and include a submit button with the text Send.

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-contact-form',
  standalone: true,
  template: `
    
      
    
  `
})
export class ContactFormComponent {}

Hint

Use <label> tags with for attributes matching the id of inputs for accessibility.

2

Add ARIA labels for better screen reader support

Add aria-label attributes to the input elements for name and email fields with the values Enter your full name and Enter your email address respectively.

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-contact-form',
  standalone: true,
  template: `
    
      Name
      

      Email
      

      Send
    
  `
})
export class ContactFormComponent {}

# Add aria-label attributes to the input elements

Hint

Use aria-label inside the <input> tags to describe the input purpose for screen readers.

3

Make the form keyboard accessible

Add a tabindex="0" attribute to the button element to ensure it is focusable by keyboard users.

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-contact-form',
  standalone: true,
  template: `
    
      Name
      

      Email
      

      Send
    
  `
})
export class ContactFormComponent {}

# Add tabindex="0" to the button element

Hint

Use tabindex="0" on interactive elements to include them in the keyboard tab order.

4

Add role and aria-live for form submission feedback

Add a <div> below the form with role="alert" and aria-live="polite" attributes to announce submission messages to screen readers. The div should have an id="submissionMessage".

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-contact-form',
  standalone: true,
  template: `
    
      Name
      

      Email
      

      Send
    
    
  `
})
export class ContactFormComponent {}

Hint

Use a <div> with role="alert" and aria-live="polite" to notify screen readers of dynamic messages.

Practice

1. What is the main purpose of accessibility testing in Angular applications?

easy

A. To ensure the app works well for users with disabilities

B. To improve the app's loading speed

C. To add more animations and effects

D. To reduce the app's file size

Solution

1. Step 1: Understand accessibility testing goal

   Accessibility testing focuses on making apps usable by everyone, including people with disabilities.

2. Step 2: Compare options with this goal

   Only To ensure the app works well for users with disabilities matches this purpose; others relate to performance or design, not accessibility.

3. Final Answer:

   To ensure the app works well for users with disabilities -> Option A

4. Quick Check:

   Accessibility testing = help all users [OK]

Hint: Accessibility testing = usability for all users, especially disabled [OK]

Common Mistakes:

• Confusing accessibility with performance optimization
• Thinking accessibility is only about visual design
• Ignoring users with disabilities

2. Which ARIA attribute is correctly used in this Angular template snippet?

<button aria-label="Close menu">X</button>

easy

A. aria-hidden="Close menu"

B. aria-label="Close menu"

C. aria-checked="Close menu"

D. aria-live="Close menu"

Solution

1. Step 1: Identify correct ARIA attribute for labeling

   The attribute aria-label provides an accessible name for elements like buttons.

2. Step 2: Check each option's meaning

   aria-hidden hides content, aria-checked is for checkboxes, aria-live is for dynamic updates. Only aria-label fits the usage.

3. Final Answer:

   aria-label="Close menu" -> Option B

4. Quick Check:

   aria-label names elements for screen readers [OK]

Hint: Use aria-label to name buttons for screen readers [OK]

Common Mistakes:

• Using aria-hidden to label elements
• Confusing aria-checked with aria-label
• Applying aria-live incorrectly on static buttons

3. What will be the effect of this Angular template code on screen readers?

<input type="text" aria-describedby="emailHelp" />
<small id="emailHelp">Enter your email address</small>

medium

A. Screen readers will read the label twice

B. Screen readers will ignore the input field

C. Screen readers will read only 'input text' without description

D. Screen readers will read 'Enter your email address' when focusing the input

Solution

1. Step 1: Understand aria-describedby usage

   aria-describedby links an element to descriptive text read by screen readers.

2. Step 2: Analyze the code behavior

   The input references the small element with id 'emailHelp', so screen readers read that description on focus.

3. Final Answer:

   Screen readers will read 'Enter your email address' when focusing the input -> Option D

4. Quick Check:

   aria-describedby adds extra description [OK]

Hint: aria-describedby links input to extra text for screen readers [OK]

Common Mistakes:

• Thinking aria-describedby hides the input
• Assuming aria-describedby duplicates label reading
• Confusing aria-describedby with aria-label

4. Identify the accessibility issue in this Angular template:

<div role="button" tabindex="-1">Click me</div>

medium

A. tabindex="-1" prevents keyboard focus on the button role element

B. role="button" is invalid on a div

C. Missing aria-label attribute

D. The div should use <span> instead

Solution

1. Step 1: Understand tabindex="-1" effect

   tabindex="-1" removes the element from keyboard focus order, so users can't tab to it.

2. Step 2: Check role and accessibility impact

   role="button" makes the div behave like a button, but without keyboard focus, it's inaccessible.

3. Final Answer:

   tabindex="-1" prevents keyboard focus on the button role element -> Option A

4. Quick Check:

   tabindex="-1" removes keyboard focus [OK]

Hint: tabindex="-1" removes element from keyboard tab order [OK]

Common Mistakes:

• Thinking role="button" alone fixes accessibility
• Ignoring keyboard focus importance
• Assuming aria-label is always required

5. You want to improve accessibility for a custom Angular dropdown component. Which combination is best practice?

hard

A. Use aria-hidden="true" on all dropdown items

B. Add only visual styles and skip ARIA roles

C. Use ARIA roles like role="listbox", keyboard navigation, and test with screen readers

D. Disable keyboard navigation to avoid confusion

Solution

1. Step 1: Identify accessibility needs for custom dropdown

   Custom dropdowns need ARIA roles to inform assistive tech and keyboard support for navigation.

2. Step 2: Evaluate options for best practice

   Use ARIA roles like role="listbox", keyboard navigation, and test with screen readers includes ARIA roles, keyboard navigation, and testing, which covers accessibility well. Others ignore key accessibility aspects or harm usability.

3. Final Answer:

   Use ARIA roles like role="listbox", keyboard navigation, and test with screen readers -> Option C

4. Quick Check:

   ARIA + keyboard + testing = accessible dropdown [OK]

Hint: Combine ARIA roles and keyboard support for custom components [OK]

Common Mistakes:

• Relying only on visual styles
• Hiding interactive elements with aria-hidden
• Disabling keyboard navigation