Accessibility
We want Absurde Requests to be usable by as many people as possible — including screen-reader users, keyboard-only users, and people with low vision. To keep that promise, we keep the app deliberately simple.
How we build for accessibility
-
Semantic HTML, server-rendered
Pages are assembled on the server. Each page has a clean heading hierarchy, real form labels, and meaningful landmarks (header, main, nav, footer). No framework obscures that.
-
Little JavaScript
Core actions — reading, submitting, voting, signing in and out — work entirely without JavaScript. JS is used only as a small convenience, e.g. for the tag input. Without JS the input is just a normal text field.
-
No hidden functionality
No secret buttons, no hidden gestures, no multi-level hover menus, no animations that hide important content. What you see on screen is in the source and reachable by keyboard.
-
Keyboard navigation
Every link, button, and form field can be reached with Tab. Users who cannot or do not want to use a mouse can operate the whole app from the keyboard.
-
Contrast & readability
Text and background combinations meet WCAG AA (at least 4.5:1); the dark sections meet AAA. The Inter typeface is loaded at scalable rem sizes.
Standard
We follow the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We aim higher where we can — we can't guarantee AAA across the board, but we regularly test with keyboard navigation and contrast checking.
Known limitations
- Icons are inlined SVG. Decorative icons next to text labels are marked aria-hidden so screen readers don't announce them twice.
- The tag suggestion dropdown on the submit page needs JavaScript. Without JS the field stays a regular text field — entries can still be submitted.
Feedback
If something is inaccessible — a missing label, a screen-reader trap, weak contrast — please tell us. Reports are taken seriously and fixes go in.
Contact: sitte@polente.de