Basic accessibility web features
@mayagbarnes is already working on this.
Since Aug 30, 2026.
Assessment
This issue has not been assessed yet.
Description
Checklist
- I have searched the existing issues for similar feature requests.
- I added a descriptive title and summary to this issue.
Summary
To begin with, it is a great product. In its current state, it seems advisable to generate a final web page with considerations for web accessibility. This includes aspects such as the page name, language, structure, and named links. Currently, these tags cannot be controlled and may result in errors or warnings in accessible web page verification tools.
Why?
The product is described as excellent. However, it lacks certain features related to web accessibility. Enhancing web accessibility can improve user experience and ensure compliance with accessibility standards. This proactive approach can also prevent errors and warnings in verification tools.
How?
To address this, efforts should be made to generate a final web page that incorporates aspects of web accessibility. This may involve adjusting tags related to page name, language, structure, and links to comply with accessibility guidelines. By implementing these changes, errors and warnings in verification tools can be minimized, thereby improving the overall accessibility and usability of the web page.
Additional Context
I know there are some questions in forums about compatibility e.g. with 508 standards (https://discuss.streamlit.io/t/508-compliance-for-streamlit/13579) which of course would be great but my recommendation would be to start with simple compatibilities that do not incorporate too much development overhead, or diminish Stremlit's capabilities.
- Dominant language
- Python
- Stars
- 45.8k
- Forks
- 4.4k
- Avg merge
- 21h 22m
- Merged PRs (30d)
- 316
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from streamlit/streamlit
-
area:backend area:network feature:embedding feature:runtime priority:P3 status:confirmed type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area:frontend area:security feature:st.file_uploader status:unlikely type:enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
area:backend area:security feature:cache feature:cache-hash-func priority:P4 status:confirmed type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area:mobile feature:st.camera_input papercut type:enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area:ai type:enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in streamlit/streamlit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100