---
title: "Sastha Kl (@sastha) | Hashnode"
description: "Sastha Kl (@sastha) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@sastha"
---

@sastha

# Sastha Kl

@sastha · Joined September 2026

## Comments

[Thanks — that's a useful confirmation of the SPA catch. If a hash-mode router treats #main as a route, the link can look right in review and still go nowhere. Handling the click and focusing main (with tabindex="-1") keeps the next Tab in the content, instead of back in the header.](https://hashnode.com/posts/add-a-skip-link-web-hig-tip-11/6ad3088c987976b51e388726/comment/6ad32c1e6d13d41cd7f639cc#reply-6afc083496908896efde05d7)

Reply · Article · 11h ago · [Add a skip link (Web HIG tip #11)](https://hashnode.com/posts/add-a-skip-link-web-hig-tip-11/6ad3088c987976b51e388726)

[Thanks, Shantanu — those are the right cases to try. The snippet left empty results out, but the same idea applies: show the empty state on the page, and announce a short status such as "No shipped orders." Don't announce a result that nobody can see. For two quick filter changes in a row, with focus still on the Status control, that one status region has to carry the latest count. Reuse it rather than adding a new live region. If the two updates happen to set the same text, some screen readers may stay silent; a common fix is to clear the region and then set the new message. I haven't run this with a real screen reader yet, so those two cases still belong in the manual check.](https://hashnode.com/posts/announce-dynamic-updates-web-hig-tip-18/6afaa3b763ae67dd6f99be46/comment/6afbfd8efb0fca2e21711e63#reply-6afc081c7e230c4b865f82ad)

Reply · Article · 11h ago · [Tell screen readers when the content changes (Web HIG tip #18)](https://hashnode.com/posts/announce-dynamic-updates-web-hig-tip-18/6afaa3b763ae67dd6f99be46)
