アクセシビリティと国際化
アクセシビリティ機能を実装し、複数の言語や地域に対応できるよう準備することで、誰もが使えるアプリにします
「アクセシビリティと国際化」はCoddyKit上の無料Indie Hacker Mobile Appsレッスンです。 これはレッスン2/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはIndie Hacker Mobile Apps学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Indie Hacker Mobile Appsコースには全4レッスンが含まれています。
このレッスンの一部はまだ翻訳されておらず、英語で表示されています。
Welcome to Inclusive Design
Making your mobile app accessible and internationally friendly isn't just good practice; it's essential for reaching a wider audience and providing a great user experience for everyone.
In this lesson, we'll explore key principles and practical steps to achieve both.
Understanding Accessibility (A11y)
Accessibility (A11y) refers to designing and developing apps that can be used by people with a wide range of abilities and disabilities.
- Visual Impairment: Users might rely on screen readers or need high contrast.
- Motor Impairment: Users might need larger touch targets or keyboard navigation.
- Hearing Impairment: Users might need captions for audio/video.
By making your app accessible, you ensure it's usable by everyone.
Screen Readers & Labels
Screen readers are assistive technologies that read out loud the content on a screen, helping visually impaired users navigate your app.
For screen readers to work effectively, interactive elements need proper accessibility labels. These labels provide a descriptive text for the element that might not be visually obvious.
Try running this conceptual example:
public class AccessibilityDemo {
// A simplified Button component concept
static class Button {
String text;
String accessibilityLabel;
Button(String text, String accessibilityLabel) {
this.text = text;
this.accessibilityLabel = accessibilityLabel;
}
// Simulate what a screen reader might announce
String getScreenReaderAnnouncement() {
if (accessibilityLabel != null && !accessibilityLabel.isEmpty()) {
return accessibilityLabel;
}
return text; // Fallback to visible text
}
}
public static void main(String[] args) {
Button submitButton = new Button("Submit", "Tap to submit the form");
Button okButton = new Button("OK", null); // Missing a specific label
System.out.println("Screen reader announces (Submit): " + submitButton.getScreenReaderAnnouncement());
System.out.println("Screen reader announces (OK): " + okButton.getScreenReaderAnnouncement());
}
}Visuals: Contrast & Scale
Good visual design is also key for accessibility:
- Color Contrast: Ensure sufficient contrast between text and background colors. This helps users with low vision or color blindness.
- Dynamic Type/Font Scaling: Allow users to adjust font sizes. Respect system-wide font size settings so your app adapts to user preferences.
Tools are available to check color contrast ratios, ensuring your designs meet accessibility standards.
Touch Targets & Interaction
For users with motor impairments or those simply using a device one-handed, the size of interactive elements matters.
- Minimum Touch Target Size: Aim for a minimum touch target size of 48x48 device-independent pixels (DIPs) on both iOS and Android.
- Clear Feedback: Provide visual feedback when an element is tapped (e.g., a ripple effect or highlight).
This improves usability for everyone, not just those with specific needs.
Understanding Internationalization (I18n)
Internationalization (I18n) is the process of designing and developing an app in a way that makes it easy to adapt to various languages and regional differences without requiring engineering changes to the source code.
This means your app can be translated into multiple languages (localization) and handle different date formats, currencies, and text directions.
Localizing Your Text Strings
The core of internationalization for text is extracting all user-facing strings into separate resource files. Instead of hardcoding text, you use a 'key' that points to the correct translation for the user's selected language.
This approach makes it simple to add new languages or update existing translations without touching your app's code logic.
See how it works conceptually:
import java.util.HashMap;
import java.util.Map;
public class LocalizationDemo {
// Simulate language resource bundles
private static final Map<String, Map<String, String>> strings = new HashMap<>();
static {
// English strings
Map<String, String> enStrings = new HashMap<>();
enStrings.put("greeting", "Hello!");
enStrings.put("welcome_message", "Welcome to our app.");
strings.put("en", enStrings);
// Spanish strings
Map<String, String> esStrings = new HashMap<>();
esStrings.put("greeting", "¡Hola!");
esStrings.put("welcome_message", "Bienvenido a nuestra aplicación.");
strings.put("es", esStrings);
}
// Method to get a localized string
public static String getString(String locale, String key) {
Map<String, String> localeStrings = strings.get(locale);
if (localeStrings != null) {
return localeStrings.getOrDefault(key, "MISSING_STRING_FOR_" + key);
}
return "UNKNOWN_LOCALE";
}
public static void main(String[] args) {
String currentLocale = "en"; // Imagine this comes from device settings
System.out.println("English Greeting: " + getString(currentLocale, "greeting"));
System.out.println("English Welcome: " + getString(currentLocale, "welcome_message"));
currentLocale = "es"; // Change locale
System.out.println("Spanish Greeting: " + getString(currentLocale, "greeting"));
System.out.println("Spanish Welcome: " + getString(currentLocale, "welcome_message"));
}
}Adapting Dates, Numbers & Currencies
Beyond text, different cultures format dates, times, numbers, and currencies uniquely:
- Dates:
MM/DD/YYYY(US) vs.DD/MM/YYYY(EU). - Numbers: Decimal separators (
.vs.,) and thousands separators vary. - Currencies: Symbol placement (
$100vs.100€) and decimal precision differ.
Most mobile platforms provide APIs to automatically format these values based on the user's device locale.
Layouts for All Languages
Some languages, like Arabic and Hebrew, are written and read from right-to-left (RTL). Your app's UI needs to adapt to this.
- Flexible Layouts: Use flexible layouts that can automatically mirror for RTL languages.
- Icons & Images: Ensure icons and images that imply direction (e.g., an arrow pointing forward) are also mirrored.
Designing with flexibility from the start avoids costly rework later.
Accessibility & I18n Check
Which of the following are important considerations when developing for accessibility and internationalization?
Your App, For Everyone
You've learned how making your app accessible (A11y) and ready for internationalization (I18n) expands your reach and improves the user experience for everyone.
- Use accessibility labels for screen readers.
- Ensure good color contrast and dynamic text sizing.
- Provide large enough touch targets.
- Externalize all strings for localization.
- Format dates, numbers, and currencies based on locale.
- Design flexible layouts for RTL languages.
By integrating these principles from the start, you build a truly inclusive mobile product.
よくある質問
「アクセシビリティと国際化」レッスンは無料ですか？
はい。「アクセシビリティと国際化」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Indie Hacker Mobile Appsコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Indie Hacker Mobile Appsコースには全4レッスンが含まれています。
「アクセシビリティと国際化」で何を学びますか？
アクセシビリティ機能を実装し、複数の言語や地域に対応できるよう準備することで、誰もが使えるアプリにします ブラウザで直接実行するハンズオンコードでIndie Hacker Mobile Appsを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。
Indie Hacker Mobile Appsを始めるのに経験は必要ですか？
事前経験は必要ありません。CoddyKitのIndie Hacker Mobile Appsは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン2/4です。
「アクセシビリティと国際化」レッスンにはどのくらい時間がかかりますか？
ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。
このIndie Hacker Mobile Appsレッスンでコードを書いて実行できますか？
はい。すべてのIndie Hacker Mobile Appsレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。