Applying EveryRamp's fixes on CivicPlus
The short answer: for a site built on CivicPlus (Municipal Websites, Web Central or Web Evolve), most text and image fixes are things your own web team can change directly. Fixes to the site-wide template, theme or forms need a CivicPlus support ticket. This page describes CivicPlus's own public support process; it is not a review of the product.
How the split works on CivicPlus
CivicPlus's editor separates a page's own content and uploaded files from site-wide settings, which are normally locked to your web team. That gives two buckets:
- Content-level — anything inside a page's content area or its uploaded files: image descriptions, link wording, headings, tables, and replacing a document. Your own editor can do this.
- Template-level — anything in the site-wide template, theme styling, or a built-in module such as navigation or forms. This needs a CivicPlus support ticket.
If you're not sure which bucket a fix falls into, try it in the page's content editor first. If there's no visible way to change it there, treat it as template-level.
Fixes you can make yourself
- Image descriptions: open the image in your page editor and add its description in the image's alt-text field. Leave it blank for a purely decorative image, rather than typing "image" or a file name.
- Headings: use your editor's heading styles (Heading 1, Heading 2, and so on) in order, top to bottom. Don't skip a level just to make text look bigger.
- Link text: change wording like "click here" or "read more" to say where the link goes.
- Tables: use your editor's table tool to mark the header row, not just bold text.
- Page title: look for a "Page Title" or "SEO Title" field separate from the visible heading. If you can't find one, treat it as template-level instead.
Menu names can vary by contract. If a step above doesn't match what you see, look for the field in your own editor that serves the same purpose.
Fixes that need a CivicPlus support ticket
Sign in to your CivicPlus help center and use its "Submit a request" form. Paste this into the description, filling in your own page addresses:
Our website was tested against WCAG 2.1 AA and the following findings are outside our own content editor:
- 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 has no programmatic label (WCAG 1.3.1, 4.1.2) — [form/page 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 whether each of these is a setting we can change ourselves or needs a change on your side.
Include only the lines that actually apply — check your own EveryRamp fix pack for the exact list, since it names your pages and elements.
Replacing a PDF without breaking its link
- Open the document in your Document Center or Agenda Center's file manager.
- Upload EveryRamp's rebuilt file as a replacement for the existing one, 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 your document tool has no replace-in-place option, ask CivicPlus support (using the ticket wording above, naming the document and its address) to confirm the right way to update it without changing the address.
After you fix things
Once your fixes are live — yours and, if needed, CivicPlus's — go back to your EveryRamp order page and press "Re-test my site." Your test report updates automatically. EveryRamp also re-tests every month for 12 months, so a fix that lands later still gets picked up.
This page is general information, not legal advice.