Current Page Link Solutions
summary
Compares practical ways to mark the current page link and rejects visual-only classes and replacing links with inert elements, notes testing with NVDA+Firefox and JAWS, and reports ~44 blog comments that produced better ideas. Flags ARIA label for overriding link text and translation problems, praises aria-describedby appended text for announcing “current page,” warns against aria-hidden removal, and recommends the simplest working solution: use #main fragment so the nav link becomes a same-page link that also serves as a skip-to-main.
AI-written summary · about
chapters (21)
- 0:00Intro
- 14:10Class
- 15:12Interoperability
- 15:50Text
- 18:12Techniques
- 18:30Remove the link
- 20:00Use areahidden
- 21:19Inconsistent navigation
- 23:13Area
- 27:41Testing
- 28:31Area to Area
- 29:45About Current Page
- 34:54About Same Page Link
- 36:39About Navigation Blocks
- 38:18About AriaCurrent
- 40:00Housekeeping
- 41:07RNIB
- 41:37Current
- 44:18NVDA
- 45:03Jonathan
- 46:25Daniel
related talks
47mBuilding Accessible Web Components
47mThe Links vs. Buttons Showdown
01h 01mA web for anyone, anywhere, anytime
01h 07mA web for anyone, anywhere, anytime
40mWebsite Accessibility Examples That Hinder Accessibility
45mA Web for Anyone, Anywhere, Anytime
27mMaking Interactions Accessible to All Users
23mPractical A11Y for Web Apps