Laveena is an experienced Testing Consultant with a comprehensive understanding of tools available for software testing and analysis. She aims to provide valuable insights that have high technical aptitude and hopes to inspire others in the world through her work. Laveena holds a degree in Business Computing from Queen Mary University of London and regularly speaks at events on data science models and other topics.
How often have you heard that ‘Yes this is important, but we don’t have the capacity right now’ or ‘Sure let’s put it in the backlog’? This is something we should not brush off or take lightly. Accessibility testing is vital especially when your product is a user-facing application. We need to be socially aware as a team and build quality towards our product by making it more accessible. At least 1 in 5 people in the UK have a long-term illness, impairment, or disability. Many more have a temporary disability. A recent study found that 4 in 10 local council homepages failed basic tests for accessibility. This is quite vital and the sooner we as testers can advocate this to our teams, we make our product more accessible, reduce the risk of bad product reviews, and reputation and also be more socially aware. Let’s shift left and make accessibility testing built in our teams.
- Introduction to A11Y
- The importance of having accessibility as part of your non-functional testing
- Discussions with the audience as per the audience’s experience
- The tools that exist and how we can during the session explore some of the tools via keyboards, screen readers, and plugins for vision deficiencies, motor or learning difficulties only, and what we learn from them
- Help the audience make a checklist
- Manual vs Automation, we will build some automated checks
- Legislation to do with Accessibility
PC or MAC