Accessibility Statement

Last updated: August 2026

Our Commitment to Accessibility

Folk Project is committed to providing an inclusive and accessible online experience for all visitors, including people with disabilities.

As a California-based company specializing in furniture, home décor, and handcrafted products, we believe our digital experience should be welcoming and usable by as many people as possible, regardless of ability or the technology used to access our websites.

Accessibility has been considered throughout the design, development, and optimization of our digital platforms. We are committed to continuously reviewing and improving the accessibility and usability of our websites.

Websites Covered by This Statement

This Accessibility Statement applies to Folk Project’s digital properties, including:

  • folk-project.com — our main website, providing information about Folk Project, our collections, our story, our artisans, and our work.

  • shop.folk-project.com — our online store, where visitors can browse products and complete purchases.

These websites use different technologies and platforms. The main website is powered by WordPress, while the online store is powered by Shopify.

We aim to provide a consistent and accessible experience across both platforms while recognizing that certain third-party technologies, themes, applications, and components may affect accessibility.

Accessibility Standards

Our websites are designed and developed with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA in mind.

WCAG is an internationally recognized set of recommendations for improving the accessibility of web content for people with a wide range of disabilities.

Our accessibility work takes into consideration the four fundamental principles of WCAG:

  • Perceivable — information and user interface components should be presented in ways that users can perceive.

  • Operable — navigation and functionality should be usable through different methods of interaction, including keyboard navigation.

  • Understandable — information and interface operation should be clear and predictable.

  • Robust — content should be compatible with a variety of browsers, assistive technologies, and other user tools.

Accessibility Practices and Improvements

As part of our accessibility efforts, we have reviewed and improved various aspects of our websites.

Structure and Navigation

We have reviewed the HTML structure and ARIA attributes used throughout the websites in order to improve the semantic structure and accessibility of interactive components.

Our work has included:

  • Reviewing HTML structure and ARIA implementations.

  • Identifying and removing broken links detected during accessibility reviews.

  • Reviewing broken or invalid ARIA references within dynamic components.

  • Reviewing keyboard navigation within interactive components.

  • Checking the use of tabindex and the accessibility of hidden elements within sliders and carousels.

  • Reviewing dynamically generated accessibility attributes to reduce invalid or unnecessary ARIA references.

  • Optimizing carousel and slider components where automatically generated accessibility attributes could create accessibility issues.

Particular attention has been given to interactive components such as Slick sliders and carousels, including their keyboard behavior, focus management, hidden slides, and automatically generated ARIA attributes.

Images and Alternative Text

We have reviewed the use of alternative text throughout the websites, with particular attention to product imagery.

Our accessibility work includes:

  • Reviewing alternative text (alt) on product images.

  • Configuring automated alternative-text generation through Tiny SEO where appropriate.

  • Establishing an ALT text pattern based on relevant product information, including the product name and store name.

  • Reviewing linked images and product thumbnails.

  • Identifying redundant alternative text and duplicate descriptions.

  • Reviewing cases where different images of the same product may require differentiated alternative text.

Alternative text is intended to provide meaningful information about informative images while avoiding unnecessary or repetitive descriptions for users of assistive technologies.

Content and Readability

We have also reviewed the visual and structural presentation of content to improve readability and accessibility.

This includes:

  • Reviewing text and background contrast.

  • Identifying accessibility issues associated with text embedded directly within images.

  • Maintaining a separation between visual imagery and textual content where this provides a clearer experience for users and assistive technologies.

  • Paying attention to content hierarchy and semantic organization.

  • Reviewing the readability and logical structure of content for screen reader users.

Where possible, important information is provided as actual page content rather than being communicated exclusively through an image.

E-commerce Accessibility

Accessibility considerations have also been applied to the e-commerce experience on shop.folk-project.com.

Our work has included reviewing product presentation, product imagery, interactive components, and elements generated by the Shopify theme and associated functionality.

We have also removed or disabled unnecessary review-related elements that were generating accessibility issues during testing and cleaned up unused functionality where appropriate in order to reduce unnecessary elements within the page structure and DOM.

Because the online store relies on Shopify, its theme, and potentially third-party applications and services, certain components may be generated automatically and may not be entirely within Folk Project’s control.

Accessibility Testing

Accessibility improvements have been supported by a combination of automated testing and manual review.

Testing and review have focused on areas including:

  • HTML and semantic structure.

  • ARIA attributes and references.

  • Keyboard navigation.

  • Focus behavior.

  • Interactive components and carousels.

  • Alternative text.

  • Color contrast.

  • Product imagery.

  • Forms and e-commerce functionality.

  • Dynamically generated content and components.

Automated accessibility tools are useful for identifying potential issues, but they cannot detect every accessibility barrier. For this reason, automated results are considered alongside manual review and practical testing of interactive components.

Known Limitations and Ongoing Improvements

While we have taken steps to improve accessibility across our websites, some accessibility issues may remain.

In particular, certain dynamic components and third-party or platform-generated functionality may produce accessibility attributes or behaviors that are not entirely within our control.

During accessibility reviews, we have identified areas such as:

  • ARIA references generated by third-party carousel functionality that may occasionally reference unavailable elements.

  • Decorative/technical zoom images: The product image zoom functionality generates additional technical image elements without alternative text. These images duplicate the primary product image and do not provide additional information to screen reader users.

  • Repeated or redundant alternative text in certain product image configurations.

  • Automatically generated ARIA roles and attributes within carousel components.

  • Automatically generated tabindex values within certain dynamic components.

  • Accessibility behaviors associated with third-party or platform-generated components.

  • Form upload field: The primary file input is correctly associated with a visible label. The Avada form from wordpress component generates an additional disabled text input used for the file-upload interface, which is flagged by automated accessibility testing as missing a form label. This auxiliary field is not user-editable and does not represent an independent form control.

  • Avada Image Select Field limitation: The Avada Image Select Field from wordpress provides a configurable Field Label, but the current component does not provide an option to render this label as a <legend> associated with the generated <fieldset>. Individual radio options are nevertheless provided with associated labels.

  • Same-page link: The “Back” button uses a dynamic same-page reference (#previousStep) handled by the Avada from wordpress multi-step form functionality. Automated testing identifies the reference as a broken same-page link because the corresponding target is not present as a conventional HTML anchor. The button was manually tested and correctly returns to the previous form step.

  • Automated testing may identify certain contact information, such as phone numbers or email addresses, as potential headings. These are not headings but correctly structured list items, and no corrective action is required.

  • Instagram feed – long alternative text: The third-party Instagram feed generates excessively long alternative text containing the full Instagram caption and hashtags. The image is marked aria-hidden=”true” and the feed provides a separate screen-reader text describing the content. The alternative text is generated automatically by the third-party plugin and cannot be configured through the current site settings.

Where possible, we have modified, disabled, or optimized these behaviors when they created identifiable accessibility issues. We continue to review these components as the websites evolve.

Some technical issues identified during testing, such as certain localStorage errors associated with sandboxed scripts or iframes, may be unrelated to the accessibility of the websites themselves and are therefore not necessarily considered accessibility barriers.

Accessibility is an ongoing process, and we will continue to work toward improving the accessibility and usability of our digital experience.

Third-Party Content and Services

Some features of our websites rely on third-party platforms, applications, themes, embedded content, payment services, or other external technologies.

These technologies may have their own accessibility characteristics and may not always be fully within Folk Project’s control.

Where possible, we aim to select, configure, and maintain third-party technologies in a way that supports an accessible user experience.

Accessibility Feedback

If you experience difficulty accessing any content or functionality on either of our websites, or if you identify an accessibility barrier, we encourage you to contact us.

Please provide, where possible:

  • The URL or location of the content where you encountered the issue.

  • A description of the accessibility barrier.

  • Information about the technology or device you were using, if relevant.

  • The type of assistance or alternative access you are requesting.

We will make reasonable efforts to review accessibility feedback and provide assistance or an alternative way to access the requested information or service whenever possible.

Contact:
folkproject1@gmail.com

Our Ongoing Commitment

Our goal is to make Folk Project’s digital experience as inclusive, usable, and accessible as reasonably possible.

We recognize that accessibility is an ongoing process rather than a one-time project. We will continue to review our websites, address accessibility barriers when identified, and consider accessibility as part of future design, development, content, and technology updates.

We welcome feedback from our visitors and customers and appreciate the opportunity to continue improving the accessibility of the Folk Project experience.

Last reviewed: August 2026