Skip to main content
Accessibility.com, LLC
Category: Assistive Technologies

Sip-and-Puff Device

Also known as: SNP, Sip-and-puff, Sip 'n' puff, Sip and puff switch
Simply put

A sip-and-puff device is a type of assistive technology that lets a person operate a computer or other device by breathing into a tube, either by inhaling (sipping) or exhaling (puffing). It is commonly used by people with significant mobility limitations who cannot easily use their hands. The different breath actions send signals that the connected device interprets as commands.

Formal definition

A sip-and-puff (SNP) device is a form of switch-based assistive technology that converts air-pressure inputs into discrete control signals. Users generate commands by sipping (inhaling) or puffing (exhaling) through a tube or mouthpiece, with variations such as hard versus soft breaths often mapped to distinct switch actions. SNP is frequently used by individuals with severe motor or mobility impairments and can serve as an input method for switch-access frameworks (for example, switch control on operating systems) as well as for controlling equipment such as power wheelchairs. As with other switch systems, effective use typically depends on how the SNP inputs are mapped to the target device's accessibility settings and scanning or selection methods.

Why it matters

Sip-and-puff devices provide a critical pathway to independence for people with significant motor or mobility impairments who cannot reliably use their hands to operate a keyboard, mouse, touchscreen, or the controls of equipment such as a power wheelchair. By converting simple breath actions into discrete commands, an SNP device can give a user meaningful control over computers, communication tools, and mobility equipment that would otherwise be inaccessible. For accessibility practitioners, understanding how these devices work underscores that input methods vary widely across the disability community and that digital experiences must accommodate more than conventional pointing and typing.

Because a sip-and-puff device functions as a switch-based input, the accessibility of any software or website it is used with depends heavily on whether that interface supports switch-access and keyboard-operable navigation. An interface that requires precise mouse movements, hover-only interactions, or elements that cannot be reached and activated through switch scanning can effectively exclude an SNP user even when no visual barrier exists. This makes SNP an important consideration when evaluating whether a product genuinely supports the full range of assistive technologies rather than assuming standard input methods.

Designing and testing with switch-based access in mind helps surface barriers that automated checks alone may not detect. Ensuring that all functionality is operable without a mouse, that focus order is logical, and that interactive elements can be reached and selected through sequential navigation generally benefits SNP users along with people relying on other switch and keyboard-based methods. This guidance is educational and not legal advice; specific obligations depend on the applicable authority and evolving requirements, and organizations should consult qualified counsel where legal questions arise.

Who it's relevant to

People with significant mobility limitations
Individuals with severe motor or mobility impairments who cannot easily use their hands may rely on sip-and-puff devices to operate computers, communication tools, and equipment such as power wheelchairs. For these users, the device can be a primary means of interacting with technology and maintaining independence.
Accessibility engineers and QA testers
Because SNP is a switch-based input, engineers and testers should verify that all functionality is operable through switch-access and keyboard-equivalent navigation, with logical focus order and reachable, selectable interactive elements. Manual and assistive-technology testing are needed here, as automated checks detect only a portion of potential barriers.
UX and product designers
Designers can support SNP users by avoiding interactions that depend on precise pointer movement or hover-only behavior and by ensuring that scanning or sequential selection can reach every interactive control. Considering switch-based access early helps prevent barriers that are difficult to remediate later.
Occupational therapists and assistive technology specialists
Practitioners who configure and support these devices help map sip and puff inputs, including hard and soft breath variations, to a user's target devices and accessibility settings. Their role is central to translating an individual's abilities into an effective control scheme.
Compliance officers and accessibility program leads
Those responsible for accessibility programs should recognize SNP as one of many assistive technologies that products must accommodate. Supporting switch and keyboard-based access can be part of a broader effort to reduce barriers, though it does not by itself guarantee an accessible experience for all users or immunity from legal claims; consult qualified counsel on specific obligations.

Inside SNP

Sip-and-Puff (SNP) Input Mechanism
An assistive technology that allows a user to send signals by inhaling (sipping) or exhaling (puffing) into a wand, tube, or straw, translating breath pressure into discrete input commands.
Mouthpiece or Wand
The physical tube or straw the user interacts with by breath, typically positioned near the mouth and mounted so it can be reached without hand use.
Pressure Sensor and Signal Processor
Hardware that detects the direction and intensity of breath (hard sip, soft sip, hard puff, soft puff) and converts those pressure changes into distinct input signals.
Switch or Interface Controller
The component that maps breath signals to actions, often functioning as a switch-based input that can drive scanning interfaces, mouse emulation, or keyboard emulation.
Target User Group
People with limited or no use of their hands or arms, including individuals with conditions affecting mobility, who rely on breath control to operate computers, mobile devices, or powered equipment such as wheelchairs.
Relationship to Web Accessibility
As a form of assistive technology, sip-and-puff devices depend on content and interfaces that support keyboard-equivalent and switch-based operation, which relates to WCAG success criteria addressing keyboard accessibility and input methods.

Common questions

Answers to the questions practitioners most commonly ask about SNP.

Does supporting sip-and-puff devices require special code or a dedicated integration on my website?
Generally, no. Sip-and-puff devices typically function as input emulators, translating breath actions into standard inputs such as keystrokes, mouse movements, switch activations, or scanning selections at the operating system or assistive technology level. Because of this, websites and applications usually do not need device-specific code. What matters is that your interface is fully operable through the input methods these devices emulate, most commonly keyboard and switch access. Building robust keyboard operability and, where relevant, switch-friendly interaction generally does the practical work of supporting sip-and-puff users, rather than any custom integration.
Is a sip-and-puff device only used by people who cannot use their hands at all?
Not necessarily. Sip-and-puff devices are commonly associated with users who have significant motor disabilities, including those affecting the arms and hands, but the population is broader and varied. Individuals may use these devices for many reasons and with differing levels of other motor ability. Framing accessibility around a single assumed user profile can lead to gaps; the more reliable approach is to ensure your interface works well through the underlying input methods (such as keyboard and switch input) that sip-and-puff and other alternative input devices depend on, which benefits a wide range of users.
Which WCAG success criteria are most relevant when designing for sip-and-puff users?
Because sip-and-puff devices commonly emulate keyboard or switch input, criteria addressing keyboard operability are especially relevant, including keyboard accessibility and the ability to move focus away from any component without becoming trapped. Criteria addressing sufficient time to complete actions and avoiding time limits that cannot be adjusted are also important, since alternative input can be slower. Success criteria added in later WCAG versions concerning pointer and motor interaction may further apply depending on your interface. Consult the current W3C WCAG documentation for the exact criteria, their conformance levels, and the version in which each was introduced.
How should timeouts and time limits be handled to accommodate slower input?
Because navigating and selecting with a sip-and-puff device can take longer than with a mouse or standard keyboard, avoid imposing time limits where possible, and where limits are necessary provide mechanisms to extend, adjust, or turn them off consistent with WCAG guidance. Session timeouts, carousels that advance automatically, and processes that expire can create barriers for slower input methods. Testing with realistic interaction speeds helps identify where time constraints may exclude users.
Can automated testing confirm that my site works with sip-and-puff devices?
No. Automated testing detects only a portion of accessibility issues and cannot confirm real-world operability with alternative input devices. Verifying support for sip-and-puff and similar tools generally requires manual testing, including keyboard-only and switch-based interaction, and ideally testing with the relevant assistive technologies and input hardware. Involving users who rely on these devices provides the most reliable picture of whether an interface is usable in practice.
What design practices most improve usability for sip-and-puff users?
Practices that support alternative input generally help, including a logical and predictable focus order, clearly visible focus indicators, sufficiently large and well-spaced interactive targets, and interactions that do not require precise timing, dragging, or complex gestures without an accessible alternative. Providing keyboard-operable equivalents for all functionality and minimizing the number of steps required to complete tasks also reduces effort. These measures address usability, which is related to but distinct from conformance and from legal compliance; this guidance is not legal advice.

Common misconceptions

Sip-and-puff devices only work with specialized software and cannot use mainstream websites or applications.
Because these devices commonly emulate keyboard, mouse, or switch input, they can generally operate standard interfaces provided those interfaces support keyboard-equivalent and switch-based operation. Content that relies on mouse-only interactions or lacks keyboard operability may not be usable regardless of the device.
If a site meets WCAG success criteria, it is automatically fully usable with a sip-and-puff device.
Meeting WCAG success criteria improves the likelihood of compatibility but does not guarantee a usable experience for every assistive technology user. Manual testing with actual assistive technology and input methods is needed to confirm real-world usability.
Supporting sip-and-puff users requires building a separate, dedicated accessible interface.
Supporting these users is generally accomplished by making a single interface robustly keyboard- and switch-operable rather than by creating a separate version. Separate interfaces often introduce maintenance gaps and can lag behind the primary experience.

Best practices

Ensure all interactive functionality is operable through keyboard-equivalent input, since sip-and-puff devices commonly rely on keyboard, switch, or mouse emulation.
Provide a logical, predictable focus order and clearly visible focus indicators so users navigating sequentially can track their position.
Avoid interactions that require simultaneous inputs, precise timing, or mouse-only gestures that breath-based switching cannot reproduce.
Support efficient navigation mechanisms such as skip links, landmarks, and headings to reduce the number of discrete inputs required to reach content.
Test with actual assistive technology and switch or scanning input methods, recognizing that automated checks detect only a portion of potential barriers.
Consult current W3C guidance and, where legal obligations are a concern, qualified legal counsel, since this entry is informational and requirements evolve through regulation and case law.