Accessible by Default: How Nyura is Building for Everyone

Over 1 billion people worldwide live with some form of disability. When we build apps that only work with a mouse and perfect vision, we exclude a huge part of our potential users. At Nyura, we believe productivity tools should work for everyone — whether you navigate with a keyboard, use a screen reader, or rely on voice control.

Accessibility is not just about compliance. It makes apps better for everyone: keyboard shortcuts speed up power users, proper contrast helps in bright sunlight, and semantic HTML improves SEO. Every accessibility improvement is a UX improvement.

ARIA labels are invisible text annotations that tell screen readers what interactive elements do. A sighted user sees a trash can icon and knows it means delete. A screen reader user hears nothing — unless the button has an aria-label.

In the latest release, we audited every icon-only button in Nyura and added proper ARIA labels:

- Music player controls (play, pause, add to queue, clear search)
- Playlist management (share, rename, delete, back navigation)
- Travel cards (nearby lounges, segment details)
- Contact suggestions (dismiss, mark as contacted)
- Task timeline sections (expand/collapse with proper aria-expanded)
- Spotify search tabs (role=tablist with aria-selected)

Every button now announces what it does. No more silent icons.

When a keyboard user presses Tab on a web page, focus moves through every navigation link before reaching the main content. On complex apps like Nyura with sidebars and top bars, that could mean 20+ Tab presses just to get to your tasks.

We added a skip-to-content link that becomes visible when you press Tab. One keystroke and you are at the main content. It is invisible to mouse users, but it is the first thing keyboard users and screen readers encounter.

This is tested automatically in our E2E test suite — we verify that pressing Tab on any public page makes the skip link visible and focused.

We use axe-core, the industry-standard accessibility testing engine, integrated directly into our Playwright end-to-end test suite. Every public page is scanned for WCAG 2.1 AA violations on every deployment.

Our test pipeline catches:
- Missing alt text on images
- Form inputs without labels
- Insufficient color contrast
- Interactive elements without accessible names
- Heading hierarchy violations

Currently 6 public pages are scanned: login, pricing, blog, legal, GDPR, and privacy. Any critical or serious violation fails the build.

We also run 35 QA convention tests that enforce code quality ratchets — limits on silent error catches, localStorage access patterns, file complexity, and more. These limits can only decrease over time, never increase. Quality only goes up.