Decision inputs
Facts that change the policy answer
The request sits in marketing and communications and connects approved product images and page context with accessible image descriptions. That context distinguishes it from a generic permission to use AI.
- 1Task and owner
- Web editor wants to write alt text for product images. The request needs an accountable owner for accessible image descriptions, even when the tool prepares most of the first draft.
- 2Information involved
- Approved product images and page context. Check uploads, history and connected systems before describing the request as low sensitivity.
- 3Tool and account
- An approved company account. Approval must cover the account and its settings, not merely the product name.
- 4Intended result
- The expected result is accessible image descriptions. Follow the result to its real endpoint so the request captures its practical effect.
- 5Consequence if it is wrong
- Generic descriptions can miss the information the image contributes to the page. A familiar task still needs escalation when this consequence becomes plausible.
- 6Human review
- accessibility owner should inspect, change, reject or stop the result. Review is meaningful only when that person has enough context and authority to change the result.
Possible policy routes
The task name alone cannot decide it.
A published workplace policy can return different answers for the same task. These are the practical branches worth encoding.
A routine policy route may be possible
The lower-friction route begins when the exact account is approved, only the minimum public information is used, accessible image descriptions remains within the stated purpose, and accessibility owner reviews it before use.
Approval may be required
A named reviewer should take over when the account or data handling is uncertain, generic descriptions can miss the information the image contributes to the page, or accessible image descriptions reaches people or systems beyond the requester’s authority.
The request may need to stop or change
The company may need a safer design when restricted information would enter an unapproved service, the output would act before accessibility owner can intervene, or review each description in its page context and keep decorative images empty cannot be maintained. Consider less information, a controlled account or a non-AI process.
Request checklist
Questions to ask before using the tool
- 01
Has the company approved this account configuration for write alt text for product images, rather than only approving the product?
- 02
Could approved product images and page context be reduced to a short de-identified extract?
- 03
Will accessible image descriptions remain working material, reach another person or make another system act?
- 04
Does accessibility owner have enough authority and time to stop the result?
- 05
When must the employee stop and run the policy check again?
Worked request
What the employee should submit
This example supplies decision facts without pasting the underlying material into the approval record.
- requester
- web editor
- task
- Use AI to write alt text for product images.
- information
- approved product images and page context
- tool
- An approved company account
- frequency
- Recurring work
- region
- Where the work and affected people are located
- purpose
- Draft or analyse
- impact
- External publication
- review
- Complete human review
- owner
- accessibility owner
Useful safeguards
Controls that fit this request
- ✓
Review each description in its page context and keep decorative images empty
- ✓
Keep whole files, mailboxes and datasets out of the prompt when a short part of approved product images and page context is enough.
- ✓
Write the boundary around accessible image descriptions clearly so later users do not expand the approval by assumption.
- ✓
Preserve who accepted accessible image descriptions, when they did so and which rule version they applied.
Questions people ask
About this AI use
Is using AI to write alt text for product images automatically allowed?
Treat this as a request pattern. The authoritative answer comes from the current company policy and the employee’s completed submission.
Which facts should be submitted before work begins?
Describe accessible image descriptions, identify approved product images and page context, name the exact tool and account, explain who will receive or rely on the output, and state how accessibility owner will review it.
How should a later reviewer understand this decision?
Preserve who accepted accessible image descriptions, when they did so and which rule version they applied. A classification and controlled reference may be enough when copying approved product images and page context would create unnecessary risk.