This page records what keeps the site's accessibility fixes working,
what to check before you publish, and the conventions for new content.
It does not list findings or counts; those live in the audit register in
this repository under wix/accessibility/. If something here
looks wrong or out of date, tell Karl rather than working around it.
Before every publish
There is no staging site. Publish goes straight to the live site, and the only way back is Site History, which restores the whole site to an earlier version, not one change.
- Open Site History (Editor, Site, Site History). Find the newest entry marked Published by and star it. That star is the restore point if this publish has to come back out.
- Look for Saved by entries above it. Those are unpublished edits, and Publish takes them live too. On 25 September 2026 two pages went offline that way. If a save is not yours, or you do not remember it, check before publishing.
- Publish, then hard-refresh the live site (hold Shift while reloading) before checking the change. A normal reload often shows the old page.
- If Karl has a re-scan or an Aaron verification in progress, publish content changes before or after it, not during, so each change can be attributed. Tell him when you publish.
Restore: Site History, arrow on the starred entry, Restore. It loads that version into the Editor; publish to make it live. Blog posts, bookings, forms and other app data are shared across versions and are not affected by a restore.
The Editor is single-session. Opening it evicts whoever is in it. Karl works in it without asking unless Wix warns that someone else is there.
Settings that hold fixes in place
Each fix below depends on a setting somewhere. Changing that setting, or replacing the element it lives on, undoes the fix silently: nothing in the Editor warns you. If you need to change one of these, tell Karl so it can be re-tested.
| Fix | Where it lives | What undoes it |
|---|---|---|
| Consent dialog shows a visible focus outline (shipped 10 September 2026) | A styling rule in the CookieHub dashboard, which Karl administers. Not in Wix. | Changing the CookieHub theme or accessibility level. When checking anything CookieHub, hard-refresh: the browser keeps the old styling. |
| Pop-ups no longer open on page load (shipped 25 September 2026) | Editor, Popups list. "Find What You're Looking For" and "Disability at Work Survey" are both set to Automatically display popup on pages: No. The homepage button "Not sure where to start?" opens the first. The survey pop-up has your 45 second delay. | Setting any pop-up to display automatically on load, or adding a new one that does. A pop-up that opens over the consent banner traps keyboard users. |
| Footer links are far enough apart to tap (shipped 28 September 2026) | The six footer column text elements (Employers, Job Seekers, Talent Partners, About, Resources, Community & Events), each at line spacing 1.8. Select the text, Edit Text, Character & line spacing. Font size is unchanged. | Rebuilding a column, pasting a new text element, or resetting the spacing. Set 1.8 again on anything new in the footer. |
| Slideshow controls are large enough on every page that has one: the logo slideshows on twelve pages, the Employers text slideshow and the homepage testimonials slideshow (shipped 30 September 2026; the homepage settings from 28 September had not held) | Select the slideshow, Layout. Logo slideshows: slide buttons off, arrows 24 px. Homepage testimonials slideshow: slide buttons 12 px with 24 px spacing, arrows 24 px. | Replacing a slideshow, or changing the Layout panel. A copied slideshow brings its old settings with it, so check Layout on any new slideshow before publishing. |
| Link lists have room to tap: the pricing cards on the training page, the partner grid, the job seeker resource cards, the agency solutions cards, the speakers' Topics boxes, and the footer's Privacy Policy and Accessibility Statement links (shipped 30 September 2026) | Each list is a text element at line spacing 1.8. Select the text, Edit Text, Character & line spacing, Custom. The two footer links sit on separate lines. | Pasting a new text element or resetting the spacing. Set 1.8 on any new list of links, and keep the two footer links on their own lines. |
| Accessibility statement carries a "Known Limitations" section on browser zoom (shipped 28 September 2026) |
The /accessibility-statement page, between "If you
have any comments" and the date line.
|
Editing it out. Karl adds one sentence to it when the zoom workaround ships. Since 30 September 2026 the Conformance Status paragraph says WCAG 2.2 level AA, which is the standard Aaron tests to; keep 2.2 everywhere on the page. |
| Blog post sidebar titles are headings at the right level (shipped 28 September 2026) | Blog Post page, the four sidebar titles (Featured Posts, Recent Posts, Search By Tags, Archive), HTML tag set to H2 under the text element's SEO & accessibility settings. The look is unchanged. | Recreating the titles. If the sidebar widgets are removed, this goes with them and that is fine. |
| A custom "Page not found" page replaces Wix's default 404 (shipped 30 September 2026) |
Pages & Menu, the page "Page not found" (its URL is fixed to
error404). One H1, a sentence, a "Back to Homepage"
button, site header and footer.
|
Deleting the page, which brings back Wix's default with no language or landmarks. Edit the text freely; keep the heading as Heading 1 and the paragraph on a dark text style. |
| Dev Mode stays on (from 25 September 2026) | Editor, Dev Mode. | Turning it off. Nothing depends on it yet, but the navigation fix will be built with it on. |
The menu
Do not swap the menu component. It has been tried three times and the problem is in Wix's own markup, so every menu component fails the same way. The planned fix is a small script that corrects the menu after the page loads. That script finds the menu by its structure, so replacing the component afterwards would silently undo it. Adding and removing pages is fine; send Karl the old and new URLs when you do.
Conventions for new content
These are the rules that keep new pages from re-creating the problems the audit found. Wix's Accessibility Wizard helps with alt text and contrast and is worth running, but it is silent on the navigation and on most of the list below, so a clean Wizard result is not a pass.
The existing pages' backlog against these rules is the separate content work list, read from the live site page by page and refreshed by Karl after each change.
Images, icons and linked boxes
- Alt text describes the content or, for a linked image, where the link goes: "Shaker Recruitment Marketing website", not "logo". Never the file name. Wix pre-fills the file name on upload, so replace it every time.
- Icons are named by what they are: "LinkedIn", not "Black LinkedIn Icon". Award badges name the award, not the year.
- A card or box that is one big link needs a name that says where it goes, on the box link's accessibility setting or on the image inside it.
- Purely decorative images are marked decorative, with no alt.
Links and buttons
- Link text says where it goes. "Learn more" on its own does not; "Take the Disability at Work survey" does.
- A link that opens a new tab says so in the text, for example "(opens in a new tab)".
- Anything clickable is at least 24 by 24 pixels. For a list of links in a text element, set line spacing to 1.75 or more; the font size does not change. Slideshow dots are 12 px with 24 px spacing, or off.
Headings
- One H1 per page, and every page has one.
- Levels go in order: H2 under H1, H3 under H2. Do not pick a heading level for its look. The HTML tag is set under the text element's SEO & accessibility settings and the style is set separately, so any level can look any way.
Pop-ups, video and slideshows
- Pop-ups open on a click or after a delay, never on page load. The consent banner has to be dealt with first.
- Video goes in as Wix Video, not a YouTube embed, with captions. Nothing autoplays.
- Slideshows do not auto-advance, and their arrows and dots follow the sizes above.
Pages and tables
- A page that promises a language serves that language. Do not create pages with a translated heading over English text.
- Tables are for data only, never layout, and narrow enough that they do not scroll sideways on a phone.
- Every page has a language set (English), including any custom error page.
- After replacing any component, not only the menu, tell Karl so the page can be re-tested. A component swap keeps the look and changes the markup.
Colour and contrast
Text needs a contrast ratio of at least 4.5 to 1 against its background, or 3 to 1 if it is large (24 px, or 19 px bold). The brand teal does not reach 4.5 to 1 on white, so a slightly darker teal is used wherever teal carries normal text or fills a button. The two are hard to tell apart by eye.
| Colour | Ratio on white | Use |
|---|---|---|
Text teal
#0f7d77
|
4.98 | Links, button fills with white text, any teal text at normal size. |
Brand teal
#13938b
|
3.77 | Large text and decoration only. Never normal-size text on white, and never white normal-size text on it. Dark text on it reaches 4.34, still short, so large text only there too. |
Near black
#17221e
|
16.36 | Body text. Also fine on mint (10.02) and on pink (4.85). |
Grey
#5b5f5f
|
6.47 | Secondary text on white. |
Pink
#da61a4
|
3.37 | Decoration only. Not text on white, and not white text on it. |
Mint
#aad3c9
|
1.63 | Backgrounds, with near-black text on it. Text teal on mint is 3.05, so large text only. |
For any other pair, check it with a contrast checker such as WebAIM's contrast checker before publishing.
How fixes are verified
Aaron is the acceptance authority. A fix counts as done when he confirms it works, not when it is published. He is blind, uses a screen reader every day, and checks changes on the live site by email after they are published, so an unverified change sits live for the length of that round trip.
- One change per cycle. If two changes are live and he reports a problem, nobody can tell which one caused it, and a restore reverts both.
- He gets steps and expected outcomes, not diagnoses: what to try and what should happen.
- A fix must work with at least two screen readers on two different browser engines. Chrome and Edge share an engine, so that pair does not count. Something that works in one pairing only is not fixed.
- Aaron is on copy of every email between Ashley and Karl about this work, so he sees decisions as they happen. He verifies what has shipped; he is not asked to test things before they are built.
- When he confirms a fix, the screen reader and browser he used are recorded with it.
Wix Studio rebuild: ground rules
The Studio site "Disability Solutions rebuild" was created on 29 September 2026 with the defaults below already set, so a page built on it starts from a safe base. The site lives at karlthomas3.wixstudio.com/my-site-2 until it is transferred to the client's account and, at launch, takes over the domain. Nothing about the live classic site changes until then.
What is already set, and must stay
- Site Styles, Colours: the eight palette colours are named for their use ("Text teal, links and buttons", "Brand teal, large text only", "Pink, decoration only", "Mint, backgrounds only", "Near black, body text", "Grey, secondary text", "Light band", "White"). Pick by name and the contrast rule takes care of itself. Do not add colours without checking the pair.
- Site Styles, Typography: Montserrat for everything. Paragraph 1 is 18 px, Paragraph 2 and 3 are 16 px, all with a minimum of 16 px under Scale text, so no body text shrinks below 16 px on any screen. Paragraph 3 has line spacing 1.75 and is the style for lists of links (footer columns, resource lists); Paragraph 1 and 2 sit at 1.6. Headings run 72, 42, 38, 34, 28, 22 px in order.
- Search engines: indexing is off in SEO Settings ("Let search engines index your site"). Turn it on at launch, not before.
- Language: English, in Language & Region.
- Focus indicators and Skip to content are always on in Studio sites; there is nothing to switch. Tools, Auto DOM Order is on and stays on.
Rules for every page built on it
-
Navigation: use the Studio menu element as it is. Its
live markup was read on 29 September 2026: a dropdown parent gets a
real button ("More About pages") with
aria-expanded, the dropdown is a named group, and there is noaria-haspopup, which is the attribute that breaks the classic site's menu for screen readers. Two rules keep it that way: every top-level item, dropdown parents included, links to a page (Manage Menu, the item, set its link), because a parent with no link renders as plain text that keyboard users cannot reach except through the arrow button; and nobody adds code or ARIA to the menu. Still to check once a dropdown holds links: that Tab moves into the open dropdown and Escape closes it, on two screen readers. - Breakpoints: keep the three defaults (desktop from 1001 px, tablet 751 to 1000 px, mobile 320 to 750 px) and check every page at the 320 px end of the mobile breakpoint before publishing: nothing may scroll sideways. Use percentage or stretch widths, never a fixed pixel width on a section or a text box.
- No auto-open pop-ups, no autoplay, no YouTube embeds. Same as the classic site.
- 404 page: Studio only allows a custom 404 page on a premium plan, so it is the first thing to build after the plan moves to this site at launch. Until then the platform default shows.
- Test site before publish: Site, Create Test Site gives a version to check before it replaces the live one. Use it for anything beyond a text edit. Site History still works as the fallback.
- Everything in "Conventions for new content" above applies here unchanged.
Change log
- 30 September 2026. Statement now says WCAG 2.2 throughout; slideshow controls fixed on every page that has one; a custom "Page not found" page; line spacing 1.8 on the remaining link lists and the footer's bottom two links on separate lines.
- 29 September 2026. First issue. Covers the consent dialog, pop-up, footer, slideshow, statement and heading fixes shipped between 10 and 28 September 2026, the publish drill, the content conventions, the colour table, and the ground rules set on the new Wix Studio site the same day. The content work list page added and linked from the conventions.