Adding Accessibility Site-wide: Not a Feature, but Basic Respect

Why I Did It

Accessibility isn't about "adding features"—it's more like ensuring a site can be used normally.
For me, it's a matter of basic respect:
Keyboard users, those with reduced motion preferences, and color-sensitive individuals should all be able to browse content naturally.

What I Did (Basic but Critical)

1) Site-wide Consistent Visible Focus

All interactive elements (links, buttons, inputs) have a clear visible focus during keyboard navigation, avoiding the "where am I?" problem.

2) Respect Motion Preferences

For users who have prefers-reduced-motion enabled in their system settings,
excessive animations and transitions are disabled to prevent distractions.

Added aria-label to the sidebar search input,
so screen readers can announce it as "Search articles."

4) Perceivable Search Results

Added aria-live to the search result count,
letting screen readers know when the number of results changes.

My Principles

No "cool but uncontrollable" interactions
Interactive elements must have visible focus
Motion can be turned off when necessary

Summary

This wasn't a "feature upgrade"—it was simply about meeting the basic standards of a web page.
By keeping accessibility in mind, the site becomes more stable, elegant, and feels like a real tool.