The latest articles on DEV Community by Prashant Tyagi (@prashant_tyagi_5a9de19b00). https://dev.to/prashant_tyagi_5a9de19b00 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4201664%2F71e7bfd0-25a3-4a2a-bed8-8ba8e246ec2b.png https://dev.to/prashant_tyagi_5a9de19b00 en Prashant Tyagi Fri, 23 Oct 2026 09:53:53 +0000 https://dev.to/prashant_tyagi_5a9de19b00/screen-readers-keyboards-and-low-vision-accessibility-basics-for-developers-2e45 https://dev.to/prashant_tyagi_5a9de19b00/screen-readers-keyboards-and-low-vision-accessibility-basics-for-developers-2e45 <p>People with optic atrophy and other vision conditions often rely on screen readers, zoom or keyboard-only navigation. A few habits make your app far more usable.<br> Use semantic HTML. Real buttons, links, headings, lists and form labels give screen readers the structure they need for free.<br> Label everything. Inputs need a connected label. Icon-only buttons need an accessible name.<br> Manage focus. After opening a modal or changing the page, move focus to the right place and keep a visible focus ring.<br> Do not trap keyboard users. All interactive elements should work with Tab, Enter and Escape.<br> Announce changes. Use live regions for notifications, loading states and errors.<br> Test. Try NVDA, VoiceOver or TalkBack for ten minutes, then run an automated check like axe or Lighthouse. Automated tools catch only part of the problems.<br> Understanding how optic nerve damage affects vision makes these guidelines feel real, not abstract.<br> More at optic-atrophy.com</p> a11y frontend html webdev