Study guide

11.2 Usability, Meaningful Error Messages, and Input Validation vs. Verification

Praxis Computer Science 5652

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Praxis 5652 Exam Overview and ETS Pseudocode

1.1 Praxis 5652 Test Facts, Scoring, and Registration 1.2 Official ETS Pseudocode Notation and Tracing Strategy

2 Chapter 2: Impacts of Computing: Innovation, Access, and Effects

2.1 Computing for Creativity, Problem Solving, Communication, and Innovation 2.2 Equal Access, the Digital Divide, and Accessibility 2.3 Beneficial and Harmful Effects of Computing Innovations

3 Chapter 3: Impacts of Computing: Intellectual Property, Ethics, Privacy, and Security

3.1 Intellectual Property: Copyright, Open Source, and Creative Commons 3.2 Ethical and Unethical Computing Practices and Their Implications 3.3 Privacy, Security, Data Collection, and Local vs. Cloud Storage

4 Chapter 4: Algorithms and Computational Thinking: Abstraction, Decomposition, Number Bases, and Representation

4.1 Abstraction and Abstraction Hierarchies 4.2 Decomposition, Pattern Recognition, and Developing Algorithms 4.3 Number Bases: Binary, Octal, Decimal, and Hexadecimal 4.4 Algorithm Formats: Natural Language, Flowcharts, Pseudocode, and Tracing

5 Chapter 5: Algorithms: Efficiency, Limits of Computing, and Randomization

5.1 Algorithm Efficiency: Linear, Quadratic, Exponential, and Logarithmic Growth 5.2 Limits of Computing: Unsolvable Problems, Intractability, and Heuristics 5.3 Randomization, Random vs. Pseudorandom Numbers, and Scaling to a Range

6 Chapter 6: Algorithms: Searching, Sorting, and Recursion

6.1 Searching Algorithms: Linear Search and Binary Search 6.2 Sorting Algorithms: Tracing, Comparisons, Correctness, and Efficiency 6.3 Recursion: Base Cases, Tracing, Errors, and Iterative Equivalents

7 Chapter 7: Programming: Variables, Data Types, Strings, and Expressions

7.1 Variables, Data Types, and Type Conversion 7.2 Strings and String Operations 7.3 Operators, Precedence, Expressions, and Formulas 7.4 Boolean Expressions, Truth Tables, and Boolean Algebra

8 Chapter 8: Programming: Selection, Iteration, and Writing Code

8.1 Sequence and Selection: if, else, Chained and Nested Conditions 8.2 Iteration: for, while, do … while, and repeat … until Loops 8.3 Reading, Completing, and Modifying Code

9 Chapter 9: Programming: Procedures, Arrays, and Data Structures

9.1 Procedures, Parameters, Return Values, Nested Calls, and Scope 9.2 Arrays, Lists, and Two-Dimensional Arrays 9.3 Stacks, Queues, and Dictionaries (Maps)

10 Chapter 10: Programming: Correctness, Errors, Testing, and Code Quality

10.1 Program Correctness: Preconditions, Postconditions, Invariants, and Testing vs. Proof 10.2 Error Types and Debugging Techniques 10.3 Choosing Useful Test Cases: Boundaries, Partitions, Coverage, and Regression 10.4 Extensibility, Modifiability, and Reusability: Constants and Parameterization 10.5 Documentation, Code Reviews, Peer Feedback, and End-User Feedback

11 Chapter 11: Programming: Events, Usability, Input Validation, and APIs

11.1 Event-Driven Programming, Asynchronous Events, and Concurrency 11.2 Usability, Meaningful Error Messages, and Input Validation vs. Verification 11.3 Libraries and APIs: Reading Definitions, Making Calls, and Weighing Trade-offs

12 Chapter 12: Programming: Languages, Tools, Paradigms, and Object-Oriented Design

12.1 Low- and High-Level Languages, Compilers and Interpreters, and IDEs 12.2 Programming Paradigms: Procedural, Object-Oriented, and Others 12.3 Classes, Objects, Instance Variables, Methods, and Encapsulation 12.4 Inheritance, Polymorphism, and Overloading vs. Overriding

13 Chapter 13: Data: Bits, Encoding, Compression, and Encryption

13.1 Bits and Bytes: Why Binary, Storage Calculations, and Signed Integers 13.2 Encoding Text, Images, and Sound 13.3 Lossless and Lossy Compression: Run-Length Encoding, Huffman Coding, and Media Formats 13.4 Encoding vs. Encryption, Symmetric and Public-Key Encryption, and Their Trade-offs

14 Chapter 14: Data: Analysis Tools, Simulation, Storage, and Collection

14.1 Analyzing Data with Spreadsheets: Cleaning, Transforming, and Visualizing 14.2 Simulation and Modeling 14.3 Files, Databases, and Storage Requirements: Scale, Redundancy, and Backup 14.4 Collecting, Aggregating, and Generating Data: Public Data Sets, Surveys, Sensors, and Crowdsourcing

15 Chapter 15: Computing Systems: Hardware, Operating Systems, and Computing Environments

15.1 Hardware Components and the Fetch–Decode–Execute Cycle 15.2 Operating Systems, Software Components, and Resource Issues 15.3 Embedded Systems, the Internet of Things, and Types of Computing Systems 15.4 Local, Network, and Cloud Computing and Storage; How Binary Data Are Stored

16 Chapter 16: Networks, the Internet, the Web, and Cybersecurity

16.1 Network Types and Wired and Wireless Communication 16.2 Network Hardware and Layered Network Models (OSI and TCP/IP) 16.3 Network Performance: Bandwidth, Latency, Load, and Estimating Needs 16.4 How the Internet Works: Protocols, IP Addressing, DNS, URLs, and Reliability 16.5 The Web: HTTP, HTML and Markup Languages, Browsers, Servers, and Clients 16.6 Cybersecurity: The Five Pillars, Strong Passwords, Security Strategies, and Trade-offs

11.2 Usability, Meaningful Error Messages, and Input Validation vs. Verification

Key Takeaways Explain This Topic AI

A meaningful error message says what went wrong and how to fix it in plain language, such as "Enter a whole number from 1 to 12," instead of "Error 42" or "Invalid input."

Usability improves with clear prompts, sensible defaults, immediate feedback, confirmation before destructive actions, undo, and not making users re-enter data that was accepted.

Validation checks that input is reasonable: type, range, format, length, presence, or membership in an allowed list.

Verification checks that input is the value the user intended, for example by typing a password or email address twice or by clicking a confirmation link.

Accessibility features in code include text alternatives for images, captions, full keyboard operation, labels read by screen readers, sufficient contrast, and never using color alone to convey meaning.

Last updated: September 2026

What this competency asks

Two ETS competencies are combined here:

Be familiar with usability and user experience (for example, ease of use and accessibility): identify code that improves on given code in terms of usability or user experience, identify meaningful error messages , and identify features that improve accessibility .

Understand programming techniques to validate correct input and detect incorrect input : identify effective input validation strategies, compare data validation (proper range and format) and data verification (for example, password verification), and identify improvements to code for which data validation is required.

Usability and user experience

Usability is how easily people can use software to accomplish their goals. User experience (UX) is broader and includes how the whole interaction feels. Common usability qualities include learnability, efficiency, memorability, protection from errors, and satisfaction.

  • Feature Improves usability because…
  • Clear prompts that state the expected format Users know what to enter: "Enter date (MM/DD/YYYY)"
  • Sensible defaults Common cases need fewer steps
  • Immediate feedback Users know that an action worked: "Saved" or a progress bar
  • Confirmation before destructive actions Prevents accidents: "Delete all 32 grades? This cannot be undone."
  • Undo Mistakes are recoverable
  • Keep accepted input after an error Users fix only the bad field instead of retyping everything
  • Consistent layout and wording Knowledge carries over from screen to screen
  • Limit choices to valid ones A drop-down list of months cannot produce "Febtember"
  • Meaningful error messages

Poor message Why it fails Meaningful message

"Error 0x3F" A code with no meaning to users "The file could not be saved because the disk is full. Free some space and try again."

  • "Invalid input" Does not say what is wrong or how to fix it "Quantity must be a whole number from 1 to 99."
  • "You entered it wrong!" Blames the user and gives no help "That email address is missing an @ symbol."

"NullPointerException at line 88" Technical detail meant for developers "We couldn't load your class list. Please refresh the page." (Log the details for developers.)

A meaningful message is specific, written in plain language, polite, placed next to the problem, and tells the user how to recover .

Accessibility features in code

Accessible software works for people with visual, hearing, motor, and cognitive disabilities (Section 2.2). Features a programmer can add:

  • Text alternatives for images and icons (alt text), and labels on form fields that screen readers announce
  • Captions and transcripts for audio and video
  • Full keyboard operation with a visible focus indicator

Sufficient color contrast , and meaning that never depends on color alone (add text or icons to red and green status)

  • Resizable text and layouts that reflow when text is enlarged
  • Adjustable or no time limits , and pause controls for moving content
  • Error messages that are announced to screen readers, not only shown in color
  • Input validation

Input validation checks that data are acceptable before the program uses them. It prevents crashes (such as a runtime error from converting "abc" to a number), prevents wrong results, and protects security, since unvalidated input enables attacks such as SQL injection.

  • Check Question it asks Example
  • Type Is it the right kind of data? Age must be an integer
  • Range Is it within limits? 0 ≤ age ≤ 120; 1 ≤ month ≤ 12
  • Format Does it match a pattern? Email has one @ and a domain; ZIP code is 5 digits
  • Length Is it too short or long? Password at least 12 characters
  • Presence Is a required field filled in? Last name is not empty
  • Allowed values (lookup) Is it one of the permitted choices? Grade level is 9, 10, 11, or 12
  • Consistency Do related fields agree? End date is not before start date
  • Validating in code int month ← readInt ( )
  • while ( ( month < 1 ) or ( month > 12 ) )
  • print "Month must be a whole number from 1 to 12. Please try again."
  • month ← readInt ( )
  • end while

The loop re-prompts with a meaningful message until the value is valid. The condition describes the invalid values, which is the negation of the valid range 1 ≤ month ≤ 12 (De Morgan, Section 7.4).

Where validation is required: any place external input enters the program, including keyboard input, files, sensors, network messages, and form fields. Look especially at values used as divisors , array indexes , loop bounds , file names , and parts of database queries . On the web, validate on the server as well as in the browser, because browser checks can be bypassed.

Validation vs. verification

Validation Verification

Question Is the data reasonable : the right type, range, and format? Is the data what the user intended , or does it match the true value?

Example Rejecting a birth year of 3025 Asking the user to type a new password twice and checking that the two entries match

Another example Checking that an email address has the right format Sending a confirmation link to that address

Can it catch a plausible typo? No: 1986 typed as 1968 passes range checks Yes: double entry exposes mismatches

Validation cannot guarantee correctness. A valid value can still be wrong . Verification confirms that the entered value is the intended one, commonly through double entry or confirmation . ETS gives password verification as the example.

Checking a login password against the stored (hashed) password is also a verification, of identity. That is authentication, covered in Section 16.6.