making websites work for everyone web accessibility @ ucla

26
MAKING WEBSITES WORK FOR EVERYONE WEB ACCESSIBILITY @ UCLA Patrick Burke Lloyd Nicks

Upload: ember

Post on 24-Mar-2016

37 views

Category:

Documents


1 download

DESCRIPTION

Making websites work for everyone web Accessibility @ UCLA. Patrick Burke Lloyd Nicks. What does ‘Accessible’ mean?. “the degree to which a product, device, service, or environment is available to as many people as possible” source: wikipedia. UCLA Disability Awareness WEEk. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Making websites work for everyone web Accessibility @ UCLA

MAKING WEBSITES WORKFOR EVERYONE

WEB ACCESSIBILITY @ UCLA

Patrick BurkeLloyd Nicks

Page 2: Making websites work for everyone web Accessibility @ UCLA

“the degree to which a product, device, service, or environment is available to as many people as possible”source: wikipedia

WHAT DOES ‘ACCESSIBLE’ MEAN?

Page 3: Making websites work for everyone web Accessibility @ UCLA

UCLA DISABILITY AWARENESS WEEK

Disability Awareness week is in progress, with several events still open. Details are available on the UCLA Committee on Disability website at http://ucod.ucla.edu

Page 4: Making websites work for everyone web Accessibility @ UCLA

Many years before he joined Google as a Director of Engineering, Ray Kurzweil invented much of the adaptive technology we use, including:

Optical Character Recognition (OCR)Text to SpeechSpeech recognitionLearning disability software

MODERN DAY ACCESSIBILITY

Page 5: Making websites work for everyone web Accessibility @ UCLA

Adaptive software development hasn’t been part of mainstream, so new tech often causes new problems, excluding groups of people almost at random;

Inclusive Design needs to be considered early in projects to ensure access for all;

Include testing by people with disabilities during a project.

WHY IS ACCESSIBILITY IMPORTANT?

Page 6: Making websites work for everyone web Accessibility @ UCLA

Many Legal risks associated with lack of accessibility:

Accessible alternatives must provide equivalent functionality. So if a website is inaccessible, any alternative must be available 24/7, from any location, etc.

An accessible website is almost always the most cost-effective and universal solution:

Cheaper than staffing a 24/7 call center, or providing a full-time assistant.

ACCESSIBILITY LEGAL ISSUES

Page 7: Making websites work for everyone web Accessibility @ UCLA

Organizations (like UCLA) can improve accessibility by purchasing accessible software, or programs that make it easy to produce accessible content.

Selecting commercial and open source applications with accessibility in mind (Drupal and other CMS options).

Including accessibility requirement as part of contracts with outsourced developers

ACCESSIBILITY STRATEGY

Page 8: Making websites work for everyone web Accessibility @ UCLA

Three levels of compliance documented by the WCAG 2.0 Level A Level AA Level AAA

UC Electronic Accessibility policy specifies WCAG AA as goal. Level AA has broad international acceptance. Balances what helps most users with what is achievable.

ACCESSIBILITY SPECIFICATIONS

Page 9: Making websites work for everyone web Accessibility @ UCLA

blind user low vision usercolor blind userdeaf / hard of hearing useruser with dexterity/mobility disabilityuser with cognitive disability

USER SCENARIOS

Page 10: Making websites work for everyone web Accessibility @ UCLA

WHAT IS MISSING?

Tests for elements that can only be evaluated by a human. Color Contrast Captions Navigation

Non technical assessment toolsPractical / Case based analysis

Page 11: Making websites work for everyone web Accessibility @ UCLA

WHY QUICK TESTS?

AMP automated tests still show many items that require human judgment of accessibility (AMP scores show either 100% or 0% success)

Page 12: Making websites work for everyone web Accessibility @ UCLA

QUICK TEST SCOPE

We aim to create a fast process to make many of those human-judgment assessments.

We do not attempt to show how to fix accessibility errors in this talk.

Page 13: Making websites work for everyone web Accessibility @ UCLA

QUICK TESTS GOALS

Further prioritize the 21 Level A WCAG checkpoints. (Most can be checked by AMP.)

Do verifiable, repeatable tests for the 13 AA items (that mostly require human judgment).

Find simple, quick tests that can be applied to large amounts of content.

Page 14: Making websites work for everyone web Accessibility @ UCLA

THE TESTS

Consistent NavigationColor ContrastDouble-Size TestCopy TestLogical StructureFocus VisibleCaptionsImage Accessibility

Page 15: Making websites work for everyone web Accessibility @ UCLA

CONSISTENT NAVIGATION

Maximum 5 min: Are there unusual changes to the navigation or other page components?

Things to check: Consistency between Front page and secondary page

navigation Choose a common navigation element and use

keyboard only to get there.

Page 16: Making websites work for everyone web Accessibility @ UCLA

Run tests on 4-5 potential problem areas, concentrating on extreme cases requiring immediate fix. WebAIM’s Jared Smith mention readability is a

continuum. Text at 4.4:1 isn’t suddenly totally illegible. So focus

on the biggest problems.

COLOR CONTRAST

Page 17: Making websites work for everyone web Accessibility @ UCLA

Color Contrast Checking tools Snook.ca

http://snook.ca/technical/colour_contrast/colour.html Juicy Studio:

http://juicystudio.com/services/luminositycontrastratio.php

COLOR CONTRAST

Page 18: Making websites work for everyone web Accessibility @ UCLA

DOUBLE SIZE TEST

Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)

Use CTRL-+ (CMD-+) to test whether the site is readable at 2x magnification.

Page 19: Making websites work for everyone web Accessibility @ UCLA

COPY TEST

Browser/OS-level test To test if images of text are being used, try

copying any “suspicious” items. WCAG: (1.4.5) Text that cannot be copied is

likely to be inaccessible.

Page 20: Making websites work for everyone web Accessibility @ UCLA

LOGICAL STRUCTURE - WCAG 2.4.6

Headings and Labels: Headings ands labels should describe topic or purpose. (Level AA)

Headings should not be used for visual effects, on large blocks of content.

Use judiciously (too much structure without content is a problem).

Page 21: Making websites work for everyone web Accessibility @ UCLA

LOGICAL STRUCTURE

Are headings used for logical structure? Does structure make sense? Do not worry about skipping consecutive

heading levels (even though it is a red flag in AMP).

Page 22: Making websites work for everyone web Accessibility @ UCLA

VISIBLE FOCUS – WCAG 2.4.7

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)

Is there a clear focus indicator when tabbing with keyboard.

On the homepage & 5 subpages, test focus by tabbing through the page.

Page 23: Making websites work for everyone web Accessibility @ UCLA

CAPTIONS

Quantify & assess portion of content that is multimediaEnsure controls are easy to identify and to enable captioning.If significant in quantity or importance, play 30 sec of 3-5 clips Are captions present? Are they readable?

Page 24: Making websites work for everyone web Accessibility @ UCLA

IMAGES

Survey Content: Appropriate Use of ALT text on ImagesCheck 3-5 random images (or prominent images) on a site for appropriateness of alt text. Fail if several of those images have alt text = the

filename. Fail if significant amounts of text is embedded in

images. Fail if most images on the site have the same alt text

Page 25: Making websites work for everyone web Accessibility @ UCLA

REFERENCES

UCLA Disabilities and Computing Program http://dcp.ucla.edu

Electronic Accessibility Leadership Team http://www.ucop.edu/electronic-accessibility/

SSB Bart Group AMP https://uc.ssbbartgroup.com

WebAIM http://webaim.org/

W3c Easy Checks http://www.w3.org/WAI/EO/Drafts/eval/checks

BBC Mobile Accessibility Guidelines 0.8 http

://www.bbc.co.uk/guidelines/futuremedia/accessibility/mobile_access.shtml

Page 26: Making websites work for everyone web Accessibility @ UCLA

Testing AMP

https://www.ssbbartgroup.com/amp Wave

http://wave.webaim.org/ Validators

http://www.w3.org/QA/Tools/#validators Color Contrast

Snook.ca http://snook.ca/technical/colour_contrast/colour.html

Juicy Studio: http://juicystudio.com/services/luminositycontrastratio.php

MOBILE ACCESSIBILITY RESOURCES