Published November 16, 2026 · Accessibility · 8-minute read
Visual, vibrating and silent alarms: a 9-test accessibility checklist
Not every useful reminder makes a noise. A meeting cue may need to be visible, a morning wake-up may need a strong bed-shaker, and a quiet work reminder may be better felt on the wrist. The right alert depends on the person, the environment, and the consequences of missing it. This practical guide helps you choose a reminder and verify that it reaches you.
1. Match the alert to the task
There is no universal silent alarm. The UK's RNID guidance describes waking aids based on vibration, light, and amplified sound. The National Deaf Children’s Society notes that some vibrating watches are suitable for discreet daytime reminders but may not be powerful enough to wake someone. Test with the individual, not just against a product specification.
| Use case | Try | Verify |
|---|---|---|
| Waking from sleep | Dedicated bed-shaker or purpose-built vibrating alarm, with a separate backup. | Can it wake the actual sleeper in their usual position? Does it work after a power interruption? |
| Quiet desk work | On-screen status plus optional wearable vibration. | Can you notice the cue while looking elsewhere? |
| Busy shared room | Readable text and a high-contrast visual cue; optional sound if useful. | Is it understandable without hearing or distinguishing colors? |
| Important appointment | Calendar or operating-system reminder plus a second independent notification channel. | Do both alerts survive browser closure and screen lock? |
2. Know what a browser can and cannot promise
A web page might show a visible message while open, and supported browsers may display operating-system notifications after permission is granted. But the MDN Notifications API documentation marks platform support as limited, describes permission and HTTPS requirements, and distinguishes page-bound notifications from service-worker notifications. Some mobile browsers cannot use the regular Notification() constructor.
Likewise, the MDN Vibration API reference reports limited availability: calling navigator.vibrate() does not guarantee an actual vibration. Hardware availability, browser support, user interaction, and device settings all matter. A webpage should never say “vibration enabled” until an actual user confirms feeling it on that device.
For Alarmclock.click specifically, the countdown interface and alarm sound can assist while the site is active, but an open tab is not a substitute for a dedicated wake-up alarm. See the browser alarm reliability checklist for tab suspension, sound permissions, and backup arrangements.
3. Nine practical tests before you trust an alert
Use this as an acceptance checklist with the person receiving the alerts. Check “works” only after observing the real device. You can print the page to mark results by hand.
| Test | How to run it | Result / notes |
|---|---|---|
| 1. Visible state | Start and finish a noncritical one-minute test. Look for the exact message “Timer finished,” not only a color shift. | □ Works □ Needs change ____________ |
| 2. Without sound | Mute the browser or device. Check whether you still notice and understand the cue. | □ Works □ Needs change ____________ |
| 3. Across the room | Move to your usual work or sleep position. Check whether light or vibration is actually perceivable. | □ Works □ Needs change ____________ |
| 4. Locked screen | Lock the phone or computer and repeat a noncritical test. Record exactly what appears. | □ Works □ Needs change ____________ |
| 5. Closed tab | Close the web page before a noncritical reminder. If it fails, document that and use an independent alternative. | □ Works □ Needs change ____________ |
| 6. Permission denied | Test with browser notification permission disabled. Does the page explain the limitation clearly? | □ Works □ Needs change ____________ |
| 7. Vibration support | If an app advertises vibration, ask the user to trigger a test intentionally and confirm they felt it. | □ Works □ Needs change ____________ |
| 8. Keyboard and text | Operate the reminder without a mouse. Confirm labels, status text, and controls remain readable at zoom. | □ Works □ Needs change ____________ |
| 9. Independent backup | Disconnect the internet or switch off the browser. Verify a separate device still alerts at the intended time. | □ Works □ Needs change ____________ |
4. Accessibility details developers often miss
- Never use color alone: Show “Running,” “Paused,” or “Finished” in text, with shape or icon cues if useful. This follows W3C's guidance on use of color.
- Make reminders user-controlled: Let people choose when to be reminded and how they receive an alert, consistent with the W3C cognitive accessibility pattern for reminders.
- Communicate completion semantically: When a web interface displays a non-urgent status message, appropriate semantics such as
role="status"can help assistive technology announce it without moving keyboard focus. See W3C's status-message explanation. Do not turn every ticking second into a screen-reader announcement. - Offer a non-audio acknowledgment: A visible “Dismiss” or “Acknowledge” control matters when sound cannot be heard; make it operable by keyboard and touch.
- Distinguish personal reminders from emergency equipment: Visual fire alarms and other regulated alerting systems have separate requirements. A personal productivity timer does not satisfy them.
5. A two-minute setup card
Task: ____________________ Next reminder: __________
Primary channel (tested): _________________________________
Backup device (independent): ____________________________
Tested on device / browser: ______________________________
Works with muted sound? □ Yes □ No · Works with screen locked? □ Yes □ No
Owner / next retest date: __________________________________
If the reminder affects a real deadline, set it in a trusted calendar or device alarm first. Use the web timer as a convenient additional cue, not the only one. For UI-level testing, pair this guide with the 12-point accessible timer checklist and 15-case timer test matrix.
Sources and further reading
- RNID: Alarm clocks for people who are deaf or have hearing loss
- National Deaf Children’s Society: Alarm clocks
- MDN: Vibration API
- MDN: Notifications API
- W3C WCAG: Understanding use of color
- W3C WAI: Provide reminders
- W3C WAI: Understanding status messages
This guide is educational and does not certify any particular device or website as an accessible or safety-critical alarm.