1 of 35

You Say You’re My A11y, But Then UX Me

(You Say You're my Ally, But Then You Ex Me)​

By Saša Stojić-Ito, LACCD

2 of 35

Facilitator​

  • M.Ed. Health & Kinesiology, M.S. Instructional Design and Technology​
  • Certificates: IAAP CPACC (International Association of Accessibility Professionals Certified Professional in Accessibility Core Competencies), ATACP​ (Assistive Technologies Applications)
  • Online Multimedia Specialist, Instructional Designer, and Accessibility Consultant ​
  • Specializing in inclusive design, digital accessibility, and UDL in higher education

3 of 35

Outcomes

  • Differentiate between accessibility compliance and inclusive, usable design in the context of higher education.
  • Evaluate course content and digital tools through the lens of both accessibility and user experience.
  • Identify practical steps faculty and staff can take to democratize accessibility, making it a shared responsibility rather than a compliance task.

4 of 35

You Say You’re My A11y, But Then UX Me

A11y=Accessibility

Numeronym.

Number 11 stands for 11 letters between the letters A and Y.

UX=User Experience

Create products that are useful, easy to use, and provide a positive experience for the end user.

5 of 35

Have you ever created something

accessible but got

flooded with

confused questions?

6 of 35

Accessibility ≠ Usability

7 of 35

Technically Accessible… (1 of 3)

Alt Text Present

<alt =”image”>

<alt=” graphic1.jpg”

8 of 35

Technically Accessible… (2 of 3)

Color Use

Color is only indicator

9 of 35

Technically Accessible… (3 of 3)

Headings

Skipping Hierarchy

10 of 35

Meet WCAG

Web Content Accessibility Guidelines (WCAG) is set of international standards for making content more accessible to people with a wide range of disabilities.

  • Developed by World Wide Web Consortium (W3C)
  • POUR guidelines apply across any platform and content development/creation

11 of 35

P for Perceivable

Information must be presented in ways users can access with their senses (see it, hear it, feel it).

12 of 35

O for Operable

Navigation and actions must be possible for everyone—whether using a mouse, keyboard, switch device, or voice commands.

13 of 35

U for Understandable

Content should be clear and predictable. Users shouldn’t need a decoder ring to figure out your course page.

14 of 35

R for Robust

Content should work with assistive technologies now and adapt to future tech.

15 of 35

POUR

P for Perceivable: Information must be presented in ways users can access with their senses (see it, hear it, feel it).

O for Operable: Navigation and actions must be possible for everyone—whether using a mouse, keyboard, switch device, or voice commands.

U for Understandable: Content should be clear and predictable. Users shouldn’t need a decoder ring to figure out your course page.

R for Robust: Content should work with assistive technologies now and adapt to future tech.

16 of 35

How do you practice POUR?

17 of 35

When UX Fails, A11y Falls With It​

18 of 35

UX Crisis

  • UX issues can create real-world consequences: confusion, frustration, course dropout
  • The cost of poor UX is higher for students using assistive tech or learning with cognitive differences

19 of 35

Student Experience (1 of 2)

“I couldn’t figure out how to submit my assignment. I just gave up.”

“The instructions were long, dense, and buried in a wall of text.”

20 of 35

Student Experience (2 of 2)

“The contrast hurt my eyes, and I have no idea where to start.”

21 of 35

What is one frustrating moment ​you’ve had with A11y & UX?

22 of 35

A11y is Everyone's Job​

23 of 35

What We Can Do

Faculty

Use heading styles, write clear instructions, label links

Admins

Fund captioning tools, training, education

DSPS

Provide Support, but not fix everything post-hoc

24 of 35

A11y Culture

25 of 35

From Checklist to Care​

26 of 35

Usability is not a luxury add-on. It’s what turns access into actual learning.

27 of 35

Building Inclusively

Chunking

Clear Labels

Logical Reading Order

Descriptive Links

Heading Hierarchy

Accessible Names

White Spaces

No Color-Only

Keyboard Navigable

Plain Instructions

28 of 35

Design for All

  • Inclusive design help everyone
  • Supports diverse learners needs
  • Removes barriers
  • Allows independence

29 of 35

A11y vs. A11y & UX

30 of 35

Small Habits, Big Shifts​

31 of 35

Key Ideas

Progress Over Perfection

  • Accessibility grows through repetition, not perfection.

Scaffolding Learning

  • Pick a single inclusive design habit and stick with it. Then add one more.

32 of 35

A11y Is Not A Feature​

33 of 35

A11y & UX

When UX fails, accessibility suffers. And when we silo accessibility, everyone loses.

Let’s stop UX-ing our allies and start building content worth trusting.

34 of 35

Q&A

Thank you Everyone for the work that you do, for the questions you ask, for pointing out what work needs to be done, and for not stopping your advocacy…

Accessibility isn’t a feature, it is a foundation!

35 of 35

Contact Information

Saša Stojić-Ito

Faculty email: stojics@laccd.edu

Personal email: sasa.stojic.ID@gmail.com