508 Compliance For streamlit

Random
1

Hi there,

Is there a plan to make Streamlit 508 compliant? This would allow using it across tremendous amount of government dashboards and would take away from Tableau.

Sincerely,
Yegór

2

Hi @iopheam

Thanks for the question. We haven’t done an official accessibility assessment. That said, we write our frontend code with accessibility in mind, using a widget component library that is accessible, looking at contrast ratios when designing, etc.

But we’re aware this is by all means not enough! That’s why we have a roadmap item to officially assess accessibility and address issues that arise. It’s important to note we don’t control user themes, plotting libraries, and custom components, and a lot of the accessibility of actual apps will fall on users who are writing these apps.

Can you share a little more on your use case? What kind of dashboards are you building and how have you historically demonstrated 508 compliance before you started using Streamlit?

Thanks!

3

Hi @abhi,

Thanks for the reply. We are building various dashboards for various government agencies. We are using Streamlit for quick prototyping but have to redo everything in tableau as it is 508 compliant: Build Data Views for Accessibility - Tableau

Each agency has a department that formally assesses an app for compliance. Historically, it was hard to do, especially for custom components. But “ Tableau supports several controls to enable you to build a view that complies with US Section 508 requirements when consuming a view in Tableau Online or Tableau Server that meets the Web Content Accessibility guidelines (WCAG 2.0 AA).” So, when an agency reviews your product they make sure you used those controls and confirm your compliance quicker.

That is why if Streamlit had such controls many prototypes would have a chance to be used in production in government environments.

Hope this helps.

4

Hi @iopheam,

Thanks for the additional context, it was really helpful!

I’ve added 508 Accessibility as an item to our roadmap. We are scoping our longer term roadmap so I don’t have exact information on when we’ll get to work on this. But once we have more clarity on timeline I’ll share details on this thread.

1 Like
5

Hi @abhi

I am in a similar position to @iopheam facing WCAG requirements for publishing apps for government. Do you have an update on where this might fit into the roadmap?

1 Like
6

Hi! Has there been any update to the 508 compliance issues?

1 Like
7

It would be really good to get an update on this.

The fact that Streamlit doesn’t meet accessibility standards makes it effectively unable to be used in any UK government work. I would love to see this change so that we can allow the 100s of data scientists in government to use it.

2 Likes
8

This is a wonderful tool but without a way to make apps 508 compliant, we are not allowing access to a large percentage of folks who would benefit from our data.

9

Hi,

Is there any update on the 508 compliance issue?

This is very, very important to address ASAP.

Thanks!

1 Like
10

508 Compliance does not appear on Streamlit’s current public roadmap. As pointed out above, 508 Compliance is a prereq for the widespread use of Streamlit in the public sector.

Can someone on the Streamlit team update us on this?

1 Like
11

I would like to know what is the update on the streamlit 508 compliance topic too. Is it on the roadmap for future Streamlit development? Is seems a lot of people has similar concern. It would be really helpful to make sure the contrast ratios of Streamlit components are compliant, and support success criterion SC 4.1.2, etc. Thank you!

12

IMHO as an outsider, there might be more progress on this if the concerned people filed concrete usability issues in github. Like specific streamlit components that don’t have accesible contrast ratios.

13

st.multiselect is one example. The contrast ratio does not meet the requirement 4.5:1.

14

I suggest you file create an issue about that.