![]() HMRC have written a blog post about how they use and manage an app component library. If your app is complex, or you have many teams working on it at once, you may want to develop a component library with approved, tested items that teams can use to build new functionality and screens. This normally means you get all the in-built accessibility features of the mobile operating system - but you should double check, for example, how a component reacts to screen readers and keyboard/switch inputs ( switch access is assistive technology that is often used on mobiles). Where possible, use native Android or iOS components to build your app to be accessible. Use native features when building mobile apps We’ve been talking to teams in the public sector that develop mobile apps to find out what makes a good accessible app. There are some WCAG success criteria that do not make sense for mobile apps, and extra guidelines for mobile features such as biometrics, which we explain more in our information about the requirements. The technical accessibility standard is the same for mobile apps as for websites ( EN 301 549 v2.1.2), which for the most part translates to the Web Content Accessibility Guidelines (WCAG) 2.1 AA as the minimum level of accessibility. ![]() The deadline for public sector websites to be accessible and to have published an accessibility statement was 23 September 2020.įrom 23 June 2021, public sector mobile applications, or apps, need to be accessible and publish an accessibility statement. ![]() The aim of the regulations is to make public sector websites and mobile apps accessible to all users. Accessibility regulations were made UK law on 23 September 2018.
0 Comments
Leave a Reply. |