دانلود کتاب توسعه اپلیکیشن‌های موبایل فراگیر، ساخت اپلیکیشن‌های قابل دسترس برای iOS و اندروید

Accessibility and inclusion are intertwined. Inclusivity is about creating experiences that are welcoming to as many people as possible. Accessibility – the practice of making your app usable by people with diverse needs – is one part of building software that results in an inclusive experience. In Chapter 1, I provide background on accessibility, its history, and why it matters; Chapter 2 extends this into digital inclusion. The foundation of digital accessibility is the Web Content Accessibility Guidelines (WCAG). These serve as the benchmark by which we judge whether software is accessible. They are built on extensive research and expertise, so to use any other measure is vanity. However, for good reason, they are written in a way that can be impenetrable for anyone who isn’t an academic with a deep background in Web accessibility. So in Chapter 3, I aim to present the WCAG requirements in a way that feels more approachable to mobile developers and others working in the mobile space. This book is intended for anyone involved in creating mobile app experiences who wants to ensure what they are building is accessible and inclusive. I come from a native iOS development background, with occasional work in native Android, and so this book naturally focuses on implementation and how to create accessible apps from a developer’s perspective. That said, it is not limited to those who write code. While there are many code samples, they are a means of achieving the concepts discussed in the book – concepts that span visual design, user interface design, system design, and any other decisions that precede writing code. One of the strengths of software development is that we can build almost anything. However, certain approaches can lead to fragile implementations or poor experiences. The guidelines and discussions in this book should help you identify what makes a robust, accessible experience and guide your decisions. The code examples then demonstrate how to build the most accessible version of the experience you choose to create. Code is presented in Swift and SwiftUI for iOS and Kotlin and Jetpack Compose for Android. Where these frameworks do not yet support certain features, I may occasionally drop into UIKit or the Android view system where necessary. This book does not cover mobile web accessibility or any crossplatform frameworks. For mobile web, standard web accessibility techniques should apply. I do not have first-hand experience with crossplatform frameworks, so I have chosen not to cover them. More broadly, my view is that tools aiming to serve both major platforms often struggle to create an experience that feels at home on either, and the accessibility experience magnifies this. This book focuses on the two leading mobile platforms at a code level. However, if you are building apps for alternative operating systems such as KaiOS or Sailfish OS, the principles discussed in the non-code chapters should still apply. Chapter 4 explores how the accessibility system works on Android with Jetpack Compose, including techniques and knowledge for working with the accessibility tree. Chapter 5 covers feature-specific considerations for assistive technologies and accessibility features on Android. Chapter 6 examines the accessibility system on iOS, providing the knowledge and tools to allow the system to construct an effective accessibility tree. Chapters 7–10 then cover considerations and implementation details for specific assistive technologies and accessibility features in iOS. You may notice that Android receives fewer dedicated chapters than iOS. This is not a reflection of one platform being more or less accessible. Rather, it reflects differences in platform design. iOS, being historically design-led, often requires additional considerations to adapt or override default behaviors. Android, due in part to greater device diversity, has evolved differently. Chapter 11 provides practical guidance for testing accessibility aimed at QA engineers or anyone involved in validating user experiences. It covers both tools and techniques to improve coverage and iteration speed. Finally, Chapter 12 returns to the topic of inclusivity, exploring how the ideas introduced throughout the book can be applied to create more inclusive experiences for a wide range of users.