You implement the product.

Use semantically correct elements

Always use semantically correct elements to support assisting technologies as much as possible. Distinguish all types of headlines, lists, tables etc. with the appropriate elements and set the correct language for your document.

Help for correct semantics: https://www.accessibility-developer-guide.com/examples

Reference 1: https://www.w3.org/TR/WCAG21/#info-and-relationships
Reference 2: https://www.w3.org/TR/WCAG21/#language-of-page

Use standard elements

Both in HTML and in mobile apps, native elements save you a great deal of hassle. The elements are already optimised in terms of accessibility; otherwise their entire behaviour must be recreated. Tell this to your designer too if they are insisting on something.

Help for typical non-native elements: https://inclusive-components.design

Reference: https://www.w3.org/TR/WCAG21/#name-role-value

Ensure correct linearization

Make sure that content is not only sensibly arranged visually, but also in the code. Try to make everything understandable if someone navigates from top to bottom through the document without CSS styling.

Testing: Switch off the CSS in the browser or use the screen reader on the phone.

Reference: https://www.w3.org/TR/WCAG21/#meaningful-sequence

Support orientation

At the start of a page, build in skip links and use different landmark elements. These two tools help users, particularly those with screen readers, to jump directly to the different parts of the content.

Help on skip links: https://webaim.org/techniques/skipnav
Overview of landmark elements: https://www.w3.org/WAI/ARIA/apg/practices/landmark-regions/

Reference: https://www.w3.org/TR/WCAG21/#bypass-blocks