508 User Experience first in the development lifecycle Captions - - PowerPoint PPT Presentation

508
SMART_READER_LITE
LIVE PREVIEW

508 User Experience first in the development lifecycle Captions - - PowerPoint PPT Presentation

Solve your UI Optimize workflow Avoid back-pedaling and waivers Arva Adams U.S. Patent and Trademark Office 508 User Experience first in the development lifecycle Captions A key accessibility feature is captions. Naturally, they make sure


slide-1
SLIDE 1

508

first

Solve your UI Optimize workflow Avoid back-pedaling and waivers

Arva Adams

U.S. Patent and Trademark Office User Experience

in the development lifecycle

slide-2
SLIDE 2

508

first

Captions

A key accessibility feature is

  • captions. Naturally, they make sure

that people who can’t hear the video can understand the video.

slide-3
SLIDE 3

508

first

Captions

But how many of you multi-taskers are familiar with this scenario?

I’m learning about patent prior art and can still follow the game. I c a n h e a r t h e g a m e a n d t e x t m y f r i e n d s w i t h

  • u

t h e a r i n g S a m ’ s b

  • r

i n g v i d e

  • .
slide-4
SLIDE 4

508

first

Visuals

Start with our trusty dusty U.S. Web Design System. Search “U.S. Web Design System” in Google and boom.

slide-5
SLIDE 5

508

first

AA and AAA contrast

AAA is the W3C’s recommendation for contrast, and AA contrast is mandated by Section 508. You can use many tools to test for and achieve AAA contrast. This makes your content readable by users with color vision issues.

slide-6
SLIDE 6

508

first

AA and AAA contrast

Users with low vision and imperfect color vision will have less difficulties reading.

slide-7
SLIDE 7

508

first

AA and AAA contrast

And here’s the user with perfect vision in an airport.

slide-8
SLIDE 8

508

first

AA and AAA contrast

And now the user with perfect vision is in an airport next to the huge windows overlooking the runway on a super-sunny day.

slide-9
SLIDE 9

508

first

Text size

Back to the our U.S. Web Design System. You’ll find text size and line spacing guidelines that are accessible.

slide-10
SLIDE 10

508

first

Text size and line spacing

But, in addition to being accessible, look how readable and

scannable content is when it follows good typography.

slide-11
SLIDE 11

508

first

Consistent style tags ALT tags Meaningful links

Of course, these 508 practices help people who use screen readers.

<h2> <th> <td> <alt=>

Yes! Learn more at www... No! Click here to learn more at www...

slide-12
SLIDE 12

508

first

Consistent style tags ALT tags Meaningful links

But, they also improve your product’s search engine game. SEO is magically improved with accessibility best practices.

<h2> <th> <td> <alt=>

Yes! Learn more at www... No! Click here to learn more at www...

slide-13
SLIDE 13

508

first

Tab and read orders

Naturally, your product’s tab order and read order must be correct for your content to be accessible for people who rely on screen readers or can’t use a mouse.

slide-14
SLIDE 14

508

first

Tab and read orders

But, most form filler-outers prefer to keep their hands on the keyboard throughout the form, regardless of their visual and physical abilities.

1 2 3 4

slide-15
SLIDE 15

508

first

Put accessibility upstream in the development process.

You know the user story must be accessible, by law, so 508 it first.

slide-16
SLIDE 16

Develop and test 508 in parallel.

Instead of...

Define the UI user story Add product

  • wner

acceptance criteria Massage acceptance criteria with dev team Develop UI user story Test user story against acceptance criteria Test 508 with a blanket user story Test prototype with users Test FQT version with users

UX issue Can’t find call to action UX issue Users squinting UX issue Bad color choices Defect Color contrast flagged D e f e c t R e a d

  • r

d e r w r

  • n

g Defect UI lost when zoomed

slide-17
SLIDE 17

Develop and test 508 in parallel.

Do this:

Define the UI user story Add PO acceptance criteria w/508 Massage acceptance criteria with dev team Develop UI user story Test user story against ACs, which include 508 Test prototype with users Test dev version with users

508 in

prototype

508 in

dev

508 in

planning Test 508 with a blanket user story 508 final sanity check

slide-18
SLIDE 18

Develop and test 508 in parallel.

Do this...

Define the UI user story Add PO acceptance criteria w/508 Massage acceptance criteria with dev team Develop UI user story Test user story against acceptance criteria Test 508 with a blanket user story Test prototype with users Test FQT version with users

508 in

prototype

508 in

dev

508 in

planning

508

final sanity check

UX issue Can’t find call to action UX issue Users squinting UX issue Bad color choices Defect Color contrast flagged D e f e c t R e a d

  • r

d e r w r

  • n

g Defect UI lost when zoomed

slide-19
SLIDE 19

508

first

Solve your UI Optimize workflow Avoid back-pedaling and waivers

Arva Adams

U.S. Patent and Trademark Office User Experience

in the development lifecycle