hermes

Start here 1

The general, start-from-zero entry for a need in this category: it works from a blank start, asks for what it needs and hands off to the specific entries. Example: Plan a trip.

Search and filter in Accessibility

Specific 54

One situation, audience, tool or format inside the category. Example: Plan a road trip with children.

  • Accessibility specialist

    Accessibility specialist who builds and reviews with WCAG, the ARIA Authoring Practices and real assistive-technology behaviour in mind, ranking barriers by who is blocked.

  • Frontend accessibility rules

    Standing rules that make an assistant write accessible frontend code, with semantic HTML first, labels, keyboard and focus handling, contrast, motion and ARIA only where native elements fall short.

  • Write alt text for images

    Writes context-aware alt text for images on a page or in a document, or marks them decorative, following the W3C alt decision tree. Use when publishing images on the web.

  • Write a screen-reader test plan

    Writes a manual screen-reader test script for a user flow on NVDA, JAWS, VoiceOver or TalkBack, with keystrokes and expected announcements per step. Use before releasing a key flow.

  • Audit game accessibility

    Audits a game build or design for motor, vision, hearing and cognitive barriers using the Game Accessibility Guidelines and Xbox Accessibility Guidelines, ranked by players helped per effort.

  • Audit motor accessibility

    Audits a web or mobile UI for people using voice control, switch access, head pointers or one hand, covering label-in-name, target size, gestures, dragging and timing, with code fixes.

  • Build or fix an accessible form

    Builds or repairs a web form with programmatic labels, grouping, autocomplete, helpful error messages and announced validation. Use for sign-up, checkout, settings or any data-entry form.

  • Prioritise accessibility findings

    Turns a long external accessibility audit into a fix plan that deduplicates by shared component, ranks by impact on key journeys, and groups work into sprints with design-system fixes first.

  • Review cognitive accessibility

    Reviews a built flow against the WCAG 2.2 cognitive criteria and W3C COGA patterns, covering login, time limits, redundant entry, errors and plain language, with code and copy changes.

  • Write an accessibility bug report

    Turns a rough accessibility finding into a bug report developers can reproduce, with the assistive technology and browser, steps, expected and actual announcements, WCAG criterion and user impact.

  • Preview screen reader announcements

    Predicts what a screen reader would announce as you tab and arrow through markup or a component, explains why, and flags confusing announcements. For learning, not a substitute for real testing.

  • Review colour contrast and fix the palette

    Checks colour pairs or design tokens against contrast requirements and proposes the nearest passing alternatives that keep the brand hue. Use when defining or auditing a palette or theme.

  • Audit motion and flashing

    Audits animations, parallax, carousels and video for vestibular and seizure risk against WCAG 2.2.2, 2.3.1 and 2.3.3, then adds reduced-motion handling and pause controls.

  • Make a CLI accessible

    Reviews and fixes a command-line tool for screen-reader, low-vision and colour-blind users, covering colour-only output, spinners, box drawing, prompts, NO_COLOR and a plain output mode.

  • Make in-app charts accessible

    Fixes app charts (SVG, canvas or a chart library) with a text summary, data table fallback, keyboard exploration, non-colour encodings and contrast. Code fixes, not design critique.

  • Write accessibility acceptance criteria

    Turns a user story or design into testable accessibility acceptance criteria per component, mapped to WCAG success criteria, so QA and developers can check them before merge.

  • Fix accessible names

    Finds controls, links and images whose accessible name is missing, wrong or misleading, computes what assistive technology actually gets, and fixes it with visible text first and ARIA last.

  • Audit a mobile screen for accessibility

    Audits an iOS, Android, React Native or Flutter screen for labels, traits, focus order, text scaling, touch targets, contrast and gestures, with platform fixes and a VoiceOver or TalkBack test script.

  • Fix keyboard navigation in a component

    Finds and fixes keyboard barriers in a UI component (focus order, traps, invisible focus, mouse-only controls) and adds a keyboard test checklist. Use when a widget fails without a mouse.

  • Set up automated accessibility checks

    Adds layered automated accessibility checks to a web or mobile project (editor lint, component tests, CI page scans with a baseline) and states what automation cannot catch.

  • Audit HTML email accessibility

    Audits HTML email code for screen-reader and low-vision problems specific to email clients, then returns fixed markup that still renders across Outlook, Gmail and Apple Mail.

  • Fix data table accessibility

    Rebuilds a complex data table (grouped headers, sorting, sticky headers, row actions, responsive collapse) so screen readers announce each cell's context, with before and after markup.

  • Native mobile accessibility rules

    Standing rules that make an assistant write accessible iOS, Android, React Native and Flutter UI code, with labels and traits, target sizes, text scaling, focus order and announcements.

  • Support forced colors mode

    Makes a web UI usable in Windows contrast themes and other forced colors modes, fixing invisible icons, focus rings, borders and states with system colour keywords and the forced-colors media query.

  • Write accessibility regression tests

    Writes component and end-to-end tests that assert roles, accessible names, keyboard behaviour and focus, so accessibility fixes stay fixed after refactors.

  • Build or fix an accessible carousel

    Builds or repairs a carousel or slider of slides with a pause control, labelled slides and controls, keyboard and screen-reader support, and no focus lost to hidden slides.

  • Build an accessible media player

    Builds or fixes a web video or audio player with captions, transcripts, audio description, operable controls and no autoplay traps, mapped to the WCAG 1.2 media criteria.

  • Build accessible tooltips and toggletips

    Builds or fixes tooltips and toggletips that open on hover, focus and touch, can be dismissed, stay while hovered, and are named or described correctly for screen readers.

  • Fix automated accessibility scan violations

    Takes axe, Lighthouse or WAVE output, explains each violation, fixes the code at its source and flags false positives and what the scan could not see.

  • Fix information shown by colour alone

    Finds places where status, errors, links, required fields or chart series are shown only by colour, and adds text, icons, patterns or underlines without breaking the design.

  • Fix cookie consent banner accessibility

    Fixes a cookie consent banner or preferences modal so it is reachable first, labelled, does not hide or trap the page, has equally operable choices and works with zoom and screen readers.

  • Fix page structure and landmarks

    Repairs a page's skeleton for screen-reader navigation, covering title, language, heading outline, landmarks, skip link and list semantics, with corrected markup and a heading and landmark map.

  • Fix reflow and text resize

    Fixes layouts that break at 400% zoom, 200% text size or custom text spacing, finding fixed heights, clipped text and sideways scrolling, with CSS changes mapped to WCAG 1.4.4, 1.4.10 and 1.4.12.

  • Make a documentation site accessible

    Fixes a developer documentation site's code blocks, syntax colours, copy buttons, tabs, search, sidebar navigation and version switcher for keyboard, screen-reader and low-vision users.

  • Make an interactive map accessible

    Makes a web map such as a store locator, property search or delivery zone picker usable without sight or a mouse, with a synced list alternative, keyboard panning, named markers and text directions.

  • Manage focus after in-page UI updates

    Fixes where keyboard focus goes after deleting or adding items, inline editing, closing panels or loading content, so keyboard and screen-reader users are not dropped to the top of the page.

  • Accessibility fix sweep for a web app

    Fixes accessibility issues across a web app with a scan, keyboard and accessibility-tree checks, small fixes, a re-scan and a list for human testing. Use to clear accessibility debt in a sprint.

  • Build accessibility into a team's delivery process

    Sets up accessibility checks across a team's design, development, code review, QA and release process, with owners, definition of done, tooling, training and a way to measure progress.

  • Learn to test with a screen reader

    Teaches a developer to start NVDA, VoiceOver or TalkBack, the dozen commands that matter, and how to check their own component without fooling themselves.

  • Turn an accessibility complaint into a verified fix plan
    PromptAccessibilityLegal · safety checks

    Turns a user's accessibility complaint or a formal demand into a verified list of issues, a remediation plan with priorities and a factual draft reply for review, without legal positions.

  • Fix route changes in single-page apps

    Fixes silent navigation in client-side routed apps by managing focus, page titles, live announcements and scroll on route change, plus toasts and loading states.

  • Add keyboard shortcuts that do not break assistive tech

    Adds or fixes app keyboard shortcuts so they do not clash with screen readers or browsers, can be turned off or remapped, are discoverable and exposed to assistive technology.

  • Add live region announcements that actually speak

    Adds reliable screen-reader announcements for toasts, status messages, loading states and result counts, using live regions that work across NVDA, JAWS, VoiceOver and TalkBack.

  • Build an accessible site navigation or mega menu

    Builds or fixes site navigation, dropdown and mega menus with disclosure buttons, a mobile menu, current page marking and Escape support, without misusing the ARIA menu role.

  • Build an accessible single or range slider

    Builds or fixes a single-value or range slider with native input where possible, full keyboard steps, readable value text, labels and a typed input alternative for precise values.

  • Make a chat or AI assistant interface accessible

    Makes a chat or AI assistant UI usable with keyboard and screen readers, with a message log, sensible announcement of streamed replies, focus that stays put and labelled controls.

  • Make infinite scroll and load-more feeds accessible

    Fixes infinite scroll and load-more feeds so keyboard users can reach the footer, new items are announced, position is kept and screen readers know the feed structure.

  • Make a multi-step form or wizard accessible

    Makes a multi-step form or wizard accessible, with a progress indicator people can understand, focus and titles on step change, per-step errors, back navigation and saved progress.

  • Make search results and faceted filters accessible

    Makes a search page with faceted filters accessible, with labelled filter groups, announced result counts, keyboard-friendly applied-filter chips and focus that survives result updates.

  • Assess technical readiness for the European Accessibility Act
    PromptAccessibilityLegal · safety checks

    Helps a product team work out whether its digital product is likely in scope of the European Accessibility Act and what technical work is needed, as a gap plan for legal review.

Showing 50 of 54. See them all in search

Advanced 10

Expert or deep work that assumes the user can judge expert output. Example: Plan croissant lamination.

  • Build an accessible ARIA widget

    Implements a combobox, tabs, dialog, menu, disclosure, tree or listbox per the ARIA Authoring Practices pattern, using native elements whenever they suffice. Use for custom interactive widgets.

  • Make generated PDFs accessible

    Changes the code that generates invoices, statements or certificates so the PDFs come out tagged and PDF/UA-ready, with reading order, alt text, language and table headers checked in CI.

  • Build accessible drag and drop

    Builds or fixes drag-and-drop reordering, kanban moves or file drops so keyboard, screen-reader, voice and single-pointer users can do the same task, with announcements and a non-drag alternative.

  • Write an accessibility conformance report

    Writes an accessibility conformance report (ACR) in the VPAT format from audit results, with a conformance level and specific remarks per criterion. Use when customers or procurement ask for a VPAT.

  • Audit desktop app accessibility

    Audits a desktop app (Electron, Tauri, WPF, WinUI, Qt, AppKit or GTK) for keyboard access, focus, accessible names and roles exposed to the platform accessibility API, scaling and contrast themes.

  • Build an accessible interactive data grid

    Builds or fixes an editable, spreadsheet-like grid with one tab stop, arrow-key cell navigation, an edit mode, selection, sorting and announcements, following the ARIA grid pattern.

  • Make a rich-text editor accessible

    Makes a rich-text editor usable with keyboard and screen readers, with a labelled editing area, a toolbar that follows the toolbar pattern, announced formatting state and documented shortcuts.

  • Audit a component library for accessibility

    Audits a design system or component library component by component for semantics, keyboard, focus, states and docs, with a status per component and fixes ranked by reuse.

  • Build or fix an accessible date picker

    Builds or repairs a date or date-range picker with typed entry, a dialog calendar grid with full keyboard support, clear labels and announcements, and native input where it is enough.

  • Make custom elements accessible across shadow DOM

    Makes web components (custom elements with shadow DOM) accessible, solving label association, ARIA references across the shadow boundary, form participation and focus delegation.

Wins over code-review, testing and ui-design when accessibility is the outcome.