Sign In

Kae Anderson, CPACC

IAAP Certified Digital Accessibility Specialist | Inclusive Design | WCAG | I help companies make their sites work well for as many people as possible

Kae Anderson, CPACC, is a talented professional with a background in anthropology, front-end development, and UX design, specializing in digital accessibility.

With a passion for creating positive digital experiences, Kae has leveraged her empathy and technical skills to ensure that digital products are usable by everyone.

Through roles at various organizations, such as The Reserves Network, Kae has honed her expertise as a Digital Accessibility Specialist, focusing on inclusive design and product usability.

Having completed a Bachelor's degree in Anthropology at the University of Northern Iowa and certifications in Front-End Development and UX Design, Kae brings a diverse skill set to her work.

She has experience working with both small entrepreneurs and large corporations to address accessibility issues at the design level, where she believes most problems can be effectively resolved.

In addition to her professional pursuits, Kae is an avid traveler, book enthusiast, and TV show aficionado, with a keen interest in learning and problem-solving.

With a portfolio showcasing her work and a desire to continue making a positive impact in the field of digital accessibility, Kae is actively seeking new opportunities to contribute her expertise.

Kae's unique blend of skills, experience, and personal interests make her a valuable asset in creating inclusive and user-friendly digital experiences for all.

Highlights

Aug 28 · linkedin

There are no silly accessibility questions - field labels version!

You might have heard an accessibility person say that form fields should have labels. And if you’re a designer you might have thought forms looked better without them. So I’m going to talk about why they matter!

Some of you will have heard these things before, but I’m going to say them again just in case. People rely on form fields to help them fill out a form. And if you’re creating a form then (hopefully!) your goal is to make it easy for people to fill out.

Everyone benefits from having field labels. They give us clarity about what we’re doing and help us understand what information to put in the field. When fields have placeholders they give some of us the context for the field at first. But when we start to type in it then the information goes away.

If the form has more than a couple fields then it takes more brain capacity to fill out. The longer something is, the more effort it takes. And if you get distracted in the middle of a field (maybe your dog wants to play or you get a notification) then you have to reorient yourself when you get back to the form. Having labels helps people figure out where they are faster when they come back.

And people who can’t see the form rely on the labels to let them know what the field is for. Some screen reader / browser combinations will announce the placeholder text when someone first gets to a field. But once someone types in it then that placeholder goes away and probably won’t be announced again. The labels and help text should be actual text to make sure everyone can access it each time they go to the field.

The labels should be connected to the fields in the code with an ID. That will make it so people understand that the field goes with that specific label and not something else around it.

Labels help people fill out forms more quickly and accurately, and this is definitely the type of thing where little changes make a big difference.

Here are some resources if you want to get better at making accessible forms!

  • A beginner’s guide to form accessibility: the 5 things accessible forms need and how to fix common mistakes by Whitney E Lewis (article) -  https://lnkd.in/eRsTnNkb

  • Creating Accessible Forms from WebAIM (article) -  https://lnkd.in/eUtk8Wja

  • Form missing accessible label screen reader example from Pope Tech (2 minute video) - https://lnkd.in/eedqReea

  • Forms Tutorial by W3C (multi-page article) - https://lnkd.in/eq-BQ6s8

  • A Guide To Accessible Form Validation from Smashing Magazine (article) - https://lnkd.in/emDwHTz2

  • The anatomy of accessible forms: Best practices by Uday Shetty (article) - https://lnkd.in/e7vtuxDz

#Accessibility #A11y #AccessibilityMatters #UserExperience #AccessibleForms

Aug 21 · linkedin

There are no silly accessibility questions - carousels version!

You might have heard an accessibility person go on an angry rant about carousels. Most of us aren’t big fans, and this post gives you a quick introduction to why we don’t like them!

Carousels are often used as a way to improve the experience of people working at the company. Maybe someone on one team thinks their stuff is the most important. And they’re trying to compete with people on other teams. They all want the best spot at the top of the page.

So a carousel becomes the way to have several things at the top of the page. Everyone wins, right? Probably not!

Because carousels are often used to satisfy people at a company, they’re not really used to give people what they’re looking for. They can be a big ad for something people aren’t looking for, instead of directing people to the things they want.

That means most people will scroll past them. And it also means that some people will get stuck in them while they’re trying to get past them.

They can be a little tricky to make accessible. Someone who uses a keyboard might not be able to get past them without tabbing a whole bunch of times. And someone with ADHD might get distracted and forget what they came for. And someone using a screen reader might hear a message like "left arrow white circle white circle white circle white circle right arrow" instead of something useful!

If you actually want to show people things at once, there are other ways to do that.

You could find out what the most visited parts of your site are and have them in cards near the top of the page. You could have sections of the home page with useful headings that help people know where to go. And you could make sure the navigation includes easy ways to get to the things people are searching for.

And if you need to use a carousel please make it accessible for everyone! That means making sure:

  • everything gets announced correctly by a screen reader
  • it works with a keyboard
  • the navigation has high color contrast
  • there are ways to skip over it
  • it doesn’t auto rotate

If you have thoughts about carousels feel free to share in the comments!

Here are some resources if you want to learn more:

  • A Step-By-Step Guide To Building Accessible Carousels by Sonja Weckenmann, WAS (article) -  https://lnkd.in/erp2Yd74

  • Carousels by Brad Frost (post) - https://lnkd.in/e_dCnJt8

  • Should I Use A Carousel by Jared Smith (site) -  https://lnkd.in/e9U4QPtV

  • Why carousels don't work by Anton Stén (article) - https://lnkd.in/eadS-23r

  • Why Image Carousels Are Almost Always A Bad Idea by Jon MacDonald (article) - https://lnkd.in/eBbKQK8r

#Accessibility #A11y #AccessibilityMatters #UserExperience

Kae Anderson, CPACC
Add to my network

Location

Knoxville, Tennessee, United States