<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/accessibility-preference-settings-information-architecture-and-internalized-ableism-2s0t0sylf" -->

---
title: Accessibility preference settings, information...
description: Exploring how internalized ableism keeps people from engaging with accessibility settings, using macOS's Accessibility system preferences as an example. Many...
canonical: https://daily.dev/posts/accessibility-preference-settings-information-architecture-and-internalized-ableism-2s0t0sylf
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Accessibility preference settings, information architecture, and internalized ableism | daily.dev
og:description: Exploring how internalized ableism keeps people from engaging with accessibility settings, using macOS's Accessibility system preferences as an example. Many...
og:url: https://daily.dev/posts/accessibility-preference-settings-information-architecture-and-internalized-ableism-2s0t0sylf
og:image: https://api.daily.dev/og/posts/2s0t0SYlf.png
og:image:alt: Accessibility preference settings, information architecture, and internalized ableism
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Accessibility preference settings, information architecture, and internalized ableism

**[Eric Bailey](https://daily.dev/sources/ericwbailey)** · 4 min read · 0 upvotes · 0 comments

## Summary

Exploring how internalized ableism keeps people from engaging with accessibility settings, using macOS's Accessibility system preferences as an example. Many people don't identify as disabled, so they overlook features like magnification, color filters, or white noise that could help them. The piece discusses how information architecture and categorization choices—like Apple placing 'always show scrollbars' under Appearance rather than Accessibility—affect discoverability, and points to WCAG Success Criterion 2.4.5 (Multiple Ways) as guidance for providing alternate paths like search. It closes with practical suggestions for both people who build digital products and those who use them.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://ericwbailey.website/published/accessibility-preference-settings-information-architecture-and-internalized-ableism>

## Questions this post answers

### What does WCAG Success Criterion 2.4.5 Multiple Ways require for accessibility?

Success Criterion 2.4.5 (Multiple Ways) encourages providing more than one method for people to locate content or functionality, such as a search feature alongside categorized navigation. Applied to operating system preferences, this means including a search input so people can find accessibility-related settings even if they're not categorized under an obvious label.

_daily.dev surfaces practical accessibility standards for developers weighing how to structure settings and navigation._

### Why do people avoid using accessibility settings even when those settings would help them?

Internalized ableism causes many people to avoid accessibility settings because they don't identify as disabled, so they assume the accessibility area doesn't apply to them. This is why some internal training talks intentionally avoid mentioning screen readers or VoiceOver, focusing instead on universally useful features like white noise, color filters, and magnification to shift that mindset.

_developers designing settings menus can use daily.dev to explore approaches for improving accessibility discoverability._

## Similar posts on daily.dev

- [If It's Not Accessible, It's Not Design](https://daily.dev/posts/if-it-s-not-accessible-it-s-not-design-eyj1yetec) · DEV · 3 upvotes · 0 comments
- [You Can't Opt-Out of Accessibility](https://daily.dev/posts/you-can-t-opt-out-of-accessibility-qatebjjev) · Lobsters · 25 upvotes · 9 comments
- [Enhancing Web Design: Recognizing Accessibility Issues Now](https://daily.dev/posts/enhancing-web-design-recognizing-accessibility-issues-now-ujieme4gp) · A List Apart · 0 upvotes · 0 comments
- [Why Accessibility Is An Operational Capability, Not A Feature — Smashing Magazine](https://daily.dev/posts/why-accessibility-is-an-operational-capability-not-a-feature-smashing-magazine-vush3kmuc) · Smashing Magazine · 5 upvotes · 0 comments
- [Hidden Web Accessibility Issues Most Designers Miss in 2026](https://daily.dev/posts/hidden-web-accessibility-issues-most-designers-miss-in-2026-gm6w0zamx) · Netguru · 0 upvotes · 0 comments

---

Tags: [#accessibility](https://daily.dev/tags/accessibility), [#mac](https://daily.dev/tags/mac), [#ux](https://daily.dev/tags/ux)

[View this post on daily.dev](https://daily.dev/posts/accessibility-preference-settings-information-architecture-and-internalized-ableism-2s0t0sylf)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Accessibility preference settings, information architecture, and internalized ableism","url":"https://daily.dev/posts/accessibility-preference-settings-information-architecture-and-internalized-ableism-2s0t0sylf","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/accessibility-preference-settings-information-architecture-and-internalized-ableism-2s0t0sylf"},"datePublished":"2026-09-20T07:44:12.812Z","dateModified":"2026-10-15T02:25:08.341Z","description":"Exploring how internalized ableism keeps people from engaging with accessibility settings, using macOS's Accessibility system preferences as an example. Many...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a182eac2497233305cb365c0c4ac0ffc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a182eac2497233305cb365c0c4ac0ffc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Eric Bailey","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Eric Bailey","logo":"https://media.daily.dev/image/upload/s--r1vwe6z1--/f_auto,q_auto/v1789890198/logos/ericwbailey?_a=BAMAMicg0","url":"https://daily.dev/sources/ericwbailey"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/accessibility-preference-settings-information-architecture-and-internalized-ableism-2s0t0sylf","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"accessibility,mac,ux","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Eric Bailey","item":"https://daily.dev/sources/ericwbailey"},{"@type":"ListItem","position":3,"name":"Accessibility preference settings, information architecture, and internalized ableism"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/accessibility-preference-settings-information-architecture-and-internalized-ableism-2s0t0sylf#faq","mainEntity":[{"@type":"Question","name":"What does WCAG Success Criterion 2.4.5 Multiple Ways require for accessibility?","acceptedAnswer":{"@type":"Answer","text":"Success Criterion 2.4.5 (Multiple Ways) encourages providing more than one method for people to locate content or functionality, such as a search feature alongside categorized navigation. Applied to operating system preferences, this means including a search input so people can find accessibility-related settings even if they're not categorized under an obvious label. daily.dev surfaces practical accessibility standards for developers weighing how to structure settings and navigation."}},{"@type":"Question","name":"Why do people avoid using accessibility settings even when those settings would help them?","acceptedAnswer":{"@type":"Answer","text":"Internalized ableism causes many people to avoid accessibility settings because they don't identify as disabled, so they assume the accessibility area doesn't apply to them. This is why some internal training talks intentionally avoid mentioning screen readers or VoiceOver, focusing instead on universally useful features like white noise, color filters, and magnification to shift that mindset. developers designing settings menus can use daily.dev to explore approaches for improving accessibility discoverability."}}]}
```

