White paper on the availability of PhoneGap
The Global Inclusive ICT Initiative (G3ict), in collaboration with Adobe Systems Incorporated, has published a white paper on the development of accessible interfaces for mobile applications using the PhoneGap framework, also known as Apache Callback or Apache Cordova. This ten-page document describes the current state of mobile application accessibility, the inherent advantages of PhoneGap's approach to creating accessible cross-platform applications of this category, as well as Adobe’s motives for creating a special plug-in that reduces the gap between web-access technologies and native accessibility API of mobile platforms. .
Recall that the PhoneGap Mobile Accessibility Plugin , introduced about a year ago, transmits information to applications such as the status of font size and other settings. As a result, PhoneGap applications get closer interaction with accessibility functionality in one or another operating system, comparable to native applications.
Mobile devices need built-in accessibility support, similar to that found on personal computers. This document from G3ict highlights the features of Adobe PhoneGap, a free open source framework that allows developers to create mobile applications using standard web-based APIs for cross-platform development. The PhoneGap Mobile Accessibility Plugin works by providing developers with access to the built-in accessibility features of each mobile device, which allows you to create accessible applications that can be compiled to run on any operating system. That is, PhoneGap allows you to universalize not only the graphical component of the interface, but also its level of accessibility of functionality, but the published white paper is designed to highlight the various nuances of using these technologies in the development process.
The white paper on the availability of PhoneGap can be downloaded free of charge in electronic form or ordered on printed media on the G3ict website .
')
Frankly, the interfaces rendered in WebView are still far from ideal accessibility when it comes to users with critical visual impairments who work with screen readers, especially on Android OS. However, in Android 5, the availability of WebView has improved quite dramatically, so the excuses about the dampness of accessibility technologies, which previously could justify the inaction of the developers of web-based applications, are no longer relevant. So it’s time to join all the available accessibility tools, because the responsibility for the accessibility of web interfaces already smoothly creeps onto the application developer, since the developer of the Android platform has completely realized the necessary minimum. Well, on iOS this minimum was from the very beginning.
Recall that the PhoneGap Mobile Accessibility Plugin , introduced about a year ago, transmits information to applications such as the status of font size and other settings. As a result, PhoneGap applications get closer interaction with accessibility functionality in one or another operating system, comparable to native applications.
Mobile devices need built-in accessibility support, similar to that found on personal computers. This document from G3ict highlights the features of Adobe PhoneGap, a free open source framework that allows developers to create mobile applications using standard web-based APIs for cross-platform development. The PhoneGap Mobile Accessibility Plugin works by providing developers with access to the built-in accessibility features of each mobile device, which allows you to create accessible applications that can be compiled to run on any operating system. That is, PhoneGap allows you to universalize not only the graphical component of the interface, but also its level of accessibility of functionality, but the published white paper is designed to highlight the various nuances of using these technologies in the development process.
The white paper on the availability of PhoneGap can be downloaded free of charge in electronic form or ordered on printed media on the G3ict website .
')
Frankly, the interfaces rendered in WebView are still far from ideal accessibility when it comes to users with critical visual impairments who work with screen readers, especially on Android OS. However, in Android 5, the availability of WebView has improved quite dramatically, so the excuses about the dampness of accessibility technologies, which previously could justify the inaction of the developers of web-based applications, are no longer relevant. So it’s time to join all the available accessibility tools, because the responsibility for the accessibility of web interfaces already smoothly creeps onto the application developer, since the developer of the Android platform has completely realized the necessary minimum. Well, on iOS this minimum was from the very beginning.
Source: https://habr.com/ru/post/254407/
All Articles