This is a longer version of my presentation "Responsible Design: Accountable Accessibility" but with a catchier name :)
This talk tells my story of how I went from front end developer who knew nothing about accessibility to an accessibility advocate.
Included in this talk are my "10 Tips" that any developer can use on day one without any experience authoring accessible HTML.
This talk was originally presented at the Accessibility Conference in Guelph, Ontario, Canada on May 29, 2013.
Selfish Accessibility: Presented at GoogleAdrian Roselli
We can all pretend that we're helping others by making web sites and software accessible, but we are really making them better for our future selves. Learn some fundamentals of accessibility and how it can benefit you (whether future you from aging or you after something else limits your abilities). We'll review simple testing techniques, basic features and enhancements, coming trends, and where to get help. This isn't intended to be a deep dive into ARIA, but more of an overall primer for those who aren't sure where to start nor how it helps them.
You know it's important for your web project to be accessible to people who use all kinds of assistive technology to access the internet. But all the guidelines for web accessibility you can find don't go much beyond "make sure all your images have alt text", and all the resources you can find treat "accessibility" as a synonym for "making your site work in a screen reader". You know there are other things you should be doing and other forms of assistive technology you should be accomodating, but all the best practices documents are a complicated morass of contradicting information (if you can find best practices documents at all.)
Have no fear! This tutorial gives you a number of concrete steps to take to make things more accessible.
This presentation has downloadable notes and exercises available at http://denise.dreamwidth.org/tag/a11y . Video of the talk should be available later.
I was invited by the Hatchery+ to give a presentation and workshop on building products - a brief overview on modern web apps, tech stacks, languages, frameworks, services, APIs and more.
Making Your Site Printable: CSS Summit 2014Adrian Roselli
The push for responsive web design has helped web developers consider how the sites they develop can adapt to different devices, including sizes, screen resolutions, and even contexts.
It should now be easier than ever to respond to a format that has existed since the start of the web -- print.
I'll walk through the process for making your responsive sites respond to the format we most often forget and show you how to use Google Analytics to track what pages are printed from your site.
We can all pretend that we’re helping others by making web sites accessible, but we are really making the web better for our future selves. Learn some fundamentals of web accessibility and how it can benefit you (whether future you from aging or you after something else limits your abilities). We’ll review simple testing techniques, basic features and enhancements, coming trends, and where to get help. This isn’t intended to be a deep dive into ARIA, but more of an overall primer for those who aren’t sure where to start nor how it helps them.
We can all pretend that we're helping others by making web sites accessible, but we are really making the web better for our future selves. Learn some fundamentals of web accessibility and how it can benefit you (whether future you from aging or you after something else limits your abilities). We'll review simple testing techniques, basic features and enhancements, coming trends, and where to get help. This isn't intended to be a deep dive into ARIA, but more of an overall primer for those who aren't sure where to start nor how it helps them.
Selfish Accessibility: Presented at GoogleAdrian Roselli
We can all pretend that we're helping others by making web sites and software accessible, but we are really making them better for our future selves. Learn some fundamentals of accessibility and how it can benefit you (whether future you from aging or you after something else limits your abilities). We'll review simple testing techniques, basic features and enhancements, coming trends, and where to get help. This isn't intended to be a deep dive into ARIA, but more of an overall primer for those who aren't sure where to start nor how it helps them.
You know it's important for your web project to be accessible to people who use all kinds of assistive technology to access the internet. But all the guidelines for web accessibility you can find don't go much beyond "make sure all your images have alt text", and all the resources you can find treat "accessibility" as a synonym for "making your site work in a screen reader". You know there are other things you should be doing and other forms of assistive technology you should be accomodating, but all the best practices documents are a complicated morass of contradicting information (if you can find best practices documents at all.)
Have no fear! This tutorial gives you a number of concrete steps to take to make things more accessible.
This presentation has downloadable notes and exercises available at http://denise.dreamwidth.org/tag/a11y . Video of the talk should be available later.
I was invited by the Hatchery+ to give a presentation and workshop on building products - a brief overview on modern web apps, tech stacks, languages, frameworks, services, APIs and more.
Making Your Site Printable: CSS Summit 2014Adrian Roselli
The push for responsive web design has helped web developers consider how the sites they develop can adapt to different devices, including sizes, screen resolutions, and even contexts.
It should now be easier than ever to respond to a format that has existed since the start of the web -- print.
I'll walk through the process for making your responsive sites respond to the format we most often forget and show you how to use Google Analytics to track what pages are printed from your site.
We can all pretend that we’re helping others by making web sites accessible, but we are really making the web better for our future selves. Learn some fundamentals of web accessibility and how it can benefit you (whether future you from aging or you after something else limits your abilities). We’ll review simple testing techniques, basic features and enhancements, coming trends, and where to get help. This isn’t intended to be a deep dive into ARIA, but more of an overall primer for those who aren’t sure where to start nor how it helps them.
We can all pretend that we're helping others by making web sites accessible, but we are really making the web better for our future selves. Learn some fundamentals of web accessibility and how it can benefit you (whether future you from aging or you after something else limits your abilities). We'll review simple testing techniques, basic features and enhancements, coming trends, and where to get help. This isn't intended to be a deep dive into ARIA, but more of an overall primer for those who aren't sure where to start nor how it helps them.
We can all pretend that we're helping others by making web sites and software accessible, but we are really making the experience better for our future selves. Learn some fundamentals of web and software accessibility and how it can benefit you (whether future you from aging or you after something else limits your abilities).
We'll review simple testing techniques, basic features and enhancements, coming trends, and where to get help. This isn't intended to be a deep dive, but more of an overall primer for those who aren't sure where to start nor how it helps them.
Insights:
- Broader context for how all users are or will be disabled, whether temporarily or permanently.
- Basic tests and best practices that can be integrated into development team workflows to make interfaces accessible.
- Introduction to standards and tools already available.
Accessibility is not disability Drupal South 2014Gareth Hall
Accessibility
The web is about information sharing. Why make it hard for users to access your content. Release your site from bad building practices, make it equal access for all and get SEO benefits for free.
Get through to the disabled community
By breaking down disability barriers you open up your content to a wider community currently 600,000+ in NZ.
There are definite dos and don’ts when it comes to building for the disabled. Learn what works for them.
WordPress Blogs 101 is a deck of notes for a training presentation for beginners. It's a hands-on presentation, and so this shouldn't be considered a "finished" product because many of the speaker notes won't mean anything to most users unless they're led through it by a trainer.
This is version 2 prepared for the annual Seton Hall University Student Technology Days series, aimed at student organizations' leaders who are interested in building an on-line presence for their group.
It covers the basics of obtaining and working with a blog in the University's self-hosted WordPress multisite environment, including examples, using the dashboard, managing comments, posts and pages, media embeds, options such as themes, widgets and menus.
Mistakes, misconceptions, over-indulgences, minutia, and generally silly aspects of modern web accessibility. Presented by Jared Smith
at Accessing Higher Ground Conference 2009.
Making your site printable: WordCamp Buffalo 2013Adrian Roselli
The push for responsive web design has helped web developers consider how the sites they develop can adapt to different devices, including sizes, screen resolutions, and even contexts. It should now be easier than ever to respond to a format that has existed since the start of the web – print. I’ll walk through the process for making your responsive sites respond to the format we most often forget.
Presentation for the Denver HTML5 Users Group on advanced HTML techniques.
Focuses, specifically, on semantic markup (POSH), new HTML5 structural elements, microformats, microdata and ARIA landmark roles
Developers: Why Care About the User? (2017)Andrew Malek
As developers, we deal with technologies, frameworks, and data, making it very easy to forget that what we create is meant for real people to use.
While designers and UI specialists should handle most decisions about how a product or service looks and feels, we should all be on the same page to make better solutions. Whether we are building an interface for a desktop website, mobile application, or chatbot, what are some basic design concepts that we as developers can pick up, allowing us to be on the same page with designers and product owners during product meetings and discussions?
Design and Development Techniques for Accessibility: WordCamp Tampa 2015Robert Jolly
I’ll explore basic web accessibility principles for web designers, developers, and site owners, then show how to turn seemingly daunting and confusing accessibility requirements into understandable, actionable tasks and techniques. The talk will cover some of the accessibility-specific WordPress plugins and themes available, as well as some quick, easy tests to integrate into design and development workflows.
Why Nobody Fills Out My Forms (Updated)Andrew Malek
Has your web form conversion rate hit a wall? Are users not receiving confirmation e-mails, getting pestered with password or data format warnings *after* they finish entering their information, or bailing after being asked the same questions multiple ways? Find out why not enough people are filling out your web forms, and learn suggestions of A/B tests you can try to help encourage more people to interact.
In this session, we will explore the how the recent explosion of devices has disrupted the process of designing a website that we've crafted over the past decade.
When designers only have one instance of website (i.e., desktop) to design, the layout is uniform. The header, content area, sidebar, and footer all remain static. Furthermore, the elements are relatively uniform as well. Buttons, navigation, typography, and images are all basically the same across across the various pages. But if you are designing a responsive website – one whose look and feel adapts depending whether you're using a phone, laptop, or tablet – then these elements and especially the layout begin to diverge.
After this session, you should leave with the confidence to argue the importance of responsive design to your client or boss – and that the with the proper strategy, the extra effort and costs can be justified (and hopefully minimized).
The web standards gentleman: a matter of (evolving) standards)Chris Mills
This talk discusses standards evolution, HTML5 and CSS3 in detail. Starting with the history of HTML and CSS, it goes on to show how HTML5 and CSS3 were developed, why they were necessary, the problems they aim to solve, what the main new features are and why they are so useful, and how we can start using these features in the real world, right now. It also provides advice for the discerning web standards gentleman.
In this talk we will go over the basics of accessibility and building it into your website. We will cover accessibility principles (POUR: Perceivable, Operable, Understandable, Robust), using screen readers, and approaches to achieving accessibility guidelines.
Web accessibility refers to the inclusive practice of removing barriers that prevent interaction with, or access to, websites by people with disabilities. When your website is inaccessible, research shows you could be excluding up to 20 percent of your visitors from interacting with your content and functionality. If your university website is inaccessible, you could be preventing access to education, student services, and more.
When your website is accessible, everyone can consume your information freely. Visually-impaired users can visit your website using a screen reader. Those who can’t use a mouse can navigate your site using a keyboard or other input device.
While creating accessible websites involves every step, including design and content, the foundation for good accessibility starts with good markup. Join my workshop to learn more about accessibility and how to program a high-quality user experience that is inclusive and beneficial to all.
How to create accessible websites - WordCamp New YorkRachel Cherry
Web accessibility refers to the inclusive practice of removing barriers that prevent interaction with, or access to, websites by people with disabilities. When your website is inaccessible, research shows you could be excluding up to 20 percent of your visitors and customers. When your website is accessible, everyone can consume your information and interact with you and your services. Visually-impaired users can visit your website using a screen reader. Those who can’t use a mouse can navigate your site using a keyboard or other input device. Designing with accessibility in mind will also improve your SEO. Join my workshop to learn more about accessibility, the importance of universal design, and how to create a high-quality user experience that is inclusive and beneficial to all.
We can all pretend that we're helping others by making web sites and software accessible, but we are really making the experience better for our future selves. Learn some fundamentals of web and software accessibility and how it can benefit you (whether future you from aging or you after something else limits your abilities).
We'll review simple testing techniques, basic features and enhancements, coming trends, and where to get help. This isn't intended to be a deep dive, but more of an overall primer for those who aren't sure where to start nor how it helps them.
Insights:
- Broader context for how all users are or will be disabled, whether temporarily or permanently.
- Basic tests and best practices that can be integrated into development team workflows to make interfaces accessible.
- Introduction to standards and tools already available.
Accessibility is not disability Drupal South 2014Gareth Hall
Accessibility
The web is about information sharing. Why make it hard for users to access your content. Release your site from bad building practices, make it equal access for all and get SEO benefits for free.
Get through to the disabled community
By breaking down disability barriers you open up your content to a wider community currently 600,000+ in NZ.
There are definite dos and don’ts when it comes to building for the disabled. Learn what works for them.
WordPress Blogs 101 is a deck of notes for a training presentation for beginners. It's a hands-on presentation, and so this shouldn't be considered a "finished" product because many of the speaker notes won't mean anything to most users unless they're led through it by a trainer.
This is version 2 prepared for the annual Seton Hall University Student Technology Days series, aimed at student organizations' leaders who are interested in building an on-line presence for their group.
It covers the basics of obtaining and working with a blog in the University's self-hosted WordPress multisite environment, including examples, using the dashboard, managing comments, posts and pages, media embeds, options such as themes, widgets and menus.
Mistakes, misconceptions, over-indulgences, minutia, and generally silly aspects of modern web accessibility. Presented by Jared Smith
at Accessing Higher Ground Conference 2009.
Making your site printable: WordCamp Buffalo 2013Adrian Roselli
The push for responsive web design has helped web developers consider how the sites they develop can adapt to different devices, including sizes, screen resolutions, and even contexts. It should now be easier than ever to respond to a format that has existed since the start of the web – print. I’ll walk through the process for making your responsive sites respond to the format we most often forget.
Presentation for the Denver HTML5 Users Group on advanced HTML techniques.
Focuses, specifically, on semantic markup (POSH), new HTML5 structural elements, microformats, microdata and ARIA landmark roles
Developers: Why Care About the User? (2017)Andrew Malek
As developers, we deal with technologies, frameworks, and data, making it very easy to forget that what we create is meant for real people to use.
While designers and UI specialists should handle most decisions about how a product or service looks and feels, we should all be on the same page to make better solutions. Whether we are building an interface for a desktop website, mobile application, or chatbot, what are some basic design concepts that we as developers can pick up, allowing us to be on the same page with designers and product owners during product meetings and discussions?
Design and Development Techniques for Accessibility: WordCamp Tampa 2015Robert Jolly
I’ll explore basic web accessibility principles for web designers, developers, and site owners, then show how to turn seemingly daunting and confusing accessibility requirements into understandable, actionable tasks and techniques. The talk will cover some of the accessibility-specific WordPress plugins and themes available, as well as some quick, easy tests to integrate into design and development workflows.
Why Nobody Fills Out My Forms (Updated)Andrew Malek
Has your web form conversion rate hit a wall? Are users not receiving confirmation e-mails, getting pestered with password or data format warnings *after* they finish entering their information, or bailing after being asked the same questions multiple ways? Find out why not enough people are filling out your web forms, and learn suggestions of A/B tests you can try to help encourage more people to interact.
In this session, we will explore the how the recent explosion of devices has disrupted the process of designing a website that we've crafted over the past decade.
When designers only have one instance of website (i.e., desktop) to design, the layout is uniform. The header, content area, sidebar, and footer all remain static. Furthermore, the elements are relatively uniform as well. Buttons, navigation, typography, and images are all basically the same across across the various pages. But if you are designing a responsive website – one whose look and feel adapts depending whether you're using a phone, laptop, or tablet – then these elements and especially the layout begin to diverge.
After this session, you should leave with the confidence to argue the importance of responsive design to your client or boss – and that the with the proper strategy, the extra effort and costs can be justified (and hopefully minimized).
The web standards gentleman: a matter of (evolving) standards)Chris Mills
This talk discusses standards evolution, HTML5 and CSS3 in detail. Starting with the history of HTML and CSS, it goes on to show how HTML5 and CSS3 were developed, why they were necessary, the problems they aim to solve, what the main new features are and why they are so useful, and how we can start using these features in the real world, right now. It also provides advice for the discerning web standards gentleman.
In this talk we will go over the basics of accessibility and building it into your website. We will cover accessibility principles (POUR: Perceivable, Operable, Understandable, Robust), using screen readers, and approaches to achieving accessibility guidelines.
Web accessibility refers to the inclusive practice of removing barriers that prevent interaction with, or access to, websites by people with disabilities. When your website is inaccessible, research shows you could be excluding up to 20 percent of your visitors from interacting with your content and functionality. If your university website is inaccessible, you could be preventing access to education, student services, and more.
When your website is accessible, everyone can consume your information freely. Visually-impaired users can visit your website using a screen reader. Those who can’t use a mouse can navigate your site using a keyboard or other input device.
While creating accessible websites involves every step, including design and content, the foundation for good accessibility starts with good markup. Join my workshop to learn more about accessibility and how to program a high-quality user experience that is inclusive and beneficial to all.
How to create accessible websites - WordCamp New YorkRachel Cherry
Web accessibility refers to the inclusive practice of removing barriers that prevent interaction with, or access to, websites by people with disabilities. When your website is inaccessible, research shows you could be excluding up to 20 percent of your visitors and customers. When your website is accessible, everyone can consume your information and interact with you and your services. Visually-impaired users can visit your website using a screen reader. Those who can’t use a mouse can navigate your site using a keyboard or other input device. Designing with accessibility in mind will also improve your SEO. Join my workshop to learn more about accessibility, the importance of universal design, and how to create a high-quality user experience that is inclusive and beneficial to all.
Byg Tilgængeligt - Build Accessibly. My presentation for Community Day 2012 on 10 May 2012. Communityday.dk - for developers. Download file to get all the great tips and links in the notes.
10 Simple Rules for Making My Site AccessibleHelena Zubkow
From the basic principle that the web should be great for everyone, Chris Albrecht and Helena Zubkow team up to present an informative accessibility demo that will rock your world. The goal of this session is to introduce developers to web accessibility – what it is, why it’s important, and how to build and test sites to make them as accessible as possible.
This includes a demo of how to do things the right way and the wrong way, some great tools, and a walkthrough of basic standards for accessibility.
- Intro - What is web accessibility?
- Why does web accessibility matter?
- Accessibility fundamentals (web accessibility in practice / code demo)
- Web accessibility tools to assess and improve your projects
- Q&A session
The WAI-ARIA specification has been a shot in the arm for accessibility on the web. In this talk, I'll cover the basics of building accessible web applications without ARIA, and then how to add ARIA for some extra accessibility magic.
Making your website accessible for users with disabilities isn’t flashy, but it’s necessary. Websites built for universal access benefit all users, not just users with a disability. They’re also more SEO friendly, and are generally built to be more user friendly. From generating increased revenue, to providing better access to services, the benefits of developing accessible websites are real and measurable.
The State of Georgia recently completed an Accessible Platform initiative, reviewing the templates and themes for our enterprise Drupal platform for accessibility gaps, and launching rolling improvements to the platform over several months to meet WCAG 2.0 (Level AA) compliance levels.
Accessibility doesn’t have to be an additional step in the web development process. Out of this initiative came a number of lessons learned on how code can be written to be accessible from the beginning, to mitigate the need for such cleanup efforts in the future. Building websites with accessibility in mind from the start saves time and money in the long haul. By following best practices for front end development, accessibility can be a seamless, invisible step in the build process.
Presentation given to students on the Bachelor in Web Development degree at the Business Academy Southwest (https://www.easv.dk/en) in Esbjerg, Denmark on the 17th November 2017.
By making your site accessible, you'll get a better understanding of HTML semantics, an increased audience reach, Google will reward you... and you will become good looking, admired by your peers, and be the most interesting person in the room.
User Interface is King: Developing a Web App UIDave Olsen
An overview of what the user experience is, changes you can make to your applications, and tips for testing. Uses before and after examples from our content management system (CMS) slate to demonstrate the topics.
Neil Perlin - We're Going Mobile! Great! Are We Ready?LavaConConference
In this session attendees will learn:
Technical options for going mobile, including responsive design, converting traditional online help to an app, and creating a “true” app using RMAD (Rapid Mobile App Development) tools. The pros and cons of each approach and some of the tools available for creating each option.
Anticipated changes in content creation practices and workflows including the elimination of local formatting, adoption of a “mobile first” philosophy, rethinking the role of tables, and more.
How company issues like terminology standardization, strategic benefit, politics, and the development of metrics and standards can help or hinder a move to mobile.
We can all pretend that we’re helping others by making web sites and software accessible, but we are really making them better for our future selves. Learn some fundamentals of accessibility and how it can benefit you (whether future you from aging or you after something else limits your abilities). We’ll review simple testing techniques, basic features and enhancements, coming trends, and where to get help. This isn’t intended to be a deep dive, but more of an overall primer for those who aren’t sure where to start nor how it helps them.
DevDay 2013 - Building Startups and Minimum Viable ProductsBen Hall
DevDay (http://devday.pl),
20th of September 2013, Kraków
Video at http://www.youtube.com/watch?v=L4eTOvq2WmM&feature=c4-overview-vl&list=PLBMFXMTB7U74NdDghygvBaDcp67owVUUF
Similar to How Accessibility Made Me a Better Developer (20)
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
2. Agenda … or why are we here?
• Who
am
I?
• My
Journey
into
Accessibility
• Ten
“Day
1”
Accessibility
Aps
• QuesAons,
Comments,
Your
stories
3. About me
…or, who the H#LL is Billy Gregory?
I’m
a
front
end
developer
who’s
passionate
about
digital
accessibility.
I’ve
been
working
in
or
around
digital
accessibility
since
early
2008.
I
was
a
member
of
“Team
Canada”
in
the
Knowbility
Open
Air
CompeEEon
in
2012.
5. The Web is Evolving
More
and
more
demands
are
being
place
on
our
code.
We
can
no
longer
predict
or
control
how
a
user
accesses
our
code
Accessibility
is
becoming
the
law.
7. My Journey
If
I
can
do
it,
so
can
you.
As
developers,
you
already
possess
many
of
the
required
skills.
…or, if it worked for me…
8.
9. 2008
I
had
just
taken
a
job
as
a
front
end
developer
My
new
employer
had
been
working
with
the
TTC
(Toronto
Transit
Commission)
for
several
months
redesigning
their
site
11. Trial By Fire
Forced
to
learn
the
hard
way
For
the
first
7me
in
my
career
I
was
using
HTML
elements,
tags,
and
a@ributes
properly
Or
in
some
cases,
for
the
first
7me
at
all.
12. Own Your Code
… and not just the
stuff you did right!
The real lessons
are in the stuff
you did wrong
14. My moment of clarity
My
work
took
on
a
whole
new
meaning
to
me…
• I
realized
that
I
was
building
a
tool,
not
a
sta7c
page
• My
code
had
a
life
of
it’s
own,
it
wasn’t
there
to
be
READ,
it
was
there
to
be
USED
Through Clarity Came Focus
I
no7ced
my
skills
as
a
developer
had
evolved
• I
was
carefully
choosing
how
and
why
I
was
coding
every
element
on
the
page,
knowing
it
was
going
to
be
tested
and
I
needed
to
defend
my
choices
17. I tried to speak to the creative department, but they didn’t
like me questioning their designs
Yo dawg, I heard you like
the color grey…
18. The UX team didn’t take too kindly to me suggesting
alternative approaches
Yo dawg, I heard you like
modals…
So I put a modal…
In your
Modal!
19. It was tough to get other clients interested in Accessibility
The most common excuses
were that accessibility was
“too hard” or “too costly”
so it wasn’t included in the
documentation.
But, like most devs….
But
isn’t
Accessibility
EXPENSIVE?!...
But isn’t
Accessibility
EXPEN$IVE ?!...
21. DIY a11y
I took it on myself to make my work more accessible
I knew the heart of accessible code, was semantic HTML
I read the WCAG document top to bottom
Then I read it again. And again.
Then I had someone smarter than me translate it so I
could finally understand.
And again.
I reached out to the accessibility community.
#a11y on twitter will yield results.
22. When good enough stopped
being “Good Enough”
I approached my development process a little differently
• I spent more time planning my code up front, which lead to
less time fixing it later
• I always assumed at least SOME level of accessibility
• I stopped LOOKING at the designs I was building from, and
learned to READ them
28. “You kids today….”
Accessibility
has
come
a
long
way
since
2008.
JQuery
UI
and
other
libraries
have
taken
the
“baked
in”
approach
and
oWen
include
keyboard
support,
WAI-‐ARIA
and
other
common
accessibility
requirements.
There
are
a
lot
more
tools
available
to
assist
in
Accessibility
tesAng.
31. My Top Ten
Over
7me,
I
kept
adding
to
the
list
of
things
I
could
"get
away"
with
or
had
complete
control
over
1) Language
2) Seman7c
mark-‐up
3) Code
Order
/
Tab
Order
4) ARIA
Landmark
Roles
5) Focus
6) Keyboard
control
7) Skip
Links
8) Form
labels
&
fieldsets
9) Alt
text
10) “Hidden”
text
33. Semantic Mark-up
Make
sure
your
pages
are
Atled
appropriately
and
meaningfully.
• it’s
the
first
thing
a
screen
reader
will
read
Use
elements
for
their
intended
purpose.
• Use
buons
as
buons,
lists
as
lists,
tables
as
tables,
etc.
2
USE
HEADINGS!!!
37. Code Order vs Tab Order
Code
Order:
The
order
the
elements
are
marked-‐up
on
the
page
Tab
Order:
The
order
in
which
the
elements
on
the
page
receive
focus.
3
38. Code Order vs Tab Order
Element Element Element Element
This…
Element Element Element Element
NOT This…
3
39. ARIA Landmark Roles
WAI-‐ARIA
Web
Accessibility
IniEaEve
Accessible
Rich
Internet
ApplicaEons
• ARIA
meant
to
help
bridge
the
semanEc
gap
between
screen
readers
and
HTML5
• Landmark
Roles
are
just
the
Ep
of
the
iceberg.
• Screen
reader
users
can
use
ARIA
landmarks
to
help
navigate
the
page
• Provides
further
semanEc
meaning
to
page
elements
4
42. Focus
In
your
CSS,
for
every
:hover
pseudo
element,
use
the
:focus
pseudo
element
• :hover
is
bound
to
the
mouse.
• keyboards
don’t
hover
• Don’t
override
the
outline
• Use
more
than
color
alone
to
show
the
focus.
text-‐decoraEon:underline;
is
best.
5
43. Focus
Make
sure
that
when
new
elements
are
opened,
the
focus
shi_s
accordingly.
For
instance,
when
a
user
opens
• Modals
• Tool
Eps
Be
careful
when
forcing
focus
on
an
element.
• The
user
might
not
be
expecEng
this.
• Error
messages
• Search
form
on
a
new
page
5
45. Keyboard Control
POP
QUIZ!…
or
trick
ques7on
QuesEon:
Who
among
your
users
might
not
be
using
a
mouse?
Answer:
Anyone!
…It’s
not
up
to
us
to
decide
that
;)
Example:
Have
you
ever
tabbed
through
a
form
when
you’re
filling
it
out?
6
47. Keyboard Control
Test
that
your
work
can
be
navigated
by
keyboard
alone.
Look
out
for
“keyboard
traps”
–
make
sure
you
don’t
open
something
that
would
result
in
your
cursor
/
focus
being
behind
an
element
like
a
modal
window.
*I
totally
stole
the
Akbar
thing
from
George
Zamfir
-‐
@good_wally
6
48. Skip Links
• Skip
links
provide
a
means
for
keyboard
users
as
well
as
screen
reader
users
a
way
to
skip
repeated
blocks
of
content
• Skip
links
can
be
used
to
skip
OVER
or
skip
TO
parts
of
a
page.
• Be
careful
to
move
keyboard
focus
and
not
just
visual
focus
when
adding
skip
links.
7
49.
Skip Links
<main
id=“main-‐content”
role=“main”
… <div
id=“right-‐col”
role=“complementary”…
<footer
id=“footer”
role=“contenAnfo”
…
<a
href="#main-‐content">skip
to
main
content</a>
<ul>
<!–
this
is
a
repeated
block
of
content
-‐-‐>
…
7
51. Alternative Text
The
“alt”
aeribute
contains
text
that
describes
an
image
alt=“DescripEve
text
would
go
in
here”
9
TSA
To
Introduce
New
Security
Measures.
BAD
alt
text:
alt=“TSA
officer”
GOOD
alt
text:
alt=“A
TSA
Agent
looking
into
the
camera
while
snapping
on
a
rubber
glove.”
52. “Hidden” Text
One
of
the
best
pracEces
for
“hiding”
text
off
screen
is
to
use
css
to
visually
remove
text
from
the
code
order
while
sEll
keeping
it
visible
to
screen
readers.
10