Jonatan Witoszek

In each place where we show/hide elements on a page based on interaction, we should use the Disclosure component pattern. WAI APG docs: https://www.w3.org/WAI/ARIA/apg/patterns/disclosure/ - `aria-expanded` for the container element...

We can improve our current HTML structure so that it's easier to navigate by screen readers: - Move "Order summary" to be the 1st element in the HTML (it's already...

If there's an error inside our checkout form, then the "Pay" button is disabled. We should provide a reason why (at least for screen readers by using `aria-describedby`) in a...

Our Radiobox components used inside delivery methods and payment methods are not accessible by keyboard and screen readers. It should adhere to WAI APG specification: https://www.w3.org/WAI/ARIA/apg/patterns/radiobutton/

Our current form inputs aren't really accessible. Here's an action list on what we can improve: - Link `` with `` by using `for=` attribute - Link error messages with...

Add autocomplete attributes to form elements so that browsers and password maangers (e.g. 1Password) can easily enter correct data in the forms automatically. Shipping and billing address should be differentiated...

Our current `` component isn't focusable by keyboard and is not visible to screen readers. It also doesn't support arrow navigation. It should confront to the Listbox specification defined in...

Handle authenticated checkout

3

## Problem Right now, if a user signs into storefront with their account and adds items to a cart, we create a checkout session that is assigned to this specific...

Add Sentry integration based on work made in [`saleor-app-template`](https://github.com/saleor/saleor-app-template/pull/53)

Void transactions in Adyen when received `transaction-action-request` event from Saleor with `actionType` - `VOID`