> For the complete documentation index, see [llms.txt](https://docs.klai.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/elements/avatar.md). # Avatar 😁 * [ ] Visualizer Show what the avatar looks like before posting or updating * [ ] Link to upload or select avatar Accessible link for a user to select * [ ] Placeholder image If a user hasn't uploaded or added an avatar yet there should be a placeholder e.g. a default icon, or the user's initials * [ ] Acceptable file types Tell the user what file types are allowed (JPEG, PNG, SVG) * [ ] Status change updating avatar This doesn't have to be apart of the avatar component (it can be a banner or toast for example), but it is possible to incorporate it * [ ] Alternatives If a user doesn't want to upload an image, offer an illustrative alternative, as it's better than nothing and can still convey their personality * [ ] Editing uploaded avatar Allow a user to crop and resize their avatar before saving it --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/elements/avatar.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.