Screen Readers, Keyboards and Low Vision: Accessibility Basics for Developers

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.
Use semantic HTML. Real buttons, links, headings, lists and form labels give screen readers the structure they need for free.
Label everything. Inputs need a connected label. Icon-only buttons need an accessible name.
Manage focus. After opening a modal or changing the page, move focus to the right place and keep a visible focus ring.
Do not trap keyboard users. All interactive elements should work with Tab, Enter and Escape.
Announce changes. Use live regions for notifications, loading states and errors.
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.
Understanding how optic nerve damage affects vision makes these guidelines feel real, not abstract.
More at optic-atrophy.com