Добавил:
Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
lawrence_shaun_introducing_net_maui_build_and_deploy_crosspl.pdf
Скачиваний:
46
Добавлен:
26.06.2023
Размер:
5.15 Mб
Скачать

Chapter 7 Accessibility

Apple’s offering can be found at https://developer.apple.com/ library/archive/technotes/TestingAccessibilityOfiOSApps/ TestAccessibilityiniOSSimulatorwithAccessibilityInspector/ TestAccessibilityiniOSSimulatorwithAccessibilityInspector.html.

macOS

Apple provides a little extra functionality when testing on macOS. It does provide the Accessibility Inspector as per iOS and well as the Accessibility Verifier. This tool allows you to run tests against your application to verify items like the accessibility description have been defined on all required elements. Further information on these features can be found at https://developer.apple.com/library/archive/ documentation/Accessibility/Conceptual/AccessibilityMacOSX/ OSXAXTestingApps.html.

Windows

Microsoft offers the biggest amount of options when it comes to testing the accessibility of your applications. The Windows Software Development Kit (SDK) provides several tools such as the ability to inspect an application and view all related properties as plus automation tests that verify the state of accessibility. All details of the tools can be found at https://docs. microsoft.com/windows/apps/design/accessibility/accessibilitytesting.

Accessibility Checklist

The following checklist is provided by Microsoft on their documentation site at https://docs.microsoft.com/dotnet/maui/fundamentals/ accessibility#accessibility-checklist. I haven’t added to it or

216

Chapter 7 Accessibility

reworded because I believe it provides an excellent breakdown of the possible ways to provide accessible support.

Follow these tips to ensure that your .NET MAUI apps are accessible to the widest audience possible:

•\

Ensure your app is perceivable, operable,

 

understandable, and robust for all by following the Web

 

Content Accessibility Guidelines (WCAG). WCAG is

 

the global accessibility standard and legal benchmark

 

for web and mobile. For more information, see Web

 

Content Accessibility Guidelines (WCAG) Overview.

•\

Make sure the user interface is self-describing. Test

 

that all the elements of your user interface are screen

 

reader accessible. Add descriptive text and hints when

 

necessary.

•\

Ensure that images and icons have alternate text

 

descriptions.

•\

Support large fonts and high contrast. Avoid

 

hardcoding control dimensions, and instead prefer

 

layouts that resize to accommodate larger font sizes.

 

Test color schemes in high-contrast mode to ensure

 

they are readable.

•\

Design the visual tree with navigation in mind. Use

 

appropriate layout controls so that navigating between

 

controls using alternate input methods follows the

 

same logical flow as using touch. In addition, exclude

 

unnecessary elements from screen readers (for

 

example, decorative images or labels for fields that are

 

already accessible).

217