Where each fix goes on your website platform

The short answer: your EveryRamp fix pack lists every fix already, page by page. Some of those fixes you can make yourself, in your own page editor. Others live in your platform's shared template or theme, and need a support ticket to your platform's vendor instead. Which bucket a fix falls into depends on which website system your site runs on. Pick your platform below for the exact split, and wording you can paste into a support ticket.

Pick your platform

  • CivicPlus — Municipal Websites, Web Central and Web Evolve, built on CivicPlus's Hosted Content Management System.
  • Granicus GovAccess — Granicus's general-purpose website system, also shown as OpenCities. For the separate meeting/agenda system, see Legistar below.
  • Revize — Revize's eGov content management system.
  • Municode — the Code of Ordinances hosted at library.municode.com, a CivicPlus product with its own editorial process.
  • BoardDocs — the board and council meeting-agenda portal.
  • Legistar — Granicus's meeting-agenda and packet system, separate from a city or county's main website.
  • WordPress — a site built on WordPress with the standard block editor.

Not sure which platform your site uses?

Look at the web address of a document linked from your site, or ask whoever manages your website. If your site isn't on any of these seven, most of what your fix pack lists can still be done in your own page editor; ask your web host or developer about anything that looks like a site-wide template or theme setting.

Content-level and template-level, in general

Across every platform, the same two buckets show up:

  • Content-level: image descriptions, headings, link wording, tables, page titles, and replacing a PDF with EveryRamp's rebuilt version, where the platform allows it. Your own web team can usually do these directly.
  • Template-level: page language, pinch-zoom and text-resize, color contrast, keyboard-focus visibility, skip-navigation, keyboard traps, and titles on embedded maps, calendars or videos. These are normally site-wide theme or module settings, outside a content editor, and need your platform's support team.

Each platform page below gives the exact wording to paste into a support ticket for the template-level items, and the steps for the content-level ones.

This page is general information, not legal advice.