23
WEB ACCESSIBILITY FOR DEVS Helpful hints and tips for dev to build better websites Peter Bui - PB Web Development

Web accessibility for developers

Embed Size (px)

Citation preview

Page 1: Web accessibility for developers

WEB ACCESSIBILITY FOR DEVSHelpful hints and tips for dev to build better websites

Peter Bui - PB Web Development

Page 2: Web accessibility for developers

OVERVIEW OF THINGS

TO LOOK OUT FOR..

Just a quick overview

Page 3: Web accessibility for developers

SEMANTICS

➤ Headings, h1, h2, h3

➤ H1, H3, H2 or H2

➤ Using ordered lists and unordered lists

Page 4: Web accessibility for developers

MARKUP

➤ Designate areas of a site with correct areas, e.g header, navigation, aside, content and footer

➤ Use ARIA Roles

➤ role=navigation, role=banner, role=contentinfo

➤ Examples of ARIA role landmarks - http://www.html5accessibility.com/tests/roles-land.html

Page 5: Web accessibility for developers

CORRESPONDING HTML5 AND ARIA ROLES

➤ Designate areas of a site with correct areas, e.g header, navigation, aside, content and footer

➤ Use ARIA Roles

➤ role=navigation, role=banner, role=contentinfo

➤ Examples of ARIA role landmarks - http://www.html5accessibility.com/tests/roles-land.html

Page 6: Web accessibility for developers

SKIP LINKS

➤ Please always have skip links

➤ Experience returning users navigate quickly

Page 7: Web accessibility for developers

IMAGES

➤ Decorative vs meaningful

➤ Alternative text

➤ Longdesc linking to alternative page describing the image

Page 8: Web accessibility for developers

SEO BENEFITS

➤ Headings for importance

➤ Context

Page 9: Web accessibility for developers

FORMS

➤ Buttons versus links

➤ Form fields

➤ labels

➤ fieldsets, legends, don’t use placeholders

➤ Warning and validation

➤ Timers

Page 10: Web accessibility for developers

TIMERS ON FORMS

➤ Alert with a timer before expires

➤ Use ARIA alerts

Page 12: Web accessibility for developers

TEXT SIZING AND TYPOGRAPHY

➤ Make sure you can zoom by 200%

➤ base font size of 14px is a good starting point

➤ Choose readable fonts

➤ Heading sizes should be distinguishable

Page 13: Web accessibility for developers

CAPTCHA

➤ It’s Evil

➤ Google ReCaptcha isn’t usable

➤ Cognitive issues and moretextcaptcha.com

Page 14: Web accessibility for developers

MEDIA

➤ Auto playing media - don’t do it

➤ Flashing video

➤ Keyboard accessible media controls

Page 15: Web accessibility for developers

LANGUAGES

➤ <html lang=“en”>

➤ Joomla is accessible by language by default WIN

Page 16: Web accessibility for developers

KEYBOARD NAVIGATION

➤ Tab tab tab, shift tab shift tab

➤ :focus

Page 17: Web accessibility for developers

VALID CODE

➤ Valid code reads better for screen readers

➤ use free html validators

Page 18: Web accessibility for developers

HTML

➤ Anyone uses HTML for layouts?

➤ Use Table headers, TH, table captions and so on to describe a table and its data. Give meaning to the data

Page 19: Web accessibility for developers

VALID CODE

➤ Valid code reads better for screen readers

➤ use free html validators

Page 20: Web accessibility for developers

TESTERS

➤ Squiz JS tester

➤ tenon.io for build testing and reporting.

Page 21: Web accessibility for developers

CASE STUDY TIME

Need a volunteer website

Page 22: Web accessibility for developers

SOCIAL MEDIA MARKETING

➤ Engage with your customers in their space

➤ Advertise in a cost effective area

➤ Take advantage of public comments, recommendations and complaints

Page 23: Web accessibility for developers

QUESTIONS?TWITTER: @ASTROBOYSOUP