Accessibility is never an afterthought.
We build FaStart toward WCAG 2.1 AA: keyboard navigation, visible focus, semantic structure, and readable contrast, from the very start of the design. This is not a finished certification, it is work we keep doing.
The four principles we design against
Perceivable
Content you can see and hear: text, contrast, and alternatives.
Operable
Everything works by keyboard and pointer, with no traps.
Understandable
Interfaces that are consistent, predictable, and easy to read.
Robust
Clean, semantic markup that works with assistive technology.
This page is FaStart's accessibility commitment. We are working toward WCAG 2.1 AA: keyboard access, visible focus rings, semantic HTML, and readable contrast are designed in from the start. This is ongoing work, not a finished certification; if you hit a barrier, tell us and we will prioritize it.
Our commitment
Toward WCAG 2.1 AA, step by step
We build FaStart toward level AA of the Web Content Accessibility Guidelines (WCAG) 2.1. That means an interface that is not only well designed but navigable by keyboard, readable with screen readers, and legible even with low vision. We apply these principles as we design new screens, rather than patching them in later.
Let us be honest: accessibility is not a finished certification, it is ongoing work. As the product grows, new screens arrive, and we keep reviewing them so each one holds the same bar. In some flows we are not yet where we want to be; we know it and we fix it in turn. That is why we do not say 'certified' or 'fully compliant', because this is a direction, not a destination.
What we aim for
We take WCAG 2.1 AA as our reference and design every new screen against it.
Where we stand
The foundations are in place; some flows are still improving, and we know exactly which.
What we don't claim
We do not claim a third-party audit or a 'fully compliant' badge.
The practices that make accessibility concrete
We clearly separate what sits in the product's foundation today from what is still on the way.
Keyboard navigation and visible focus
Menus, forms, and buttons work with a keyboard, not only a mouse. The focused element is always marked with a visible ring, so you never lose track of where you are.
Semantic HTML and ARIA
We build the interface with headings, landmarks, and correct roles. We add ARIA labels where needed so screen readers can read the page in a meaningful way.
Contrast and readable type
We aim for enough contrast between text and background, comfortable font sizes, and line spacing. We review the remaining edge cases on a regular basis.
Responsive layout and text zoom
Pages adapt smoothly from phone to desktop. When you enlarge the text, content reflows without overflowing and without forcing you into horizontal scrolling.
Accessible theme defaults
Storefront themes start with legible sizes, sufficient contrast, and keyboard-usable components. Because final contrast also depends on the colors you pick, we keep the defaults on the safe side.
Skip-to-content link
A link that lets keyboard users skip past repeated menus and jump straight to the content is on our near-term roadmap across all apps; we will say so plainly when it goes live.
Conformance
Toward WCAG 2.2 AA: an honest statement
How we describe FaStart's accessibility conformance today, without overstating it.
Conformance statement
We evaluate FaStart against the Web Content Accessibility Guidelines, Level AA. Today our working reference is WCAG 2.1 AA, and we are moving that target to WCAG 2.2 AA as we adopt its newer criteria. This is our own assessment of ongoing work, not a third-party audit and not a certification.
In the language accessibility statements use, we would describe FaStart as partially supporting Level AA: the core patterns are in place and some flows are still improving. That is why we do not use the words 'certified' or 'fully compliant' anywhere, we would rather tell you plainly where the work stands.
This statement is reviewed regularly. Last reviewed: July 2026.
Conformance at a glance
- Live
Design against WCAG 2.1 AA
Level AA success criteria are our reference on every new screen.
- Live
Ongoing internal self-review
We re-check contrast, focus, and keyboard paths as flows change.
- Roadmap
Adopting the new WCAG 2.2 AA criteria
We plan to align our target with the additional 2.2 success criteria.
- Roadmap
Formal conformance report (VPAT-style)
A documented, criterion-by-criterion report is planned; not published yet.
A formal conformance report is on the roadmap
A documented, criterion-by-criterion accessibility conformance report, sometimes called a VPAT or an ACR, is planned. It will record, one success criterion at a time, what FaStart supports, partially supports, or does not yet support, based on our own testing. We have not published one yet, so this is shown as a concept, not a result.
Accessibility Conformance Report
WCAG 2.2 AA · self-assessment · draft
Criterion-by-criterion results will appear here.
How to keep your store accessible
Themes start with accessible defaults. As you build, these three habits make the biggest difference.
Keep the contrast
When you change colors, keep enough contrast between text and background; avoid pale text on a light field.
Alt text on images
Add short, descriptive alternative text to product and content images; screen readers and search both benefit.
Legible sizes
Keep font sizes legible and don't bake text into images; it should stay readable when enlarged.
Report an issue
Hit a barrier? Write to us directly at accessibility@fastart.co, or use our contact page. If you could not use a page with a keyboard, a screen reader skipped something, or the contrast was hard for you, we want to hear it; add the barrier you hit, the device you used, and your assistive technology so we can resolve it faster.
What happens next
We treat every incoming access report like a bug: we reproduce it, prioritize it by how many people it affects and how severe the barrier is, and put the fix on our plan. We put major barriers ahead of small refinements.
Need this text in another format?
If you prefer, we'll send this statement in another format, such as large print, simplified language, or plain text. Just ask; write to accessibility@fastart.co.
Commerce should work for everyone.
You can't choose in advance who visits your store. Someone using a keyboard, listening with a screen reader, or enlarging the text should be able to finish the purchase too. That is why we design accessibility in from the very start.
Frequently asked questions
Is FaStart accessibility certified?
No. We target WCAG 2.1 AA and build the product against those principles, but we do not claim a third-party audit or a 'fully compliant' badge. Accessibility is ongoing work for us, and we will not present something as done before it is.
Which accessibility practices are in place today?
Keyboard navigation with visible focus rings, semantic HTML and ARIA, readable typography with attention to contrast, and responsive layouts with text zoom are part of the product's foundation today. Storefront themes ship with accessible defaults too; final contrast also depends on the colors you choose.
What should I do if I hit an accessibility barrier?
Write to us from our contact page and describe the barrier along with the device and assistive technology you use. We treat access barriers like bugs and prioritize them.
How do I keep my store accessible as I build it?
Themes start with accessible defaults: legible font sizes, sufficient contrast, and keyboard-usable components. When you change colors and images, keep contrast in mind and add descriptive alternative text to images; those two habits make the biggest difference.
Is there full screen-reader support?
We build with semantic HTML and ARIA with screen readers in mind, and we keep widening coverage. Still, rather than claim 'full support', we prefer to be honest: some flows are more mature than others. If you spot a gap, tell us and we will get to it quickly.
Part of the same commitment
Accessibility, trust, and responsibility are parts of the same whole.
Build a store everyone can use.
Try FaStart in the demo, then get started. Accessibility is not a finished job for us; if you spot a barrier along the way, we want to hear it.