Ian Lloyd/Patrick H. Lauke: Accessified - practical accessibility fixes any web developer can use / South By Southwest SXSW / Austin, Texas, 11 March 2007

•

0 gostou•100 visualizações

Tecnologia

Accessified
Patrick H. Lauke / Ian Lloyd / South by Southwest / Austin, Texas / 11 March 2007
practical accessibility fixes any web developer can use

About us
Ian - accessify.com
Patrick - splintered.co.uk (Salford Uni)
Web Standards Project Accessibility Task Force
(AKA WaSP ATF)

About the session
What we're not covering:
* Fine details of WCAG 1 or 2
* Expensive tools and services
* Advanced/experimental techniques
Not here to argue complex points...

About the session
*What we are covering:
* Simple creation tools/wizards - free
* Evaluation tools in your browser
* Using pre-recorded screencasts

Part 1: Setting out on the right foot
“Because prevention is better than a cure”

Accessify Tools
*Just a handful to demonstrate
* Accessible table builder
* Accessible form builder
* List-o-matic

Accessify Tools
*Accessible table builder
*View video on YouTube

Accessify Tools
*Accessible form builder
*View video on YouTube

Accessify Tools
*List-o-matic
*View video on YouTube

Part 2: Evaluating accessibility
with toolbars
“Don’t be a tool. Use one.”

11
Headings & accessibility
*screen reader users
*keyboard navigation
11

12
Web Dev Toolbar:
Page headings & document outline
*View video on YouTube
12

13
Semantic markup in general
*using right element for the right job
*some AT currently does not support all semantic
markup
*right thing to do, nonetheless
13

14
Web Dev Toolbar:
Highlighting custom elements
*View video on YouTube
14

15
JavaScript
*not necessarily evil
*depending on type of site, may need to have to
work without it
15

16
Web Dev Toolbar:
Disabling JavaScript
*View video on YouTube
16

17
Labels for forms
*labels unequivocally tie text to form element
*usability for all users (even sighted mouse users)
17

18
Web Dev Toolbar:
Form fine points
*View video on YouTube
18

19
Alt text - deceptively simple?
*most basic accessibility requirement
*still “controversial” - many differing opinions on
“good” alt
19

20
Web Dev Toolbar:
Image alts - how they should be
*View video on YouTube
20

Part 3: Other useful tools you may
like to try ...

22
Graybit - Test Colour Contrast
*View video on YouTube
22

Part 4: Unobtrusive accessibility
AKA: Doing the right thing, without your boss
noticing...

Further learning
*Forums
* www.accessifyforum.com
* www.webaim.org
*These slides (may be *) available at:
*accessify.com/sxsw2007/
** File size permitting!

Mais conteúdo relacionado

Mais procurados

Full stack-web-design

Kevin Conboy

Build a better(reactive) word press

Bhushan Jawle

Ie9 и ie10. алекс могилевский. зал 2

rit2011

Develop 4 Developers

Christian Güdemann

La integración continua es una práctica de ingeniería de software que consiste en hacer integraciones automáticas de un proyecto lo más a menudo posible, para así poder detectar fallos cuanto antes. Podríamos pensar que en 2020 todos lo equipos integran continuamente, pero conversando con diferentes profesionales podemos ver que no siempre es así. En esta sesión revisitaremos esta importante práctica, clave en DevOps, que por ser una de las más básicas, damos demasiadas veces por superada.

Back to basic: continuous integration (Madrid DevOps)

Sergio Navarro Pino

OpenNTF Essentials

Christian Güdemann

Android development War Stories

Lope Emano

Advanced deployment scenarios

Sergio Navarro Pino

Advanced deployment scenarios (netcoreconf)

Sergio Navarro Pino

There is a lot of confusion about the WebDriver W3C standard: what does it mean, what do I need to do, and how urgent is it? Marcus will cover several steps you need to take in order to stay up-to-date with the latest version, as well as some of the history the project has gone through, which led to this historic standard. Code will be made simple, examples will be shown, and myths will be dispelled.

Selenium 4 ukraine keynote slides

Marcus Merrell

ChatBots for self-service DevOps

Simon Massey

Why You Should Start Using Docker

Alexandru Bolboaca

WordCamp Barcelona 2015 : From Design to a Theme

Pancho Pérez Salazar

That worked before

Christian Güdemann

Mais procurados (14)

Full stack-web-design

Build a better(reactive) word press

Ie9 и ie10. алекс могилевский. зал 2

Develop 4 Developers

Back to basic: continuous integration (Madrid DevOps)

OpenNTF Essentials

Android development War Stories

Advanced deployment scenarios

Advanced deployment scenarios (netcoreconf)

Selenium 4 ukraine keynote slides

ChatBots for self-service DevOps

Why You Should Start Using Docker

WordCamp Barcelona 2015 : From Design to a Theme

That worked before

Semelhante a Ian Lloyd/Patrick H. Lauke: Accessified - practical accessibility fixes any web developer can use / South By Southwest SXSW / Austin, Texas, 11 March 2007

Test Automation with Twist and Sahi

ericjamesblackburn

VAST 8.0

ESUG

In this session you will kick-start your citizen developer journey by running your first Ui (user interaction platform) automation. You will learn how to automate data related processes involving online platforms. Then you will transfer and manage that data in an internal application. 15:00 Hello & welcome to RPA Summer School 15:05 Introduction to User Interface automation 15:10 Getting familiar with StudioX activities for UI automation 15:15 Open Studio X and download project file 15:20 Create Your first UI automation project (Web application) 15:50 What more can be automated with UI (Desktop application) 16:00 Interaction and Q&A 16:20 Academy follow-up and examples.

RPA summer school session 2.2: Run your first UI automation

Cristina Vidu

Homestead demo

Saranga Tripathy

Module 2-web-a11y-steve lee

Steve Lee

Stanislav Khorunzhyi, "Front-end it like a PRO"

Sigma Software

In this session you will kick-start your citizen developer journey by running your first UI (user interaction platform) automation. You will learn how to automate data related processes involving online platforms. Then you will transfer and manage that data in an internal application. 15:00 Hello & welcome to RPA Summer School 15:05 Introduction to User Interface automation 15:10 Getting familiar with StudioX activities for UI automation 15:15 Open Studio X and download project file 15:20 Create Your first UI automation project (Web application) 15:50 What more can be automated with UI (Desktop application) 16:00 Interaction and Q&A

RPA Summer School Session 2.1: Run your first UI automation

Cristina Vidu

I've managed a team that developed serious android apps, and ended up dabbling with tools out there and processes/systems. Here is a quick summary of the various things to think about if you're serious about android development, and in some cases, my recommendations. This covers: IDE Build Source Control Bug/Task tracking Crash reporting Analytics Test Automation Continuous Integration Device Matrix testing Performance testing Beta testing A/B testing Backend-as-a-Service

Tools/Processes for serious android app development

Gaurav Lochan

The Battle on Selenium Camp conferece February 2017 http://seleniumcamp.com/talk/qa-livecoding-battle-typed-element-framework-jdi-vs-untyped-elements-framework-selenide/ Why typed elements (like Buttons, Images, Checkboxes, Links etc.) are bad practice in UI tests? Or are non-typed elements (like SelenideElement for ´em all!) more evil? Is it better to have predefined Element hierarchy or not? Alexei and Roman have delivered a sound theoretical battle earlier at Heisenbug-2016 Conference in Moscow. But were everything said just words? The both QA wrestlers are still standing behind their concepts and are willing to prove their point at live coding sessions before the judging audience! In this QA Battle the parties will solve problems using a typed framework JDI and an non-typed one – Selenide, commenting their actions. The audience will decide with their votes which of the concept was better.

Roman iovlev battle - JDI vs Selenide - Selenium Camp

Роман Иовлев

Testing your applications with mbunit

Ben Hall

Overview on Anypoint Platform APIs and Anypoint Studio Tips and Tricks

MergeStack

jp06_bossola

Bruno Bossola

Beautfiul world of Flutter Testing

Max Weber

The Test way

Mikhail Grinfeld

3 App Tools Maura Amato TECH510

maurameyers

In this talk we will discuss different levels of automation and what automation has in common with DevOps, Product Maturity and Machine learning. We will show how automation enables fast feedback and finally, while looking at an example of an observable and continuous deployable system we will show how automation can make your team more productive (while delivering more stable software and decrease time to market).

A brief history of automation in Software Engineering

Georg Buske

Selenium- A Software Testing Tool

Zeba Tahseen

LITA Instructional Technologies IG - Presentation at MW Philly 2014

Oregon State University Libraries and Press

Usable Software Design

Alexandru Bolboaca

Continuous test automation

Viresh Doshi

Semelhante a Ian Lloyd/Patrick H. Lauke: Accessified - practical accessibility fixes any web developer can use / South By Southwest SXSW / Austin, Texas, 11 March 2007 (20)

Test Automation with Twist and Sahi

VAST 8.0

RPA summer school session 2.2: Run your first UI automation

Homestead demo

Module 2-web-a11y-steve lee

Stanislav Khorunzhyi, "Front-end it like a PRO"

RPA Summer School Session 2.1: Run your first UI automation

Tools/Processes for serious android app development

Roman iovlev battle - JDI vs Selenide - Selenium Camp

Testing your applications with mbunit

Overview on Anypoint Platform APIs and Anypoint Studio Tips and Tricks

jp06_bossola

Beautfiul world of Flutter Testing

The Test way

3 App Tools Maura Amato TECH510

A brief history of automation in Software Engineering

Selenium- A Software Testing Tool

LITA Instructional Technologies IG - Presentation at MW Philly 2014

Usable Software Design

Continuous test automation

Mais de Patrick Lauke

WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the guidelines' normative text. And, of course, it is not perfect - with some omissions, handwaving, and straight-up loopholes. So where does this leave developers and auditors? In this talk - a reprise of a previous talk, now updated to cover new SCs from WCAG 2.2 - Patrick may not have all the answers, but he'll have a good rant around the subject anyway...

These (still) aren't the SCs you're looking for ... (mis)adventures in WCAG 2...

Patrick Lauke

Update about Pointer Events Level 3 work for the upcoming W3C Technical Plenary and Advisory Committee (TPAC) 2023 in Seville https://www.youtube.com/watch?v=r0spZl1qaa0 https://w3c.github.io/pointerevents/ https://www.w3.org/TR/pointerevents/ https://www.w3.org/2023/09/TPAC/ https://patrickhlauke.github.io/touch/w3c_tpac2023_pewg/ Cross-posted from https://www.w3.org/2023/09/TPAC/group-updates.html#pointer-events

Pointer Events Working Group update / TPAC 2023 / Patrick H. Lauke

Patrick Lauke

WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the actual guidelines' normative text. And of course they're not perfect - with some omissions, handwaving, and straight up loopholes. So where does this leave developers and auditors? In this talk, Patrick may not have all the answers, but he'll have a good rant around the subject anyway...

These aren't the SCs you're looking for ... (mis)adventures in WCAG 2.x inter...

Patrick Lauke

WCAG is supposed to give us a reasonably objective way of saying whether or not the sites we are building/auditing are "accessible" (to a particular baseline). However, they are only as useful as our understanding and interpretation of the actual guidelines' normative text. And of course they're not perfect - with some omissions, handwaving, and straight up loopholes. So where does this leave developers and auditors? In this talk, Patrick may not have all the answers, but he'll have a good rant around the subject anyway...

These aren't the SCs you're looking for ... (mis)adventures in WCAG 2.x inter...

Patrick Lauke

Too much accessibility - good intentions, badly implemented / Public Sector F...

Patrick Lauke

Styling Your Web Pages with Cascading Style Sheets / EDU course / University ...

Patrick Lauke

Evaluating web sites for accessibility with Firefox / Manchester Digital Acce...

Patrick Lauke

Managing and educating content editors - experiences and ideas from the trenc...

Patrick Lauke

Implementing Web Standards across the institution: trials and tribulations of...

Patrick Lauke

Geolinking content - experiments in connecting virtual and physical places / ...

Patrick Lauke

All change for WCAG 2.0 - what you need to know about the new accessibility g...

Patrick Lauke

Web Accessibility - an introduction / Salford Business School briefing / Univ...

Patrick Lauke

Doing it in style - creating beautiful sites, the web standards way / WebDD /...

Patrick Lauke

Web standards pragmatism - from validation to the real world / Web Developers...

Patrick Lauke

The state of the web - www.salford.ac.uk / 2007

Patrick Lauke

Keyboard accessibility - just because I don't use a mouse doesn't mean I'm se...

Patrick Lauke

Vanilla HTML is limiting and boring. Our clients demand highly engaging and interactive web experiences. And wouldn’t you know, with just a bit of HTML and JavaScript we can craft amazing custom controls, widgets and effects that go far beyond the confines of traditional static markup. But how can we ensure that these custom experiences are both understandable and usable for people with disabilities, and in particular those using assistive technologies such as screen readers? In this talk, we will look at the basics of making some common custom-built components accessible - covering how browsers and assistive technologies interact, the limitations of HTML, and how ARIA can help make interactive experiences more accessible. In addition, we will explore some of the recent additions in ARIA 1.1, as well as some particular challenges when it comes to traditional ARIA patterns and assistive technologies on mobile/tablet/touch devices. Evergreen slidedeck at https://patrickhlauke.github.io/aria/presentation/ / https://github.com/patrickhlauke/aria/

WAI-ARIA An introduction to Accessible Rich Internet Applications / JavaScrip...

Patrick Lauke

WAI-ARIA An introduction to Accessible Rich Internet Applications / CSS Minsk...

Patrick Lauke

WAI-ARIA An introduction to Accessible Rich Internet Applications / AccessU 2018

Patrick Lauke

Beyond smartphones and tablets, touchscreens are finding their way into laptops and even desktop computers. With hardware support for touch becoming increasingly ubiquitous, it's time to explore what new possibilities are available to developers. This session will cover the basics of handling touch events - from making sure simple single-tap interactions are as responsive as possible, all the way to examples of full multitouch, gesture-enabled elements.

Getting touchy - an introduction to touch and pointer events / Frontend NE / ...

Patrick Lauke

Mais de Patrick Lauke (20)