UX

• WCAG
• Personas

WCAG

Notes for content

• 1.2
  • YT videos must be accessible (sign language, audio content)
• no flashes
• must be in easy language
• no abbreviations
• no unusual words

Notes for UX

• 1.3.3
• 1.4.3

other notes

• the text in the search bar is truncated sometimes. This could be a problem
• we need a replacement for the banner

questions

• 1.4.8 should we specifiy line-height or not??
• 1.4.9 how labels in map??
• 2.2 not applicable, right? even with map-flying and lazy-loading?
• does 2.4.1 apply?
• 2.4.8 what would be necessary?
• 2.5.2 nothing to do, right?
• 2.5.5 and map markers?
• is the scrolling / gesture thing a problem?
• 3.1.2 relevant?
• 3.2 discuss change of context
• 3.3.3 guidance on filters / maps ?
• how to handle map clusters?
• one-pointer & smartphone two-finger a problem?
• 3.2.2 live search?

Time need

• First check (this one)
  •  7h first pass and creating this list
  • +1h
• Implementing: 53h
  
• Consulting specialists: 3h + 2h
  
• Taking iterations after being checked: 10h

⇒ 76h

Legend

• done / nothing to do
  
• easy
• not-now / content
  
• some work
• hard

1 Perceivable: 22h

1.1 Text alternatives: 1h

Level A

1.1.1 Non-text content: 1h

• alt-label
• SK: easy

1.2 Time-based media: only content: 1h

• Concerns time-based media like videos and audio. As SK itself doesn't use any of those media, this is not relevant now. But this means, ^^we need to take care when embedding Youtube videos.^^
• Level AAA goes up to sign language! We might need to disallow YT altogether?

1.3 Adaptable: 6h

Level A: 3h

1.3.1 Info and Relationships: 3h

• huge field, rather unspecific in the specification
• Aria labels, semantic structure.
• probably hard to get everything right on the first try, but most of it should be fairly straightforward

1.3.2 Meaningful sequence

• When the sequence in which content is presented affects its meaning, a [[https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence.html#dfn-correct-reading-sequence][correct reading sequence]] can be [[https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence.html#dfn-programmatically-determined][programmatically determined]].

• Not really a problem, I'd say.

1.3.3 Sensory characteristics: for UX

• Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound.

• Need to also write category, not only icon
• Filters need to explicit. Not only color-coding. (Was an idea for tags menu)
• Needs to be considered for visual UX

Level AA: 1h

1.3.4 Orientation

• Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is [[https://www.w3.org/WAI/WCAG21/Understanding/orientation.html#dfn-essential][essential]].

• That already works

1.3.5 Identify Input Purpose: 1h

• The purpose of each input field collecting information about the user can be [[https://www.w3.org/WAI/WCAG21/Understanding/identify-input-purpose.html#dfn-programmatically-determined][programmatically determined]] when:

  • The input field serves a purpose identified in the [[https://www.w3.org/WAI/WCAG21/Understanding/identify-input-purpose.html#input-purposes][Input Purposes for user interface components section]]; and

  • The content is implemented using technologies with support for identifying the expected meaning for form input data.

• Affects search and filters

Level AAA: 2h

1.3.6 Identify Purpose: 2h

• In content implemented using markup languages, the purpose of [[https://www.w3.org/WAI/WCAG21/Understanding/identify-purpose.html#dfn-user-interface-component][user interface components]], icons, and [[https://www.w3.org/WAI/WCAG21/Understanding/identify-purpose.html#dfn-region][regions]] can be [[https://www.w3.org/WAI/WCAG21/Understanding/identify-purpose.html#dfn-programmatically-determined][programmatically determined]].

• ARIA landmarks
• own Icon sets? Aria Icons!

1.4 Distinguishable: 14h

Level A: 0h

1.4.1 Use of color

• Color is not used as the only visual means of conveying information, indicating an ation, prompting a response, or distinguishing a visual element.

• we already have this :PROPERTIES: :background-color: green :END:

1.4.2 Audio control

Level AA: 10h

1.4.3 Contrast (Minimum)

• in general, we meet this easily
• only affects which images we may use if it contains relevant text

1.4.4 Resize Text: 0h. Actually just works (Take 1h as buffer)

• Except for [[https://www.w3.org/WAI/WCAG21/Understanding/resize-text.html#dfn-captions][captions]] and [[https://www.w3.org/WAI/WCAG21/Understanding/resize-text.html#dfn-image-of-text][images of text]], [[https://www.w3.org/WAI/WCAG21/Understanding/resize-text.html#dfn-text][text]] can be resized without [[https://www.w3.org/WAI/WCAG21/Understanding/resize-text.html#dfn-assistive-technology][assistive technology]] up to 200 percent without loss of content or functionality.
  
  

  The scaling of content is primarily a user agent responsibility. User agents that satisfy [[https://www.w3.org/TR/WAI-USERAGENT/guidelines.html#tech-configure-text-scale][UAAG 1.0 Checkpoint 4.1]] allow users to configure text scale. The author's responsibility is to create Web content that does not prevent the user agent from scaling the content effectively.
  
  

  The author cannot rely on the user agent to satisfy this Success Criterion for HTML content if users do not have access to a user agent with zoom support. For example, if they work in an environment that requires them to use IE 6.

• zoom ≠ text resizing
• as I understand this, we comply by just not messing up the design when zooming text
• SK assessment
  • Map labels get bigger as well, but get pixelated
  • Banner images don't scale (need anyway responive version)
  • need to fix the footer

1.4.5 Images of text: 1h for banner integration

• If the technologies being used can achieve the visual presentation, [[https://www.w3.org/WAI/WCAG21/Understanding/images-of-text.html#dfn-text][text]] is used to convey information rather than [[https://www.w3.org/WAI/WCAG21/Understanding/images-of-text.html#dfn-image-of-text][images of text]] except for the following:

  • Customizable: The image of text can be [[https://www.w3.org/WAI/WCAG21/Understanding/images-of-text.html#dfn-visually-customized][visually customized]] to the user's requirements;
  • Essential: A particular presentation of text is [[https://www.w3.org/WAI/WCAG21/Understanding/images-of-text.html#dfn-essential][essential]] to the information being conveyed.

• SK assessment
  • I consider map essential
  • logo is essential
  • ^^footer banner again^^

1.4.10 Reflow: 1h

• Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 [[https://www.w3.org/WAI/WCAG21/Understanding/reflow.html#dfn-css-pixel][CSS pixels]]; Except for parts of the content which require two-dimensional layout for usage or meaning.

• SK assessment
  • Works fine
  • Prefilled search bar text is too wide?
  • Tags are scrolled horizontally. But tags go
    
  • banner again

1.4.11 Non-text contrast: 4h

• The visual [[https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html#dfn-presentation][presentation]] of the following have a [[https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html#dfn-contrast-ratio][contrast ratio]] of at least 3:1 against adjacent color(s):

• User Interface Components Visual information required to identify [[https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html#dfn-user-interface-component][user interface components]] and [[https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html#dfn-state][states]], except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
• Graphical Objects Parts of graphics required to understand the content, except when a particular presentation of graphics is [[https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html#dfn-essential][essential]] to the information being conveyed.
• https://bootcamp.uxdesign.cc/wcag-accessible-colour-and-contrast-ratios-5e94ea3f81f4
• SK assessment
  • probably relevant for cards
  • maybe menus?
  • how much is 3:1?
  • links in header
  • map style!
  • clusters
  • icons on map!
  • icons on cards!
  • banner
  • tag pills (overwie and details)

1.4.12 Text spacing: 3h

• In content implemented using markup languages that support the following [[https://www.w3.org/WAI/WCAG21/Understanding/text-spacing.html#dfn-text][text]] [[https://www.w3.org/WAI/WCAG21/Understanding/text-spacing.html#dfn-style-property][style properties]], no loss of content or functionality occurs by setting all of the following and by changing no other style property:

• Line height (line spacing) to at least 1.5 times the font size;
• Spacing following paragraphs to at least 2 times the font size;
• Letter spacing (tracking) to at least 0.12 times the font size;
• Word spacing to at least 0.16 times the font size.

• Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.

• CSS
  

body {
  letter-spacing: 0.12em;
  line-height: 150%;
  word-spacing: 0.16em;
}
p {
  margin-bottom: 2em;
}

• SK assessment
  • cards overflow vertically probably. Need elipsis. activation -> click on card
  • ^^footer flow into each other^^
  • ^^headings' line height is overwritten (see heading Göteborg)^^
  • drop-down, tags, search-default, hamburger, language-selector, load-more button not affected
  • we set p>margin-bottom at some point
  • easy, but might affect design

1.4.13 Content on hover or focus: 0h

• Where receiving and then removing pointer hover or keyboard focus triggers > additional content to become visible and then hidden, the following are true: […]

• We don't have such content right now. This would be for example a menu, that opens up on hover. Probably not happening.

Level AAA: 4h

1.4.6 Contrast (enhanced): 2h

• The visual presentation of [[https://www.w3.org/WAI/WCAG21/Understanding/contrast-enhanced.html#dfn-text][text]] and [[https://www.w3.org/WAI/WCAG21/Understanding/contrast-enhanced.html#dfn-image-of-text][images of text]] has a [[https://www.w3.org/WAI/WCAG21/Understanding/contrast-enhanced.html#dfn-contrast-ratio][contrast ratio]] of at least 7:1, except for the following: […]

• stronger version of 1.4.3
  
• ^^We need a walk-throuh in the end for checking and fixing the issues. This should be easy then.^^
• Banner!

1.4.7 Low or no background audio: 0h

1.4.8 Visual representation: 2h

For the visual presentation of [[https://www.w3.org/WAI/WCAG21/Understanding/visual-presentation.html#dfn-blocks-of-text][blocks of text]], a [[https://www.w3.org/WAI/WCAG21/Understanding/visual-presentation.html#dfn-mechanism][mechanism]] is available to achieve the following:

• Text is not justified (aligned to both the left and the right margins).
  
• ^^Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.^^
  
• Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text [[https://www.w3.org/WAI/WCAG21/Understanding/visual-presentation.html#dfn-on-a-full-screen-window][on a full-screen window]].

• SK assessment
  • this is only relevant for "blocks of text" i.e. main content
  • this is currently working for SK
  • background is not working
  • card-text is not colored
  • small windows work
  • we don't use justification
  • how about the page becoming unreadable by changing background-colors?
  • https://www.w3.org/WAI/WCAG21/Understanding/visual-presentation.html -> sufficient techniques
  • things are a bit unclear, but probably easy to implement

1.4.9 images of text (no exception): 1h for banner. Already in AA -> 0h

https://www.w3.org/WAI/WCAG21/Understanding/images-of-text-no-exception.html

• [[https://www.w3.org/WAI/WCAG21/Understanding/images-of-text-no-exception.html#dfn-image-of-text][Images of text]] are only used for [[https://www.w3.org/WAI/WCAG21/Understanding/images-of-text-no-exception.html#dfn-pure-decoration][pure decoration]] or where a particular presentation of [[https://www.w3.org/WAI/WCAG21/Understanding/images-of-text-no-exception.html#dfn-text][text]] is [[https://www.w3.org/WAI/WCAG21/Understanding/images-of-text-no-exception.html#dfn-essential][essential]] to the information being conveyed.

• SK
  • replace banner, otherwise fine
  • ^^how Map?!^^

2 Operable: 21h

2.1 Keyboard accessible: 3h

Level A: 3h

2.1.1 Keyboard: 3h

• All [[https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html#dfn-functionality][functionality]] of the content is operable through a [[https://www.w3.org/WAI/WCAG21/Understanding/keyboard.html#dfn-keyboard-interface][keyboard interface]] without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

• Means for us that the focus order reaches all elements. Should work.
• There is a focus-loop on the map right now, but should work.
• pop-ups don't work

2.1.2 No keyboard trap: 0h

• I don't find any keyboard traps.

2.1.4 Character key shortcuts: 0h

• we don't have shortcuts

Level AAA: 0h

2.1.3 Keyboard (no exception): -> 0h

• All [[https://www.w3.org/WAI/WCAG21/Understanding/keyboard-no-exception.html#dfn-functionality][functionality]] of the content is operable through a [[https://www.w3.org/WAI/WCAG21/Understanding/keyboard-no-exception.html#dfn-keyboard-interface][keyboard interface]] without requiring specific timings for individual keystrokes.

• same as (-> Keyboard) since the exception is not relevant

2.2 Enough time: 0h

• as our UI doesn't use timing at all, this is not relevant

2.3 Seizures and physical reactions: 1h

Level A

2.3.1 Three flashes ro below threshold

• relevant for videos we embed

Level AAA

2.3.2 Three flashes

• same as for (-> 2.3.1) holds

2.3.3 Animation from interaction: 1h

• [[https://www.w3.org/WAI/WCAG21/Understanding/animation-from-interactions.html#dfn-motion-animation][Motion animation]] triggered by interaction can be disabled, unless the animation is [[https://www.w3.org/WAI/WCAG21/Understanding/animation-from-interactions.html#dfn-essential][essential]] to the functionality or the information being conveyed.

• currently only relevant for the map-fly and probably scroll-up at region change. both can be disabled easily. Maybe we can jump up?

2.4 Navigable: 14h

Level A: 5h

2.4.1 Bypass blocks: 1h

• A [[https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html#dfn-mechanism][mechanism]] is available to bypass blocks of content that are repeated on multiple [[https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html#dfn-web-page][Web pages]].

• Not sure if it applies. But easy

2.4.2 Page titled: 1h

2.4.3 Focus order: 1h

• If a [[https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html#dfn-web-page][Web page]] can be [[https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html#dfn-navigated-sequentially][navigated sequentially]] and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

• right now, good

2.4.4 Link purpose (in context): 2h

• The [[https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html#dfn-link-purpose][purpose of each link]] can be determined from the link text alone or from the link text together with its [[https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html#dfn-programmatically-determined-link-context][programmatically determined link context]], except where the purpose of the link would be [[https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html#dfn-ambiguous-to-users-in-general][ambiguous to users in general]].

Level AA: 5h

2.4.5 Multiple ways: 1h because things need an overhaul

• More than one way is available to locate a [[https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways.html#dfn-web-page][Web page]] within a [[https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways.html#dfn-set-of-web-pages][set of Web pages]] except where the Web Page is the result of, or a step in, a [[https://www.w3.org/WAI/WCAG21/Understanding/multiple-ways.html#dfn-process][process]].

• SK provides several ways
  • search
  • map
  • sitemap
  • scrolling the huge list

2.4.6 Headings and labels: 2h

• Headings and [[https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels.html#dfn-label][labels]] describe topic or purpose.

2.4.7 Focus visible: 2h

• Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

• needs to be fixed

Level AAA: 4h

2.4.8 Location: 2h

• Information about the user's location within a [[https://www.w3.org/WAI/WCAG21/Understanding/location#dfn-set-of-web-pages][set of Web pages]] is available.

• it's probably easy to give more clues, but is that necessary?

2.4.9 Link purpose (link only): 2.4.4 + 1h

• A [[https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-link-only#dfn-mechanism][mechanism]] is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be [[https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-link-only#dfn-ambiguous-to-users-in-general][ambiguous to users in general]].

• SK
  • interesting for
    • footer
    • cards
    • map markers
    • map clusters
    • should be fairly easy once identified

2.4.10 Section headings: 1h

• [[https://www.w3.org/WAI/WCAG21/Understanding/section-headings#dfn-section][Section]] headings are used to organize the content.

2.5 Input modalities: 3h

Level A: 2h

2.5.1 Pointer gestures: 0h

• All [[https://www.w3.org/WAI/WCAG21/Understanding/pointer-gestures.html#dfn-functionality][functionality]] that uses multipoint or path-based gestures for operation can be operated with a [[https://www.w3.org/WAI/WCAG21/Understanding/pointer-gestures.html#dfn-single-pointer][single pointer]] without a path-based gesture, unless a multipoint or path-based gesture is [[https://www.w3.org/WAI/WCAG21/Understanding/pointer-gestures.html#dfn-essential][essential]].

• relevant for map
• is already the case
• we have zoom buttons
• it's not path based

2.5.2 Pointer cancellation: 0h

• For [[https://www.w3.org/WAI/WCAG21/Understanding/pointer-cancellation#dfn-functionality][functionality]] that can be operated using a [[https://www.w3.org/WAI/WCAG21/Understanding/pointer-cancellation#dfn-single-pointer][single pointer]], at least one of the following is true:

  • No Down-Event: The [[https://www.w3.org/WAI/WCAG21/Understanding/pointer-cancellation#dfn-down-event][down-event]] of the pointer is not used to execute any part of the function; ** Abort or Undo: Completion of the function is on the [[https://www.w3.org/WAI/WCAG21/Understanding/pointer-cancellation#dfn-up-event][up-event]], and a [[https://www.w3.org/WAI/WCAG21/Understanding/pointer-cancellation#dfn-mechanism][mechanism]] is available to abort the function before completion or to undo the function after completion;
  • Up Reversal: The up-event reverses any outcome of the preceding down-event;
  • Essential: Completing the function on the down-event is [[https://www.w3.org/WAI/WCAG21/Understanding/pointer-cancellation#dfn-essential][essential]].

• Only see a difference for drop-down (undo) and vanishing tooltips on the map.

2.5.3 Label in name: 1h

• For [[https://www.w3.org/WAI/WCAG21/Understanding/label-in-name#dfn-user-interface-component][user interface components]] with [[https://www.w3.org/WAI/WCAG21/Understanding/label-in-name#dfn-label][labels]] that include [[https://www.w3.org/WAI/WCAG21/Understanding/label-in-name#dfn-text][text]] or [[https://www.w3.org/WAI/WCAG21/Understanding/label-in-name#dfn-image-of-text][images of text]], the [[https://www.w3.org/WAI/WCAG21/Understanding/label-in-name#dfn-name][name]] contains the text that is presented visually.

2.5.4 Motion actuation: 0h

• [[https://www.w3.org/WAI/WCAG21/Understanding/motion-actuation#dfn-functionality][Functionality]] that can be operated by device motion or user motion can also be operated by [[https://www.w3.org/WAI/WCAG21/Understanding/motion-actuation#dfn-user-interface-component][user interface components]] and responding to the motion can be disabled to prevent accidental actuation, except when: […]

• not relevant

Level AAA: 1h

2.5.5 Target size: 1h

• The size of the [[https://www.w3.org/WAI/WCAG21/Understanding/target-size#dfn-target][target]] for [[https://www.w3.org/WAI/WCAG21/Understanding/target-size#dfn-pointer-input][pointer inputs]] is at least 44 by 44 [[https://www.w3.org/WAI/WCAG21/Understanding/target-size#dfn-css-pixel][CSS pixels]] except when:

• Generally not difficult, but
• problematic for the map markers as they are 16x41
• And maybe relevant for the social links

2.5.6 Concurrent input mechanism

• Web content does not restrict use of input modalities available on a platform except where the restriction is [[https://www.w3.org/WAI/WCAG21/Understanding/concurrent-input-mechanisms#dfn-essential][essential]], required to ensure the security of the content, or required to respect user settings.

• We don't restrict.

3 Understandable: 6h

3.1 Readable: 2h

Level A: 1h

3.1.1 Language of page

• The default [[https://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html#dfn-human-language][human language]] of each [[https://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html#dfn-web-page][Web page]] can be [[https://www.w3.org/WAI/WCAG21/Understanding/language-of-page.html#dfn-programmatically-determined][programmatically determined]].

• should work

Level AA: 0h

3.1.2 Language of parts

• is that relevant for single-language pages?

Level AAA: 1h

3.1.3 Unsual words

• A [[https://www.w3.org/WAI/WCAG21/Understanding/unusual-words#dfn-mechanism][mechanism]] is available for identifying specific definitions of words or phrases [[https://www.w3.org/WAI/WCAG21/Understanding/unusual-words#dfn-used-in-an-unusual-or-restricted-way][used in an unusual or restricted way]], including [[https://www.w3.org/WAI/WCAG21/Understanding/unusual-words#dfn-idiom][idioms]] and [[https://www.w3.org/WAI/WCAG21/Understanding/unusual-words#dfn-jargon][jargon]].

• relevant for curators!

3.1.4 Abrreviations

• A [[https://www.w3.org/WAI/WCAG21/Understanding/abbreviations#dfn-mechanism][mechanism]] for identifying the expanded form or meaning of [[https://www.w3.org/WAI/WCAG21/Understanding/abbreviations#dfn-abbreviation][abbreviations]] is available.

• technically probably hard. We musn't use abbreviations :\

3.1.5 Reading level

• When text requires reading ability more advanced than the [[https://www.w3.org/WAI/WCAG21/Understanding/reading-level#dfn-lower-secondary-education-level][lower secondary education level]] after removal of proper names and titles, [[https://www.w3.org/WAI/WCAG21/Understanding/reading-level#dfn-supplemental-content][supplemental content]], or a version that does not require reading ability more advanced than the lower secondary education level, is available.

• relevant for curators

3.1.6 Pronounciation

• A [[https://www.w3.org/WAI/WCAG21/Understanding/pronunciation#dfn-mechanism][mechanism]] is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation.

• hopefully for us not relevant

3.2 Predictable: 1h

Level A: 0h

3.2.1 On focus

• When any [[https://www.w3.org/WAI/WCAG21/Understanding/on-focus.html#dfn-user-interface-component][user interface component]] receives focus, it does not initiate a [[https://www.w3.org/WAI/WCAG21/Understanding/on-focus.html#dfn-changes-of-context][change of context]].

• check

3.2.2 On input

• Changing the setting of any [[https://www.w3.org/WAI/WCAG21/Understanding/on-input#dfn-user-interface-component][user interface component]] does not automatically cause a [[https://www.w3.org/WAI/WCAG21/Understanding/on-input#dfn-changes-of-context][change of context]] unless the user has been advised of the behavior before using the component.

• I think that's true

Level AA: 0h

3.2.3 Consistent navigation

• Navigational mechanisms that are repeated on multiple [[https://www.w3.org/WAI/WCAG21/Understanding/consistent-navigation#dfn-web-page][Web pages]] within a [[https://www.w3.org/WAI/WCAG21/Understanding/consistent-navigation#dfn-set-of-web-pages][set of Web pages]] occur in the [[https://www.w3.org/WAI/WCAG21/Understanding/consistent-navigation#dfn-same-relative-order][same relative order]] each time they are repeated, unless a change is initiated by the user.

• works for us

3.2.4 Consistent identification

• Components that have the [[https://www.w3.org/WAI/WCAG21/Understanding/consistent-identification#dfn-same-functionality][same functionality]] within a [[https://www.w3.org/WAI/WCAG21/Understanding/consistent-identification#dfn-set-of-web-pages][set of Web pages]] are identified consistently.

• should be fine

Level AAA: 1h

3.2.5 Change on request

• [[https://www.w3.org/WAI/WCAG21/Understanding/change-on-request#dfn-changes-of-context][Changes of context]] are initiated only by user request or a [[https://www.w3.org/WAI/WCAG21/Understanding/change-on-request#dfn-mechanism][mechanism]] is available to turn off such changes.

• Maximally when page is loading …

3.3 Input assistance: 3h

Level A: 1h

3.3.1 Error identification: 0h

• If an [[https://www.w3.org/WAI/WCAG21/Understanding/error-identification.html#dfn-input-error][input error]] is automatically detected, the item that is in error is identified and the error is described to the user in text.

• we don't have errors

3.3.2 Labels or instructions. 1h

• [[https://www.w3.org/WAI/WCAG21/Understanding/labels-or-instructions#dfn-label][Labels]] or instructions are provided when content requires user input.

• need instructions for the search, categories, tags, … our whole mess of categories?

Level AA: 0h

3.3.3 Error suggestion: 0h

• If an [[https://www.w3.org/WAI/WCAG21/Understanding/error-suggestion#dfn-input-error][input error]] is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

• we don't have errors

3.3.4 Error prevention: 0h

• not relevant

Level AAA: 2h

3.3.5 Help: 2h

• [[https://www.w3.org/WAI/WCAG21/Understanding/help#dfn-context-sensitive-help][Context-sensitive help]] is available.

• might be very involved

3.3.6 Error prevention (all): 0h

• not relvant

4 Robust: 4h

4.1 Compatible: 4h

Level A: 3h

4.1.1 Parsing (removed in 2.2)

4.1.2 Name, role, value: 3h

• For all [[https://www.w3.org/WAI/WCAG21/Understanding/name-role-value#dfn-user-interface-component][user interface components]] (including but not limited to: form elements, links and components generated by scripts), the [[https://www.w3.org/WAI/WCAG21/Understanding/name-role-value#dfn-name][name]] and [[https://www.w3.org/WAI/WCAG21/Understanding/name-role-value#dfn-role][role]] can be [[https://www.w3.org/WAI/WCAG21/Understanding/name-role-value#dfn-programmatically-determined][programmatically determined]]; states, properties, and values that can be set by the user can be [[https://www.w3.org/WAI/WCAG21/Understanding/name-role-value#dfn-programmatically-set][programmatically set]]; and notification of changes to these items is available to [[https://www.w3.org/WAI/WCAG21/Understanding/name-role-value#dfn-user-agent][user agents]], including [[https://www.w3.org/WAI/WCAG21/Understanding/name-role-value#dfn-assistive-technology][assistive technologies]].

• Probably some work
• Maybe even hard to test

Level AA: 1h

4.1.3 Status messages: 1h

• In content implemented using markup languages, [[https://www.w3.org/WAI/WCAG21/Understanding/status-messages#dfn-status-message][status messages]] can be [[https://www.w3.org/WAI/WCAG21/Understanding/status-messages#dfn-programmatically-determined][programmatically determined]] through [[https://www.w3.org/WAI/WCAG21/Understanding/status-messages#dfn-role][role]] or properties such that they can be presented to the user by [[https://www.w3.org/WAI/WCAG21/Understanding/status-messages#dfn-assistive-technology][assistive technologies]] without receiving focus.

• we don't really have status messages, except failures

Personas

Miroboard by Madeleine https://miro.com/welcomeonboard/VndVcHJnZHluUXNYd0FhaDJGUTRXS0l0MU0yYmFtbUt5T29tV3JkakJEQ1BWcjZzQTdTMkxXTVlPYlZkWTFUMXwzNDU4NzY0NTQ1NTIwNzk1NDI2fDI=?share_link_id=277417793078 (seems deleted) → https://slack-files.com/T1RAQ0NBF-F062PJSDPMM-6d65344847

Doc by Jonte & Issi https://slack-files.com/T1RAQ0NBF-F06305D0VDE-bb807aa186