w3c/wcag21

Success Criterion 2.5.3 Target Size Dec WD Comment Public Comment ~comment-target-size
#631 opened Dec 13, 2017 by MichellanneLi
Success Criterion 1.4.13 Content on Hover or Focus Dec WD Comment Public Comment ~comment-content-on-hover-or-focus
#630 opened Dec 13, 2017 by MichellanneLi
Success Criterion 1.3.4 Identify Common Purpose needs Understanding and Techniques Dec WD Comment Public Comment ~comment-identify-common-purpose
#629 opened Dec 13, 2017 by carmacleod
Success Criterion 1.4.11 Graphics Contrast Dec WD Comment Public Comment ~comment-graphics-contrast
#628 opened Dec 13, 2017 by MichellanneLi
Success Criterion 1.3.4 Identify Common Purpose - comment on "COMPOSE" Dec WD Comment Public Comment ~comment-identify-common-purpose
#624 opened Dec 13, 2017 by carmacleod

1
2.6 Suggested Guideline Text Dec WD Comment Member Comment
#622 opened Dec 12, 2017 by SuzanneTaylor
Success Criterion 2.6.1 Motion Actuation: Consider separating device motion and user motion into two SC to make guidance easier to understand and to prepare for future SC under 2.6 Dec WD Comment Member Comment ~comment-motion-actuation
#621 opened Dec 9, 2017 by SuzanneTaylor

3
Success Criterion 2.6.1 Motion Actuation - SC includes user motion, but understanding document does not Dec WD Comment Member Comment ~comment-motion-actuation
#620 opened Dec 9, 2017 by SuzanneTaylor

1
Success Criterion 2.6.1 Motion Actuation: Probably need to establish scale of motion within the understanding documentation Dec WD Comment Member Comment ~comment-motion-actuation
#619 opened Dec 9, 2017 by SuzanneTaylor

2
Typos and things Dec WD Comment Public Comment
#618 opened Dec 8, 2017 by StommePoes

1
1.4.11 - *active* user interface components? Dec WD Comment Public Comment ~comment-graphics-contrast
#617 opened Dec 8, 2017 by jared-w-smith
SC title for 1.4.11 will cause confusion Dec WD Comment Public Comment ~comment-graphics-contrast
#616 opened Dec 8, 2017 by karlgroves

3
WHICH vs THAT Grammatical - but some with normative implications Dec WD Comment Member Comment
#609 opened Dec 7, 2017 by GreggVan

5
Success Criterion 2.2.6 Accessible Authentication§ Dec WD Comment Member Comment ~comment-accessible-authentication
#608 opened Dec 7, 2017 by GreggVan
Success Criterion 3.2.6 Status Change - Scope is too narrow in current Editor's Draft & Final Draft Dec WD Comment Member Comment ~comment-status-messages
#605 opened Dec 6, 2017 by SuzanneTaylor

1
Success Criterion 1.3.4 Identify Common Purpose [Trace] Dec WD Comment Member Comment ~comment-identify-common-purpose
#602 opened Dec 6, 2017 by GreggVan
Conventional Links / skip to main content Public Comment ~comment-identify-common-purpose
#601 opened Dec 5, 2017 by michael-n-cooper

2
Exit criteria technology-specific? Public Comment
#598 opened Dec 1, 2017 by kerstinp
Security of autofill Member Comment ~comment-identify-common-purpose
#590 opened Nov 23, 2017 by alastc

9
Understanding document Zoom Content / Reflow Content Public Comment
#589 opened Nov 21, 2017 by kerstinp
For purpose of controls, more terms are needed Public Comment ~comment-identify-common-purpose
#586 opened Nov 20, 2017 by User1stAmihai
Contrast range for alpha transparent colors Implementation Follow-up Member Comment
#571 opened Nov 8, 2017 by LeaVerou

2
Concern with 1.3.4 Purpose of Controls Member Comment ~comment-identify-common-purpose
#570 opened Nov 7, 2017 by mbgower

4
remove the word "accessible" from handles for SCs Member Comment ~comment-accessible-authentication
#568 opened Nov 6, 2017 by DavidMacDonald
"Legal requirement" in SC2.2.6 Public Comment ~comment-accessible-authentication
#564 opened Nov 6, 2017 by guyhickling

Previous 1 2 3 4 5 Next

ProTip! Type g i on any issue or pull request to go back to the issue listing page.