Applying EveryRamp's fixes on Revize
The short answer: for a site built on Revize's eGov content management system, most text and image fixes are things your own web team can change directly, in an editor that works much like a word processor. Fixes to the site-wide theme or forms need a Revize support request. This page describes Revize's own public support process; it is not a review of the product.
How the split works on Revize
Revize's own page editor needs no coding — staff use it much like Microsoft Word to edit pages, add documents, and add new pages. That gives two buckets:
- Content-level — text, images, links, headings and tables inside a page, changed in the page editor.
- Template-level — the site-wide theme, any built-in form module, and embedded-content boxes such as maps or calendars. These usually sit outside the page editor and need a Revize support request.
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 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, the same way you'd apply Heading 1, 2 or 3 styles in a word processor. Don't just make text bold and bigger.
- Link text: rewrite text like "click here" so it says where the link goes.
- Tables: use your editor's table tool to mark the header row or column, the same way Word lets you mark a header row, rather than only bolding it.
- Page title: look for a separate page-title or SEO-title field from the visible heading.
Fixes that need a Revize support request
Revize offers unlimited technical support through an online portal, by phone at 248-269-9263, or by email. Send this wording through whichever channel your account normally uses:
Our website was tested against WCAG 2.1 AA. The following findings are in the site template, not something we can change in our own page 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 which of these we can adjust 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.
- Upload EveryRamp's rebuilt PDF as a replacement for the existing file, rather than deleting the old one and adding a new file. 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 Revize support (contact above) to confirm the right way to update the document without changing its address.
After you fix things
Once your fixes — and, if needed, Revize'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.