Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Accessibility issues #317

Open
bansp opened this issue Sep 28, 2024 · 3 comments
Open

Accessibility issues #317

bansp opened this issue Sep 28, 2024 · 3 comments
Labels
accessibility concerns accessibility properties of the SIS as a site discussion hub Meant as target for individual action tickets. Please don't assign 'hub' tickets.
Milestone
the milestone tha...

Comments

@bansp
Copy link
Member

bansp commented Sep 28, 2024 •
edited
Loading

I have taken a glimpse at the slides on web accessibility in CLARIN. The SIS is explicitly mentioned there with a score of 70%, which is not entirely bad, given that the best CLARIN site scores at 87%, while the worst at 50%. But we can do better and this ticket is designed to gather issues that target accessibility.

First, a list of the most important issues. I have numbered them for ease of referencing.

  1. Use good contrast.
  2. Black and white is not bad.
  3. Does it work on phones and laptops?
  4. Give alternative text to graphics and pictures.
  5. Underline your links and state the purpose in the text of the link.
  6. State the languages in use.
  7. Encode your structures.
    a. Use regions like header, main and footer.
    b. Use headlines hierarchies.

There are tools that assist in checking sites for the above properties and others. In my Chromium, I can see Lighthouse (under dev tools), but I don't yet understand its output. Another free tool mentioned in the slides is WAVE.

One thought that occurs to me is that the aesthetics of the SIS is not fully in line with the above hints (compare item 5), but we would probably prefer to keep it, at least as a default. So the first question is: how sensible would it be to install a switch from the default SIS interface to one with enhanced accessibility features? I guess I should turn that into a separate issue...

List of the relevant issues:
@bansp bansp added discussion hub Meant as target for individual action tickets. Please don't assign 'hub' tickets. accessibility concerns accessibility properties of the SIS as a site labels Sep 28, 2024
@bansp bansp added this to the the milestone that isn't milestone Sep 28, 2024
@bansp bansp mentioned this issue Sep 28, 2024
Open
@bansp
Copy link
Member Author

bansp commented Sep 28, 2024

To be sure, we can work on certain features (such as ensuring metainformation in the generated HTML <head> sections) without a switch. The switch would work for, e.g., link decoration, colour pallette, etc. -- the visible elements.

@bansp
Copy link
Member Author

bansp commented Sep 28, 2024

https://wave.webaim.org/report#/https://standards.clarin.eu/sis/index.xq
-- that is pretty cool. For example, it shows that we should add lang="en" to the <html> element -- that's something to be fixed right away. But then, it points to low contrast between the text and the background -- and that is a matter of a switch, I'd say.
We should go through them one by one (but first hunt for examples and discussion of an auto-triggered (?) switch; maybe it's hiding somewhere in the CSS media selectors?).

bansp added a commit that referenced this issue Sep 29, 2024
@bansp
stamp the entire html tree with lang="en", because if we switch langs…
15cce6f 
…, we only do so locally (for now); references #317
@bansp
Copy link
Member Author

bansp commented Sep 30, 2024

This is the initial state, produced with Lightning (emulating desktop, analysing a snapshot of the home page), for the record:
image

I have submitted one fix, but the rest of the score is going to take quite a while, I'm afraid.

bansp added a commit that referenced this issue Sep 30, 2024
@bansp
add lang="en" to all html roots under views/ (#317)
ff93867
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accessibility concerns accessibility properties of the SIS as a site discussion hub Meant as target for individual action tickets. Please don't assign 'hub' tickets.
Projects
None yet
Milestone
the milestone that isn't
Development

No branches or pull requests
1 participant
@bansp