Favvy.

Accessibility Information

Last updated: July 27, 2026

1. Our commitment

palmstudio GmbH wants Favvy to be usable by as many people as reasonably possible, including people who use a keyboard, screen reader, zoom, voice input, high-contrast settings, or other assistive technology.

Favvy is a small experimental service and has not yet completed an independent accessibility audit. We therefore do not currently claim full conformity with WCAG 2.2, EN 301 549, or every requirement that may apply under the German Accessibility Strengthening Act (BFSG).

We publish this information so users can understand the service, known limitations, available assistance, and how to report a barrier. Mandatory accessibility rights remain unaffected.

2. Provider and contact

Favvy is provided by:

palmstudio GmbH
Pfalzgrafenstraße 38
67434 Neustadt an der Weinstraße
Germany

Email: support@favi.link

When reporting an accessibility problem, use the subject Favvy accessibility and include the page, feature, browser, device, and assistive technology involved where you are comfortable doing so.

3. General description of the service

Favvy is a web application for curating and ranking favorite things. It is available through a modern web browser.

The main service functions are:

  • creating an Account with email, password, and username;
  • signing in and signing out;
  • editing a profile, display name, username, biography, avatar, and cover image;
  • choosing public or private profile visibility;
  • creating ranked lists and collections;
  • adding songs, artists, places, links, and plain-text entries;
  • moving, replacing, and removing list items;
  • viewing how a list changed over time;
  • searching for profiles;
  • following or unfollowing users;
  • reading a feed based on followed public profiles;
  • managing Account settings and deleting the Account;
  • reading legal information and managing cookie consent.

The service uses text, buttons, forms, lists, cards, dialogs, images, and links. Some data and search results come from third-party providers.

4. How to use Favvy

Account and navigation

The global header provides the Favvy home link and available Account or search actions. The footer provides Legal, reporting, cookie, settings, and sign-out controls where applicable.

After registration, users can navigate to their profile, create lists, open a list, add items, change item order, and view history. Protected pages require a signed-in session.

Forms

Forms accept keyboard input for registration, profile fields, list details, search, and other supported actions. Validation messages are shown when required information is missing or invalid.

Lists and ranking

List items can be added through search, URL preview, or manual entry where supported. Ranked lists preserve the order chosen by the Account owner. Reordering and some complex editing interactions can require controls that are still being improved for assistive-technology use.

Images

Users can choose, crop, and upload an avatar or cover image. Cropping is a visual interaction and is one of the areas where a more complete keyboard and screen-reader alternative is still needed.

Cookie preferences

CookieHub provides the production consent dialog and preference center. Cookie settings can be reopened from Favvy's footer or Legal page. CookieHub's own accessibility behavior is maintained by CookieHub and can change independently of Favvy.

5. Accessibility measures currently used

Favvy currently uses or aims to use:

  • semantic page, heading, navigation, form, button, link, list, and dialog elements where available;
  • visible keyboard focus styles;
  • keyboard-operable standard buttons and links;
  • responsive layouts that adapt to smaller screens;
  • text that can wrap and reflow instead of requiring a fixed desktop width;
  • centralized color and contrast design tokens;
  • status, loading, error, banner, and toast components;
  • descriptive control labels or accessible names for icon-only controls;
  • reduced reliance on color alone to communicate errors or status;
  • predictable route and navigation patterns;
  • plain English for core product and legal information;
  • no essential audio-only instructions and no automatically playing audio;
  • native browser and operating-system zoom support.

Accessibility is part of ongoing product work. The presence of these measures does not mean that every screen or state has been fully tested with every assistive technology.

6. Current conformance status

Favvy has not yet been evaluated through a complete WCAG 2.2 AA or EN 301 549 audit. Its current status must therefore be treated as not yet formally determined rather than fully conformant.

The repository uses accessibility-oriented semantic and focus patterns, but code review alone cannot establish complete real-world conformity. Manual keyboard testing, screen-reader testing, zoom and reflow testing, contrast verification, and testing with users with disabilities remain necessary.

7. Known and potential limitations

The following limitations are currently known or reasonably expected:

  • The profile-image crop interaction is primarily visual and may not offer an equivalent precise crop workflow for keyboard-only or screen-reader users.
  • Dragging or complex list reordering may not yet provide complete keyboard instructions, position announcements, or an equally efficient non-drag alternative in every state.
  • Some form inputs or validation states may require further review for consistently associated visible labels, instructions, and error announcements.
  • Loading, optimistic updates, feed changes, and dynamic search results may not be announced consistently by every screen reader.
  • Images and metadata obtained from users or third-party catalog providers may have missing, incomplete, duplicated, or low-quality text alternatives.
  • User-written titles, descriptions, biographies, link text, and image choices can be unclear or inaccessible even when the surrounding Favvy interface is accessible.
  • Dense ranked lists and timelines can require substantial navigation and may need better landmarks, summaries, or skip mechanisms.
  • The CookieHub widget and live cookie declaration are third-party interfaces. Favvy can configure and position them but does not control all generated markup or assistive-technology behavior.
  • Very high zoom levels, unusual browser font settings, forced colors, voice-control tools, and older assistive-technology combinations have not been comprehensively tested.
  • External destinations such as Spotify, Google Maps, and user-added websites have their own accessibility status, which Favvy does not control.

If one of these limitations prevents you from using a feature, contact us. We will try to provide the information or a reasonable alternative and use the report to prioritize remediation.

8. Supported environment

Favvy is designed for current versions of major browsers with JavaScript enabled, including Chrome, Edge, Firefox, and Safari. The current Next.js framework targets modern browser versions.

Accessibility can depend on the combination of browser, operating system, screen reader, zoom level, and input method. Older or unsupported browsers may not receive all functionality or accessibility improvements.

Necessary JavaScript is required for authentication, dynamic list editing, CookieHub controls, and other interactive features. The legal text itself is rendered as standard HTML and is intended to remain readable with common assistive technologies.

9. Third-party and user-provided content

Favvy displays data or links associated with Spotify, Geoapify, OpenStreetMap, Google Maps, CookieHub, Firebase, and external websites. It can also display user-uploaded images and user-written text.

palmstudio GmbH cannot guarantee the accessibility of third-party destinations or the quality of user-provided descriptions. We can remove or adjust a Favvy-controlled presentation where appropriate, but changes to a provider's own service must be addressed by that provider.

10. Accessibility feedback and assistance

To report a barrier or request assistance, email support@favi.link.

Helpful information includes:

  • the exact page URL;
  • what you were trying to do;
  • what happened and what you expected;
  • browser and operating system;
  • assistive technology and version, if relevant;
  • a screenshot or short recording, if safe and convenient;
  • the format or alternative you need.

Do not include passwords, authentication tokens, or unnecessary sensitive information.

We aim to acknowledge accessibility messages within 10 business days and provide a substantive response or status update within one month. Complex technical changes can take longer, but we will try to explain the next step and expected timing.

Available assistance may include explaining a workflow, providing information in a simpler text format, helping locate Account controls, receiving a report by email, or correcting a Favvy-controlled barrier.

11. Preparation and assessment method

This information was prepared on July 27, 2026 through:

  • review of Favvy's implemented routes and product flows;
  • review of shared semantic components, focus styles, forms, dialogs, lists, and navigation;
  • identification of complex interactions and third-party interfaces;
  • comparison with the general principles of perceivability, operability, understandability, and robustness;
  • review of the service-information expectations described in Annex 3 to the German BFSG.

This was an internal technical review, not an independent certification or complete accessibility audit.

We plan to revise this page after material interface changes, a formal audit, or validated feedback that changes the known status.

12. German BFSG information

To the extent that Favvy is a service within the scope of the German Accessibility Strengthening Act, this page is intended to provide the service description and accessibility information required by Section 14 and Annex 3 BFSG in a clearly perceptible and accessible form.

The service is provided through a web interface. Its essential functions and current accessibility measures are described above. Favvy aims to make information and interaction available through text, semantic structure, keyboard-operable controls, visible focus, scalable layouts, and compatibility with common assistive technologies. The known limitations in Section 7 show where the current implementation does not yet support a claim of complete conformity.

The competent German market-surveillance body for covered products and services is:

Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF AöR)
Carl-Miller-Straße 6
39112 Magdeburg
Germany

Email: kontakt@mlbf-barrierefrei.de
Telephone: +49 391 289 230 23
Website: https://www.mlbf-barrierefrei.de

You can contact us first so we have an opportunity to fix the issue, but doing so does not limit any statutory right to contact the competent body.

13. Updates

This page will be updated when:

  • a material Favvy flow changes;
  • a verified barrier is fixed or discovered;
  • an accessibility audit establishes a new conformance status;
  • provider interfaces materially change;
  • applicable legal information changes.

The Last updated date at the top identifies the current version.