QA Interview Handbook
  • 🏠Home Page
  • About Testing
    • 💖Qualities of A Great Tester
  • Manual Testing
    • 💡Overview
      • ✋Demand for Software Testing
      • 😄Tester's Role in Manual Testing
      • 7️Testing Principles
      • 🚨V & V
      • ❔Interview Questions
    • ♻️SDLC
      • 📒Phase 1: Planning
      • 🔍Phase 2: Requirement Analysis
      • 👔Phase 3: Design
      • ⛑️Phase 4: Development
      • 🧪Phase 5: Testing
      • 🚚Phase 6: Deployment
      • 🖱️Phase 7: Maintenance
      • ⚔️Common Challenges
      • ❔Interview Questions
    • 🌀STLC
    • 🌊Waterfall
    • ✳️Agile
      • 😁Tester's Role in Scrum
    • 🔢Types
      • ⬜White Box Testing
      • ⬛Black Box Testing
        • 🔰Techniques Used in Black Box Testing
        • 🚘Functional Testing
          • 1️⃣Unit Testing
          • 2️⃣Integration Testing
            • 🔰Techniques Used in Integration Testing
          • 3️⃣System Testing
            • 📼Types of System Testing
            • 🌊Phases of System Testing
            • 🌀Regression Testing
            • 🌫️Smoke Testing
          • 4️⃣Acceptance Testing
            • ⚙️User Acceptance Testing
            • 🅰️Alpha Testing
            • 🅱️Beta Testing
        • 🕳️Non Functional Testing
      • 📑Grey Box Testing
    • 🪄User Story
      • ⏺️Sample User Stories
    • 📓Test Cases
      • ⏺️Sample Test Cases
      • ❔Interview Questions
    • ✖️Defect Life Cycle
      • ☣️Priority + Severity
      • ⏺️Sample Defect Reports
      • ❔Interview Questions
      • 🐛Buggy Questions
    • 🌐Atlassian JIRA
      • 🐞JIRA Issues
      • ❔Interview Questions
    • ❔Interview Questions
  • Accessibility Testing
    • 💡Overview
    • 🤓Tester's Role in Accessibility Testing
    • 📚WCAG Principles
      • 👁️Perceivable
      • 🏹Operable
      • 🧠Understandable
      • 🤖Robust
    • 🔧Axe DevTools
      • ❔Interview Questions
    • 📓Test Cases
    • ❔Interview Questions
  • API Testing
    • 💡Overview
    • 😀Tester's Role in API Testing
    • 🍊HTTP Methods & CRUD
      • 🍂HTTP Status Codes
    • 🍍API Tools
      • 🟠Postman
        • ☄️Sending your first API request
        • 🔬HTTP Requests with Java
        • 🎲GitHub Sample
        • ❔Interview Questions
      • ⛑️REST Assured
        • 🎇Dependency
        • ❔Interview Questions
    • 📓Test Cases
    • 🦧API Cheatsheet
    • ❔Interview Questions
  • Database Testing
    • 💡Overview
    • 😆Tester's Role in Database Testing
    • 🔵SQL
      • ⛓️Constraints
      • 🛢️Referencing a Column
      • 🔼DDL Commands
      • 🔼DML Commands
        • 🖌️Operators
        • 🛠️Functions
          • ⏯️Aggregate Functions
        • 🎅Clauses
          • ⏫Join Clauses
          • 🔵Filter Clauses
          • ⏬Set Operations
      • 🃏Wildcard Character
      • ❔Interview Questions
    • 📓Test Cases
    • 🧤SQL Practice Sites
    • 🫐SQL Cheatsheet
    • ❔Interview Questions
  • Java
    • ⛩️Introduction
    • 😄Tester's Reason to Learn Java
    • Ⓜ️Main Method
      • ❔Interview Questions
    • 📐Variables & Types
      • 🪢Special Types
    • 🥁Modifiers
    • 🅾️Operators
    • 🪡String
      • 🩺String Methods
        • String Method Problems
      • 🚨Delimiter
      • ❔Interview Questions
    • 🖇️Conditionals
      • 💎Common If Statements
      • 💎Common Ternary Operator Statements
    • Ⓜ️Math Class
    • 🌊Loops
      • 💎Common Loop Examples
      • 🔃Nested For Loops
    • 🍼OOPS
      • 🏛️Classes and Objects
        • ❔Interview Questions
      • 🎃Constructor
        • ⚡Static
          • ❔Interview Questions
        • 📍This() & Super()
          • ❔Interview Questions
        • 🍀Finalization
      • 🔓Encapsulation
      • 🐥Inheritance
      • 🦋Polymorphism
      • 🕸️Abstraction
    • 🏮Java Practice Sites
    • ☑️Data Structures + Algorithms
      • 🅾️Big O
      • ☑️Data Structures
        • 🔸Array
        • 🔳Array Problems
        • Page
      • 🪟Sliding Window Technique
        • 🪟Sliding Window Problems
        • 🥐LeetCode #53
        • 🥐LeetCode #209
    • ❔Interview Questions
  • Automation Testing
    • 🚰Flow
      • 💡Overview
      • 🤩Tester's Role in Automation Testing
      • 🍀Selenium
        • 🕸️Selenium WebDriver
          • 🕷️WebDriver Commands
            • 🌐WebElement
              • 🔆HTML Tags
              • 🔬Find Element(s)
              • 🦎Locators
                • ❌Xpath
                • 🏰CSS Selector
                • 📀DOM
                • 🏠Quick Reference for XPath + CSS
            • ✋Waits
            • Browser Management
            • 🏎️Navigation
            • Alerts
          • 🏷️Advanced User Interactions
            • 🗯️Action vs. Actions
            • 💧Drop Down
            • ✅Check Box
            • 🖇️Forms
          • ⚠️Exceptions
        • 🍏OOPS + Selenium
        • 🚢Frameworks
          • ⚓Module Based Framework
          • 🎹Keyword Driven Framework
          • 🎋Data Driven Framework
          • 🌺Hybrid Framework
          • 🌴Log4j
          • 📄Page Object Model
        • 🧪Testing Frameworks
          • 💡TestNG
          • 🉑JUnit
          • 🥒BDD
            • 🥒Cucumber
        • 🌉Selenium Grid
          • ✖️Desired Capabilities
        • ❔Interview Questions
      • 🔄API Testing with Selenium
      • ⏪Database Testing with Selenium
      • Ⓜ️Maven
      • 🐙Git
        • ❔Interview Questions
      • 🕵️‍♂️Jenkins
        • ❔Interview Questions
      • 🐳Docker
        • ❔Interview Questions
      • 📙AWS
        • ❔Interview Questions
  • Behavioral
    • 📣Mixed Interview Questions
    • ⭐STAR Method
      • 🌟Sample Responses
Powered by GitBook
On this page

Was this helpful?

  1. Accessibility Testing
  2. WCAG Principles

Operable

PreviousPerceivableNextUnderstandable

Last updated 1 year ago

Was this helpful?

Operable ⚙️

User interface components and navigation must be operable:

  • Make all functionality accessible from keyboard ⌨️

  • Give users enough time to read and use content ⏳

  • Avoid content that causes seizures 💥

  • Help users navigate and find content 🔍

Keyboard Accessible

Make all functionality available from a keyboard.

Success Criterion 2.1.1 Keyboard

(Level A)

All of the content is operable through a without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

Note

This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.

Note

This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

Success Criterion 2.1.2 No Keyboard Trap

(Level A)

If keyboard focus can be moved to a component of the page using a , then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

Note

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See .

Success Criterion 2.1.3 Keyboard (No Exception)

|

(Level AAA)

All of the content is operable through a without requiring specific timings for individual keystrokes.

Success Criterion 2.1.4 Character Key Shortcuts

|

(Level A)

If a is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:

Turn off

A is available to turn the shortcut off;

Remap

A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc);

Active only on focus

The keyboard shortcut for a is only active when that component has focus.

Enough Time

Provide users enough time to read and use content.

Success Criterion 2.2.1 Timing Adjustable

|

(Level A)

For each time limit that is set by the content, at least one of the following is true:

Turn off

The user is allowed to turn off the time limit before encountering it; or

Adjust

The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or

Extend

The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or

Real-time Exception

The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or

Essential Exception

The time limit is and extending it would invalidate the activity; or

20 Hour Exception

The time limit is longer than 20 hours.

Note

This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with , which puts limits on changes of content or context as a result of user action.

Success Criterion 2.2.2 Pause, Stop, Hide

(Level A)

For moving, , scrolling, or auto-updating information, all of the following are true:

Moving, blinking, scrolling

For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to , stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is ; and

Auto-updating

For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

Note

Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

Note

An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

Success Criterion 2.2.3 No Timing

(Level AAA)

Timing is not an part of the event or activity presented by the content, except for non-interactive and .

Success Criterion 2.2.4 Interruptions

(Level AAA)

Interruptions can be postponed or suppressed by the user, except interruptions involving an .

Success Criterion 2.2.5 Re-authenticating

(Level AAA)

When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.

Success Criterion 2.2.6 Timeouts

(Level AAA)

Users are warned of the duration of any that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.

Seizures and Physical Reactions

Do not design content in a way that is known to cause seizures or physical reactions.

Success Criterion 2.3.1 Three Flashes or Below Threshold

(Level A)

do not contain anything that flashes more than three times in any one second period, or the is below the .

Note

Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See .

Success Criterion 2.3.2 Three Flashes

(Level AAA)

do not contain anything that more than three times in any one second period.

Success Criterion 2.3.3 Animation from Interactions

(Level AAA)

triggered by interaction can be disabled, unless the animation is to the functionality or the information being conveyed.

Navigable

Provide ways to help users navigate, find content, and determine where they are.

Success Criterion 2.4.1 Bypass Blocks

(Level A)

A is available to bypass blocks of content that are repeated on multiple .

Success Criterion 2.4.2 Page Titled

(Level A)

have titles that describe topic or purpose.

Success Criterion 2.4.3 Focus Order

(Level A)

If a can be and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

Success Criterion 2.4.4 Link Purpose (In Context)

(Level A)

The can be determined from the link text alone or from the link text together with its , except where the purpose of the link would be .

Success Criterion 2.4.5 Multiple Ways

(Level AA)

More than one way is available to locate a within a except where the Web Page is the result of, or a step in, a .

Success Criterion 2.4.6 Headings and Labels

(Level AA)

Headings and describe topic or purpose.

Success Criterion 2.4.7 Focus Visible

(Level AA)

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

Success Criterion 2.4.8 Location

(Level AAA)

Information about the user's location within a is available.

Success Criterion 2.4.9 Link Purpose (Link Only)

(Level AAA)

A is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be .

Success Criterion 2.4.10 Section Headings

(Level AAA)

headings are used to organize the content.

Note

"Heading" is used in its general sense and includes titles and other ways to add a heading to different types of content.

Input Modalities

Make it easier for users to operate functionality through various inputs beyond keyboard.

(Level A)

Note

This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

Success Criterion 2.5.2 Pointer Cancellation

(Level A)

No Down-Event

Abort or Undo

Up Reversal

The up-event reverses any outcome of the preceding down-event;

Essential

Note

Functions that emulate a keyboard or numeric keypad key press are considered essential.

Note

This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

Success Criterion 2.5.3 Label in Name

(Level A)

Note

A best practice is to have the text of the label at the start of the name.

Success Criterion 2.5.4 Motion Actuation

(Level A)

Supported Interface

Essential

Success Criterion 2.5.5 Target Size

(Level AAA)

Equivalent

The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;

Inline

The target is in a sentence or block of text;

User Agent Control

The size of the target is determined by the user agent and is not modified by the author;

Essential

Success Criterion 2.5.6 Concurrent Input Mechanisms

(Level AAA)

Success Criterion 2.5.1 Pointer Gestures

All that uses multi-point or path-based gestures for operation can be operated with a without a path-based gesture, unless a multi-point or path-based gesture is .

For that can be operated using a , at least one of the following is true:

The of the pointer is not used to execute any part of the function;

Completion of the function is on the , and a is available to abort the function before completion or to undo the function after completion;

Completing the function on the down-event is .

For with that include or , the contains the text that is presented visually.

that can be operated by device motion or user motion can also be operated by and responding to the motion can be disabled to prevent accidental actuation, except when:

The motion is used to operate functionality through an interface;

The motion is for the function and doing so would invalidate the activity.

The size of the for is at least 44 by 44 except when:

A particular presentation of the target is to the information being conveyed.

Web content does not restrict use of input modalities available on a platform except where the restriction is , required to ensure the security of the content, or required to respect user settings.

📚
🏹
functionality
keyboard interface
keyboard interface
Conformance Requirement 5: Non-Interference
§
Understanding Keyboard (No Exception)
How to Meet Keyboard (No Exception)
functionality
keyboard interface
§
Understanding Character Key Shortcuts
How to Meet Character Key Shortcuts
keyboard shortcut
mechanism
user interface component
§
Understanding Timing Adjustable
How to Meet Timing Adjustable
essential
Success Criterion 3.2.1
§
blinking
pause
essential
§
essential
synchronized media
real-time events
emergency
§
§
user inactivity
§
Web pages
flash
general flash and red flash thresholds
Conformance Requirement 5: Non-Interference
§
Web pages
flashes
§
Motion animation
essential
§
mechanism
Web pages
§
Web pages
§
Web page
navigated sequentially
§
purpose of each link
programmatically determined link context
ambiguous to users in general
§
Web page
set of Web pages
process
§
labels
§
§
set of Web pages
mechanism
ambiguous to users in general
Section
§
functionality
single pointer
essential
functionality
single pointer
down-event
up-event
mechanism
essential
user interface components
labels
text
images of text
name
Functionality
user interface components
accessibility supported
essential
target
pointer inputs
CSS pixels
essential
essential