STEPS TO WCAG 2.0CSUN20131 mars 2013

1

AURELIEN LEVYaccessibility expert

Temesis2

EXPERT POINT OF VIEWweb accessibility expert want to have fun

3

DEVELOPER POINT OF VIEWWeb developer want short and simple coding instruction

image function

?

logo ?

yes ?

informative ?

decorative ?

no ?

alternative ?

links ? short ?

longdescription ?

links ?? ??

??

??

?

4

THE MOUNT WCAG 2.0• errors - first step (81 instructions)

• risks - second step (49 instructions)5

FIRST STEP TO WCAG 2.0

• All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below

• Use the alt attribute for every img element

• If the img element is the only child of a button or an a element, do not leave its alt attribute empty

6

SECOND STEP TO WCAG 2.0

• The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

• Use with caution the target attribute with a _blank value for an a element

7

AGILE LEARNING/TEACHING• 4 hands coding

• quick review

• online helpdesk8

OPQUAST DESKTOP• Firefox extension available at https://desktop.opquast.com/en/

• Source code on Github9

OPQUAST FRAMEWORK• Opquast Checklist

• Opquast Reporting

• Opquast Helpdesk10

HTML5, CSS3, ARIAdon’t use autoplay attribut,

use with caution the assertive value for aria-live attribut, etc..

11

QUESTIONS ?

18, rue Lucien Granet - 33150 Cenon - France

Tél. : +33 (0)5 56 401 402www.temesis.com

@goetsuaurelien.levy@temesis.com

https://checklists.opquast.com/en/accessibilityfirststep

https://checklists.opquast.com/en/accessibilitysecondstep

12