Skip to Main Content

Main Story. 04. 02.

Polartec.com Accessibility Conformance Report

At Polartec (www.polartec.com), we are dedicated to providing a digitally accessible experience for all users, including individuals with disabilities. Our goal is to ensure that our website meets the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA standards and follows best practices to improve usability for everyone.


Our Commitment to Accessibility

Polartec is committed to creating an inclusive and user-friendly digital experience. To support accessibility on Polartec.com, we:

  • Integrate accessibility into our design and development processes
  • Provide ongoing accessibility training for our development team
  • Regularly audit our website to identify and address accessibility barriers
  • Encourage and incorporate feedback from users with disabilities
  • Respond promptly to accessibility concerns and suggestions


Feedback & Contact Information

If you encounter any accessibility barriers or have suggestions for improvement, please get in touch with us at [email protected] or fill out the form below. Your feedback is valuable in helping us create a more inclusive experience for all users.
 

Accessibility Feedback Form

Notes

This Accessibility Conformance Report is based on an audit performed on key user-facing pages and interactions within Polartec.com.

When issues related to a Success Criterion impact usability, explanations, and remarks have been provided to describe the extent of the issue and any known workarounds.

The following pages and interactions were evaluated as part of this audit:

  • Homepage
  • Product pages
  • Fabric pages / Search functionality
  • Partner Portal (Login & Registration)
  • Contact and Support pages

 

Testing focused on ensuring accessibility for all users, including those using assistive technologies such as screen readers, keyboard navigation, and alternative input devices. No third-party plugins or integrations beyond the core website functionality were included in the scope of this evaluation.

 

Evaluation Methods Used

A representative sampling approach was used to ensure efficient testing of similar page structures. For example, one product page was tested as a representative sample for all product listings, and one login screen was tested for authentication-related accessibility.

Each page was broken down into its key components, and various states (e.g., error messages, modal interactions, dynamic content updates) were analyzed.

Testing methods included:

  • Automated and guided manual testing: Using the axe DevTools Pro browser extension for identifying WCAG violations.
  • Advanced manual testing: Following the Axe Advanced Testing Coverage guide to ensure comprehensive testing beyond automated results.
  • Screen reader testing: Conducted using a combination of NVDA (Firefox), JAWS (Chrome), and VoiceOver (Safari).
  • Keyboard navigation testing: Ensuring full navigation and interaction without a mouse.
  • Color contrast analysis: Verifying text readability against background colors.

Additional testing was conducted for WCAG 2.2 AA Success Criteria not yet covered in automated tools.

 

Applicable Standards/Guidelines

The Web Content Accessibility Guidelines (WCAG) define requirements for improving accessibility. These guidelines have three levels of conformance: Level A, Level AA, and Level AAA. Polartec.com is partially conformant with WCAG 2.2 Level AA, meaning that while most of our content meets accessibility standards, some areas may still require improvement.

This report evaluates conformance with the following accessibility standards:

Standard/Guideline Included In Report
Web Content Accessibility Guidelines 2.0

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Web Content Accessibility Guidelines 2.1

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Web Content Accessibility Guidelines 2.2

Level A (Yes)

Level AA (Yes)

Level AAA (No)

 

Compatibility with Browsers & Assistive Technologies

Polartec.com is designed to be compatible with the following assistive technologies:

  • Modern web browsers (Chrome, Firefox, Edge, Safari) with screen readers.
  • Mobile and desktop operating systems that support accessibility features.

Polartec.com may not be fully compatible with:

  • Browsers older than 3 major versions.
  • Mobile operating systems older than 5 years.
     

Technical Specifications

The accessibility of Polartec.com relies on the following technologies:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript
  • SVG
  • PDF

These technologies ensure compatibility with various assistive tools.

 

Limitations & Alternatives

Despite our best efforts, some accessibility limitations may exist. Below are known limitations and solutions:

Known Limitations Description Solution
User-generated content Some uploaded images may lack text alternatives. We monitor and address missing alt text within 10 business days. Please report issues to us.
Archived documents Older documents may not fully support screen readers. We convert documents to accessible formats upon request within 3 business days. Contact us for assistance.

If you encounter an issue not listed above, please reach out to us.

 

Terms

The terms used in the Conformance Level information are defined as follows:

  • Supports: The functionality of the website has at least one method that fully meets the criterion without known defects or provides an equivalent alternative.
  • Supports: Some website functionality does not fully meet the criterion.
  • Does Not Support: The majority of website functionality does not meet the criterion.
  • Not Applicable: The criterion is not relevant to the website.
  • Not Evaluated: The website has not been tested against this criterion (only applicable to WCAG 2.0 Level AAA).

1 Perceivable

1.1 Text Alternatives

Success Criterion Result Observations
1.1.1: Non-text Content
Entire sample

Result: Passed

All non-text content, such as images and icons, includes appropriate alternative text for screen reader users. Decorative images are correctly marked to be ignored.

1.2 Time-based Media

Success Criterion Result Observations
1.2.1: Audio-only and Video-only (Prerecorded)
Entire sample

Result: Not present

Prerecorded audio-only and video-only content is missing text-based alternatives

1.2.2: Captions (Prerecorded)
Entire sample

Result: Passed

All prerecorded videos include synchronized captions that accurately reflect spoken dialogue and important audio cues.

1.2.3: Audio Description or Media Alternative (Prerecorded)
Entire sample

Result: Not present

Prerecorded videos do not include audio descriptions or a media alternative for users who are blind or have low vision.

1.2.4: Captions (Live)
Entire sample

Result: Passed

Live video content includes captions that make the content accessible to users who are deaf or hard of hearing.

1.2.5: Audio Description (Prerecorded)
Entire sample

Result: Not present

No audio descriptions are provided for visual content that conveys important information in prerecorded videos.

1.3 Adaptable

Success Criterion Result Observations
1.3.1: Info and Relationships
Entire sample

Result: Passed

Semantics and structure are conveyed programmatically using proper HTML elements and ARIA attributes.

1.3.2: Meaningful Sequence
Entire sample

Result: Passed

Content is presented in a logical reading order, ensuring accessibility when using assistive technologies.

1.3.3: Sensory Characteristics
Entire sample

Result: Passed

Instructions do not rely solely on shape, size, color, or sound to convey meaning.

1.3.4: Orientation
Entire sample

Result: Passed

Content is operable in both portrait and landscape orientations without loss of functionality.

1.3.5: Identify Input Purpose
Entire sample

Result: Passed

Input fields use correct autocomplete attributes, helping users with cognitive disabilities or using password managers.

1.4 Distinguishable

Success Criterion Result Observations
1.4.1: Use of Color
Entire sample

Result: Passed

Color is not used as the sole means of conveying information.

1.4.2: Audio Control
Entire sample

Result: Passed

Audio that plays automatically includes controls to pause or stop the sound.

1.4.3: Contrast (Minimum)
Entire sample

Result: Passed

Text and background color combinations meet minimum contrast requirements for readability.

1.4.4: Resize text
Entire sample

Result: Passed

Content remains readable and functional when text size is increased up to 200%.

1.4.5: Images of Text
Entire sample

Result: Passed

Images of text are avoided unless essential; text is presented using real text where possible.

1.4.10: Reflow
Entire sample

Result: Passed

Content reflows appropriately when zoomed or resized, ensuring usability without horizontal scrolling.

1.4.11: Non-text Contrast
Entire sample

Result: Passed

Visual elements such as icons and focus indicators meet contrast requirements.

1.4.12: Text Spacing
Entire sample

Result: Passed

The design does not prevent the user from overriding text spacing properties for readability.

1.4.13: Content on Hover or Focus
Entire sample

Result: Passed

Any additional content that appears on hover or focus is dismissible, hoverable, and persistent.

2 Operable

2.1 Keyboard Accessible

Success Criterion Result Observations
2.1.1: Keyboard
Entire sample

Result: Passed

All functionality is accessible via keyboard alone, without requiring mouse input.

2.1.2: No Keyboard Trap
Entire sample

Result: Passed

Users can navigate freely using the keyboard and are not trapped in any component.

2.1.4: Character Key Shortcuts
Entire sample

Result: Not present

No character key shortcuts are present that would conflict with screen reader or keyboard functionality.

2.2 Enough Time

Success Criterion Result Observations
2.2.1: Timing Adjustable
Entire sample

Result: Not present

Time limits, if applicable, are not user-adjustable, potentially impacting users who need more time.

2.2.2: Pause, Stop, Hide
Entire sample

Result: Not present

There is no mechanism to pause, stop, or hide moving, blinking, or auto-updating content if present.

2.3 Seizures and Physical Reactions

Success Criterion Result Observations
2.3.1: Three Flashes or Below Threshold
Entire sample

Result: Passed

No content flashes more than three times in a second, minimizing seizure risk.

2.4 Navigable

Success Criterion Result Observations
2.4.1: Bypass Blocks
Entire sample

Result: Passed

Mechanisms like skip links are present to allow users to bypass repeated content.

2.4.2: Page Titled
Entire sample

Result: Passed

Pages have meaningful and descriptive titles that aid in orientation.

2.4.3: Focus Order
Entire sample

Result: Passed

Focusable elements receive focus in a logical order consistent with the visual layout.

2.4.4: Link Purpose (In Context)
Entire sample

Result: Passed

Link text is descriptive and meaningful even when taken out of context.

2.4.5: Multiple Ways
Entire sample

Result: Passed

More than one way is provided to locate a web page within the site.

2.4.6: Headings and Labels
Entire sample

Result: Passed

Headings and labels are descriptive and help users understand the purpose of content.

2.4.7: Focus Visible
Entire sample

Result: Passed

A visible indicator is present when elements receive focus.

2.4.11: Focus Not Obscured (Minimum)
Entire sample

Result: Passed

Focus indicators are not hidden or obscured by other elements.

2.5 Input Modalities

Success Criterion Result Observations
2.5.1: Pointer Gestures
Entire sample

Result: Passed

All functionality can be operated using simple gestures, with no need for complex or multipoint gestures.

2.5.2: Pointer Cancellation
Entire sample

Result: Passed

Actions initiated by pointer input can be aborted before completion, minimizing accidental activation.

2.5.3: Label in Name
Entire sample

Result: Passed

The accessible name for UI elements matches visible labels, ensuring compatibility with voice control.

2.5.4: Motion Actuation
Entire sample

Result: Passed

Functionality is not reliant on motion-based gestures and includes alternatives.

2.5.7: Dragging Movements
Entire sample

Result: Not present

No dragging interactions were observed that would require alternatives for users with limited mobility.

2.5.8: Target Size (Minimum)
Entire sample

Result: Passed

Clickable elements meet minimum size requirements, aiding users with limited motor control.

3 Understandable

3.1 Readable

Success Criterion Result Observations
3.1.1: Language of Page
Entire sample

Result: Passed

The page language is correctly declared in the HTML, aiding screen reader users.

3.1.2: Language of Parts
Entire sample

Result: Passed

Changes in language within the content are correctly identified for assistive technology.

3.2 Predictable

Success Criterion Result Observations
3.2.1: On Focus
Entire sample

Result: Passed

No unexpected context changes occur when elements receive focus.

3.2.2: On Input
Entire sample

Result: Passed

Changes in input fields do not result in unexpected changes to the page context.

3.2.3: Consistent Navigation
Entire sample

Result: Passed

Navigation elements appear in consistent locations across pages.

3.2.4: Consistent Identification
Entire sample

Result: Passed

UI components that appear multiple times are consistently identified.

3.2.6: Consistent Help
Entire sample

Result: Not present

There is no clear help mechanism or support consistently available across the site.

3.3 Input Assistance

Success Criterion Result Observations
3.3.1: Error Identification
Entire sample

Result: Cannot tell

Forms could not be fully tested; unclear if error messages are provided when validation fails.

3.3.2: Labels or Instructions
Entire sample

Result: Passed

Input fields include appropriate labels or instructions to guide user input.

3.3.3: Error Suggestion
Entire sample

Result: Passed

When input errors are detected, suggestions are provided to correct them.

3.3.4: Error Prevention (Legal, Financial, Data)
Entire sample

Result: Not present

No mechanisms were observed to prevent errors in sensitive transactions.

3.3.7: Redundant Entry
Entire sample

Result: Not present

No features are present to prevent users from re-entering previously provided information.

3.3.8: Accessible Authentication (Minimum)
Entire sample

Result: Passed

Authentication does not rely on cognitive tests like puzzles and supports password managers.

4 Robust

4.1 Compatible

Success Criterion Result Observations
4.1.2: Name, Role, Value
Entire sample

Result: Passed

UI components have programmatically determined names, roles, and states for assistive technologies.

4.1.3: Status Messages
Entire sample

Result: Passed

Status messages are announced by screen readers without requiring focus.

Hello. You can get in touch with us using the form below.

Welcome in.

From Industry insider access to community updates, stay in the loop with everything we do.