Kate Kalcevich (she)

Biohacker, weston price diet follower, weight lifter, cat whisperer, hearing aid wearer. Head of Accessibility Innovation @makeitfable. Views my own.

[Kate Kalcevich (she) @katekalcevich]

The accessibility community has become less and less active on X and I'm finding the LinkedIn accessibility community very rewarding to be a part of. I'm pausing my X updates, but you can find me on LinkedIn: https://t.co/VtADBbg6Is

[Kate Kalcevich (she) @katekalcevich]

A step-by-step guide to creating accessible comboboxes from @PopeTechA11y https://t.co/8fVsqa0or9

[Kate Kalcevich (she) @katekalcevich]

contrast-color() is a good thing, but also solving the problem at the wrong layer by @ericwbailey (in short, browsers need better a11y supports)

https://t.co/xlMT9k2fWV

[Kate Kalcevich (she) @katekalcevich]

A case study on ensuring enlarged text fit nicely within the UI and the team's workflow by Steven Basset at AirBnB https://t.co/5Oxeuz6Bza

[Kate Kalcevich (she) @katekalcevich]

Choosing the right mobile keyboard for user input impacts usability and accessibility! Ksenia Toloknova dives deep into all the options in @uxdesigncc https://t.co/6kIoHHmhkT

[Kate Kalcevich (she) @katekalcevich]

A 3D model accessibility exploration by @svinkle https://t.co/bSXNH85xdC

[Kate Kalcevich (she) @katekalcevich]

Systemic changes that would help accessibility improvements accelerate by @accessarmada https://t.co/7O9hT2xbOy

[Kate Kalcevich (she) @katekalcevich]

When does an element need to be keyboard focusable? This article explains the use cases for tabindex="0"

[Kate Kalcevich (she) @katekalcevich]

A guide to screen reader pronunciation of special characters: https://t.co/RdRhw39yjx Note that you don't need to override pronunciation. Instead, rely on user feedback and testing to discover what makes sense.

[Kate Kalcevich (she) @katekalcevich]

Here's the link: https://t.co/5jehxjb6fn

[Kate Kalcevich (she) @katekalcevich]

@CerovacBogdan tested the effect of using role="application" on mobile screen readers. He also explains the effect on desktop screen readers, if you're not familiar with the role.

[Kate Kalcevich (she) @katekalcevich]

How to test for new WCAG 2.2 guidelines for authentication level AA (CAPTCHAS) https://t.co/h1wAMnIJMT

[Kate Kalcevich (she) @katekalcevich]

Use popovers and get aria-expanded and aria-details built-in! Details here: https://t.co/KnpOB6fnrj

[Kate Kalcevich (she) @katekalcevich]

@dav_idcox wrote a fantastic post about looking for clues that content might not meet WCAG 2.2 https://t.co/28UG62t6Y2

[Kate Kalcevich (she) @katekalcevich]

A great story from @webcraftsman about the journey to becoming an accessibility champion https://t.co/ZHLMJ83WLE

[Kate Kalcevich (she) @katekalcevich]

Using HTML elements with accessibility built-in is an easy way to avoid barriers (most of the time). Here are some tips and tricks for using <dialog> from @chriscoyier

https://t.co/2ZCfHkYCo2

[Kate Kalcevich (she) @katekalcevich]

What's proposed for ARIA 1.3? @abbott567 reviews the new draft: https://t.co/PiDi3L279q

[Kate Kalcevich (she) @katekalcevich]

Darin Senneff tested a few ways to announce dynamic changes to a button label and found lots of inconsistencies with screen reader output: https://t.co/IsW84BCkjM

[Kate Kalcevich (she) @katekalcevich]

Doug Abrams explains how to test for reflow issues on small screens and more importantly how to design with reflow in mind https://t.co/5vVPNMgIKB

[Kate Kalcevich (she) @katekalcevich]

An exploration on how to adapt video content for user preferences by @aardrian https://t.co/mdGUCVbZZV