Accessibility Guidance for Tile Actions
TLDR;
Is A accessible to AA WCAG standards if there is an action in the overflow menu for "View Trip"? Or do we need to use B to be considered accessible?
A: The \"View Trip\" action is in the overflow menu / B: The \"View Trip\" action is on the tile.
------
We're designing tiles for a client to be used on both a chat canvas and a traditional page. Tiles all have an image, some sort of text content, and some set of actions.
These actions usually present as either save, add to trip, or an overflow menu with a short set of secondary actions.
Tapping on these cards will always take you to a detail page for the content on the card.
If our goal is to be AA WCAG compliant...
- Is it recommended (or required) for a tile like these to have a button on the tile itself for viewing the detail page, like a "View details"?
- Or can the card itself solely act as the action to do that
If we need a clearly stated action to do that, could that be in the overflow menu (for the clearly stated version) AND have the card itself be tappable and do the same thing?