Applying EveryRamp's fixes on Legistar
The short answer: Legistar (part of Granicus) publishes council and board agendas, minutes and packets. A clerk's office can fix how an agenda item is titled and described, before the packet is published. Fixes to the shared portal template need a Granicus support case. This page describes Granicus's own public support process; it is not a review of the product. This is the meeting/agenda system — for your main township or city website, see the platform that matches that separate site instead.
Why this platform is different from a general website system
Legistar publishes agenda items as a compiled PDF packet built from everything a clerk attaches to a meeting. Unlike a page editor, there usually isn't a way for your web team to edit the surrounding page template — search box, header, navigation — since that comes from Granicus's own front end.
- Template-level (send to Granicus support): the portal's page language, zoom and reflow behavior, color contrast, keyboard-focus visibility, skip-navigation, and any keyboard trap. These are part of the shared portal template, not something your clerk's office edits.
- Content-level (your clerk's office can do this before publishing): the title and description of each agenda item, and which document is attached, set when the item is created.
Fixes that need a Granicus support case
Open a case at Granicus's support portal with this wording:
Our public meeting portal (Legistar) was tested against WCAG 2.1 AA. The following findings are in the portal template, not something our clerk's office can change when creating an agenda item:
- Page language not set correctly (WCAG 3.1.1) — [page address]
- Pinch-zoom or text-resize disabled (WCAG 1.4.4, 1.4.10) — [page address]
- Text/background color contrast too low (WCAG 1.4.3) — [page address, element]
- No visible outline when tabbing with a keyboard (WCAG 2.4.7) — sitewide
- No way to skip repeated navigation to reach page content (WCAG 2.4.1) — sitewide
- Keyboard focus gets stuck in part of the page (WCAG 2.1.2) — [page address]
Please let us know which of these are portal settings and which need a fix on your side.
Fixes you can make when creating an agenda item
Give each agenda item a title and description that says what the document actually is — for example, "Staff report: FY27 budget amendment," not "Attachment A" — before the packet is compiled. Headings inside an uploaded document live in the document itself, not the Legistar item; see the PDF section below. If a step above doesn't match what you see, look for the field in your own agenda-item editor that serves the same purpose.
Replacing a PDF without breaking its link
If a single attached document — not the whole compiled packet — needs replacing with EveryRamp's rebuilt version, do it before the meeting packet is compiled and published, through your agenda-item editor's document upload. Once a packet has already been published as one combined PDF, ask Granicus support (case format above) to confirm the right way to update a posted packet or attachment without breaking its address.
After you fix things
Once your fixes — and, if needed, Granicus's — are live, go back to your EveryRamp order page and press "Re-test my site." Your test report updates automatically, and EveryRamp re-tests every month for 12 months.
This page is general information, not legal advice.