Define minimal standards for accessibility

[fashxp]

Minium requirements we need to fulfill:

Web Content Accessibility Guidelines (WCAG 2.2) Reference: Web Content Accessibility Guidelines (WCAG) 2.2

Perceivable - Information and user interface components must be presentable to users in ways they can perceive. 1.1.1 Non-text Content [How to meet] [Understanding]

1.3.1 Info and Relationships [How to meet] [Understanding] 1.3.2 Meaningful Sequence [How to meet] [Understanding] 1.3.3 Sensory Characteristics [How to meet] [Understanding]

1.4.1 Use of Color [How to meet] [Understanding] 1.4.5 Images of Text [How to meet] [Understanding]

Operable - User interface components and navigation must be operable. 2.1.1 Keyboard [How to meet] [Understanding] 2.1.2 No Keyboard Trap [How to meet] [Understanding]

2.4.3 Focus Order (where possible) [How to meet] [Understanding] 2.4.4 Link Purpose (In Context) [How to meet] [Understanding] 2.4.6 Headings and Labels [How to meet] [Understanding] 2.4.7 Focus Visible [How to meet] [Understanding] 2.4.11 Focus Not Obscured (Minimum) [How to meet] [Understanding] 2.5.7 Dragging Movements [How to meet] [Understanding] 2.5.8 Target Size (Minimum) [How to meet] [Understanding]

Understandable - Information and the operation of user interface must be understandable. 3.1.1 Language of Page [How to meet] [Understanding] 3.1.2 Language of Parts [How to meet] [Understanding] 3.1.4 Abbreviations [How to meet] [Understanding]

3.2.1 On Focus [How to meet] [Understanding] 3.2.2 On Input [How to meet] [Understanding] 3.2.4 Consistent Identification [How to meet] [Understanding] 3.2.6 Consistent Help [How to meet] [Understanding]

3.3.1 Error Identification [How to meet] [Understanding] 3.3.2 Labels or Instructions [How to meet] [Understanding] 3.3.3 Error Suggestion [How to meet] [Understanding] 3.3.8 Accessible Authentication (Minimum) [How to meet] [Understanding]

Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. 4.1.1 Parsing [How to meet] [Understanding] 4.1.2 Name, Role, Value [How to meet] [Understanding]

[fashxp]

DEV-Accessibility Basics-220224-152535.pdf

[fashxp]

To Check

• [x] 1.1.1 Non-text Content [How to meet] [Understanding]
• [x] 1.4.5 Images of Text [How to meet] [Understanding]

@brusch

[fashxp]

Next Steps:

• [ ] research for best practices for translation key structuring
• [ ] create guideline in confluence for 'what to consider' (based on list above) and 'how to check'

[brusch]

Haven't found anything specific to "tools that help creating content" regarding the 2 points to check above. But I'd rather classify it as a chicken-egg-problem, our product is made to create (accessible) content - this is what we need to ensure, not that every aspect of the product itself is accessible.

[vin0401]

@fashxp

These are the checks that are automatically applied via storybook and github actions: https://www.npmjs.com/package/eslint-plugin-jsx-a11y https://github.com/dequelabs/axe-core/blob/HEAD/doc/rule-descriptions.md

[fashxp]

• Definition see https://pimcore.atlassian.net/wiki/spaces/PD/pages/4013031425/UI+UX+Defined+Accessibility+Minimal+Standards
• Checklists see https://pimcore.atlassian.net/wiki/spaces/PD/pages/3957587983/UI+UX+Accessibility