Answer the question about saved questions

Answer the question about saved questions

“Do you save my questions?” returned a passage about keyword-search terms. It cited the Privacy and AI page, but did not answer the question asked. A correct source link alone was not enough.

Questions about saving or storing questions, prompts or answers now use the current privacy page rather than dated proposals or general search copy. The privacy statement is direct: we don’t save questions or answers in an application database. Cloudflare still processes requests under its own policies.

The existing one-call limit, shared daily allowance, verification and keyword fallback are unchanged. No new data collection or service was added. A separate controlled question returned the complete five-minute reader-study instructions; that is a functional check, not a completed study.

Feedback remains three Yes responses, including at least two known tests, and one non-test-marked Statistics preference. Repeats and bots remain possible. There is no basis to change roadmap scores or claim measured reader benefit. Trial timings stay unchanged.

Refresh the dated traffic snapshot

The detailed Cloudflare reports now show 11 visits and 20 page views over seven days, and 2 visits and 2 page views over the last 24 hours. Both windows end on 23 October, use GMT+11 and filter to the production hostname without bot exclusion.

The Statistics snapshot keeps the windows separate. Browser records cannot distinguish owner tests, repeats or automated browsers. The older Function metrics retain their original date; they were not refreshed or presented as visitor counts. No new analytics service or permission was added.

Less repeated copy, clearer evidence

• Home replaces its repeated Journal and Roadmap promotional blocks with compact links to future ideas and evidence. The main Journal card and navigation remain.
• The Journal landing page explains records and lessons once, while keeping newest-first entries and links to original history.
• Statistics gives 24-hour browser counts their own section. Older Function metrics sit separately, labelled as backend activity. The recorded figures and collection time are unchanged.

A controlled Ask AI check could not select an answer to the highest-priority idea question. The Roadmap now states its top idea in a short summary derived from the existing scores; Search uses the same summary. Scores remain editorial judgements, not measured outcomes or commitments.

Another check about measured reader benefit selected a weaker roadmap passage. Retrieval now removes weaker mentions when a passage matches at least three question terms; short-query handling and the existing learning-question rule remain. This targets an observed relevance problem without adding model calls or services. A trial-stop question returned the correct date range. Controlled checks do not establish general answer quality or reader benefit.

Make keyboard focus easier to follow

The accessibility review found that Ask AI’s disclosure and question field used a very thin browser-default focus outline. Shared styles now give keyboard-focused links, buttons, fields, selectors and disclosures a stronger outline with a light separating band. Existing keyboard behaviour is unchanged.

The review covers selected keyboard paths, shared colour contrast and narrow layouts. It does not establish full WCAG conformance. The remaining work includes text resizing and spacing, complete task flows, screen-reader output and third-party verification. No new testing service or schedule was added.

Explain how to correct a short question

Search told a reader who had entered two characters to “Enter a question first”. It did not explain the minimum or associate the message with the field.

Ask AI now states the three-character minimum, marks the field invalid and returns focus to it. Correcting the text or choosing a suggestion clears that state. Choosing keyword Search clears the AI-only error too; short keyword searches still work.

Home keeps browser validation and adds persistent, associated guidance for empty, short and whitespace-only questions. Its privacy note stays linked to the field. Invalid questions stop locally before verification or inference. No service limit or security control changed; full accessibility conformance remains unverified.

Let question controls grow with text

A local accessibility check doubled the Home question controls’ text. The Ask button kept its fixed height and its content overflowed. The field and button now have a minimum height and can grow with the text. At the normal size they remain aligned; narrow screens keep the stacked layout.

This is a focused control fix, not proof that every page supports all text settings or meets WCAG. The remaining accessibility work stays on the roadmap. No service, data collection or trial timing changed.