w3c / wai-intro-wcag

wai-intro-wcag

Preview: https://wai-intro-wcag.netlify.com/

Translation Notes for WCAG 2 at a Glance

Please consider the wording in the WCAG 2.2 success criteria. If there is a translation of WCAG 2 in your language, review it thoughtfully. This text is not the same as the success criteria wording — it is a paraphrased summary that is intended to be easier to understand and accurate - yet it does not need to be comprehensive.

Please collaborate with others who are familiar with WCAG to refine this wording in your language. Thank you!

wai-intro-wcag's Issues

Reflow persona: emphasize the severity of horizontal scrolling at every line

Issue

From w3c-wai-ig 2020-09-18:

Please consider the following.
"It's nearly impossible to read text if I have to scroll right and left to read each line. It's disorienting and I lose my place. It makes it hard to understand what I'm reading."
ADD
"I have to scroll 50 to 100 times to read one page."

The gross amount of scrolling is overwhelming. This was the one SC that got 100% support from the LVTF.

Best, Wayne

Current content

https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/

Parent with low vision – 20/400:

Problem: It's nearly impossible to read text if I have to scroll right and left to read each line. It's disorienting and I lose my place. It makes it hard to understand what I'm reading.

Works well: I increase the text size 400% and it reflowed within the width of the window. I can read it easily without scrolling back and forth.

Proposed text

Parent with low vision – 20/400:

Problem: It's nearly impossible to read text if I have to scroll right and left to read each line. It's disorienting and I lose my place. It makes it hard to understand what I'm reading. I have to scroll 50 to 100 times to read one page.

Works well: I increase the text size 400% and it reflowed within the width of the window. I can read it easily without scrolling back and forth.

add footer

Determining conformance

In WCAG intro we currently say:

The success criteria are what determine “conformance” to WCAG. That is, in order to meet WCAG, the content needs to meet the success criteria.

What determines conformance in WCAG2 is Conformance Requirements

Which of course comprises SCs but implies more than these: complete processes, accessibility support, no interference, etc.

spam

[Persona Quote] - 1.3.6 Persona Quote issue

Problem: I have software that changes the words in the navigation into symbols. It doesn't work at all with some websites.

Works well: It works pretty good with some websites.

In a lot of the persona quotes, the "Problem" and "Works Well" are generally not connected to each other, and if they are, they can most often stand on their own too. This one, they must be connected. The Works Well quote only makes sense if you have read the Problem quote.

Maybe just defining "It" in the works well quote.

[!! New in 2.1] Tiny typo in persona quote for 1.3.5?

I think there may be a typo in the persona quote for WCAG 2.1 SC 1.3.5. I suggest putting the word "to" just before the word "work" in the last sentence:

• current text: Works well: "I love websites that can automatically fill it all in for me. Then I don't have work so hard to get the numbers and spelling right."
• proposed change: Works well: "I love websites that can automatically fill it all in for me. Then I don't have to work so hard to get the numbers and spelling right."

Provide examples for guidance on using heading levels in a dialog

Below is the update provided in the comment posted by mcking65

After discussion in the February 12, 2018 meeting, there is an agreement that the dialog titles could be either H1 or H2.
Some members point out there could also be circumstances where H3+ could be appropriate.

We concluded:

• It is helpful if there is a consistent approach across dialogs in an application.
• There is not necessarily a need for the APG to prescribe a specific approach.

Based on the above comment, if there is no need to prescribe a specific approach, we should at least provide some examples. Those examples should provide guidance to decide when to use H1 and non H1 heading levels.

[low-medium priority] breadcrumb bug

https://www.w3.org/WAI/standards-guidelines/wcag/20/glance/

WCAG 2.1 logos

Is there going to be an update in the images?
https://www.w3.org/WAI/standards-guidelines/wcag/conformance-logos/

Prepare for Translations

rel: w3c/wai-translations#22

[New in 2.1] SC CSS for DLs

SPAM

SPAM

Typo

There seems to be a typo on this page : https://www.w3.org/WAI/standards-guidelines/wcag/

"Expections" should be "exceptions"

[!! New in 2.1] Typo: cerbal palsy

This:

Person with cerbal palsy who uses a wheelchair:

should be:

Person with cerebral palsy who uses a wheelchair:

Update reference from WCAG 2.1 to WCAG 2.2 in non-web-ict overview page

Related to WCAG issue 393, when WCAG 2.2 becomes a recommendation, this content needs updating on the WCAG2ICT Overview page.

Note: WCAG2ICT is still relevant for later versions of WCAG 2. For example, WCAG 2.1 WCAG 2.2 does not change the requirements of WCAG 2.0 that are addressed in WCAG2ICT; WCAG 2.1 WCAG 2.2 adds additional requirements. W3C may update WCAG2ICT in the future to add the additional requirements from later versions of WCAG 2.

[!! New in 2.1] Typo: Yan/Yun

This:

Yan, retiree with low contrast sensitivity:

should be:

Yun, retiree with low contrast sensitivity:

Same lower in the page:

s/Yan/Yun/

(in 1.4.11. and 1.4.12.)

SPAM

SPAM

[What's New] Quote structure

The quotes look weird to me. Due to the visual and the code, I assumed “Problem“ and “Works well“ was part of the quote.

<blockquote class="quotes">
  <p>Problem: "I can't rotate my tablet —  it's attached to my wheelchair."</p>
  <p>Works well: "The application works whether I  attach my tablet horizontally or vertically."</p>
</blockquote>

If we keep that structure I think the html should be (<q> element adds quotes automatically):

<ul>
<li>Problem: <q>I can't rotate my tablet —  it's attached to my wheelchair.</q></li>
<li>Works well: <q>The application works whether I  attach my tablet horizontally or vertically.</q></li>
</ul>

It also feels weird that the text before the quote(s) is italic, but the quote is not. I wasn’t making the connection because of the formatting.

I think it would be good to have a heading “persona quote”.

And I wonder if we want to merge the quotes into one: My tablet is attached to my wheelchair and I can’t rotate it. That means that applications need to work whether I attach my tablet in portrait or landscape orientation.

update description

OK for now -- update it when updating the page overall

Preparation for the Redesign

👋 The redesign is coming to this repository soon. (Hooray! 🎉) We need to check off several steps before we can link your content to the redesign repository. I marked some of the steps with RM meaning Resource Manager. Others are marked with @yatil, and I’ll do/help you through the technical parts.

In addition to this issue, you might find other issues in your repository that are labeled with wai-redesign-before that should be addressed/resolved before the redesign. That might mean to postpone working on it until after the redesign (use the label wai-redesign-after for those issues).

• Content is updated and ready to be put into the new design. (RM)
  • The best case scenario would be that the content is ready before doing step three below. However, that might not be feasible in every case, so @yatil might do the next step before the content is ready and just port the content that is available to him.
  • Once done, add label wai-redesign-content-done.
• Tech Create branch/repository with the new structure (@yatil)
  • For simple resources (separate pages/pages that don’t need a left navigation), you will find the documents in the root directory of the repository.
  • For more complicated resources, @yatil creates a Jekyll collection which adds the left sidebar navigation amongst other things. You will then find your files in a folder called _resource_name.
  • Documentation should be available in the w3c/wai-website wiki soon.
  • Once done, add label wai-redesign-repo-done.
• Content Use current content and port it to the new design (@yatil)
  • Once this is done, all previews will be in the new design.
  • Once done, add label wai-redesign-content-ported.
• Content Check if content renders well, make changes as needed/wanted. (documentation) (RM)
  • Once done, add label wai-redesign-content-checked.
• Tech Link this repository to the w3c/wai-website repository (@yatil)
  • Once done, add label wai-redesign-repo-linked.
• When all checkpoints above are checked, close this issue.

[!] [What's New in 2.1] - clarify misunderstanding 1.4.12 Text Spacing

you do not have to set your content like that! just let users.

also, submit PR for Understanding doc to make it big and clear, probably before Intent

[!! New in 2.1] 2.4.1. Motion Actuation: link missing

The section 2.4.1. Motion Actuation lacks a link to the Understanding page:
https://www.w3.org/WAI/WCAG21/Understanding/motion-actuation.html

SPAM

Thank you so much

Deposit

Remove "attention deficit hyperactivity disorder" from text spacing persona

Hi Shawn,

As I mentioned in last week's LVTF meeting, the text "attention deficit hyperactivity disorder" should be removed from the text spacing persona as we have no research that supports ADHD. We only have research for dyslexia and low vision. Details are in the understanding doc resources section.

Thanks,
Laura

"WCAG 2.1 at a Glance" links broken

https://www.w3.org/WAI/standards-guidelines/wcag/glance/

All or most of the anchor tags on this page appear to be wrong or outdated.

Update logos page for better information about WCAG 2.1

follow up from #21

[FAQ] Add item to describe levels

It’s a question that I get a lot asked about: What is the hierarchy of A, AA, and AAA? What do I need to meet? Would be good to have a short answer to it.

spam

SPAM

SPAM

SPAM

[low] [adding logos page] configurator for version, level, color -> HTML

https://w3c.github.io/wai-intro-wcag/standards-guidelines/wcag/conformance-logos/

Wishlist: Configurator for user to select which version (2.0, 2.1), Level (A, AA, AAA) and color -- then it provides the correct HTML code.

spam

Instructions for Commenting on WCAG 2 Documents

figure out situation with these two pages:

• https://www.w3.org/WAI/standards-guidelines/wcag/commenting/
• https://www.w3.org/WAI/WCAG21/comments/

Should they both exist? Or, should one redirect to the other? Do they need updating?

Also, make them easier to read, understand, use.

spam

[2.0 Glance] fix breadcrumb

https://www.w3.org/WAI/standards-guidelines/wcag/20/glance/

has

HomeStandards/GuidelinesMobile Accessibility at W3C

Misspelled the Word "JavaScript" on the "WCAG 2 FAQ" Page

The word "JavaScript" on the "WCAG 2 FAQ" Page ( https://www.w3.org/WAI/standards-guidelines/wcag/faq/ ) is misspelled in two places on the page. It is found in the "Page Contents" section, and then the one where the text "Can I meet WCAG 2 with Javascript/Ajax, Silverlight, and other technologies?. The "S" in JavaScript should be capitalized.

[wcag3 intro] rewrite list-y

The current version has a few paragraphs of text and lots of bullets. The bullets work really well for some people (including several EOWG participants). They do not work well for some people (who have given such feedback to Shawn).

Action item: Take a pass at a rewrite to better meet differing user needs and preferences. (e.g., maybe one column of text and one column of more bullet-like, though probably not with bullets but more like diagrams (in SVG)?

[wcag2ict] [medium] add info about WCAG 2.1 adoption in EN 301 549 for other ICT?

https://www.w3.org/blog/2018/09/wcag-2-1-adoption-in-europe/

updated version of EN 301 549 “Accessibility requirements for ICT products and services”. The most significant change in this version is adoption of the W3C “Web Content Accessibility Guidelines (WCAG) 2.1″ for web content, electronic documents, and non-web software, such as native mobile applications.

Hey

Please remove plugins or add one blocking this site

Correct tag for the title of "fixed" banners (cookie consent, notifications, etc.)

For "fixed" dialogs displayed on the page, like a "cookie consent banner" or "subscribe to notifications", what is the recommended tag for the title?

Is it correct to use h1 to separate it from the main content?

Or another tag is more appropriate?

[Instructions for Commenting on WCAG 2 Documents] Says WCAG 2 is not developed anymore, despite WCAG 2.2 being developed right now

Note that comments on WCAG 2 cannot impact the standard since it is no longer in development, although we will still take them into consideration as described below.

This is probably a little misleading.

[low] [At a Glance] print version

Make new print version. The add back

<h2 id="print-version">Print Version</h2>
<p>This page is formatted for printing (without the navigation) as PDF files for A4 and 8.5” x 11” paper:</p>
<ul>
  <li><a href="https://www.w3.org/WAI/WCAG20/glance/WCAG2-at-a-Glance-a4.pdf">WCAG 2 at a Glance (PDF) A4</a></li>
  <li><a href="https://www.w3.org/WAI/WCAG20/glance/WCAG2-at-a-Glance.pdf">WCAG 2 at a Glance (PDF) 8.5x11</a></li>
</ul>

spam

spam

spam?

[!! New in 2.1] Persona name / no name

Problem:

• It feels strange that some personas were named and some not.

Correction:

• Either add names when they're missing
• Or remove names altogether.

My preference goes with adding the missing names as it helps (I think) personify the concept (like the nice “OK I know I'm a geek” one persona says, for example).

PS: I saw the footnote but assuming it won't be in final document, it feels strange. As usual, feel free to ignore my remarks etc. ;)

Expected WCAG 3.0 timeline needs updating

Looking at the WCAG 3 Introduction, it appears that several things on this page could benefit from updates, but minimally the timeline which currently indicates was last updated 7 Dec 2021 Timeline (updated 7 December 2021). Can @rachaelbradley or @michael-n-cooper provide input to @shawna-slh to help with this, or can Michael update it directly? Please ping back to me by email as well as GH if needed, thanks.

[Glance 2.1] Separate versions for 2.1 and 2.0

From @yatil #15 (comment)

Didn’t we want to get rid of version numbers? If the WCAG 2.1 stuff is clearly marked, we should be good. I would not want to have two versions of the page, and restricting it to WCAG 2.1 (by the title) is not too useful, imho.

SPAM

spam

Suggested weaks to text

https://www.w3.org/WAI/WCAG2/supplemental/

Following the supplemental guidance is not required to meet WCAG. AndHowever, we encourage you to follow this guidance in order meet more user needs.

Addressing the accessibility issues as presented in the supplemental guidance areis essential for people with certain disabilities to be able to use digital technology.