Hardware hints for accessibility testing

When you test a website or app for accessibility, the computer itself can affect what you see. A small screen, a missing keyboard, or an unreliable microphone can change the experience. Hardware details help you plan a useful test, but they cannot tell you whether a person can use the product.

Start with System Info, then check the screen and input or audio devices you plan to use. The goal is to identify conditions that may affect a test, not to grade a person or assume what they need.

Collect useful hardware hints

1. Open System Info on the device you will use. Note the processor, graphics, screen, battery, and network details it reports. These give you context if a page behaves differently on a low-powered device or while running on battery.
2. Check the actual display setup with Screens. Note which screens are connected, their reported resolution, and their scale. If you are checking visible defects or color output, use the Display Test as a separate hardware check.
3. Test the input method you intend to use. The Keyboard Test checks whether key presses register. The Touch Screen Test can reveal dead zones or missed touch points, and the Mouse Test checks buttons and scrolling.
4. For workflows that rely on speech or sound, check the available devices. The Microphone Test checks whether sound reaches the computer, and the Speaker Test checks speaker output and left and right channels.
5. Repeat the task with the assistive technology and settings used in your real test. A browser hardware check cannot confirm that a screen reader, magnifier, switch device, captions, or voice control is configured correctly.

What the results mean

The screen resolution or scale differs from your expected setup

This can change how much content fits on screen and how large controls appear. Record the screen and scale settings so you can reproduce the test. It does not tell you whether text is readable or whether a page works with magnification. Check those directly in the website or app.

A key or touch point does not register

The input device or its connection may be unreliable, or a particular key or area may have a fault. Retest after reconnecting the device. A keyboard test only sees key events that reach the browser, and a touch test does not check how well a person can reach or operate a control.

The microphone or speakers do not respond

The selected device may be wrong, muted, disconnected, or blocked by a permission setting. Check the system and browser settings before treating this as an accessibility barrier in the product. A microphone test checks input, not the accuracy of speech recognition or voice control.

The processor or graphics details look modest

This is a reason to include the device in performance testing, especially if the page has animation or heavy visual effects. It is not a reliable measure of whether assistive technology will work. Browser tests also cannot report exact RAM capacity, and they do not show every hardware feature. See why a browser cannot measure exact RAM capacity.

The device details look normal, but the task is still difficult

That is a useful result. Hardware reports cannot detect confusing labels, poor focus order, missing captions, or controls that are difficult to operate. Continue by testing the task with the intended assistive technology and, where possible, with people who use it.

Prepare a representative test setup

1. Use the device and accessories from the real scenario. Test with the same laptop, phone, external display, keyboard, or switch device that your audience may use. If the test happens on a phone, try the actual phone rather than assuming a desktop touch test represents it.
2. Check accessibility settings before the test. In Windows 11, open Settings › Accessibility and check the relevant options, such as Narrator, Magnifier, or Captions. On macOS, open System Settings › Accessibility and check options such as VoiceOver or Zoom. Menu names can vary slightly between operating system versions.
3. Keep the display settings consistent. On Windows 11, check Settings › System › Display. On macOS, check System Settings › Displays. Note resolution and scaling, and avoid changing them midway through a comparison.
4. Test each input separately. Try the task with a keyboard, touch, or mouse as appropriate. If a key does not register in the browser test, reconnect the keyboard and retest before drawing conclusions about the page.
5. Separate device problems from product problems. If a microphone or speaker fails, check it outside the app as well. If the hardware test works but the product still fails, focus on the product's permissions, controls, and settings.

Know what a hardware check cannot prove

A browser can report only the information its platform makes available. System Info does not tell you whether a person uses a screen reader, what settings they prefer, or whether a page is accessible to them. A screen resolution does not prove that text has sufficient contrast, and a working keyboard does not prove that every task can be completed without a mouse.

Treat hardware hints as setup notes. Pair them with task-based testing, the relevant operating system features, and feedback from the people the product is meant to serve.