-
Notifications
You must be signed in to change notification settings - Fork 0
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
Sphinx theme, navigation, and accessibility (a11y) #10
Comments
Here are the PRs I've submitted so far: Note that you must be logged into GitHub to see the continuous integration. The build preview can be seen by clicking the "Details" link on the |
Hello @intoverflow, the SymPy (open-source computer algebra system written in Python) team is also considering a new Sphinx theme for its documentation, and accessibility is an important criterion. Any information you can share about your evaluation of the accessibility of Sphinx themes would be greatly appreciated--on Sphinx Themes, I didn't find any accessibility evaluations. I assume that the three themes you created pull requests for (maisie, Sphinx press, and sizzle) do well on accessibility? |
Hi @bertiewooster, thank you for writing. I haven't had a chance to have a serious evaluation performed, but I suspect each of these themes needs some changes to font color & size. I hope to update this issue (and the relevant PRs) later this week with some specific feedback from an a11y specialist. I'll ping you when I have that data |
@intoverflow I'm having trouble getting external themes such as Press to work. I followed the installation instructions:
I also tried adding, as you did, to doc/requirements.txt Any tips? |
@bertiewooster In theory it should work. If you have a commit I'd be happy to test it on my environment to see if I can replicate the problem. Perhaps there's something going wrong with the python search paths? (This is just a guess.) In case it's useful, I've provided some notes below about my build environments. I've also included a note about package names, but after some testing I no longer believe it's relevant to the issue you're facing. My development environmentOn my host, sphinx & sphinx_press_theme were both installed using pip. They can be found here: ~/.local/lib/python3.9/site-packages$ ls -d sphinx sphinx_press_theme
sphinx sphinx_press_theme readthedocs.orgI've configured readthedocs.org to build every pull request. Their tools use Package nameI noticed that your On closer inspection, it seems the Press installation instructions provides conflicting instructions. One calls the package I checked my local development machine to see which I had installed: $ pip list | grep press
sphinx-press-theme 0.8.0 I tried installing "both" packages but, judging from the pip output, it appears they are synonyms: $ pip install sphinx-press-theme sphinx_press_theme
Requirement already satisfied: sphinx-press-theme in /home/tcarstens/.local/lib/python3.9/site-packages (0.8.0)
Requirement already satisfied: sphinx>=4.0.1 in /home/tcarstens/.local/lib/python3.9/site-packages (from sphinx-press-theme) (4.3.1)
Requirement already satisfied: docutils<0.18,>=0.14 in /usr/lib/python3/dist-packages (from sphinx>=4.0.1->sphinx-press-theme) (0.16)
Requirement already satisfied: snowballstemmer>=1.1 in /usr/lib/python3/dist-packages (from sphinx>=4.0.1->sphinx-press-theme) (2.1.0)
Requirement already satisfied: sphinxcontrib-htmlhelp>=2.0.0 in /home/tcarstens/.local/lib/python3.9/site-packages (from sphinx>=4.0.1->sphinx-press-theme) (2.0.0)
Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (from sphinx>=4.0.1->sphinx-press-theme) (52.0.0)
Requirement already satisfied: sphinxcontrib-serializinghtml>=1.1.5 in /home/tcarstens/.local/lib/python3.9/site-packages (from sphinx>=4.0.1->sphinx-press-theme) (1.1.5)
Requirement already satisfied: sphinxcontrib-devhelp in /home/tcarstens/.local/lib/python3.9/site-packages (from sphinx>=4.0.1->sphinx-press-theme) (1.0.2)
Requirement already satisfied: Pygments>=2.0 in /usr/lib/python3/dist-packages (from sphinx>=4.0.1->sphinx-press-theme) (2.7.1)
Requirement already satisfied: babel>=1.3 in /usr/lib/python3/dist-packages (from sphinx>=4.0.1->sphinx-press-theme) (2.8.0)
Requirement already satisfied: sphinxcontrib-qthelp in /home/tcarstens/.local/lib/python3.9/site-packages (from sphinx>=4.0.1->sphinx-press-theme) (1.0.3)
Requirement already satisfied: Jinja2>=2.3 in /usr/lib/python3/dist-packages (from sphinx>=4.0.1->sphinx-press-theme) (2.11.2)
Requirement already satisfied: requests>=2.5.0 in /usr/lib/python3/dist-packages (from sphinx>=4.0.1->sphinx-press-theme) (2.25.1)
Requirement already satisfied: packaging in /usr/lib/python3/dist-packages (from sphinx>=4.0.1->sphinx-press-theme) (20.9)
Requirement already satisfied: alabaster<0.8,>=0.7 in /usr/lib/python3/dist-packages (from sphinx>=4.0.1->sphinx-press-theme) (0.7.8)
Requirement already satisfied: imagesize in /usr/lib/python3/dist-packages (from sphinx>=4.0.1->sphinx-press-theme) (1.2.0)
Requirement already satisfied: sphinxcontrib-applehelp in /home/tcarstens/.local/lib/python3.9/site-packages (from sphinx>=4.0.1->sphinx-press-theme) (1.0.2)
Requirement already satisfied: sphinxcontrib-jsmath in /home/tcarstens/.local/lib/python3.9/site-packages (from sphinx>=4.0.1->sphinx-press-theme) (1.0.1) |
@intoverflow thanks! I've tried several variations without luck. Here's a (draft) pull request where I've tried to get the Press theme to work. In terms of my packages setup, I get the same results as you for these commands:
I build the Sphinx docs using Docker (per doc/Dockerfile.htmldoc), which works for the previous theme (
I'm still getting the error
|
Happy New Year! Adding @Cyndi206 |
We need to decide on a Sphinx theme for the guide.
We also need to decide on the requirements for selecting a guide.
Two obvious requirements stand out (please add/discuss in the comments if you have feedback/suggestions on these):
aria
tags, font & color pallet, etcProposed themes should be submitted as pull requests. Read the Docs is integrated with our continuous integration; this makes it easy to see how the theme looks with our content (and thus easy to evaluate whether or not it meets our requirements).
To ease tracking, please link your pull request with this issue.
The text was updated successfully, but these errors were encountered: