Most Atlas problems come from a mismatch between the content structure, the selected card-row behavior, and the responsive settings. Check those three areas before rebuilding the comparison.
The comparison is too wide or crowded
Preview the page at the width where the problem occurs. For responsive cards, choose Static or Slider deliberately. In slider mode, reduce the number of visible columns for the affected device range and review the matching step, peek, and gap values. Also compare Full and Content width.
Rows do not line up
Use Card Rows: Synced when corresponding features should align across cards. Keep row labels and row order consistent in every child stack. Use Independent only when each card is meant to follow its own content height. Equal Cards can correct the overall card height, while Pin CTA keeps buttons aligned at the bottom.
Headers or badges look uneven
Start with automatic header height and compare the header content in every card. Adjust Head Pad Y only after removing unnecessary line breaks. Use the fixed badge slot when some cards have badges and others do not.
The slider is difficult to understand
Use Peek Next when part of the next card should indicate that more content is available. Enable dots when readers need a visible position indicator. Check that the column and step settings make sense together at desktop, tablet, and mobile widths.
Set useful accessible names
ARIA Table names the table view and ARIA Mobile names the responsive card view. The Atlas demo uses “Comparison table” and “Comparison cards”. If a page contains more than one comparison, use more specific names such as “Hosting plan comparison” and “Hosting plan comparison cards”.
Do not rely on appearance alone
Use text as well as color for yes, no, featured, and state information. Give buttons clear action labels, keep text contrast readable, and ensure meaningful images have appropriate alternative text in the content used with Atlas. Test the page with keyboard navigation, zoom, and a narrow viewport.
Before contacting support
Record the Atlas version, Stacks App version, macOS version, the affected device width, and the exact settings involved. Add a focused screenshot and describe what you expected. Send the request to support@stackswork.com and follow What to include in a support request.
Related guides
See Getting started with Atlas, Choosing responsive layouts in Atlas, and Styling cards and headers in Atlas.