세계보건기구(WHO)와 세계은행의 2011년 보고서에 따르면 전 세계 인구의 약 15%(6명 중 1명)는 일생 동안 중대하거나 일시적인 장애를 경험합니다. 따라서 설계에서의 접근성은 포용적이고 유용하며 고품질의 앱을 만들기 위한 기본적인 요소입니다. 접근성은 사용자에게 최상의 결과를 가져다주고 큰 비용이 드는 재작업을 방지할 수 있습니다. Android에는 기본적으로 접근성 옵션을 지원하는 앱을 빌드하는 데 도움이 되는 다양한 기능이 포함되어 있습니다.
눈길을 사로잡는 디자인
색상 대비와 텍스트 크기를 확인하여 앱 콘텐츠를 가능한 한 쉽게 읽을 수 있도록 하고, 구성요소가 시각적으로 이해하기 쉽고 서로 쉽게 구분할 수 있는지 확인합니다.
다음 가이드라인에 따라 시각 접근성을 고려하여 디자인하세요.
사용자가 글꼴 크기를 조정할 수 있도록 하려면 확장 가능한 픽셀(sp)로 글꼴 크기를 지정합니다.
본문 크기를 12sp보다 작게 만들지 마세요. 이 가이드라인은 Material 서체 스케일 기본값에 부합합니다.
그림 3: 왼쪽 UI는 사용자가 스와이프로만 삭제할 수 있도록 하고 오른쪽 UI는 휴지통 아이콘 버튼 형태의 추가 어포던스도 제공합니다.
이 페이지에 나와 있는 콘텐츠와 코드 샘플에는 콘텐츠 라이선스에서 설명하는 라이선스가 적용됩니다. 자바 및 OpenJDK는 Oracle 및 Oracle 계열사의 상표 또는 등록 상표입니다.
최종 업데이트: 2025-07-27(UTC)
[null,null,["최종 업데이트: 2025-07-27(UTC)"],[],[],null,["# Accessibility\n\nAccording to a [2011 report by the World Health Organization (WHO) and the\nWorld Bank](https://www.who.int/teams/noncommunicable-diseases/sensory-functions-disability-and-rehabilitation/world-report-on-disability), approximately 15% of the global population--that is,\nabout one in six people--experience a significant or temporary disability in\ntheir lifetime. Accessibility in design, then, is *fundamental* to creating an\ninclusive, usable, and high-quality app--it leads to the best results for users\nand can prevent costly rework. Android ships with a variety of features to help\nyou build your app to support accessibility options by default. \n\nDesign for vision\n-----------------\n\nEnsure your app's content is as legible as possible by checking color contrast\nand text sizing, and that components are visually comprehensible and easy to\ndiscern from each other.\n\nFollow these guidelines to design for vision accessibility.\n\n- To allow users to adjust the font size, specify font size in [scalable pixels\n (sp)](/training/multiscreen/screendensities#TaskUseDP)\n- Don't make the body size any smaller than 12 sp. This guideline aligns with the Material typescale as a default.\n- Ensure the contrast between the background and text is at least 4.5:1. [Learn\n how to check color contrast](https://codelabs.developers.google.com/color-contrast-accessibility#0).\n- Use a 3:1 ratio between surfaces and non-text elements. For example, the ratio of a background to an icon would be 3:1.\n- Use more than one visual affordance for actions like links.\n\nUse Material's [Accessible color system](https://m3.material.io/styles/color/the-color-system/accessibility). This color system is\nbased on tonal palettes, and is central to making color schemes accessible by\ndefault.\n**Figure 1:**Example of text failing color contrast\n\nDesign for sound\n----------------\n\n[TalkBack](https://support.google.com/accessibility/android/answer/6283677) is a Google screen reader included on Android devices\nthat gives users eyes-free control. You can manually test this by [exploring\nyour app with TalkBack](/guide/topics/ui/accessibility/testing#explore_your_app_with_talkback) or with the [A11y scanner](https://play.google.com/store/apps/details?id=com.google.android.apps.accessibility.auditor).\n\nFollow these guidelines to ensure your app is prepared for screen readers:\n\n- [Describe UI elements](/guide/topics/ui/accessibility/apps#describe-ui-element) in your code. Compose uses [Semantics\n properties](/jetpack/compose/semantics#properties) to inform accessibility services about the information shown in UI elements.\n- To satisfy Android framework requirements, provide additional textual description of icons and images.\n- Set decorative item descriptions to null.\n- To allow skipping between blocks of actions and content, consider UI granularity and group UI elements..\n\nCheck out Material's [Design to Implementation Walk](https://m3.material.io/foundations/accessible-design/design-to-implementation), which\nwalks you through accessibility considerations and notation using Web Content\nAccessibility Guidelines (WCAG).\n**Figure 2:**UI elements labeled for accessibility: heading, hiding decorative image, and button label\n\nDesign for audio\n----------------\n\nAndroid provides features to enable users to interact with their devices through\na variety of voice commands and queries.\n\nThe [Voice Access](https://support.google.com/accessibility/android/answer/6151848) app for Android lets you control your device\nwith spoken commands. Use your voice to open apps, navigate, and edit text\nhands-free.\n\nDesign for motor skill\n----------------------\n\n[Switch Access](https://support.google.com/accessibility/android/answer/6122836) lets users interact with your Android device\nusing one or more devices, which can be helpful for users with limited dexterity\nwho have trouble interacting directly with a touch screen.\n\nManually test by [exploring switch access](/guide/topics/ui/accessibility/testing#explore_your_app_using_switch_access).\n\n- Don't rely on gestures to complete all actions; [create accessibility\n actions](/guide/topics/ui/accessibility/principles#accessibility-actions) to support all user flows in your app.\n- Ensure all touch targets are at least 48 dp, even if this extends past the UI element visual.\n- Consider [haptic feedback](/develop/ui/views/haptics/haptics-principles) to help inform the user with additional, real-time sensory input.\n\n\u003cbr /\u003e\n\n**Figure 3:**The UI on the left lets the user delete only by swiping, while the UI on the right also provides an additional affordance in the form of a trash icon button.\n\n\u003cbr /\u003e"]]
