In this week‘s lecture we were tasked to present our module progress to the rest of the group for critique. Throughout the session I was intrigued to hear the prevalence of accessibility considerations, as I honestly hadn’t expected them. I had expected accessibility to be a common afterthought for many of my peers, as they instead focused on other design considerations. Design for vision impairments was most common, mainly by way of colour contrast and wayfinding (such as the inclusion of a tab bar). When appropriate, I shared my strategy for focusing on one area of accessibility and trying to excel at that, rather than lightly touch as many aspects of accessibility as possible.
When the time came for my presentation, I presented a Keynote of approximately 35 slides. Although this was a considerable amount for a 10 minute presentation, many of the slides were shown quite quickly as they lacked text and illustrated enlarged versions of diagrams and wireframes. I’ve presented the video again to create a Youtube version, which you can watch here:
Overall, I was pleased to receive good, constructive feedback for my presentation. I had to clarify a few areas for some of my peers as I hadn’t explained certain aspects particularly clearly. Namely, peers who had no experience of the Multimedia Centre were unclear about the service it provided and the challenges that the Multimedia Centre AR app would address – this is certainly an aspect I must improvement upon for presenting a proof of concept; explaining the context and user need for this mobile application could be a determining factor of my proof of concept’s success. I could certainly profit from presenting to a group on a more frequent basis and reestablishing my confidence for pitching ideas to others, as this would be a valuable skill to take forward beyond the MA programme. Feedback from my lecturer commended the research and progress that I have made so far, whilst one of my peers praised my exploration of Adobe After Effects and use of Apple’s Xcode/Object Capture API. I’m glad these areas have been recognised because I’ve worked particular hard on them over the past seven weeks, and have certainly undertaken a large learning curve.