Frontend
1.0.0
1.0.0
  • Introduction
  • Project Guidelines
    • INTRODUCTION
    • PROJECT SETUP
      • Frameworks
      • Static type checking
      • Code Quality Tools
      • Enforcing good practices
      • Testing
      • Code versioning flow
      • Continuous Integration & Delivery
      • Isolated component development
    • EFFECTIVE AND CONSISTENT WORKFLOW
      • Code structure, architecture
      • Code versioning and review flow
      • Testing
      • Continuous Integration & Delivery
      • Dependency checking
      • Project Management Tools
      • Communication
    • THE QUALITY OUTPUT
      • Great UX/UI
        • Design & User Experience
        • SEO, SMO
      • Accessibility
        • Introduction
        • Why a11y?
        • Fundamentals
        • A11y in STRV
          • Share Knowledge
          • Project Life Cycle
          • A11y culture
      • Performance
        • Bundle Size
        • Deployment
        • Audits & Reports
      • Stability
        • Documentation
        • Analytics & Error Tracking
        • Quality Assurance
      • Security
    • FINAL WORDS
    • ACKNOWLEDGEMENT
Powered by GitBook
On this page

Was this helpful?

  1. Project Guidelines
  2. THE QUALITY OUTPUT
  3. Accessibility

Introduction

Have you ever used a website with your hand broken? Maybe you had problems with reading that small text on your phone in direct sunlight. Or were you in a place where you had to mute your phone, but that one app became unusable without sound cues?

All of this falls under accessibility.

But wait. You might be thinking, Isn’t “accessibility” just making sure disabled people can use our product?

Accessibility, also known as a11y, is more of a mindset that ensures no user gets left behind when developing our apps. So join us on this journey of learning how and why to make our apps better. For everyone

PreviousAccessibilityNextWhy a11y?

Last updated 4 years ago

Was this helpful?