Applying EveryRamp's fixes on Granicus GovAccess
The short answer: for a site built on Granicus's GovAccess website system (sometimes shown as OpenCities), most text and image fixes are things your own web team can change directly. Fixes to the site-wide theme or forms module 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 general-purpose website system — for the separate meeting/agenda system, see the Legistar page instead.
How the split works on GovAccess
GovAccess is a drag-and-drop page builder with a live-edit view, plus a separate digital-forms tool. That gives two buckets:
- Content-level — text, images, links, headings and tables inside your own pages, changed through the page editor's live-edit view.
- Template-level — the site-wide theme, the forms module's field rendering, and anything in the shared header, footer or navigation. This needs a Granicus support case.
Menu names can vary by contract. Where a step below doesn't match what you see, look for the field in your own editor that serves the same purpose.
Fixes you can make yourself
- Image descriptions: select the image in the live-edit view and add its description in the alt-text field. Leave it blank for a purely decorative image, rather than typing "image" or a file name.
- Headings: apply your editor's built-in heading styles in order. Don't skip a level just to make text bigger.
- Link text: rewrite text like "click here" so it names the destination, directly in the page body.
- Tables: use your editor's table tool to mark the header row, rather than only bolding it.
- Page title: set this in your page's own title or metadata field, separate from the visible on-page heading.
Fixes that need a Granicus support case
Open a case at Granicus's support portal and paste this into the description, filling in your own page addresses:
Our website (GovAccess) was tested against WCAG 2.1 AA. The following findings are in the site template or a built-in module, not something our own page editor can change:
- 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) in the site theme — [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
- A form field in the digital-forms module has no programmatic label (WCAG 1.3.1, 4.1.2), or a submitted form's error messages are not connected to the field (WCAG 3.3.1) — [form address]
- Keyboard focus gets stuck in part of the page (WCAG 2.1.2) — [page address]
- An embedded map, calendar or video box has no title (WCAG 4.1.2) — [page address]
Please let us know which of these are theme settings we can change ourselves versus items needing a fix on your side.
Include only the lines that actually apply to your own report.
Replacing a PDF without breaking its link
- Open your document library's upload tool.
- Replace the existing file with EveryRamp's rebuilt version, rather than deleting the old entry and adding a new one. Replacing in place is what normally keeps the same public link.
- Open the old link again and confirm it now shows the new file before you consider it done.
If you don't see a replace option, ask Granicus support (using the case format above) to confirm the right way to swap in the rebuilt PDF without changing 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.