Skip to content
Back to skills

Accessible Notifications

ASecurity

Use when reviewing templates, rendered HTML, or shared components related to Make notifications accessible. Validate the final browser-facing markup, not just the source framework abstraction.

  • 74,358 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 5, 2026
developmentgofrontend

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 5, 2026

npx -y skills add thedaviddias/Front-End-Checklist --skill accessible-notifications --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Accessible Notifications?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Accessible Notifications
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedaviddias-accessible-notifications/badge)](https://www.skillsdirectory.com/skills/thedaviddias-accessible-notifications)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: accessible-notifications
description: "Use when reviewing templates, rendered HTML, or shared components related to Make notifications accessible. Validate the final browser-facing markup, not just the source framework abstraction."
metadata:
  category: html
  priority: high
  difficulty: intermediate
  estimatedTime: "25"
  source: frontendchecklist.io
  url: https://frontendchecklist.io/rules/html/accessible-notifications
---

# Make notifications accessible

Without proper ARIA attributes, screen reader users miss critical notifications like form errors, success messages, and real-time updates—leaving them unaware of important page changes.

## Quick Reference

- Use aria-live regions to announce dynamic content changes
- Choose between 'polite' (waits) and 'assertive' (interrupts) based on urgency
- Ensure notifications persist long enough to be read
- Provide visible and programmatic dismiss options

## Check

Verify notifications use aria-live regions, appropriate role (alert or status), and persist long enough to be read.

## Fix

Implement notifications with role='alert' or role='status', aria-live='polite' or 'assertive', and adequate display time.

## Explain

Explain how accessible notifications ensure all users are informed of important updates regardless of how they interact with the page.

## Code Review

Review templates, server-rendered HTML, and shared components that output markup related to Make notifications accessible. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.

---

For full implementation details, code examples, and framework-specific guidance,
see `references/rule.md`.

Rule page: https://frontendchecklist.io/rules/html/accessible-notifications

Files in this skill

  • SKILL.md1.7 KB
  • references/rule.md7.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…