# data[].attributes.blurb.html
Web accessibility is easier to achieve and maintain with the right tools. Some are useful to help you make the right choices, others can find certain problems automatically, often even before your product or page ships. In this talk, Hidde will tell us all about the tools to use to improve web accessibility.

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv TOOLKIT FOR ACCESSIBILITY Hidde de Vries, Stay Curious Online, 18 January

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv Hi, I’m Hidde front-end developer + accessibility specialist + blogger (hidde.blog) Like & Subscribe

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv accessibility, a brief intro

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv Web accessibility to ensure people with disabilities can use your site/app

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv Web accessibility to ensure people with disabilities can buy your product

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv Web accessibility to ensure people with disabilities can use your service

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv 1-2% 4% blind/visually impaired colour blind ` OOGVERENIGING (1 IN 12 MEN, 1 IN 250 WOMEN) This concerns a lot of people 9% 15% deaf/heard of hearing low numerate / low literate HOORWIJZER ALGEMENE REKENKAMER

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv A lot of people - zoom in web pages use high contrast modes have screenreader need audio/video transcribed do not use a mouse use voice recognition prefer reduced motion W3C/WAI, How People with Disabilities Use the Web https://www.w3.org/WAI/people-use-web/tools-techniques

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv What to test?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv a11y standards + Best practices + (You’ll need all of the above) User testing

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv a11y standards + Best practices + (You’ll need all of the above) User testing

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv WCAG 2.1 w3.org/TR/WCAG21 WCAG: internationally implemented guidelines that provide a baseline for testing web accessibility

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv WCAG 2.1 w3.org/TR/WCAG21 Principles Guidelines Success Criteria

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv WCAG 2.1 w3.org/TR/WCAG21 Principles Guidelines Success Criteria (three levels)

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv WCAG 2.1 w3.org/TR/WCAG21 Principles Guidelines Success Criteria (three levels) 50 criteria at Level A + AA

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv quick reference w3.org/WAI/WCAG21/quickref/

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv this is wcag thisiswcag.com

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv 50 Success Criteria - about issues people with - disabilities face testable (some by humans, some by machines)

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv a11y standards + Best practices + (You’ll need all of the above) User testing

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv best practices Be careful about what you adopt, look for well-tested patterns

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv best practices Be careful about what you adopt, look for well-tested patterns https://github.com/scottaohara/accessible_components https://design-system.service.gov.uk

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv a11y standards + Best practices + (You’ll need all of the above) User testing

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv testing with users - test with a range of di ferent users: one user doesn’t speak for all f W3C, Involving Users in Web Projects for Better, Easier Accessibility

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv testing with users - test with a range of di ferent users: - one user doesn’t speak for all allow for plenty of time f Frozen Rockets, Things to consider when doing usability testing with disabled people

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv testing with users - test with a range of di ferent users: - one user doesn’t speak for all allow for plenty of time test only when you’re ready f Frozen Rockets, Things to consider when doing usability testing with disabled people

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv testing with users - test with a range of di ferent users: - one user doesn’t speak for all allow for plenty of time test only when you’re ready ensure your lab is accessible f Frozen Rockets, Things to consider when doing usability testing with disabled people

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv How to test?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual vs automated You will need both!

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual vs automated - how many issues? - how many Success Criteria? Deque, The automated accessibility coverage report

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual vs automated <img src=”50-percent-off” /> 50% off

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual vs automated <img src=”50-percent-off” /> Problem: there is no alt (machines can establish this) 50% off

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual vs automated <img src=”50-percent-off” alt=”25% off”/> f Problem: the alt does not re lect what image says (would require machine that can do OCR, most accessibility testing tools don’t) 50% off

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual vs automated <img src=”50-percent-off” alt=”Sale, 50% off”/> Sale! 50% off Problem: the alt is redundant (hard for machines to decide)

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv Manual testing Tests that most people on the team can do periodically

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: use of color Is it not the only way? Leverage agile frameworks to provide a robust synopsis for high level overviews. Iterative approaches to corporate strategy foster collaborative thinking to further the overall value proposition. Organically grow the holistic world view of disruptive innovation via workplace diversity and empowerment. Bring to the table win-win survival strategies to ensure proactive domination. At the end of the day, going forward, a new normal that has evolved from generation X is on the runway heading towards a streamlined cloud solution. User generated content in real-time will have multiple touchpoints for offshoring. Capitalize on low hanging fruit to identify a ballpark value added activity to beta test. Override the digital divide with additional clickthroughs from DevOps. Nanotechnology immersion along the information highway will close the loop on focusing solely on the bottom line.

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: use of color Is it not the only way? Leverage agile frameworks to provide a robust synopsis for high level overviews. Iterative approaches to corporate strategy foster collaborative thinking to further the overall value proposition. Organically grow the holistic world view of disruptive innovation via workplace diversity and empowerment. Bring to the table win-win survival strategies to ensure proactive domination. At the end of the day, going forward, a new normal that has evolved from generation X is on the runway heading towards a streamlined cloud solution. User generated content in real-time will have multiple touchpoints for offshoring. Capitalize on low hanging fruit to identify a ballpark value added activity to beta test. Override the digital divide with additional clickthroughs from DevOps. Nanotechnology immersion along the information highway will close the loop on focusing solely on the bottom line.

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: page title Is there a title? Does it describe the page?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: keyboard Can I get to all interactive elements?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv <select> <details> <input> <textarea> interactive elements <button> <a>

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: keyboard Can I do everything with just the keyboard?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: keyboard Can I see where I am? Leverage agile frameworks to provide a robust synopsis for high level overviews. Iterative approaches to corporate strategy foster collaborative thinking to further the overall value proposition. Organically grow the holistic world view of disruptive innovation via workplace diversity and empowerment. Bring to the table win-win survival strategies to ensure proactive domination. At the end of the day, going forward, a new normal that has evolved from generation X is on the runway heading towards a streamlined cloud solution. User generated content in real-time will have multiple touchpoints for offshoring.

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: keyboard Can I get to all interactive elements? Can I see where I am? Does the order make sense? Are you never trapped? Is there anything with tabindex > 0? Is there nothing in tab order that shouldn’t be there?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: images Do all images have an alt attribute? Is the alt appropriate? ft

le empty when it should be - contains everything that’s in the image - imagine image fails; is it a good replacement?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: images Is the image the only thing in a link? The alt is now the link’s name.

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: video Are captions available and correct? Is everything that’s visible also in audio?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: audio Is everything in the audio available as text?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv “[podcasts] really boomed during the rst months of lockdown. As a deaf person, almost all of these podcasts are inaccessible to me because they don’t have transcripts or I have to wait weeks before they are available. ” fi Darice de Cuba, The Podcast Transcript Experimentation

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: headings Do headings describe the section they’re a heading of?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: headings Is everything that looks like a heading marked up with a hx tag?
<div class=”text-5xl font-medium text-green-600”>Our products</div>

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: zoom When you zoom in (up to 400%), does everything still work? text should not overlap text should not be cut o f all controls should be usable no horizontal and vertical scrolling f

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: color modes Can everything be used with Windows High Contrast Mode on?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv manual: screenreaders Use the website with a screenreader, but

if you’re not a regular screenreader - user, add a pinch of salt, don’t jump to conclusions keep common browser/screenreader combinations in mind “it works” also depends on user skill, not all users are tech savvy

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv semi-automated testing Tests that remove some of the manual work so you can make decisions quicker

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv Firefox dev tools - Visualise tabbing order

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv Firefox dev tools - “no false positives” - integrates with existing tests - runs in major browsers and command line

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv Firefox dev tools - Visualise tabbing order - Test Contrast, Keyboard and Text Labels on a page

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv fi Firefox dev tools - Visualise tabbing order - Test Contrast, Keyboard and Text Labels on a page - Simulate colour vision de ciencies / contrast loss

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv html validator validator.nu

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv wave wave.webaim.org

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv automated testing Tests you can run against a website automatically (eg in CI/CD)

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv automated testing Tests you can run against a website automatically (eg in CI/CD)

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv automated testing Most of these integrate with your CI/CD and can export to interoperable data formats

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv automated testing

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv When to test?

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv It’s easier when you do it earlier

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv It’s easier when you do it earlier Eg, pick a CMS that supports accessibility

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv It’s easier when you do it earlier Eg, pick a CMS that supports accessibility, check designs before building

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv It’s easier when you do it earlier Eg, pick a CMS that supports accessibility, check designs before building, check builds before merging

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv It’s easier when you do it earlier Eg, pick a CMS that supports accessibility, check designs before building, check builds before merging, check merged code before shipping, etc

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv Often & early Once in a while Manual checks that most can do + automated checks WCAG audits, user tests that include users with disabilities

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv What? How? Browser tools So tware plugins f When? f Accessibility standards Best practices User testing CLI tools Formal audits O ten, during development Periodically, with audits and user tests

# data[].attributes.slidedeck.data[].slides[].desc.html
@hdv thank you. Contact/resources talks.hiddedevries.nl @hdv or hidde@hiddedevries.nl Typefaces Bungee by David Jonathan Ross (DJR) Rasa by Anna Giedryś, David Březina (Rosetta)

# data[].attributes.resources.data[].title
Quick Reference version of WCAG (filtered to 2.1)

# data[].attributes.resources.data[].title
This is WCAG (interpretation of WCAG focused on using plain language)

# data[].attributes.resources.data[].title
Involving users in web projects for better accessibility - W3C WAI

# data[].attributes.resources.data[].title
How people with disabilities use the web - tools and techniqeus - W3C WAI

# data[].attributes.resources.data[].title
Things to consider when doing usability testing with disabled people   - Frozen Rockets

# data[].attributes.resources.data[].title
The automated accessibility coverage report - Deque

# data[].attributes.resources.data[].title
The Podcast Transcript Experimentation - Darice de Cuba

# data[].attributes.resources.data[].desc.html
In which the GOV.UK folks compare different accessibility testing engines