# Should we make it a preference?: On customization, defaults, and accessibility

DevFeed: [Should we make it a preference?: On customization, defaults, and accessibility](<https://devfeed.tech/articles/should-we-make-it-a-preference-on-customization-defaults-and-accessibility-9157.md>)

Original publisher: [Read original article](<https://slack.design/articles/should-we-make-it-a-preference-on-customization-defaults-and-accessibility/>)

Author: andyacevedo

Published: 2025-01-23T18:28:29Z

Content type: article

Language: en

Sources: [Slack Design](<https://devfeed.tech/sources/slack-design.md>)

Topics: [Accessibility](<https://devfeed.tech/topics/accessibility.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [customization](<https://devfeed.tech/tags/customization.md>), [keyboard](<https://devfeed.tech/tags/keyboard.md>), [screen](<https://devfeed.tech/tags/screen.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

## AI overview

Slack Design explains when accessibility accommodations should be defaults rather than optional preferences. It argues that new users should receive an accessible experience out of the box, while preferences should support advanced customization and preserve familiar behavior during significant changes.

## Source excerpt

Design that is inclusive and accessible almost always works better for everyone. But once in a while we reach a genuine dilemma -- the more technically accessible choice adds friction or breaks expectations for everyone else. In these moments, someone inevitably asks: Can we just make it a preference? "Make it a preference" is sometimes [...] The post Should we make it a preference?: On customization, defaults, and accessibility appeared first on Slack Design.