Building Accessible Apps and Barclays Banking App March 2015 final

Editor's Notes

• #3: Mark to give overview
• #4: Mark introduces each person and asks them to say what their role is Need picture of Klara and poss updated one of Paul
• #5: Mark We work with some of the biggest names in global business, delivering world class services. They use us because they are clear about the business case
• #6: Robin – explaining how accessibility is now a mobile issue – review in relation to differences and similarities to desktop
• #7: Paul explains recent history ad how accessibility has been adopted as a core business value Plus any related activity eg digital eagles Banking channels changing and link to branch Paul explains how mobile banking services fit into the overall business of the bank Eg consumer-facing, part of evolution of customer expectations, multiple countries? With one or two details to help paint a picture eg numbers of users, etc + chief concerns with this sort of project eg security, marketing, etc
• #8: Klara explains how mobile banking services fit into the overall business of the bank Eg consumer-facing, part of evolution of customer expectations, multiple countries? With one or two details to help paint a picture eg numbers of users, etc + chief concerns with this sort of project eg security, marketing, etc
• #9: Mark to introduce Klara Joe Klara to include: - Talk about what I do – how important customers are to me and to the success of my work (if you don’t know the customer and shape a proposition to their needs, the product or feature won’t be successful) - Talk about how I got involved (team had been working on accessibility but needed business support to elevate topic - Talk about how inclusive design complements my job (always focused on customer but adds dimension which helps us deliver even better products), all customers come first and benefit of designing inclusive is that it doesn’t just benefit a customer with impairment, it is beneficial to all customers - Talk about satisfaction of supporting this activity when meeting with customers who truly benefit from accessibility enhancements at the usability testing sessions with AbilityNet
• #11: Mark to introduce Klara Joe Klara to include: - Talk about what I do – how important customers are to me and to the success of my work (if you don’t know the customer and shape a proposition to their needs, the product or feature won’t be successful) - Talk about how I got involved (team had been working on accessibility but needed business support to elevate topic - Talk about how inclusive design complements my job (always focused on customer but adds dimension which helps us deliver even better products), all customers come first and benefit of designing inclusive is that it doesn’t just benefit a customer with impairment, it is beneficial to all customers - Talk about satisfaction of supporting this activity when meeting with customers who truly benefit from accessibility enhancements at the usability testing sessions with AbilityNet
• #12: Joe talks about types of testing
• #13: Joe Here is a page from the registration process. Note that there is a visual label in place on the left hand ‘before’ screenshot. Once the user has input their data, the label is overwritten. When reading back through the form as a screenreader user, the input fields were announced using their contents. This means that a field on the left announced as “Text input: Sort code” was announced as “Text input: 0-16-56” after the user had entered their data. Providing hidden labels meant that these fields were announced correctly for screenreader users regardless of their contents, so in the right hand screenshot the sort code field would now be announced as “Text input: sort code: 20-16-56”. Note that labels within the app have separate text labels, and the longer term plan is to extend this to the registration process for consistency.
• #14: Joe has loads of screen shots
• #15: Joe   The menu behaviour was critical for screenreader users. Whilst sighted users can see the menu slide out from the left of the screen and easily interact with it, it is important for screenreader users to use this component. Button label changed from Open menu to Close menu depending on the menu state. Managing the focus within the menu e.g. setting the focus in their once it was opened Progressing the focus back to the close button after the end of the menu
• #16: Klara to describe her own learning Inclusive design helps every customer Regular reviews throughout project rather than bolted on Bringing the standards to life within the team E.g. need to embed this in the details of internal policies egg UI guidelines + Personas now include disabilities Senior commitment to this approach with all projects iOS version accredited but still difficult with Android
• #17: Paul Mark to ask Paul about benefits to Barclays and lessons being learned in Barclays about adopting accessibility
• #18: Mark to manage this and ask specific people to respond
• #19: Mark will sum up and say thank you