Understanding, Writing, and Developing Accessibility Requirements

Transcription

1 Understanding, Writing, and Developing Accessibility Requirements Contact: J. Kim, J.D. State of MN Bureau of Criminal Apprehension (BCA) LinkedIn: J Kim president@iibamsp.org

2 Accessibility Requirements Track: The Future is Now & Geek School About: Business Analysis and Design Strategies Audience: Coach, Mentor, Manager, Influencer, Business Analyst Goal: Tangible techniques and strategies 2

3 About me Career Path: Government /Non-profit United States Senate & United States House of Representatives Director, Peoples Network of Minnesota J.D., William Mitchell College of Law Attorney: Government, Product Liability, Trusts & Estates State of Minnesota Senior Business Analyst Bureau of Criminal Apprehension (BCA) President, IIBA Minneapolis St. Paul 2018 IIBA Chapter of the Year 3

4 Presentation Overview Using the framework and techniques of the Business Analysis Book of Knowledge (BABOK), we will support accessibility requirements in the workplace 4

5 Presentation Overview Presentation is: Fundamentals on how to support accessibility requirements in the workplace Presentation is not: Legal guidance or deep dive into the law 5

6 Key Proposition Understanding, Writing, and Developing Accessibility Requirements is a critical skill to have as a BA, QA, Developer, Manager, Leader 6

7 Learning points Goals: 1) Understand the common ground of what accessibility means 2) Write and reference key terminology in the world of accessibility 3) Develop how to navigate, guide and lead others in the realm of accessibility requirements 7

8 The basics Accessibility Key Knowledge What is the ADA? Why is the ADA important? What will happen if we violate the ADA? 8

9 The basics Accessibility Key Knowledge What is WCAG? What is JAWS? What is Section 508? 9

10 Learning point #1 Goal #1: 1) Understand common ground of what accessibility means 10

11 Common ground What are accessibility requirements What is web accessibility? Web accessibility refers to the inclusive practice of removing barriers that prevent interaction with, or access to websites, by people with disabilities. When sites are correctly designed, developed and edited, all users have equal access to information and functionality. Source: Wikipedia 11

12 Common ground What are accessibility requirements Accessibility is..*pour* System Functional User interface (UI) Development Other? 12

13 Learning point #2 Goal #2 2) Write and reference key terminology in the world of accessibility 13

14 Common ground What are accessibility requirements The Web Content Accessibility Guidelines (WCAG) = part of a series of web accessibility guidelines.published by the Web Accessibility Initiative (WAI).of the World Wide Web Consortium (W3C). W3C is one of the main international standards organization for the Internet. Source: Wikipedia 14

15 Writing and referencing accessibility ADA is a civil rights law that prohibits discrimination based on disability. It affords similar protections against discrimination to Americans with disabilities as the Civil Rights Act of 1964 the ADA also requires covered employers to provide reasonable accommodations to employees with disabilities, and imposes accessibility requirements on public accommodations. Source: Wikipedia 15

16 Writing and referencing accessibility WCAG WCAG embraces the thought that a business is build on the principle that all persons, of any disability, should have the same opportunity to have and share information via the internet that anybody else does. Levels of conformance: A, AA, AAA wcagcompliance.com/about-us/ 16

17 Writing and referencing accessibility JAWS "Job Access With Speech is a computer screen reader program for Microsoft Windows that allows blind and visually impaired users to read the screen either with a text-to-speech output or by a refreshable Braille display. Source: Wikipedia 17

18 Writing and referencing accessibility Section 508 (1998) Amendment to the Rehabilitation Act of 1973 Federal legislation that was enacted to eliminate barriers in information technology, to make available new opportunities for people with disabilities, and to encourage development of technologies that will help achieve these goals. Section

19 Learning point #3 Goal #3: 3) Develop how to navigate, guide and lead others in the realm of accessibility requirements 19

20 Navigating accessibility requirements Checklist Top 3 Checklist Get the facts! 1) Is there an accessibility office? 2) Is there a designated legal counsel (office or person?) 3) What is your leadership s position on accessibility requirements? Just make it accessible?! 20

21 Guiding accessibility requirements Checklist Top 3 Checklist Show the way! 1) Who is our Product Owner and Sponsor? 2) Is there a PM? 3) What education has been done on accessibility requirements of your team? (BA, QA, Business Owners, Sponsors, Developers) 21

22 Leading others in accessibility requirements Top 3 Checklist Commit to action! Defining the requirements (ask the questions) Testing the requirements Documentation, documentation, documentation 22

23 Leading others in accessibility requirements Example Some examples: Leading the team Who is your user audience? Keyboard only user Screen reader user User with low vision User with color blindness Hearing impaired user [Visual, Motor/mobility, Auditory, Seizures, Cognitive and Intellectual] Note, the State of Minnesota uses WCAG 2.0 standards along with Section 508 for its standards 23

24 Leading others in accessibility requirements Practical tips Poor accessibility requirements: Make UI accessible for people with disabilities Make it work as it does today Good accessibility requirements: A keyboard-only user should be able to reach the main navigation links with a keyboard in order to determine the different areas of the site. A color blind user must have access to information conveyed in color in order to understand all content. (customize to your agency) 24

25 Leading others in accessibility requirements Resources BABOK (IIBA Website) writing requirements 2010 ADA Standards for Accessible Design: WCAG WCAG Note, the State of Minnesota uses WCAG 2.0 standards along with Section 508 for its standards 25

26 Leading others in accessibility requirements Real World Examples 26

27 Leading others in accessibility requirements Rules to live by: It s not extra work! Requirements up front makes it a part of the process Stay knowledgeable Don t over process Ask the questions you do not need to know it all It is a team effort 27

28 Re-cap We learned the importance of: 1) Understanding the common ground of what accessibility means 2) Writing and referencing key terminology in the world of accessibility 3) Developing how to navigate, guide and lead others in the realm of accessibility requirements 28

29 Your personal commitment How will you embrace accessibility requirements in your organization? 29

30 Questions Other questions? 30

31 Understanding, Writing, and Developing Accessibility Requirements Contact: J. Kim, J.D. State of MN Bureau of Criminal Apprehension (BCA) LinkedIn: J Kim president@iibamsp.org