WordPress image descriptions · In development

Bring names and context into WordPress image descriptions

AltContext is being developed to combine an image with your site's named people roster and page context. Its review workflow lets an editor decide which names to include and edit the proposed description before applying it in WordPress.

No sign-in required. Uses a recorded example.

A name can be part of the picture’s meaning

A description can tell a reader that someone is speaking without saying who the speaker is. When the identity matters to the page, a supported name can provide useful context.

The guided prototype follows one festival photograph. Compare the saved name suggestions with reference photos, choose which names to include, and edit the draft. Leaving a person unnamed is also a valid choice.

What informs a draft

The workflow draws on the photograph, the people roster and the page. Each provides a different kind of information.

The photograph

The photograph provides the visible scene. Its people, objects and actions give the description something concrete to describe.

The people roster

The people roster provides names and reference photos associated with the site. A suggested match gives the editor an identity to consider alongside that evidence.

The page

The page helps explain why the image is being used. That purpose can affect which details and names belong in the description.

The editor chooses the final wording

Those inputs inform a draft. The editor reviews the draft, changes the wording where needed, and previews the result before applying it. Generating text and applying it are separate actions.

What you can try today

The public guided prototype demonstrates the review interaction using recorded face suggestions and sample drafts. Your edits affect only a demo copy in the current browser tab.

The WordPress product and its hosted services remain in development. The prototype demonstrates the interaction; it does not establish recognition accuracy or how well the descriptions serve readers.

Where processing happens

The recorded prototype uses its supplied example; you do not need to upload a photograph.

The WordPress product being developed uses hosted services for recognition and description. Images leave the WordPress host for that processing. The public prototype’s in-tab edits are separate from those server operations.