shadcn.io is not affiliated with official shadcn/ui
Audit Table Footer Block for Radix UI
A footer for a backup vault with an audit table in a framed figure (the programme, its scope, how often it is audited and a link to request the report) beneath the brand and three link columns.
Installation
Overview
A footer that shows its assurance programme for React with Radix UI. A first band holds the wordmark and one sentence beside three link groups in a nav labelled Footer. Under it a framed figure, with + marks on its corners, holds the audit table: four rows (a controls audit, a security standard, a penetration test, a continuity test), each with its scope, how often it is audited and a "Request" link for the report. A legal band closes the page. The programmes are generic and the rows are example data with no dates: no real certifier is named and nothing here claims a real certification, so list only what you hold. It's built from Guides, a plain table, plain links and your theme's tokens.
FAQ
How do I change the audits?
Edit the AUDITS array at the top of the file: each entry has a standard, a scope, an audit cadence and the report name that the link's hidden text uses. The cadences are words ("Annual"), not dates, so the table never goes stale; if you show a date, keep it current.
Are these real certifications?
No. The names are generic (a controls audit, a security management standard) and the caption says they are examples. Replace them with the exact name of each programme you hold, and remove any you do not, because a certification claim on a footer must be true.
What happens on a narrow screen?
The table is wider than a phone, so it scrolls sideways inside its own box instead of squeezing the columns. The box is a focusable region named by the figure's caption ("Assurance programme"), so a keyboard user can Tab to it and scroll with the arrow keys, and a screen reader says what it is. Nothing else on the page scrolls sideways at 320 pixels.
Where do the Request links go?
They are plain links (href="#"): point each at your report request form or a gated download. Each link has a hidden suffix naming its report ("Request the controls audit report"), so a list of links read out of context still makes sense.
How do screen readers move through it?
The block is a footer element, so at the end of the page it is the content-info landmark. The link groups are one nav labelled Footer, each with an h2. The table is a plain table on every target, with real column headers and the standard in each row as a row header, and the figure's caption names the region. The legal links are a labelled list.