1. Accessibility - a game changer
Srinivasu Charavarthula

2. About me
● Lead Accessibility, Informatica
● Founder, ServeOM Inclusion
● Advisor, Prakat Solutions
● Member, IAAP
● Member, Accessibility Guidelines Working
Group, W3C
● Formerly at: BarrierBreak, Yahoo!, PayPal,
HCL, Google (Contract), Deque
● Lives with wife, daughter and son

3. What is Accessibility?
● Usable
● Standard
● Diverse
● Robust
● Equal functionality
● Semantic
● Easy to use

4. What’s new in Accessibility?
● WCAG 2.1 is out
● Section 508 Refresh in the US
● ACAA in the US
● RPD Act in the India
● Europian Accessibility Act

5. Why companies care about accessibility?
● Social responsibility
● Legal obligation
● Right thing to do
● Business benefits

6. Some companies that care about
accessibility and why?
● Microsoft
● IBM
● Google
● Apple
● Facebook
● Amazon
● Uber
● PayPal

7. Why Accessibility? - Business case

8. Stand-out from the crowd
● Competition is high
● Include accessibility as core part of offering
● Grab the extra market

9. Social factors
● Get recognized
● Get respected

10. Technical factors
● Interoperability
● Quality
● Reduces time for development & maintenance
● Reduces server load time
● Enabling different configurations
● Ready for advanced web technologies

11. Financial factors
● Increases use of website
● Search engine optimization
● Decreases cost for developing for accessibility

12. Legal and Policy factors
● Standards
● Legal
● Directives
● Communications
● Orders
● Etc.,

13. Who would benefit?

14. People
● People with disabilities
● Elderly
● Users with low band-width connections
● Mobile users

15. A few things to consider

16. Checklist to begin with...
● Alternatives for non-text content such as images, controls, etc.,
● Captions for audio-only content and audio description for video-only content
● Minimum color contrast ratio of 4.5:1
● All input fields have association with their labels
● All elements are operable using keyboard
● No keyboard trap
● Meaningful tab order
● Consistent navigation
● Consistent identification
● Accessible error handling
● Parsing
● Name, role and value

17. Getting started
● Follow Web Content Accessibility Guidelines (WCAG) 2.1
● Test for accessibility using automated tools such as aXe by Deque
● Accessibility manual testing
● Include real users in testing
● Leverage accessible component libraries such as by W3C

18. Thank you
@CSrinivasu | @ServeOMAccess
https://www.serveominclusion.com