accessible-notifications SKILL.md skillA
accessible-notifications from thedaviddias/front-end-checklist is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add thedaviddias/front-end-checklist/accessible-notifications@git:20260529.7c05904Pins git:20260529.7c05904 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- thedaviddias/front-end-checklist
- Path
skills/accessible-notifications/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260529.7c05904, committed May 29, 2026
- Size
- 1,760 bytes
- Repository stars
- 74,516
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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. --- …
Read the whole file at its exact version.
How to install
mdr add thedaviddias/front-end-checklist/accessible-notifications@sha256:3fd876839e914c1dThe line at the top of this page pins the label git:20260529.7c05904, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_px2rtzntkdt63e6b)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 29, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1760 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
thedaviddias/front-end-checklist · 74,516 stars · license MIT · pushed 2026-10-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_px2rtzntkdt63e6b GET https://markdownregistry.com/api/v1/resolve?ref=thedaviddias/front-end-checklist/accessible-notifications GET https://markdownregistry.com/api/v1/blob/3fd876839e914c1d24faa67560f73564a8ea3aeca5991bd538da03468fcd6524
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.