Inclusive Design - Manual & Automated Accessibility Implementation with Agility

When websites are designed, developed all users have equal access to information& functionality. QA& Dev needs to make sure web & mobile should be accessible to all users including differently abled or having special needs, abide by legislation (WCAG, section 508, ADA) and avoid lawsuits. QA needs to make the strategy using Manual review, Accessibility toolbars, Online evaluation tools, Assistive technology and Realistic end-user testing (visually challenged) and bring automation using Protractor, Selenium, HTML code sniffer/AXE to make developers and stakeholders aware on product accessibility compliance.

I would like to mainly concentrate on 4 principles (POUR - perceivable, operable, understandable, Robust) and 12 guidelines of Text alternatives by providing alt attributes, Time based media by proving captions, Adaptable by all assistive technologies like screen readers/magnifiers, Distinguishable, Keyboard accessible, Enough Time for seeing especially for people having dyslexia, Navigate to all pages by providing appropriate headers sizes and accessible links, Readable by providing ARIA labels and roles, predictable and input assistance by providing error messages with efficient colour contrast, Compatible with all browser versions and make responsive web design suits tablets, mobile and Desktop

QA should gain expertise by going through 30- day accessibility testing and adopt across the organization by having key stakeholders, checklist and benchmark levels of WCAG (A, AA, AAA). Establish UI standards, color contrast across teams. Inspire team by making accessibility is right to use

This paper describes manual testing by reviewing HTML code and automated Accessibility techniques using evaluation tools like Voice over, AXE, HTML code sniffer, WAVE, A checker, W3c Mobile ok analyser, color contrast analyser useful for developers and QA within their automated scripts

Demonstration of Manual and Automated Accessibility tools/libraries/ utility checks and reports generated with accessibility violations of all pages in a website

 
1 favorite thumb_down thumb_up 8 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Demonstration

  1. [0-3] What, why Accessibility Testing, Web Accessibility
  2. [4-5]Technical Agility with Accessibility
  3. Adoption of Accessibility in Sprints & Iterations
  4. [6-8]Differently Abled users & Scenarios
  5. [9-10]Accessibility Lifecycle Testing Strategy
  6. [11-12]WCAG Standards & Guidelines
  7. [13]Accessibility Testing tools & Techstack
  8. [14]Case Study: How I reduced Time from 2 months Manual work to 5 mins and improved quality and ROI
  9. [15]ARIA attributes
  10. [16- 35]Live Demonstration: Accessibility Toolbars/ Plugins, Accessibility Tab in Browser, Online static Evaluation Tools, Assistive Technologies does screen readers, Keyboard strokes & Automated Accessibility Testing with Protractor
  11. [36]How to kickstart accessibility across the organization
  12. [37]30- days Accessibility Challenge
  13. [38] References
  14. [39-45] Q & A

Learning Outcome

Value proportion :

  • How UX can design specs with accessibility having good colour contrast, fonts, keyboard shortcuts, colour with icons & Hovers
  • How a developer can write/implement accessible lines of code
  • How QA can detect accessibility violations
  • Reduce Efforts and Time invested in accessibility
  • Accessibility Evaluation
  • product owner can use these metrics to showcase for prospective customers & their experience

Agenda of this demonstration is to how to prevent accessibility violations and if not detect & fix iterative iterations to enhance the customer experience in turn raises customer base of differently abled too

TakeAways:

  • Quicker feedback and high ROI for standard accessibility compliances by automated tests
  • How to kickstart, adopt accessibility in sprints & Iterations across the organization
  • Accessibility Toolbars/ Plugins, Accessibility Tab in Browser, Online static Evaluation Tools, Assistive Technologies does screen readers, Keyboard strokes & Automated Accessibility Testing with Protractor
  • How we can implement automated accessibility in middle of functional workflows
  • Accessibility Testing awareness
  • ARIA attributes
  • Different Accessibility standards
  • Automated Accessibility libraries
  • Finding accessibility violations without being an accessibility expert
  • Accessibility Test Summary Reporting

Target Audience

Developer, UXD, QA, Scrum Master, Product Owner, UX Analyst

Prerequisites for Attendees

HTML Basics

schedule Submitted 9 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Jeremy Kriegel
    By Jeremy Kriegel  ~  7 months ago
    reply Reply

    I think that accessibility is becoming more and more important to the design and development process. However, how does this talk address the track theme of innovation? How does improved accessibility lead to more innovative products?

  • Rakesh Kondreddy
    By Rakesh Kondreddy  ~  7 months ago
    reply Reply

    HI Jeremy Kriegel  / Priya Patra  / Archana Joshi

    Hope you like aspects of Inclusive design having Accessibility provides value proportions to UX, Dev, QA and Management 

    Could you please provide any update on acceptance

  • Jeremy Kriegel
    By Jeremy Kriegel  ~  8 months ago
    reply Reply

    This is a really important topic. Currently, your intro mentions QA the most, but I don't think that is going to be a common role at the Design Innovation day. Can you change it to focus on product owners, ux, and designers? I think that will resonate more with the audience.

    • Rakesh Kondreddy
      By Rakesh Kondreddy  ~  8 months ago
      reply Reply

      Hi Jeremy Kriegel

      Thank you for having a glance at my proposal 

      In my personal view, I have submitted the proposal to demonstrate this at design innovation day is different roles of the team can be benefited. We are actually taking reactive measures in many products with this demonstration i would like to make members aware of having an inclusive design in turn helps prevention of accessibility violations

      Maybe the title or some part of the description sounds like QA because of Testing keyword. If you go through different tools in the live demonstration, Technical Agility with Accessibility, Adoption of Accessibility in sprints and value proportion. With this demonstration, all members will be benefited PO, SM<, UX, Dev and QA 

      How above listed different members can be benefited? A: listed in Learning outcome takeaways & Value proportion section.

      Please feel free to share your views will try to change/enhance presentation based on the same 

      Your feedback is valuable to me 

       

       
  • Priya Patra
    By Priya Patra  ~  8 months ago
    reply Reply

    Hi Rakesh,

     Thank you for your submission.. I like the idea of inclusive design and testing which are missed out many a times. 

    On reduction of manual work from 2 months on 5 mins, is it through automation only ? It was not evident from the video and the slide provided in the proposal. 

    May be we can highlight the outcome of the project how accessibility design and testing might have increased the user base, customer experience of the product.

    Regards,

    Priya

    • Rakesh Kondreddy
      By Rakesh Kondreddy  ~  8 months ago
      reply Reply

      Hi Priya Patra 

      Happy to hear your views on the submission 

      Yes reduction of manual efforts is done through the Automated engine which goes to each & every page with the help of UI automation tools in product and shows reporting page level violations as per WCAG ( yes I have created automation project and able to demonstrate the same on live) 

      The outcome I have placed as part of Learning Outcome  and this demonstration is explained in all manual & automated ways of detecting accessibility violations 

       

      UXD & Dev can use these to design & implement accessible prototypes and prevent accessibility violations

      QA can use to coach developers & detect accessibility violations 

       product owner can use these metrics to showcase for prospective customers & their experience

       

      Agenda of this demonstration is to how to prevent accessibility violations and if not detect & fix iterative iterations to enhance customer experience inturn raises customer base of differently abled too

       
  • Archana Joshi
    By Archana Joshi  ~  8 months ago
    reply Reply

    Thank you Rakesh for the submission.

    Will you be able to update the proposal with info on how much time do you plan to spend on the outline topics that you have provided. At a first glance it seems there are 12-13 areas that you want to speak about and I want to understand how do you want to balance those topics and the demo that your submission refers to. 

    Also in the slides, I did not see the case study related content. "2 months Manual work to 5 mins". Could you please provide additional info around it?

    • Rakesh Kondreddy
      By Rakesh Kondreddy  ~  8 months ago
      reply Reply

      Thank you Archana Joshi  for sharing your valuable feedback

      Please find the below points of the updated proposal

      1. Updated Timelines for the presentation outline / Live demonstrations
      2. All live demonstrations mentioned in the outline covered on time, intact I have demonstrated live and able to complete them on time followed time-boxed approach, please find the demonstration link ( https://drive.google.com/open?id=1bWDb7d3inVh2XZm_6h0pD7L6YsRzYW6N)
      3. Regarding case study it about how automated accessibility approach can reduce manual efforts, I have conducted this on a team who performed manual testing when I gave automated engine they validated on their product they even got mostly similar violations in 5 mins in which they spent 50 days in Manual Testing

      I hope this demonstration is useful to every individual who works Agile including scrum development team ( UX, dev, QA), Scrum master, PO. Value proportions are stated as part of Learning outcome

      Please feel free to comment, Your feedback is valuable to me