WCAG Edition (Based on VPAT® Version 2.5Rev)
This is a self-assessment. MSACAlab prepared it for its own product. No independent auditor has reviewed it, and it is not a certification or a claim of legal compliance.
- Name of Product/Version
- CoreA11y for Wix, version 1.0 (Wix App Market), with the accessibility fixes of 4 November 2026
- Report Date
- 4 November 2026
- Product Description
- A Wix app that audits a Wix site for accessibility problems, offers quick fixes that can be undone, and gives Wix steps for the rest. The site owner uses it from a dashboard that opens inside Wix.
- Contact Information
- support@corea11y.com
- Applicable Standards
- WCAG 2.2, Levels A and AA
Summary
| Conformance level | Level A (32 criteria) | Level AA (24 criteria) |
|---|---|---|
| Supports | 23 | 19 |
| Partially Supports | 1 | 2 |
| Does Not Support | 0 | 0 |
| Not Applicable | 8 | 3 |
Three criteria are Partially Supported: 2.2.1 Timing Adjustable, 2.4.5 Multiple Ways and 4.1.3 Status Messages. The remarks in the tables explain each one.
Notes
What this report covers
CoreA11y's own screens, as the site owner uses them:
- Dashboard: sites list, site page, audit start page, audit report, quick fixes, alt text, guided checks (list and single check), plans, and report branding.
- Other dashboard screens reached from those: before and after, colour contrast, accessibility statement, site settings, add a site, privacy, terms, the page-not-found page, and the sign-in pages.
- The PDF report: the print page, and a PDF saved from it in Chrome.
- The audit runner panel, which the owner's own browser shows on their site during an audit.
What this report does not cover
- Wix's own dashboard around the app, Wix sign-in, and Wix checkout. Wix runs those.
- The "Show on page" overlay and the guided-check overlays on the owner's site. They were not evaluated.
- The weekly email, and the corea11y.com website.
- The owner's Wix site, and what quick fixes do to it. A report on this app says nothing about the accessibility of sites that use it.
Evaluation Methods Used
Evaluated by MSACAlab on 4 November 2026 against a local build of the app and a stand-in Wix site with a stand-in Wix API. The test site's page structure follows Wix's, and it has deliberate accessibility problems. The same code went live as the production app on 4 November 2026.
Testing was automated and AI-driven, using a real browser and scripts.
- Browser: Google Chrome 156 (headless) on Windows 11. Most checks also ran in Microsoft Edge 156 (headless) on the same day, before the last small fixes.
- Automated: axe-core 4.14.0 with the WCAG 2.0, 2.1 and 2.2 A and AA rules and best-practice rules. It ran on 18 screens in light theme, dark theme and at 320 pixels wide, with collapsible sections open, and found no violations in the final run. A further pass covered other states: Free and Agency plans, app removed from Wix, form errors, and saved results. Automated tools find only some accessibility problems.
- Keyboard: real Tab, Shift, Enter, Space, Escape and arrow key events. Tab was walked through 18 screens (390 focus stops) in light and dark themes, measuring focus order, the visible focus outline and its contrast, and whether focus could leave the page. 35 scripted task checks covered saving fixes, dismissing and restoring issues, answering guided checks, saving alt text, form errors, and copying text.
- Zoom and reflow: viewports 640 pixels wide (equal to 200% zoom on a 1280 pixel screen) and 320 pixels wide (equal to 400%). The runner panel was also tested at 320 by 180 pixels.
- Text spacing: the WCAG 1.4.12 values applied by stylesheet at 1280 and 320 pixels wide, looking for overflow and clipped text.
- Motion and contrast modes: reduced-motion setting (no animations run) and a forced-colours spot check on two screens.
- Names, roles and values: read from Chrome's accessibility tree for every control on the 18 screens and the panel.
- PDF: a PDF saved through Chrome was checked for tags, language and title. Headings, tables, lists and the score image with its text alternative are present. It was not opened in a PDF reader or checked with a PDF accessibility tool.
Limits of this testing
- No screen reader was used. Names and live regions were checked in the accessibility tree, which shows what the browser exposes. It does not prove what a screen reader says.
- The app was opened in its own tab, not inside the real Wix dashboard frame. The runner was run on the stand-in site, not a live Wix site.
- Safari, Firefox, phones, tablets, voice control and switch devices were not tested.
- Screens were reviewed through scripts, measurements and screenshots, so judgement calls such as how clear a heading or instruction is were made by the AI evaluator.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.2 | Level A (Yes) Level AA (Yes) Level AAA (No) |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
WCAG 2.2 Report
When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
The table for Level AAA has been removed because Level AAA was not evaluated.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Supports | The logo mark is hidden from assistive technology because the product name is text beside it. Score rings have a text name. Colour swatches are hidden, with the colours written out next to them. Alt text thumbnails have empty alt because the file name is the heading beside them. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | The product has no audio or video. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | The product has no video. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | The product has no video. |
| 1.3.1 Info and Relationships | Supports | Uses HTML headings, lists, tables with header cells, fieldsets, labels and landmarks. At 600 pixels and narrower, tables stack and hide their header row, and each cell shows its column name as text. The table roles stayed in place in Chromium; other browsers were not tested. The PDF saved from Chrome is tagged. |
| 1.3.2 Meaningful Sequence | Supports | Reading order follows the page source. The CSS does not reorder content. |
| 1.3.3 Sensory Characteristics | Supports | Instructions name controls and sections by their text. No instruction relies only on shape, colour, sound or position. |
| 1.4.1 Use of Color | Supports | Links are underlined. Severity and status are written as text, not shown by colour alone. |
| 1.4.2 Audio Control | Not Applicable | The product plays no audio. |
| 2.1.1 Keyboard | Supports | All tested tasks were completed with the keyboard alone. During an audit, Escape cancels from anywhere on the page, and the panel says so. |
| 2.1.2 No Keyboard Trap | Supports | Tab moved through every control and left the page on all 18 screens. The runner panel does not hold focus. |
| 2.1.4 Character Key Shortcuts | Not Applicable | The product has no letter, number or punctuation key shortcuts. |
| 2.2.1 Timing Adjustable | Partially Supports | Three signed links have fixed limits that can't be extended: the audit start link (30 minutes), the "View report" link (60 minutes), and the link that opens the app in its own tab when a browser blocks its cookie (10 minutes). There is no warning before they expire. No work is lost, and starting again gives a new link. Sessions last at least 24 hours, which is beyond the WCAG 20-hour limit. |
| 2.2.2 Pause, Stop, Hide | Supports | The dashboard has no moving content. During an audit the owner's site scrolls and changes page by itself, after the owner starts it. Escape or Cancel audit stops it. This scrolling does not change with the reduced-motion setting. |
| 2.3.1 Three Flashes or Below Threshold | Supports | Nothing in the product flashes. The dashboard runs no animations. |
| 2.4.1 Bypass Blocks | Supports | A skip link is the first focus stop on dashboard screens and moves focus to the main content. Landmarks and headings are also present. The print page has one control before its content. |
| 2.4.2 Page Titled | Supports | Each screen has a descriptive title. The print page title includes the site and date. Report pages for different audits of one site share a title. |
| 2.4.3 Focus Order | Supports | Focus follows the visual order. After a form is sent the page reloads and focus starts at the top. When a panel button is replaced, focus moves to the new button. The panel comes last in the owner's page. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text, or text with its table row or list item, gives the purpose. Links that open a new tab say so. |
| 2.5.1 Pointer Gestures | Not Applicable | The product has no path-based or multipoint gestures. |
| 2.5.2 Pointer Cancellation | Supports | Controls are native links, buttons and form fields, which act when the pointer is released. |
| 2.5.3 Label in Name | Supports | Names start with or contain the visible text. Help buttons show only a "?" symbol and are named by purpose, such as "How the score works". |
| 2.5.4 Motion Actuation | Not Applicable | Nothing is operated by moving the device. |
| 3.1.1 Language of Page | Supports | Dashboard and print pages are marked as English. The saved PDF has its language set. The runner panel marks itself as English on any site. |
| 3.2.1 On Focus | Supports | Focus never starts a change of context. Moving focus only closes an open help pop-up, and the panel may move to the other edge of the screen to keep the focused item visible. |
| 3.2.2 On Input | Supports | Changing a field does not submit a form. Every form has a submit button. |
| 3.2.6 Consistent Help | Supports | The support email is in the same place in the footer of every dashboard screen. The print page and the panel offer no help mechanism. |
| 3.3.1 Error Identification | Supports | Server checks show an error in text at the top of the page. Required and format checks use the browser's own validation, which names the field and moves focus to it. |
| 3.3.2 Labels or Instructions | Supports | Every field has a visible label. Optional fields say so, and hints are linked to their fields. |
| 3.3.7 Redundant Entry | Supports | Guided-check, alt text and branding forms keep what was typed when a save is refused. A refused contrast colour is not kept, because it must be changed; the error message quotes it. |
| 4.1.1 Parsing | Not Applicable | Obsolete and removed in WCAG 2.2. |
| 4.1.2 Name, Role, Value | Supports | Controls are native HTML. Every control on the tested screens and the panel had a name and role in Chrome's accessibility tree. Not confirmed with a screen reader. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The product has no live audio. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | The product has no video. |
| 1.3.4 Orientation | Supports | The layout is not locked to an orientation. It adapts to the window width. Not tested on a real phone or tablet. |
| 1.3.5 Identify Input Purpose | Supports | Fields for the user's name, email, password, phone and organisation have autocomplete values. |
| 1.4.3 Contrast (Minimum) | Supports | No contrast failures from axe-core in light or dark theme. Placeholder text uses the same colour as other muted text. On the contrast screen, the "before" colour samples show a site's failing colours on purpose; they are hidden from assistive technology and the colours are written out beside them. |
| 1.4.4 Resize Text | Supports | No loss of content or function at a viewport equal to 200% zoom. Browser text-only zoom was not tested. |
| 1.4.5 Images of Text | Supports | Text is real text, including the product name. The only exception is the colour samples, where the exact appearance is essential. |
| 1.4.10 Reflow | Supports | No sideways scrolling at 320 pixels wide on any tested screen, with help pop-ups and collapsible sections open. The runner panel fits at 320 by 180 pixels and scrolls inside itself. Not tested inside the Wix dashboard frame. |
| 1.4.11 Non-text Contrast | Supports | Field borders, focus outlines and selected checkboxes and radio buttons were checked in both themes. Score rings and bars also give their values as text. |
| 1.4.12 Text Spacing | Supports | No clipped or overlapping content was detected with the WCAG spacing values. |
| 1.4.13 Content on Hover or Focus | Supports | Help pop-ups open on click or key press, not on hover or focus. They close with Escape or when focus moves on. Two colour fields use a title for their format hint, shown by the browser on hover; the same hint appears in the browser's error message. |
| 2.4.5 Multiple Ways | Partially Supports | Most tool screens (alt text, colour contrast, statement, site settings) are reached one way: the Site tools links on the site page. There is no search, site map, or tools menu on the other screens. Quick fixes and guided checks also have links from reports. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe their topic or purpose. On the alt text screen, an image's heading is its file name, so it is only as clear as the name of the file. |
| 2.4.7 Focus Visible | Supports | Every focus stop on the 18 screens had a visible outline of at least 3:1 against its background, in both themes. Forced-colours mode kept a visible outline. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports | The dashboard has no fixed headers or footers, and no tested focus stop was covered. If the runner panel would cover the focused item, it moves to the other edge of the screen. |
| 2.5.7 Dragging Movements | Not Applicable | Nothing in the product is dragged. |
| 2.5.8 Target Size (Minimum) | Supports | Buttons and help controls are at least 24 by 24 pixels. Smaller targets fall under the WCAG exceptions: links within text, and items with enough space around them, such as the 22 pixel checkboxes (their labels are also clickable) and the file field. |
| 3.1.2 Language of Parts | Supports | The interface is in English. Names and text that come from the owner's site are not marked with a language. |
| 3.2.3 Consistent Navigation | Supports | The header and footer keep the same order on all dashboard screens. |
| 3.2.4 Consistent Identification | Supports | Controls with the same function have the same name, such as Undo and Back to site. |
| 3.3.3 Error Suggestion | Supports | Error messages say what to do, such as the contrast ratio a colour must reach. Colour fields add a format hint to the browser's message. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Payments happen in Wix, outside this report. Deleting a site's data needs a ticked confirmation. Quick fixes, saved alt text and applied colours can be undone. |
| 3.3.8 Accessible Authentication (Minimum) | Supports | In normal use Wix signs the owner in, outside this report. The separate login page uses an email and password with no puzzle, and allows password managers and paste. |
| 4.1.3 Status Messages | Partially Supports | Save, error and "Copied" messages and the panel's progress use live regions, seen in the accessibility tree. It was not confirmed that a screen reader announces them. The report does not update itself during an audit, so the owner has to reload it to see progress. |
Legal Disclaimer (MSACAlab)
This report is a self-assessment of the build and date stated above. It is provided for information, may change as the product changes, and is not a warranty, a certification, legal advice, or a statement that the product or any site using it complies with any law. VPAT® is a registered service mark of the Information Technology Industry Council (ITI). ITI does not review or approve reports based on the template.
Questions, or found a problem we missed? Email support@corea11y.com.