WTFAA
WTFAA is an AI web assistant that works in the Chrome side panel on the page currently open. It has three modes for different jobs: for reading, it summarizes and explains the page and extracts keywords; for design review, it checks the visual design, color contrast and accessibility; for development and testing, it identifies the front-end stack, drafts a QA checklist, audits forms and fills them with test data. It can also translate whole pages and analyze a screenshot of the current page, and before anything is sent to the AI it shows a preview with the option to mask sensitive information. Users can connect their own Gemini, OpenAI, Claude or other API keys, or subscribe to Pro and use it directly.
WTFAA is an AI web assistant that works in the Chrome side panel on the page the user has open. Common reading, design review and development tasks are set up as ready-made actions in three modes, Reader, Designer and Developer, and the results appear next to the page. It can also translate whole pages, analyze a screenshot of the current page and answer the user's own questions about the page.
What WTFAA is for
The problem it solves
When reading a long article, reviewing a page's design or testing a web form, people usually copy the page content into a separate AI tool and write a prompt explaining what they want. WTFAA moves this work into the browser's side panel. It reads the current page directly, turns common tasks into one-click actions and shows the results beside the page, so the user can compare the analysis with the original.
Main features
Three modes. Reader mode summarizes the page, explains it in plain language, extracts keywords or rewrites the content as a social media post. Designer mode provides a visual analysis, notes on color and contrast and a design critique, and checks the page for visible accessibility issues. Developer mode identifies the front-end stack the page uses, drafts a QA checklist for the page, audits form fields and can fill a form with made-up test data. The extension first lists the fields and values it will enter and fills them only after the user confirms; the form is never submitted automatically.
Questions about the page. Besides the preset actions, users can type their own questions. When Auto Page Context is turned on in the settings, the page content is sent to the AI along with the question.
Page translation. Whole pages can be translated into the extension's interface language, which is currently English, Simplified Chinese, Japanese, Korean, German, French or Khmer. The translation can be shown alongside the original text, in place of it, or when the pointer hovers over it.
Screenshot analysis. Users can capture the visible area of the current tab and ask questions about it. This requires a model that accepts images.
Preview before sending. Preset actions, and questions that include page content or a screenshot, show a preview before anything is sent to the AI. The preview lists the message, the URL and the page or form content that will be sent. Users can decide whether to include the page content and the screenshot, or switch to a version masked locally, in which email addresses, phone numbers, access tokens and API keys are replaced and password values are hidden.
Keeping results. Answers can be copied or saved as a Markdown file.
Who it is for
WTFAA is meant for readers and researchers who need to understand web pages quickly, designers who review the look and accessibility of pages, and front-end developers and testers who check a page's technology and forms.
What you need
WTFAA is a Chrome extension installed from the Chrome Web Store, and it can be used in two ways. On the free plan, users enter their own API key for Google Gemini, OpenAI, Anthropic Claude, DeepSeek or Groq in the settings; requests go from the browser straight to that provider, and no account is needed. With a Pro subscription at $9.90 a month, users sign in with a Google account and work through Datafrog's AI service, without an API key of their own. Users can switch between the two in the settings.
Developer
Identifies the front-end stack, drafts a QA checklist for the page, audits form fields and fills forms with made-up test data after the user has confirmed the list of fields and values.
Designer
Analyzes the page's visual design, comments on its colors and text contrast, gives a design critique and checks the page for visible accessibility issues.
Reader
Summarizes the current page, explains its content in plain language, extracts keywords, or rewrites the content as a post for social media.
Preview before sending
Before content goes to the AI, the message, URL and page or form content are shown. Users decide what to include or switch to a version with sensitive information masked locally.