Wix Accessibility Audit

Testing Context

This analysis combines findings from:

1. Live testing session (documented in video)

2. Backend Discovery (done after video recording) where our accessibility expert thoroughly examined platform settings and capabilities

Skip Link Implementation

Initial testing began with keyboard navigation to check for skip links. When pressing Tab, a "Skip to main content" link appeared as the first focusable element. The skip link had sufficient color contrast and was visually prominent.

Matrix Findings Summary:

✓ Passes:

• Skip link presence

• First focusable element

• Color contrast meets AA standards

⚠ Concerns:

• Skip link targets content but not first visual element on the page

✗ Fails:

• Skip link implemented as a button instead of semantic link element

Navigation Structure Implementation

Initial testing focused on semantic structure and keyboard interaction patterns. DOM inspection revealed proper use of the <nav> element and keyboard-accessible dropdowns. The Services dropdown could be triggered with the Return key, with dropdown items maintaining keyboard accessibility.

The mobile menu implementation showed mixed results, with some accessibility features present but several concerning issues in its behavior.

Matrix Findings Summary:

✓ Passes:

• Nav tag implementation

• Dropdown keyboard accessibility

• Button labeling and ARIA attributes (expanded, has-popup)

• Mobile menu activation controls

⚠ Concerns:

• Focus order incorrect in mobile menu

• Dropdown labels not sufficiently meaningful

• No focus lock in mobile menu

✗ Fails:

• Nav tag not properly labeled

• Users cannot define nav tag aria-label

• Separate open/close buttons missing for dropdowns

• Missing aria-controls on dropdown triggers

• At 400% zoom on narrower screens, navigation becomes a problematic slider with content overflow issues

Image with Text Banner Implementation

The banner section was tested for accessibility fundamentals including alternative text, keyboard interaction, and zoom behavior.

Matrix Findings Summary:

✓ Passes:

• Image alternative text present

• Visible keyboard focus on links

• Button-styled links correctly implemented without role="button"

• Color contrast requirements met

✗ Fails:

• At 400% zoom on narrower screens, the "Learn More" link overlaps text

• No heading structure present in the banner

Video Implementation

Testing covered three types of video implementations: platform-hosted autoplay videos, click-to-play videos, and YouTube embeds.

Matrix Findings Summary:

✓ Passes:

• Controls keyboard focusable

• Controls correctly coded as buttons

• YouTube embed properly implemented with titled iframe

✗ Fails:

• Autoplay videos continue playing when reduced motion is enabled

• No visible pause button for autoplay videos (only available to screen reader users)

• Captions cannot be added to platform-hosted videos

• Videos overlap headings at 400% zoom

• Focus targets entire video instead of play button

Accordion Implementation

Testing revealed significant issues with keyboard interaction and semantic structure of accordions.

Matrix Findings Summary:

✓ Passes:

• Buttons use aria-expanded

• No hidden content read by screen readers

• Visible focus indicators

✗ Fails:

• Accordion titles not implemented as headings with button tags

• Missing aria-controls references

• Cannot set proper heading levels

• Arrow keys trapped within accordion content

• Incorrect use of aria-haspopup

• Screen reader announces numerous "empty groups"

Contact Form Evaluation

Form testing revealed a mix of well-implemented features and significant accessibility gaps.

Matrix Findings Summary:

✓ Passes:

• Fields properly labeled

• Required fields both visually and programmatically indicated

• Error messages descriptive and properly connected to fields

• Color contrast requirements met

✗ Fails:

• Missing autocomplete attributes on name and email fields

• Placeholder text inappropriately duplicates labels

• No error summary above form

• Success message disappears after time interval

• Fieldset used without legend

Document Structure and Language

Overall structural analysis showed proper language definition but significant issues with content organization and reading order.

Matrix Findings Summary:

✓ Passes:

• Page language properly defined

• Content contained in landmark regions

• No justified text

✗ Fails:

• Tab order doesn't match visual order

• Reading order lacks meaningful sequence

Overall Platform Metrics

Final quantitative assessment from matrix:

• Total passing criteria: 48

• Total concerns: 3

• Total failures: 32

• Total N/A items: 2

• Percentage of good applicable checks: 57.83%

• Platform ranking: 4th out of 5 tested platforms

Technical Recommendations

Based on combined testing observations and matrix results:

Critical Priorities:

1. Fix tab and reading order issues

2. Implement proper heading structure

3. Correct accordion implementation

4. Address zoom-related overflow issues

5. Improve video player accessibility

6. Fix form field implementation issues

Enhancement Opportunities:

1. Improve mobile menu usability

2. Add proper support for video captions

3. Implement better success message handling

4. Add autocomplete attributes to form fields

5. Improve skip link targeting

Conclusion

Wix has implemented some accessibility features successfully but requires significant improvement in several critical areas. The platform scored 57.83% on applicable accessibility checks, ranking 4th among tested platforms. While basic accessibility features like skip links and form labels are present, critical issues with content structure, keyboard navigation, and zoom behavior need addressing to achieve better accessibility compliance.