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
Fixed #35143 -- Improved accessibility of 404/500 debug pages. #17787
Conversation
Apologies for the multiple failed checks; I have the pre-commit running locally now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MHLut Thanks 👍 I left comments.
As far as I can see, I've resolved all the issues we've found in the last two days. |
8acfc57
to
88978f2
Compare
@MHLut Thanks for updates 👍 |
Note: The Selenium test that failed is As far as I know, my changes should not touch the admin, and I'm not sure where this is coming from. |
This: - changes the header, main, and footer content areas to be rendered in a <header>, <main>, and <footer> tags, - adds scope attributes to <th>, - uses <code> for a patterns list, - uses <small> instead of <span>.
Fixes ticket #35143.
Notes
The HTTP 400 error page uses the same template as HTTP 500.
Requested changes
The page should have a header, main, and footer.
Done. I did not fix the indentation within the
<main>
element in the HTTP 500 template because it would cause a shift in most lines. The new CSS is hence somewhat hacky.The indentation is currently inconsistent and is best fixed in a separate ticket.
Each table should have scope attributes on th elements.
Done.
Monospaced text in the patterns list should use a code element.
Done for all the pattern items in the HTTP 404 template. I kept the CSS line that sets the list font to monospace, to prevent a visual change to the list marker font.
I have also wrapped the
Python Path
value in the HTTP 500 page in a code block, but couldn't get a working unit test for this scenario. (there is a test draft in the related commit message).I left all other
<pre>
elements without<code>
for future tickets.The small text within the h1 should use a small element instead of a span.
Done. Since
<small>
looked different from the original styled span, I reused the former's CSS.