Skip to content

Link accessibility page to FAQ when it becomes available #984

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hypha opened this issue Jan 28, 2025 · 3 comments
Closed

Link accessibility page to FAQ when it becomes available #984

hypha opened this issue Jan 28, 2025 · 3 comments

Comments

@hypha
Copy link
Contributor

hypha commented Jan 28, 2025

In previous years, the accessibility has lots of information that is relevant to everyone. But not everyone checks the page when they try to find information. If we put similar type of info on the accessibility page this year, we should link it more prominently on the FAQ page to guide people there.

@nikoshell
Copy link
Contributor

@hypha, is it the same page as last year? https://ep2024.europython.eu/accessibility/

@clytaemnestra
Copy link
Contributor

@nikoshell the information about the main venue remains the same. In 2023, we had a more detailed accessibility page: https://ep2023.europython.eu/accessibility/. This year, we’re still waiting on the contract for the sprints venue, and the social events aren't finalized yet. Once everything is confirmed, I’d like to add accessibility info for the additional venues (sprints, socials) like we had in 2023.

I’d also prefer not to include a separate FAQ section on the page. Ideally, the content should be clear enough that an FAQ isn’t needed. Instead, we can link sections from the accessibility page to the general FAQ (at /faq).

@hypha
Copy link
Contributor Author

hypha commented Jun 10, 2025

completed in #1296 by Cyril

@hypha hypha closed this as completed Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants