Increase options/guidance for compliance with Web Content Accessibility Guidelines (WCAG) in revealjs HTML output #8621
rressler
started this conversation in
Feature Requests
Replies: 5 comments 2 replies
-
@rressler are your organization's requirements publicly available someplace we can look? Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
1 reply
-
The enterprise product is Siteimprove. Here is a link to the free browser plug-in for testing<https://www.siteimprove.com/integrations/browser-extensions/>. They use this tool because it is more user-friendly.
Since Quarto is open-source, they offered the following details.
* Siteimprove uses its own Alpha Ruleset<https://alfa.siteimprove.com/rules>, which is based on the W3C ACT-Rules<https://act-rules.github.io/rules/>.
* Deque Axe<https://www.deque.com/axe/> is another popular tool preferred by developers and uses it’s Axe 4.8<https://dequeuniversity.com/rules/axe/4.8> ruleset which is also based on W3C ACT-Rules.
Both rulesets are extremely similar, so either is fine.
Lastly, automated scanning only covers about 60% of the WCAG 2.1 guidelines<https://www.w3.org/WAI/standards-guidelines/wcag/> so they use manual testing for keyboard access<https://webaim.org/techniques/keyboard/> and Content Scaling<https://webaim.org/resources/evalquickref/#scaling>. These tests only take a few seconds or minutes are a good indicator for testing if content is accessible to more WCAG guidelines.
From: Carlos Scheidegger ***@***.***>
Date: Tuesday, February 6, 2024 at 11:50 AM
To: quarto-dev/quarto-cli ***@***.***>
Cc: Richard Ressler ***@***.***>, Mention ***@***.***>
Subject: Re: [quarto-dev/quarto-cli] Increase options/guidance for compliance with Web Content Accessibility Guidelines (WCAG) in revealjs HTML output (Discussion #8621)
External Email: Use caution with links and attachments.
Sorry, I should have clarified. I know what the WCAGs are - I wanted to know what tools your organization is going to use to enforce them so we know precisely what we're targeting.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/quarto-dev/quarto-cli/discussions/8621*discussioncomment-8385108__;Iw!!IaT_gp1N!0SUiBT98Qp5gM-3AkQyO-GdaLic9lWOsV3jty3MbgvGQzCak61nN5rnBuOWt0ntVzuY7xkZ5R-mYWsyvG7XfeIW_0uo$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AOCMN3NE2LHRETGSQUQICJDYSJNODAVCNFSM6AAAAABC4EABYKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGOBVGEYDQ__;!!IaT_gp1N!0SUiBT98Qp5gM-3AkQyO-GdaLic9lWOsV3jty3MbgvGQzCak61nN5rnBuOWt0ntVzuY7xkZ5R-mYWsyvG7Xf-SajW54$>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
I've opened an enhancement issue for |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
My organization is requiring strict compliance with WCAG 2.1 for posting any HTML materials or links to other materials. There are at least two snags with current revealjs output that appear to require coding in javascript to resolve. Without it I cannot post html documents or links to them (e.g., on quarto pub) on organization pages.
I am not an expert in WCAG by any means so there may be others that could be addressed (see the a11y plugin.
It would also be helpful if there was a plug in or option to convert tabsets to individual pages (Note that one significant disadvantage to tabsets is that only the first tab will be visible when printing to PDF.) so that HTML pages could be more cleanly converted to PDF for accessibility.
Beta Was this translation helpful? Give feedback.
All reactions