PRIORITIZING P PEOPLE Accessibilit ility and Dig igit ital l Co - - PowerPoint PPT Presentation

prioritizing p people accessibilit ility and dig igit
SMART_READER_LITE
LIVE PREVIEW

PRIORITIZING P PEOPLE Accessibilit ility and Dig igit ital l Co - - PowerPoint PPT Presentation

PRIORITIZING P PEOPLE Accessibilit ility and Dig igit ital l Co Colle llectio ions Nat athan an T Tal allman an, Han anning Chen, an and H Heat ather Alexan ander ABOUT UT US US Pro roduct Owner, r, Pro roduct Analyst, and


slide-1
SLIDE 1

PRIORITIZING P PEOPLE Accessibilit ility and Dig igit ital l Co Colle llectio ions

Nat athan an T Tal allman an, Han anning Chen, an and H Heat ather Alexan ander

slide-2
SLIDE 2

ABOUT UT US US

Pro roduct Owner, r, Pro roduct Analyst, and User r Inter erface D e Des esigner er

You may be familiar with the roles or have them in your organization. But you have users. You probably want users to use your collections. But your users may have impairments. Thinking about your collections through the lens of these roles may help you make your collections more accessible to impaired users.

2 Prioritizing People: Accessibility and Digital Collections 2019-04-30

slide-3
SLIDE 3

ACTIVITY

YOU HAVE B E BEEN EEN S SMOTE E AND ARE E IMPA PAIRED ED.

  • Random impairments will be assigned. Props are

provided if necessary.

  • Using a personal device or one of the provided

laptops (installed with NVDA and JAWS software), try using your organization’s digital collections. (Or any

  • nline digital collection.)
  • A list of suggested activities to perform is provided.
  • How long does it take you to perform these activities?

Was it easy? How did the experience make you feel, personally?

3 Prioritizing People: Accessibility and Digital Collections 2019-04-30

slide-4
SLIDE 4

Activ ivit ity

2019-04-30 Prioritizing People: Accessibility and Digital Collections 4

  • Collections
  • Penn State
  • https://dbbt.io/HSIn
  • Keystone Library Network
  • https://dbbt.io/HSqH
  • Oregon Digital
  • https://dbbt.io/HSqI
  • University of Maine
  • https://dbbt.io/HSqq
  • Barnard College
  • https://dbbt.io/HSqz
  • University of Florida
  • https://dbbt.io/HSqK
  • Library of Congress
  • https://dbbt.io/HSq9
  • Stanford Libraries
  • https://dbbt.io/HSqx
  • Use your own organization’s collections!
  • Actions
  • Browse complete listing of collections and

choose one to explore.

  • Find the top five creators and subject for

your chosen collection.

  • Do a basic search and try to page through

the search results. Select one result view the object.

  • When was the original created? What

format was the original? Go back to the homepage.

  • Do an advanced search and combine at

least three fields, one of them being a phrase search.

  • After exploring the results, try to print

(pretend) and download some objects.

slide-5
SLIDE 5

PRO RODUCT OW NERSH SHIP

  • Comes from the Scrum/Agile framework.
  • PO is the chief stakeholder, defines the vision, prioritizes

work, and liaises with other stakeholders.

  • Interfaces with the development team/vendor and other

stakeholders/rest of the organization.

  • PO is accountable for delivering maximum value.
  • If accessibility is important to your organization and users,

it’s the product owner’s job to deliver an accessible application.

5 Prioritizing People: Accessibility and Digital Collections 2019-04-30

slide-6
SLIDE 6

BET ETTER ER F FOR EV EVER ERYONE

It can be e a fight for res esources es, but A FO FOCUS S ON A ACCESSI SSIBILITY O OFT FTEN LEADSTO A B BET ETTER ER EX EXPER PERIEN ENCE FO FOR A ALL USE SERS. S.

Headings clarify the structure of a page. The accessibility requirement

  • n headings will help creating a logical and coherent website in general.

Accessibility requires texts to have enough contrast with background. This works better for other types of users as well. E nforcing ALT text on image & UI elements will help everyone better understand the contents and functions of a website.

6 Prioritizing People: Accessibility and Digital Collections 2019-04-30

For example:

slide-7
SLIDE 7

W EB A ACCESSIBILITY

OUR PH PHYSICAL S SPA PACES ES ARE A E ACCES ESSIBLE, E, OUR DIGITAL SPA PACES ES NEED EED TO BE E TOO

W AI / / W CA CAG

W3C Web Accessibility Initiative, including the Web Content Accessibility Guidelines 2.1 (June 2018)

Se Section 50 504, 4, 50 508

The Rehabilitation Act of 1973 prohibits programs receiving federal funding from discriminating against people with disabilities through inaccessible interfaces.

Univ iversal l Desi sign

Universal design considers all users, including those with disabilities, and reduces or eliminates the need for adaptive technologies.

Tit itle le I II, ADA DA

Title II of the Americans with Disabilities Act of 1990 prohibits discrimination against qualified individuals from public entities.

7 Prioritizing People: Accessibility and Digital Collections 2019-04-30

slide-8
SLIDE 8

CONTE TENTd Tdm 6 6.x

OCLC’S NEW H HOSTED V VERSION OF CONTENTdm ADVER ERTISED ED A ACCES ESSIBILITY IMPROVEM EMEN

  • ENTS. WE

E AS ASKED FOR A A TRIAL AL.

  • We had stability and maintenance issues with our

self-hosted instance. Crashed on the Dean’s husband.

  • Known issues with accessibility and mobile devices.
  • Had already started work on Samvera replacement,

but was 2+ years away.

8 Prioritizing People: Accessibility and Digital Collections 2019-04-30

slide-9
SLIDE 9

2019-04-30 Prioritizing People: Accessibility and Digital Collections 9

CONTENTdm dm R Respo pons nsive

ALWAYS D DO YOUR O OWN T TESTING.

  • Worked with Penn State EIT Accessibility Group to

test new CONTENTdm with some of our collection.

  • Results were disappointing based on OCLC

messaging and strongly worded emails sent.

  • OCLC listened and their response showed they
  • cared. Successive improvements were made, with

additional rounds of testing and report sharing.

slide-10
SLIDE 10

2019-04-30 Prioritizing People: Accessibility and Digital Collections 10

ACCESSIBILITY IS M MATURING

Educ ducation o n of e everyone ne on n the he pr produc duction n cha hain i n is

  • ngo

going. g.

SO ARE WE

W e are f for

  • rtunate t

to

  • wor
  • rk

with h pa partne ners on n accessibi bility issu ssues. Accessib ibilit ility is is still ill evolv lvin ing. W e lear arned a a lot an and star art t to lo look at accessib ibilit ility from a new ew a angle. e. Standa ndards ds are still be being ng establ blishe hed a d and nd revised. d. CONTE TENTd Tdm team am at at OCL CLC C is s taking the i issu ssue se seriousl sly and nd is c cont ntinuo nuous usly mak aking accessib ibilit ility improvem emen ents to to our ur pr produc duct.

slide-11
SLIDE 11

CULTURAL H HER ERITAGE E OB OBJ ECTS R REPOS OSITOR ORY

2019-04-30 Prioritizing People: Accessibility and Digital Collections 11

  • Samvera-based digital repository with Blacklight as the only

starting UI.

  • Accessibility a priority, required feature from day one. Every

incremental release undergoes some form of accessibility testing.

  • Full testing with EIT Accessibility Group as needed and

planned for major releases.

  • MVP includes minimal/no JavaScript or other fancy UI

features to maintain focus on core accessibility for graceful fallback.

  • Staff need an accessible interface too.
slide-12
SLIDE 12

BEST PRACTICES F FOR ADAPTING & & C CREATING ACCES ESSIBLE E DIGITAL C COLLEC ECTION I INTER ERFACES ES

2019-04-30 Prioritizing People: Accessibility and Digital Collections 12

WORKING WITH VENDORS

  • Test all claims
  • Don’t be reluctant to ask or give feedback to

the team who developed it

  • When customizing, be careful not to reverse

accessibility

  • Test customizations with SiteImprove – it can

be downloaded as a Chrome extension

  • Accessibility is always evolving, we are

constantly working to make improvements to

  • ur products

DEVELOPING YOUR OWN

  • Universal design
  • Progressive enhancement
  • Routine testing, both automated & manual

(WCAG) and human using adaptive tech

  • Valid, semantic HTML encoding
  • Unicode! (Accessibility for all languages!)
  • Know how to use ALT and ARIA attributes
  • Test content without CSS and JS enabled
  • Remember screen readers when adding

hidden content and for skipping non-primary content

slide-13
SLIDE 13

Acces essible e Conten ent

Your websi site is s only as s sm smart as s you allow it W he hen n upl uploadi ding ng c cont ntent nt

  • Use descriptive yet simple English for your content
  • Give relevant names to your titles, subjects, and

description; not Page 01, Page02, Page 03

  • Title will be the same as link and alt text

W hen c conf nfiguring W CT

  • Test intended colors in webaim.org/resources/contrastchecker/
  • Text size 'Medium' is the intended sizing for the text
  • When you customize be careful writing descriptions and be

mindful of headings (make sure your site doesn't have too many headings)

13 Prioritizing People: Accessibility and Digital Collections 2019-04-30

slide-14
SLIDE 14

QUEST STIONS? S?

Penn State University, Digital Preservation Librarian

Nathan Tallman, @ @mad adcow1029

OCLC, Product Analyst

Hanni ning Che hen, @ @oclc

OCLC, User Interface Designer

Heather Alexander, @ @halex exdee ee

Thank you to our colleagues Michael Tribone (UX/UI Designer) and Linda Klimczyk (Assistant Head, I-Tech) at Penn State University Libraries for their feedback.

slide-15
SLIDE 15

5/3/2019 1

PRIORITIZING PEOPLE Accessibility and Digital Collections Nathan Tallman, Hanning Chen, and Heather Alexander ABOUT US Product Owner, Product Analyst, and User Interface Designer You may be familiar with the roles or have them in your organization. But you have users. You probably want users to use your collections. But your users may have impairments. Thinking about your collections through the lens of these roles may help you make your collections more accessible to impaired users. ACTIVITY YOU HAVE BEEN SMOTE AND ARE IMPAIRED.

  • Random impairments will be assigned. Props are provided if necessary.
  • Using a personal device or one of the provided laptops (installed with NVDA and JAWS software),

try using your organization’s digital collections. (Or any online digital collection.)

  • A list of suggested activities to perform is provided.
  • How long does it take you to perform these activities? Was it easy? How did the experience make

you feel, personally? Activity

  • Collections
  • Penn State
  • https://dbbt.io/HSIn
  • Keystone Library Network
  • https://dbbt.io/HSqH
  • Oregon Digital
  • https://dbbt.io/HSqI
  • University of Maine
  • https://dbbt.io/HSqq
  • Barnard College
  • https://dbbt.io/HSqz
  • University of Florida
  • https://dbbt.io/HSqK
  • Library of Congress
  • https://dbbt.io/HSq9
  • Stanford Libraries
  • https://dbbt.io/HSqx
  • Use your own organization’s collections!
  • Actions
  • Browse complete listing of collections and choose one to explore.
  • Find the top five creators and subject for your chosen collection.
  • Do a basic search and try to page through the search results. Select one result view the object.
  • When was the original created? What format was the original? Go back to the homepage.

1 2 1 2 3 1 2 4 1 2 2 1 2 3 1 2 4 1 2

slide-16
SLIDE 16

5/3/2019 2

  • Do an advanced search and combine at least three fields, one of them being a phrase search.
  • After exploring the results, try to print (pretend) and download some objects.

PRODUCT OWNERSHIP

  • Comes from the Scrum/Agile framework.
  • PO is the chief stakeholder, defines the vision, prioritizes work, and liaises with other stakeholders.
  • Interfaces with the development team/vendor and other stakeholders/rest of the organization.
  • PO is accountable for delivering maximum value.
  • If accessibility is important to your organization and users, it’s the product owner’s job to deliver

an accessible application. BETTER FOR EVERYONE It can be a fight for resources, but A FOCUS ON ACCESSIBILITY OFTEN LEADS TO A BETTER EXPERIENCE FOR ALL USERS. Headings clarify the structure of a page. The accessibility requirement on headings will help creating a logical and coherent website in general. Accessibility requires texts to have enough contrast with background. This works better for other types of users as well. Enforcing ALT text on image & UI elements will help everyone better understand the contents and functions of a website. WEB ACCESSIBILITY OUR PHYSICAL SPACES ARE ACCESSIBLE, OUR DIGITAL SPACES NEED TO BE TOO W3C Web Accessibility Initiative, including the Web Content Accessibility Guidelines 2.1 (June 2018) WAI / WCAG Universal design considers all users, including those with disabilities, and reduces or eliminates the need for adaptive technologies. Universal Design The Rehabilitation Act of 1973 prohibits programs receiving federal funding from discriminating against people with disabilities through inaccessible interfaces. Section 504, 508 Title II of the Americans with Disabilities Act of 1990 prohibits discrimination against qualified individuals from public entities. Title II, ADA CONTENTdm 6.x OCLC’S NEW HOSTED VERSION OF CONTENTdm ADVERTISED ACCESSIBILITY IMPROVEMENTS. WE ASKED FOR A TRIAL.

  • We had stability and maintenance issues with our self-hosted instance. Crashed on the Dean’s

husband.

  • Known issues with accessibility and mobile devices.
  • Had already started work on Samvera replacement, but was 2+ years away.

5 6 1 2 7 1 2 3 4 5 6 7 8 9 8 1 2 5 6 1 2 7 1 2 3 4 5 6 7 8 9 8 1 2

slide-17
SLIDE 17

5/3/2019 3

CONTENTdm Responsive ALWAYS DO YOUR OWN TESTING.

  • Worked with Penn State EIT Accessibility Group to test new CONTENTdm with some of our

collection.

  • Results were disappointing based on OCLC messaging and strongly worded emails sent.
  • OCLC listened and their response showed they cared. Successive improvements were made, with

additional rounds of testing and report sharing. ACCESSIBILITY IS MATURING CULTURAL HERITAGE OBJECTS REPOSITORY

  • Samvera-based digital repository with Blacklight as the only starting UI.
  • Accessibility a priority, required feature from day one. Every incremental release undergoes some

form of accessibility testing.

  • Full testing with EIT Accessibility Group as needed and planned for major releases.
  • MVP includes minimal/no JavaScript or other fancy UI features to maintain focus on core

accessibility for graceful fallback.

  • Staff need an accessible interface too.

BEST PRACTICES FOR ADAPTING & CREATING ACCESSIBLE DIGITAL COLLECTION INTERFACES WORKING WITH VENDORS

  • Test all claims
  • Don’t be reluctant to ask or give feedback to the team who developed it
  • When customizing, be careful not to reverse accessibility
  • Test customizations with SiteImprove – it can be downloaded as a Chrome extension
  • Accessibility is always evolving, we are constantly working to make improvements to our products

DEVELOPING YOUR OWN

  • Universal design
  • Progressive enhancement
  • Routine testing, both automated & manual (WCAG) and human using adaptive tech
  • Valid, semantic HTML encoding
  • Unicode! (Accessibility for all languages!)
  • Know how to use ALT and ARIA attributes
  • Test content without CSS and JS enabled
  • Remember screen readers when adding hidden content and for skipping non-primary content

Accessible Content Your website is only as smart as you allow it

  • Use descriptive yet simple English for your content
  • Give relevant names to your titles, subjects, and description; not Page 01, Page02, Page 03
  • Title will be the same as link and alt text

9 1 2 10 11 12 1 2 13 1 2 9 1 2 10 11 12 1 2 13 1 2

slide-18
SLIDE 18

5/3/2019 4

When uploading content

  • Test intended colors in webaim.org/resources/contrastchecker/
  • Text size 'Medium' is the intended sizing for the text
  • When you customize be careful writing descriptions and be mindful of headings (make sure your

site doesn't have too many headings) When configuring WCT QUESTIONS? Penn State University, Digital Preservation Librarian Nathan Tallman, @madcow1029 OCLC, Product Analyst Hanning Chen, @oclc OCLC, User Interface Designer Heather Alexander, @halexdee

3 4 5 14 1 2 3 4 5 6 3 4 5 14 1 2 3 4 5 6