Accessibility Kiwi

Wording

• Clear structure for easy understanding.
• Clarified purpose of the content or the component.
• Start with the most important (descriptive) information.
• #Unique headings are beneficial.
• Clarity out of context is beneficial.
• One word or a single character may suffice.

Users

People with screen readers as well as people with visual perception usually navigate by grasping the first words when jumping from heading to heading.

Headings

<!-- Recommended -->
<h1>Kiwi preparation</h1>
<h2>Hatching</h2>
<h2>Growing</h2>

<!-- Not Recommended -->
<h1>Preparation for Kiwi</h1>
<h2>Preparation for Hatching</h2>
<h2>Preparation for Growing</h2>

<!-- Not Recommended -->
<h1>Preparation</h1>
<h2>Preparation</h2>
<h2>Preparation</h2>

Labels

Form input controls with labels that clearly describe the content that is expected to be entered helps users know how to successfully complete the form.

(w3.org)

Recommended

• “First Name” and “Last Name” clearly define the input. Starting with “First” and “Last” makes navigation faster in the “Name” group.

Not recommended

• Starting with “Name” for “First” and “Last”, because the input fields are in the “Name” group and don’t need this definition every time.
• Using the same label more than once in a group without clear differentiation, which part of the name is required.
• No label. They are not neccessarily required for this criterion, however, they should be included for better accessibility and fulfilling other criteria, for example 3.3.2: Labels or instructions.

Relations

• 1.3.1: Info and relationships (A) for programmatical determination.
• 2.4.4: Page titled (A) for navigation through pages and tabs.
• 3.3.2: Labels or instructions (A) as more detailed requirement for labels.
• 4.1.2: Name, role, value (A) for programmatical determination.