Accessibility Guidelines Working Group - Activity in 2019
No matches.
Lifecycle
-
1 charter started.
-
Chartered until 31 October 2022. Participants had to rejoin under this charter.
-
Participants
-
1 participant joined.
-
Paul Bohman (Deque Systems, Inc.) joined.
-
-
6 participants left.
-
Scott Cooley (Deque Systems, Inc.) left.
-
Juli-Ann Rowsell (W3C Invited Experts) left.
-
Alina Lupu (W3C Invited Experts) left.
-
Greg Lowney (W3C Invited Experts) left.
-
Pietro Cirrincione (W3C Invited Experts) left.
-
Srinivasu Chakravarthula (W3C Invited Experts) left.
-
-
8 organizations joined.
-
TetraLogical Services Ltd joined.
-
DAISY Consortium joined.
-
Adobe joined.
-
Level Access joined.
-
Deque Systems, Inc. joined.
-
Knowbility joined.
-
Educational Testing Service joined.
-
Gain joined.
-
-
49 organizations left.
-
Royal National Institute of Blind People (RNIB) left.
-
Duck Duck Go, Inc. left.
-
Green Technology Co left.
-
Mada Center, Qatar left.
-
Amazon left.
-
Macmillan Learning left.
-
Dyno Mapper left.
-
Thomson Reuters Corp. left.
-
eyeo GmbH left.
-
Salesforce left.
-
Cyxtera Technologies, Inc. left.
-
Wells Fargo Bank N.A. left.
-
TetraLogical Services Ltd left.
-
NYC Department of Education left.
-
AKEA Web Solutions, LLC left.
-
AccessibilityOz left.
-
Universidad Politécnica de Madrid left.
-
Media Access Australia left.
-
Search Engine Optimization Inc left.
-
Microsoft Corporation left.
-
HM Government left.
-
AMAC Accessibility Solutions & Research Center left.
-
SAP SE left.
-
Fraunhofer Gesellschaft left.
-
Accessibility Foundation left.
-
University of Illinois left.
-
NIC.br - Brazilian Network Information Center left.
-
University of Southampton left.
-
MITRE Corporation left.
-
Google LLC left.
-
Zhejiang University left.
-
AbleDocs left.
-
Oracle Corporation left.
-
IBM Corporation left.
-
Boeing Company left.
-
Educational Testing Service left.
-
Alibaba Group left.
-
LSEG left.
-
Association BrailleNet left.
-
DAISY Consortium left.
-
Level Access left.
-
BarrierBreak Solutions Private Limited left.
-
Deque Systems, Inc. left.
-
Pearson plc left.
-
Adobe left.
-
Gain left.
-
Knowbility left.
-
Siteimprove left.
-
TPGi left.
-
GitHub
w3c/wcag
-
15 issues opened.
-
2.4.7 as it applies to static content and programmatic focus w3c/wcag#1001, by @mfairchild365.
-
Add WCAG-EM / ATAG reference w3c/wcag#1000, by @alastc.
-
1.3.5 w3c/wcag#996, by @detlevhfischer.
-
Testing of events with JS w3c/wcag#995, by @JAWS-test.
-
Remove URI from section headers w3c/wcag#989, by @sajkaj.
-
Should C39 be a technique for 2.2.2: Pause, Stop, Hide? w3c/wcag#988, by @alastc.
-
Human review isn't all bad w3c/wcag#986, by @sajkaj.
-
Can text buttons fail 1.1.1 and 3.3.2? w3c/wcag#985, by @WilcoFiers.
-
Treatment of ad content w3c/wcag#983, by @detlevhfischer.
-
Scoping issue: Treatment of sub-domain content w3c/wcag#982, by @detlevhfischer.
-
-
13 issues closed.
-
Remove URI from section headers w3c/wcag#989.
-
Is Challenge #3 also about user provided content? w3c/wcag#947.
-
Human review isn't all bad w3c/wcag#986.
-
1.3.5 w3c/wcag#996.
-
Should guidance extend beyond web content? w3c/wcag#945.
-
Challenge #1 should be renamed w3c/wcag#956.
-
Terms to Define in Our Glossary w3c/wcag#962.
-
Document goals need a better explanation w3c/wcag#972.
-
Better Design Templates and Procedures Can Help w3c/wcag#938.
-
-
41 issues received 162 new comments.
-
Can text buttons fail 1.1.1 and 3.3.2? w3c/wcag#985 (35 comments by @alastc, @awkawk, @bruce-usab, @DavidMacDonald, @JAWS-test, @mraccess77, @patrickhlauke, @Ryladog, @WilcoFiers)
-
Human review isn't all bad w3c/wcag#986 (15 comments by @alastc, @detlevhfischer, @JAWS-test, @michael-n-cooper, @NeilMilliken, @peterkorn, @sajkaj)
-
Text spacing: does it require compatibility with one or all methods? w3c/wcag#975 (9 comments by @alastc, @JAWS-test, @mraccess77, @patrickhlauke)
-
2.4.7 as it applies to static content and programmatic focus w3c/wcag#1001 (8 comments by @JAWS-test, @mfairchild365, @patrickhlauke)
-
Understanding 3.3.1: Error Identification slightly unfocused/mixes up various concepts w3c/wcag#977 (8 comments by @alastc, @JAWS-test, @mraccess77, @patrickhlauke)
-
Meet 1.3.5 via name attributes mapping to schema.org? w3c/wcag#935 (7 comments by @jake-abma, @JAWS-test, @mraccess77)
-
Should C39 be a technique for 2.2.2: Pause, Stop, Hide? w3c/wcag#988 (6 comments by @alastc, @mraccess77, @patrickhlauke)
-
Extend "programmatically determined" for markup language via A11Y API w3c/wcag#984 (6 comments by @alastc, @awkawk, @patrickhlauke)
-
Automatic testing makes less sense than expected (using SC 1.4.3 as an example) w3c/wcag#998 (5 comments by @JAWS-test, @Myndex)
-
SC 1.4.10: What is the minimum height for vertically scrolling content? w3c/wcag#987 (5 comments by @alastc, @JAWS-test, @mraccess77, @Myndex, @patrickhlauke)
-
Scoping issue: Treatment of sub-domain content w3c/wcag#982 (5 comments by @alastc, @detlevhfischer, @jake-abma, @mraccess77)
-
Users Don't See Partially Constructed Web Content w3c/wcag#941 (4 comments by @alastc, @peterkorn, @sajkaj)
-
The solutions given in section 5.4 of WCAG 2.1 should be cited, and their implications discussed. w3c/wcag#993 (4 comments by @jasonjgw, @peterkorn, @sajkaj)
-
ACT-Rule for page title may be at odd with WCAG 2 interpretation of page titles w3c/wcag#980 (4 comments by @mraccess77, @patrickhlauke, @Ryladog)
-
Examples for SC 2.1.4 too faint - difficult to discern w3c/wcag#953 (3 comments by @JAWS-test, @mraccess77, @spanchang)
-
Language for 1.13 Reflow challenges (SC 1.4.10) needs more description. w3c/wcag#960 (3 comments by @joecron, @sajkaj)
-
Urban Construction Metaphor is a Different Situation w3c/wcag#939 (3 comments by @detlevhfischer, @sajkaj, @slauriat)
-
+copyrighted, etc. challenges -issue raissed at TPAC 2019 w3c/wcag#944 (2 comments by @alastc, @sajkaj)
-
1.3.4 Orientation - F97 (Locking orientation) - screen size irrelevant in testing? w3c/wcag#877 (1 comment by @JAWS-test)
-
What does nested according to the specification mean in SC 4.1.1 w3c/wcag#978 (1 comment by @alastc)
-
Testing templates / reusable widgets; responsibility for 3rd party content w3c/wcag#948 (1 comment by @sajkaj)
-
1.4.13 Content on Hover or Focus - dismissable and persistent clarification w3c/wcag#914 (1 comment by @JAWS-test)
-
-
7 pull requests opened.
-
Delete charter.html w3c/wcag#1002, by @toki1314.
-
Update index.html w3c/wcag#992, by @joecron.
-
Fix minor typo in G54 techniques w3c/wcag#991, by @dashdashzako.
-
Update index.html w3c/wcag#981, by @joecron.
-
-
4 pull requests merged.
-
Fix minor typo in G54 techniques w3c/wcag#991.
-
Update index.html w3c/wcag#981.
-
1 pull request closed.
-
Update index.html w3c/wcag#992.
-
-
6 pull requests received 9 new comments.
w3c/wcag3
-
1 issue opened.
-
Button accessible name context w3c/wcag3#184, by @mraccess77.
-
-
1 issue received 1 new comment.
Low Vision Accessibility Task Force
GitHub
w3c/low-vision-a11y-tf
-
1 issue opened in the Low Vision Accessibility Task Force.
-
Minimum size and Scaling w3c/low-vision-a11y-tf#85, by @Myndex.
-
Participants
-
1 participant joined.
-
Cybele Sack (W3C Invited Experts) joined.
-
-
1 organization joined.
-
Duck Duck Go, Inc. joined.
-
GitHub
w3c/wcag
-
47 issues opened.
-
What does nested according to the specification mean in SC 4.1.1 w3c/wcag#978, by @mraccess77.
-
2.2.1 Timing Adjustable and notifications/toasts/etc w3c/wcag#976, by @patrickhlauke.
-
Broken links in Understanding Contrast (Minimum) w3c/wcag#973, by @plannero.
-
Document goals need a better explanation w3c/wcag#972, by @sajkaj.
-
"Conformance requirements title" not present in Understanding w3c/wcag#970, by @jake-abma.
-
Understanding Conformance 2.1 only talks about 2.0 w3c/wcag#967, by @jake-abma.
-
Wrong linking Understanding pages WCAG 2.1 w3c/wcag#966, by @jake-abma.
-
The challenges document has some value judgments about WCAG w3c/wcag#965, by @DavidMacDonald.
-
Terms to Define in Our Glossary w3c/wcag#962, by @lauracarlson.
-
Incorrect info in Understanding Guideline 1.2: Time-based Media w3c/wcag#958, by @shawna-slh.
-
Challenge #1 should be renamed w3c/wcag#956, by @awkawk.
-
Participant list needs to be updated w3c/wcag#955, by @awkawk.
-
SC 1.3.5 isn't a challenge for non-web technologies w3c/wcag#954, by @awkawk.
-
Examples for SC 2.1.4 too faint - difficult to discern w3c/wcag#953, by @spanchang.
-
Sticky headers/footers violation of SC 2.4.7? w3c/wcag#952, by @JAWS-test.
-
Text alternatives that are not alternatives confusion w3c/wcag#951, by @LaurenceRLewis.
-
Add warning to technique H45 that longdesc is obsolete w3c/wcag#950, by @joppekroon.
-
Request for examples of problems combining content blocks w3c/wcag#949, by @sajkaj.
-
Is Challenge #3 also about user provided content? w3c/wcag#947, by @sajkaj.
-
Who should handle text spacing? w3c/wcag#946, by @sajkaj.
-
Should guidance extend beyond web content? w3c/wcag#945, by @sajkaj.
-
+copyrighted, etc. challenges -issue raissed at TPAC 2019 w3c/wcag#944, by @sajkaj.
-
Are there limits to the accessible component template approach? w3c/wcag#943, by @sajkaj.
-
Is this a question of scaling? More test surface than can be tested? w3c/wcag#942, by @sajkaj.
-
Users Don't See Partially Constructed Web Content w3c/wcag#941, by @sajkaj.
-
Is this a testability or conformance challenge? w3c/wcag#940, by @sajkaj.
-
Urban Construction Metaphor is a Different Situation w3c/wcag#939, by @sajkaj.
-
Better Design Templates and Procedures Can Help w3c/wcag#938, by @sajkaj.
-
Consider Sampling Strategies as in WCAG-EM w3c/wcag#937, by @sajkaj.
-
Meet 1.3.5 via name attributes mapping to schema.org? w3c/wcag#935, by @detlevhfischer.
-
Does the WebAim search input fails 1.4.11: Non-text Contrast? w3c/wcag#934, by @jake-abma.
-
Document title isn't conveying sufficient contextualization w3c/wcag#933, by @sajkaj.
-
1.4.10 Reflow: Is scrolling to reach the content allowed? w3c/wcag#932, by @gundulaniemann.
-
Real world accuracy of WCAG contrast formula? w3c/wcag#928, by @incyphe.
-
WCAG 2.1 SC 1.4.11 - techniques are inconsistent/unclear w3c/wcag#926, by @maryjom.
-
-
9 issues closed.
-
Urban Construction Metaphor is a Different Situation w3c/wcag#939.
-
Text alternatives that are not alternatives confusion w3c/wcag#951.
-
Real world accuracy of WCAG contrast formula? w3c/wcag#928.
-
40 issues received 197 new comments.
-
Technique H64 interpreted as 4.1.2 requiring descriptive accessible name? w3c/wcag#929 (50 comments by @awkawk, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke, @WilcoFiers)
-
SCR39 example (SC 1.4.13 content/hover) needs improving w3c/wcag#915 (19 comments by @alastc, @awkawk, @detlevhfischer, @JAWS-test, @mraccess77, @patrickhlauke)
-
Meet 1.3.5 via name attributes mapping to schema.org? w3c/wcag#935 (17 comments by @aardrian, @detlevhfischer, @johnfoliot, @patrickhlauke)
-
Does the WebAim search input fails 1.4.11: Non-text Contrast? w3c/wcag#934 (16 comments by @alastc, @jake-abma, @jared-w-smith, @lauracarlson, @patrickhlauke)
-
WCAG 2.1 SC 1.4.11 - techniques are inconsistent/unclear w3c/wcag#926 (11 comments by @alastc, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
Add warning to technique H45 that longdesc is obsolete w3c/wcag#950 (11 comments by @alastc, @awkawk, @JAWS-test, @joppekroon, @lauracarlson, @LJWatson, @mraccess77, @patrickhlauke)
-
Sticky headers/footers violation of SC 2.4.7? w3c/wcag#952 (9 comments by @alastc, @jake-abma, @JAWS-test, @mraccess77)
-
Challenge #1 should be renamed w3c/wcag#956 (8 comments by @alastc, @awkawk, @DavidMacDonald, @jake-abma, @mraccess77, @sajkaj)
-
"setting all of the following" wording nitpick in normative 1.4.12: Text Spacing w3c/wcag#930 (5 comments by @detlevhfischer, @jake-abma, @JAWS-test, @patrickhlauke)
-
2.2.1 Timing Adjustable and notifications/toasts/etc w3c/wcag#976 (4 comments by @detlevhfischer, @JAWS-test, @patrickhlauke)
-
3.3.1 Error identification - does the default browser error validation count as PASS? w3c/wcag#961 (4 comments by @JAWS-test, @mraccess77, @mtelgkamp, @patrickhlauke)
-
Understanding 3.3.1: Error Identification slightly unfocused/mixes up various concepts w3c/wcag#977 (3 comments by @patrickhlauke)
-
Language for 1.13 Reflow challenges (SC 1.4.10) needs more description. w3c/wcag#960 (3 comments by @detlevhfischer, @peterkorn)
-
Text alternatives that are not alternatives confusion w3c/wcag#951 (3 comments by @alastc, @JAWS-test, @LaurenceRLewis)
-
1.4.10 Reflow: Is scrolling to reach the content allowed? w3c/wcag#932 (3 comments by @alastc, @gundulaniemann, @JAWS-test)
-
SC 1.3.5 isn't a challenge for non-web technologies w3c/wcag#954 (2 comments by @detlevhfischer, @sajkaj)
-
accessibility supported and accessibility-supported are used interchangeably w3c/wcag#969 (2 comments by @alastc, @jake-abma)
-
Link for Understanding Conformance goes to 2.0 version, NOT the 2.1 w3c/wcag#968 (2 comments by @jake-abma)
-
Incorrect info in Understanding Guideline 1.2: Time-based Media w3c/wcag#958 (2 comments by @alastc, @shawna-slh)
-
What does nested according to the specification mean in SC 4.1.1 w3c/wcag#978 (1 comment by @JAWS-test)
-
Is this a question of scaling? More test surface than can be tested? w3c/wcag#942 (1 comment by @sajkaj)
-
Editorial change to Conformance Challenges, 1.24 Focus Order (Success Criterion 2.4.3) w3c/wcag#964 (1 comment by @sajkaj)
-
Greyed out submit buttons (conditional upon successful form completion) w3c/wcag#922 (1 comment by @alastc)
-
quickref: Sufficient Techniques & Failures not correct for 1.3.4 Orientation Level AA w3c/wcag#927 (1 comment by @yatil)
-
Ambiguity in understanding for 1.3.3 sensory characteristics w3c/wcag#750 (1 comment by @electronicwoft)
-
-
6 pull requests opened.
-
Additional content pre FPWD w3c/wcag#974, by @sajkaj.
-
Additions and Edits Preparatory to FPWD Consideration w3c/wcag#963, by @sajkaj.
-
On input w3c/wcag#959, by @JAWS-test.
-
Pull Request for Challenges w3c/wcag#957, by @sajkaj.
-
WCAG22 - focus visible enhanced w3c/wcag#936, by @alastc.
-
Non text contrast updates w3c/wcag#931, by @alastc.
-
-
3 pull requests merged.
-
Additional content pre FPWD w3c/wcag#974.
-
Pull Request for Challenges w3c/wcag#957.
-
Additions and Edits Preparatory to FPWD Consideration w3c/wcag#963.
-
-
2 pull requests closed.
-
Update glossary contrast ratio w3c/wcag#912.
-
On input w3c/wcag#959.
-
-
2 pull requests received 27 new comments.
-
WCAG22 - focus visible enhanced w3c/wcag#936 (26 comments by @alastc, @awkawk, @detlevhfischer, @JAWS-test, @mraccess77)
-
w3c/wcag-act
-
2 issues opened.
-
"accessibility requirements" does not allow for best practices w3c/wcag-act#424, by @WilcoFiers.
-
Old links in WG Note w3c/wcag-act#421, by @moekraft.
-
-
2 pull requests opened.
-
Generating updated draft with URLs to TR w3c/wcag-act#423, by @moekraft.
-
Update Common Input Aspects URLs w3c/wcag-act#422, by @moekraft.
-
-
2 pull requests merged.
-
Generating updated draft with URLs to TR w3c/wcag-act#423.
-
Update Common Input Aspects URLs w3c/wcag-act#422.
-
-
1 pull request received 1 new comment.
w3c/wcag3
-
1 issue received 2 new comments.
TR publications
-
1 document published.
-
Accessibility Conformance Testing (ACT) Rules Format 1.0 published as a Recommendation. History of Accessibility Conformance Testing (ACT) Rules Format 1.0
-
Participants
-
2 organizations left.
-
National Information Society Agency (NIA) left.
-
Web Watch Inc. left.
-
GitHub
w3c/wcag-act
-
1 issue closed.
-
Resolving "Page has a title" feedback w3c/wcag-act#416.
-
w3c/wcag
-
13 issues opened.
-
Typo in 3.2.4 Sufficient Technique Note 1 w3c/wcag#925, by @yatil.
-
WCAG 2.1 translations missing WCAG 2.0 errata w3c/wcag#921, by @WilcoFiers.
-
WCAG 2.0 errata missing from WCAG 2.0 w3c/wcag#920, by @WilcoFiers.
-
ARIA11 update the banner definition w3c/wcag#919, by @pgrucza.
-
Using CSS letter-spacing to control spacing within a word w3c/wcag#918, by @vikassharma1112.
-
1.4.11: please list color values with examples w3c/wcag#917, by @fstorr.
-
Clarify toolbar exception in Understanding Reflow 1.4.10 w3c/wcag#916, by @smhigley.
-
SCR39 example (SC 1.4.13 content/hover) needs improving w3c/wcag#915, by @JAWS-test.
-
Broken link on documentation page w3c/wcag#913, by @ginestra.
-
predicted amount change a status message? 4.1.3: Status Messages w3c/wcag#911, by @jake-abma.
-
-
3 issues closed.
-
Typo in 3.2.4 Sufficient Technique Note 1 w3c/wcag#925.
-
Understanding Non-text Contrast w3c/wcag#346.
-
-
27 issues received 92 new comments.
-
Technique G13 - allows surveys to advance on input with notice, even radio buttons? w3c/wcag#898 (16 comments by @alastc, @JAWS-test, @mraccess77)
-
Does 3.3.2 mandate forms that have required/optional fields indicate this visually? w3c/wcag#923 (11 comments by @awkawk, @JAWS-test, @mraccess77, @patrickhlauke, @WilcoFiers)
-
Greyed out submit buttons (conditional upon successful form completion) w3c/wcag#922 (7 comments by @jake-abma, @JAWS-test, @meesrutten, @mraccess77, @tremby)
-
Ambiguity in understanding for 1.3.3 sensory characteristics w3c/wcag#750 (6 comments by @alastc, @detlevhfischer, @JAWS-test, @patrickhlauke)
-
Using CSS letter-spacing to control spacing within a word w3c/wcag#918 (5 comments by @awkawk, @jake-abma, @JAWS-test, @mraccess77, @vikassharma1112)
-
Notifications - UI component contrast understanding 1.4.11 w3c/wcag#713 (5 comments by @alastc, @JAWS-test, @mraccess77, @petewoodhouse-rg)
-
1.4.13 Content on Hover or Focus - dismissable and persistent clarification w3c/wcag#914 (5 comments by @alastc, @JAWS-test, @smhigley)
-
Clarify toolbar exception in Understanding Reflow 1.4.10 w3c/wcag#916 (4 comments by @alastc, @JAWS-test, @smhigley, @WayneEDick)
-
predicted amount change a status message? 4.1.3: Status Messages w3c/wcag#911 (4 comments by @alastc, @detlevhfischer, @jake-abma)
-
Visited and Unvisited link color a failure of Use of Color? w3c/wcag#905 (3 comments by @alastc, @JAWS-test, @Myndex)
-
Does G183 only apply to "links and controls" with additional requirements or in general? w3c/wcag#871 (3 comments by @alastc, @JAWS-test)
-
Clarify the meaning of "is also available" in step #3 of F3 test w3c/wcag#80 (1 comment by @mraccess77)
-
Do issues with Windows high contrast mode fall under WCAG 2.1? w3c/wcag#623 (1 comment by @jlukosky)
-
Cursor as sole focus indicator of inputs sufficient to meet 1.4.11? w3c/wcag#680 (1 comment by @alastc)
-
Understanding SC 1.4.11 Active User Interface Components button examples text contrast w3c/wcag#551 (1 comment by @alastc)
-
1.2.5 requirements for Audio description when soundtrack of video has no gaps w3c/wcag#909 (1 comment by @bruce-usab)
-
Interpretation of 2.2.1 "Timing Adjustable" for content that counts down (and resets) time w3c/wcag#908 (1 comment by @bruce-usab)
-
-
2 pull requests opened.
-
making examples failures per public comment w3c/wcag#924, by @awkawk.
-
Update glossary contrast ratio w3c/wcag#912, by @JAWS-test.
-
-
2 pull requests merged.
-
Create F_1_3_5.html w3c/wcag#889.
-
Edits to 135 failure w3c/wcag#890.
-
-
3 pull requests received 3 new comments.
w3c/wcag3
-
3 issues received 16 new comments.
-
Note 4 in definition "contrast ratio" still relevant (1.4.3, 1.4.6, 1.4.11)? w3c/wcag3#187 (14 comments by @alastc, @jake-abma, @JAWS-test, @mraccess77, @Myndex)
-
Low Vision Accessibility Task Force
GitHub
w3c/low-vision-a11y-tf
-
1 issue opened in the Low Vision Accessibility Task Force.
-
Blue on Black is a "design fail", and other CVD examples. w3c/low-vision-a11y-tf#84, by @Myndex.
-
Participants
-
1 organization joined.
-
Green Technology Co joined.
-
GitHub
w3c/wcag
-
22 issues opened.
-
F87 is incomprehensibly formulated w3c/wcag#907, by @JAWS-test.
-
Wrong link in Understanding 3.3.2 w3c/wcag#906, by @cmuncharaz.
-
Visited and Unvisited link color a failure of Use of Color? w3c/wcag#905, by @mbgower.
-
Text in an image for Reflow 1.4.10 w3c/wcag#904, by @WayneEDick.
-
exception for logos (1.4.3, 1.4.11) w3c/wcag#902, by @JAWS-test.
-
ARIA 19 technique with broken link and typo w3c/wcag#900, by @mbgower.
-
Wanted to confirm my understanding as SC 1.4.11 applies to hover w3c/wcag#896, by @mraccess77.
-
Formatting of Exceptions w3c/wcag#895, by @bruce-usab.
-
Supplement Understanding 4.1.3 w3c/wcag#894, by @JAWS-test.
-
Outdated link in ARIA19 w3c/wcag#893, by @JAWS-test.
-
Why is progressbar mentioned in F103? w3c/wcag#892, by @JAWS-test.
-
Semantic conveyed through Indented UI and Reflow 1.4.10 w3c/wcag#887, by @cscrosati.
-
Invalid Links in Key Terms w3c/wcag#883, by @JAWS-test.
-
10 issues closed.
-
Wrong link in Understanding 3.3.2 w3c/wcag#906.
-
1.4.1 or 1.4.11? w3c/wcag#875.
-
"Not applicable" in 1.4.11 w3c/wcag#870.
-
Outdated link in ARIA19 w3c/wcag#893.
-
39 issues received 208 new comments.
-
Must the tooltip of icons match the accessible name? (for "Label in Name", SC 2.5.3) w3c/wcag#891 (40 comments by @awkawk, @detlevhfischer, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
Proposal for color and contrast (1.3.1, 1.4.1, 1.4.3., 1.4.6, 1.4.11) (WCAG 3.0) w3c/wcag#901 (21 comments by @JAWS-test, @Myndex, @patrickhlauke, @StommePoes)
-
labelled navigation landmarks should be added to sufficient techniques for 2.4.4 w3c/wcag#619 (15 comments by @alastc, @awkawk, @JAWS-test, @mraccess77, @Wildebrew)
-
What does "support the following text style properties" mean (1.4.12)? w3c/wcag#884 (13 comments by @alastc, @awkawk, @jake-abma, @JAWS-test, @patrickhlauke)
-
Technique G13 - allows surveys to advance on input with notice, even radio buttons? w3c/wcag#898 (12 comments by @alastc, @awkawk, @JAWS-test, @jhausler1266, @mraccess77)
-
Explanation of exception in F81 insufficient w3c/wcag#873 (10 comments by @alastc, @JAWS-test, @mraccess77)
-
Wanted to confirm my understanding as SC 1.4.11 applies to hover w3c/wcag#896 (10 comments by @alastc, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
Semantic conveyed through Indented UI and Reflow 1.4.10 w3c/wcag#887 (7 comments by @alastc, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke, @WayneEDick)
-
1.3.4 Orientation - F97 (Locking orientation) - screen size irrelevant in testing? w3c/wcag#877 (5 comments by @alastc, @detlevhfischer, @jake-abma, @patrickhlauke)
-
Interpretation of 2.2.1 "Timing Adjustable" for content that counts down (and resets) time w3c/wcag#908 (5 comments by @detlevhfischer, @jake-abma, @mraccess77, @patrickhlauke)
-
No technique using figcaption to meet 1.1.1 Non-text content w3c/wcag#852 (5 comments by @JAWS-test, @mbgower, @mraccess77)
-
Confirming 3rd bullet of Character Key Shortcuts w3c/wcag#844 (4 comments by @alastc, @awkawk, @mbgower)
-
Visited and Unvisited link color a failure of Use of Color? w3c/wcag#905 (3 comments by @alastc, @JAWS-test)
-
Clarification on button distinguishing indicator for 1.4.11 Non-text Contrast w3c/wcag#865 (3 comments by @alastc, @LaurenceRLewis)
-
Understanding 2.5.3 - actually rendered examples but no markup examples? w3c/wcag#882 (2 comments by @alastc, @detlevhfischer)
-
SC 1.3.5 Technique "Use type attribute on fields in simple login forms"? w3c/wcag#504 (2 comments by @detlevhfischer, @patrickhlauke)
-
In Understanding 3.3.2, a link to 2.4.6 Headings and Labels is broken w3c/wcag#874 (1 comment by @alastc)
-
Does G183 only apply to "links and controls" with additional requirements or in general? w3c/wcag#871 (1 comment by @alastc)
-
Do issues with Windows high contrast mode fall under WCAG 2.1? w3c/wcag#623 (1 comment by @JAWS-test)
-
2.5.2 Pointer Cancellation and Success Technique Matching the accessible name to the visible label w3c/wcag#888 (1 comment by @awkawk)
-
-
9 pull requests opened.
-
Tweaks/additions to Understanding Pointer Gestures w3c/wcag#910, by @patrickhlauke.
-
Normalise references to 44 by 44 CSS pixels target size w3c/wcag#897, by @robinwhittleton.
-
Edits to 135 failure w3c/wcag#890, by @awkawk.
-
Create F_1_3_5.html w3c/wcag#889, by @awkawk.
-
errata for text spacing w3c/wcag#886, by @awkawk.
-
reflow errata w3c/wcag#885, by @awkawk.
-
Tech fail text spacing clipping w3c/wcag#881, by @awkawk.
-
Tech failure path based gesture (2.5.1) w3c/wcag#880, by @detlevhfischer.
-
Exceptions for failures w3c/wcag#879, by @awkawk.
-
-
7 pull requests merged.
-
Normalise references to 44 by 44 CSS pixels target size w3c/wcag#897.
-
Motion actuation failure w3c/wcag#845.
-
Tech failure path based gesture (2.5.1) w3c/wcag#880.
-
reflow errata w3c/wcag#885.
-
Requirements acceptance criteria w3c/wcag#862.
-
Tech fail text spacing clipping w3c/wcag#881.
-
Exceptions for failures w3c/wcag#879.
-
-
2 pull requests closed.
-
Adding suggestion from 228 w3c/wcag#774.
-
errata for text spacing w3c/wcag#886.
-
-
7 pull requests received 34 new comments.
-
Edits to 135 failure w3c/wcag#890 (27 comments by @awkawk, @detlevhfischer, @jake-abma, @johnfoliot, @mraccess77, @patrickhlauke)
-
w3c/wcag3
-
2 issues opened.
-
Proposal for a new SC for hover (WCAG 3.0) w3c/wcag3#185, by @JAWS-test.
-
Keyboard operation with assistive technology: 2.1.1 or 4.1.2? w3c/wcag3#186, by @JAWS-test.
-
-
4 issues received 29 new comments.
-
Note 4 in definition "contrast ratio" still relevant (1.4.3, 1.4.6, 1.4.11)? w3c/wcag3#187 (12 comments by @alastc, @JAWS-test, @mraccess77, @Myndex)
-
Keyboard operation with assistive technology: 2.1.1 or 4.1.2? w3c/wcag3#186 (10 comments by @alastc, @detlevhfischer, @JAWS-test, @mraccess77, @patrickhlauke)
-
Proposal for a new SC for hover (WCAG 3.0) w3c/wcag3#185 (5 comments by @alastc, @JAWS-test, @jhausler1266)
-
w3c/wcag-act
-
2 issues opened.
-
Resolve "HTML has lang attribute" feedback w3c/wcag-act#419, by @WilcoFiers.
-
Resolve "lang and xml:lang match" feedback w3c/wcag-act#417, by @WilcoFiers.
-
-
1 pull request opened.
-
Update wcag-ruleset-review-process.md w3c/wcag-act#418, by @nitedog.
-
w3c/coga
-
1 issue opened.
-
1 issue received 2 new comments.
w3c/earl
-
1 pull request opened.
-
chore: remove axe report for act rules w3c/earl#3, by @jeeyyy.
-
-
1 pull request merged.
-
chore: remove axe report for act rules w3c/earl#3.
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
1 issue opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
1 issue in the Cognitive and Learning Disabilities Accessibility Task Force received 2 new comments.
Participants
-
1 organization joined.
-
Mada Center, Qatar joined.
-
GitHub
w3c/wcag
-
21 issues opened.
-
1.4.1 or 1.4.11? w3c/wcag#875, by @JAWS-test.
-
Explanation of exception in F81 insufficient w3c/wcag#873, by @JAWS-test.
-
"Not applicable" in 1.4.11 w3c/wcag#870, by @JAWS-test.
-
1.4.3, 1.4.11 Contrasts of disabled elements w3c/wcag#869, by @JAWS-test.
-
Clarity on Understanding 1.4.11 regarding hue w3c/wcag#868, by @fstorr.
-
Error of the User Agents part of WCAG or not w3c/wcag#866, by @JAWS-test.
-
Question to clarify 1.4.11 Non-text Contrast (AA) w3c/wcag#861, by @LaurenceRLewis.
-
Clarity on 1.4.11 as it applies to "Cards" w3c/wcag#856, by @chucktheonewhobutles.
-
No technique using figcaption to meet 1.1.1 Non-text content w3c/wcag#852, by @mbgower.
-
1.4.11 hover state clarification w3c/wcag#849, by @mfairchild365.
-
17 issues closed.
-
1.4.3, 1.4.11 Contrasts of disabled elements w3c/wcag#869.
-
Editorial issue with Concurrent Input Mechanisms w3c/wcag#322.
-
Outdated tabindex technique w3c/wcag#526.
-
Advisory techniques vs Recommended techniques w3c/wcag#527.
-
Question to clarify 1.4.11 Non-text Contrast (AA) w3c/wcag#861.
-
missing character on SCR24 (example1) w3c/wcag#837.
-
Typo (Understanding SC2.2.2)? w3c/wcag#288.
-
H57, H58 and xml:lang w3c/wcag#759.
-
Typo in G203 example "produced by produced by" w3c/wcag#838.
-
31 issues received 187 new comments.
-
Should role button and input button be a WCAG fail if cannot be activated using space? w3c/wcag#857 (31 comments by @alastc, @detlevhfischer, @JAWS-test, @LaurenceRLewis, @mraccess77, @patrickhlauke)
-
Clarity on 1.4.11 as it applies to "Cards" w3c/wcag#856 (23 comments by @alastc, @awkawk, @chucktheonewhobutles, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke, @srinivasuchakravarthula)
-
Can title on links (e.g. linked icon) as sole source of accName ever pass 1.1.1? w3c/wcag#867 (19 comments by @detlevhfischer, @jake-abma, @JAWS-test, @LaurenceRLewis, @LJWatson, @mraccess77, @patrickhlauke, @stevefaulkner)
-
Error of the User Agents part of WCAG or not w3c/wcag#866 (13 comments by @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
Do issues with Windows high contrast mode fall under WCAG 2.1? w3c/wcag#623 (10 comments by @alastc, @electronicwoft, @JAWS-test, @patrickhlauke, @StommePoes)
-
Clarity on Understanding 1.4.11 regarding hue w3c/wcag#868 (10 comments by @fstorr, @JAWS-test, @mraccess77, @patrickhlauke)
-
2.5.1 Pointer Gestures: clarity on path-based language in Understanding document w3c/wcag#522 (10 comments by @alastc, @detlevhfischer, @goetsu)
-
"Not applicable" in 1.4.11 w3c/wcag#870 (8 comments by @jake-abma, @JAWS-test, @lauracarlson, @patrickhlauke)
-
gh-pages branch contains two "understanding" folders with different character casing w3c/wcag#850 (8 comments by @alastc, @awkawk, @EricDunsworth, @nschonni)
-
Motion actuation (2.5.4) question on exception w3c/wcag#727 (6 comments by @mbgower, @patrickhlauke, @steverep)
-
No technique using figcaption to meet 1.1.1 Non-text content w3c/wcag#852 (6 comments by @alastc, @lauracarlson, @mraccess77, @Ryladog)
-
Qualify F94 Failure of Success Criterion 1.4.4 due to text sized in viewport units? w3c/wcag#854 (5 comments by @alastc, @patrickhlauke)
-
Does using the placeholder with a value alone pass 3.3.2 Labels or Instructions? w3c/wcag#864 (4 comments by @LaurenceRLewis, @mraccess77, @patrickhlauke)
-
Tweak glossary definition for "images of text" w3c/wcag#264 (3 comments by @alastc, @awkawk, @patrickhlauke)
-
What does WCAG require of SVGs to pass SC 1.1.1 w3c/wcag#840 (3 comments by @jake-abma, @mraccess77, @patrickhlauke)
-
Question to clarify 1.4.11 Non-text Contrast (AA) w3c/wcag#861 (2 comments by @alastc, @LaurenceRLewis)
-
1.3.4 Orientation - F97 (Locking orientation) - screen size irrelevant in testing? w3c/wcag#877 (1 comment by @patrickhlauke)
-
Clarification on button distinguishing indicator for 1.4.11 Non-text Contrast w3c/wcag#865 (1 comment by @jake-abma)
-
Potential failure techniques (or at least checks) for Text Spacing? w3c/wcag#683 (1 comment by @alastc)
-
Applicability of 2.5.3 Label in Name when no label is present (or just placeholder) w3c/wcag#855 (1 comment by @alastc)
-
Anchor link is not working due to incorrect link URL (Understanding SC 1.4.12) w3c/wcag#847 (1 comment by @awkawk)
-
The description of the number of figures is incorrect (Understanding SC 1.4. 12) w3c/wcag#831 (1 comment by @alastc)
-
-
10 pull requests opened.
-
Adding extra paragraph tp F94 for issue 854 w3c/wcag#863, by @alastc.
-
Requirements acceptance criteria w3c/wcag#862, by @michael-n-cooper.
-
Text spacing update w3c/wcag#860, by @alastc.
-
*minor* fix and suggestion w3c/wcag#859, by @shawna-slh.
-
Fix links to CSS3 values in 1.4.3 and 1.4.6 w3c/wcag#858, by @jfhector.
-
Status message error w3c/wcag#853, by @mbgower.
-
Fix malformed technique links w3c/wcag#851, by @EricDunsworth.
-
Motion failure mike w3c/wcag#848, by @mbgower.
-
Bringing Mike Gower's fork up to date w3c/wcag#846, by @awkawk.
-
Motion actuation failure w3c/wcag#845, by @rachaelbradley.
-
-
16 pull requests merged.
-
Text spacing update w3c/wcag#860.
-
Status message error w3c/wcag#853.
-
Adding extra paragraph tp F94 for issue 854 w3c/wcag#863.
-
Fix links to CSS3 values in 1.4.3 and 1.4.6 w3c/wcag#858.
-
Updating an example for buttons. w3c/wcag#813.
-
Removing DHTML note from 4.1.2 w3c/wcag#779.
-
Updating pause-stop-hide-understanding w3c/wcag#778.
-
De-XMLifying H57 and H58 lang techniques w3c/wcag#766.
-
Tech failure content disappearing on reflow w3c/wcag#843.
-
Update status-messages.html w3c/wcag#694.
-
Update identify-purpose.html w3c/wcag#842.
-
Motion failure mike w3c/wcag#848.
-
Fixing typo in G203 w3c/wcag#839.
-
Create shortcut-mechanism.html w3c/wcag#836.
-
-
3 pull requests closed.
-
Change to normative text of 1.4.12: at least > up to w3c/wcag#637.
-
Glossary definition for "images of text", from #264 w3c/wcag#777.
-
Bringing Mike Gower's fork up to date w3c/wcag#846.
-
-
14 pull requests received 33 new comments.
w3c/wcag3
-
2 issues opened.
-
New SC for keyboard operation? w3c/wcag3#188, by @JAWS-test.
-
3 issues received 18 new comments.
-
New SC for keyboard operation? w3c/wcag3#188 (13 comments by @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
Note 4 in definition "contrast ratio" still relevant (1.4.3, 1.4.6, 1.4.11)? w3c/wcag3#187 (4 comments by @awkawk, @JAWS-test, @mraccess77)
-
w3c/wcag-act
-
2 issues opened.
-
Resolving "Page has a title" feedback w3c/wcag-act#416, by @WilcoFiers.
-
Proposed recommendation points to editor draft of WG note w3c/wcag-act#413, by @moekraft.
-
-
1 issue closed.
-
Proposed recommendation points to editor draft of WG note w3c/wcag-act#413.
-
-
2 pull requests opened.
-
fixed link to Common Input Aspects WG Note w3c/wcag-act#415, by @nitedog.
-
Create w3c-ruleset-review-process.md w3c/wcag-act#414, by @WilcoFiers.
-
-
1 pull request merged.
-
fixed link to Common Input Aspects WG Note w3c/wcag-act#415.
-
-
1 pull request received 46 new comments.
-
Create w3c-ruleset-review-process.md w3c/wcag-act#414 (46 comments by @annethyme, @maryjom, @tbostic32, @WilcoFiers)
-
w3c/coga
-
1 issue opened.
-
Design Guide terminology w3c/coga#98, by @AndrewArch.
-
-
1 issue reopened.
-
Design Guide terminology w3c/coga#98, by @SteveALee.
-
-
1 issue received 2 new comments.
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
1 issue opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Design Guide terminology w3c/coga#98, by @AndrewArch.
-
-
1 issue reopened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Design Guide terminology w3c/coga#98, by @SteveALee.
-
-
1 issue in the Cognitive and Learning Disabilities Accessibility Task Force received 2 new comments.
TR publications
-
2 documents published.
-
Accessibility Conformance Testing (ACT) Rules Format 1.0 published as a Proposed Recommendation. History of Accessibility Conformance Testing (ACT) Rules Format 1.0
-
Participants
-
1 participant left.
-
Thaddeus Cambron (W3C Invited Experts) left.
-
-
2 organizations joined.
-
Amazon joined.
-
Macmillan Learning joined.
-
-
1 organization left.
-
VitalSource | Ingram Content Group left.
-
GitHub
w3c/wcag
-
21 issues opened.
-
Confirming 3rd bullet of Character Key Shortcuts w3c/wcag#844, by @mbgower.
-
What does WCAG require of SVGs to pass SC 1.1.1 w3c/wcag#840, by @mraccess77.
-
Typo in G203 example "produced by produced by" w3c/wcag#838, by @mitchellevan.
-
missing character on SCR24 (example1) w3c/wcag#837, by @momdo.
-
Draft of new 2.2 SC "Dragging" w3c/wcag#835, by @detlevhfischer.
-
Referencing latest understanding and quick ref docs w3c/wcag#834, by @mattgarrish.
-
Bookmarklet for testing character key shortcuts (SC 2.1.4) w3c/wcag#833, by @detlevhfischer.
-
How does 2.5.3 Label in Name apply to cards w3c/wcag#829, by @mraccess77.
-
F38 disallows techniques that actually satisfy 1.1.1 w3c/wcag#828, by @mitchellevan.
-
When content is, and isn't, "web content" w3c/wcag#827, by @patrickhlauke.
-
Better distinguish 2.4.4 and 2.4.9 in Understanding w3c/wcag#826, by @DavidMacDonald.
-
Outdated links in Understanding SC 2.4.2 (Page Titled) w3c/wcag#825, by @cstrobbe.
-
We need a position natural language inputs w3c/wcag#824, by @DavidMacDonald.
-
G145 procedure doesn't include text-size measure w3c/wcag#820, by @alastc.
-
F63 shouldn't indicate use of preceding heading to meet 2.4.4 w3c/wcag#819, by @mraccess77.
-
JavaScript error on working example (script-expand-links) w3c/wcag#817, by @maxstarkenburg.
-
Add BBC Subtitle Guidelines as a resource w3c/wcag#816, by @nigelmegitt.
-
What is sufficient for SC 1.4.10? (PDF) w3c/wcag#814, by @KerstinProbiesch.
-
-
24 issues closed.
-
Understanding 4.1.3 - wrong id reference in anchors w3c/wcag#465.
-
Link to "programmatically determined " not working w3c/wcag#328.
-
Minor link errors in Understanding 1.4.12 Text spacing w3c/wcag#443.
-
H80 Example 3 w3c/wcag#233.
-
Technique C36 missing content? w3c/wcag#682.
-
How does 2.5.3 Label in Name apply to cards w3c/wcag#829.
-
Problem with Technique G131 w3c/wcag#339.
-
Section missing from Understanding Conformance w3c/wcag#807.
-
Are Reflow, Text Size and Orientation cumulative? w3c/wcag#391.
-
ARIA in HTML conformance to conform WCAG ? w3c/wcag#717.
-
ARIA authoring pratices design pattern to conform WCAG ? w3c/wcag#718.
-
Failure F26 links to the wrong SC? w3c/wcag#258.
-
Luminance / Luma confusion w3c/wcag#236.
-
H33 Supplementing link text with title attribute w3c/wcag#305.
-
Link to user agents doesn't work w3c/wcag#336.
-
Link to assistive technologies doesn't work w3c/wcag#337.
-
-
30 issues received 141 new comments.
-
What is sufficient for SC 1.4.10? (PDF) w3c/wcag#814 (27 comments by @alastc, @awkawk, @KerstinProbiesch, @mraccess77, @patrickhlauke, @WayneEDick)
-
"at least" should be "at most" in WCAG 2.1 SC 1.4.12 w3c/wcag#635 (24 comments by @alastc, @jake-abma, @lauracarlson, @mraccess77, @Myndex, @patrickhlauke, @WayneEDick)
-
Failure technique F94 (1.4.4 resize text): remove "1280 pixels wide" step in test procedure w3c/wcag#704 (12 comments by @alastc, @mraccess77, @patrickhlauke)
-
When content is, and isn't, "web content" w3c/wcag#827 (11 comments by @bruce-usab, @electronicwoft, @mraccess77, @patrickhlauke, @WayneEDick)
-
Link to "programmatically determined " not working w3c/wcag#328 (6 comments by @alastc, @awkawk, @patrickhlauke)
-
Screen, Display, Reflow, Adaptive and Responsive w3c/wcag#799 (6 comments by @jake-abma, @patrickhlauke)
-
F38 disallows techniques that actually satisfy 1.1.1 w3c/wcag#828 (5 comments by @alastc, @mitchellevan, @patrickhlauke)
-
We need a position natural language inputs w3c/wcag#824 (5 comments by @alastc, @DavidMacDonald, @mraccess77, @patrickhlauke)
-
2.5.3: Must the visible label of site logos linking to the start page be included in the accName? w3c/wcag#722 (4 comments by @alastc, @awkawk, @mbgower, @mraccess77)
-
F63 shouldn't indicate use of preceding heading to meet 2.4.4 w3c/wcag#819 (4 comments by @alastc, @mraccess77)
-
H33 Supplementing link text with title attribute w3c/wcag#305 (4 comments by @alastc, @electronicwoft, @lauracarlson)
-
WCAG 2.2 Focus more visible - can a visible change only in size be a failure? w3c/wcag#812 (4 comments by @alastc, @eschafer, @patrickhlauke)
-
2.4.7 Focus Visible - explanation/understanding addition about "mode of operation"? w3c/wcag#301 (3 comments by @alastc, @patrickhlauke)
-
anchor IDs do not match between definition links (in Understanding doc) and definition anchors w3c/wcag#841 (2 comments by @awkawk, @mbgower)
-
How does 2.5.3 Label in Name apply to cards w3c/wcag#829 (2 comments by @mraccess77, @patrickhlauke)
-
ARIA authoring pratices design pattern to conform WCAG ? w3c/wcag#718 (2 comments by @alastc, @mbgower)
-
Add some actionable advice to "Large scale (text) > Note 1" in the glossary w3c/wcag#228 (1 comment by @alastc)
-
Clarification on "language versions" within definition of "set of web pages" w3c/wcag#310 (1 comment by @alastc)
-
1.4.11 if a button has a background less than 3:1 and no border does it pass w3c/wcag#800 (1 comment by @alastc)
-
Add a nuance in wording for not generalizing the cognitive group w3c/wcag#329 (1 comment by @alastc)
-
-
12 pull requests opened.
-
Tech failure content disappearing on reflow w3c/wcag#843, by @detlevhfischer.
-
Update identify-purpose.html w3c/wcag#842, by @mbgower.
-
Fixing typo in G203 w3c/wcag#839, by @mitchellevan.
-
Create shortcut-mechanism.html w3c/wcag#836, by @mbgower.
-
Removed mentions of heading w3c/wcag#832, by @alastc.
-
Update ensuring-single-pointer.html w3c/wcag#823, by @mbgower.
-
CSS doorslam technique rewrite w3c/wcag#822, by @mbgower.
-
Update control-orientation.html w3c/wcag#821, by @mbgower.
-
JS error in script-expand-links working example, issue 817 w3c/wcag#818, by @maxstarkenburg.
-
Failure technique for 2.5.2 w3c/wcag#815, by @patrickhlauke.
-
Updating an example for buttons. w3c/wcag#813, by @alastc.
-
-
15 pull requests merged.
-
Updating 3rd example in H80 w3c/wcag#775.
-
Removed mentions of heading w3c/wcag#832.
-
Pointer cancellation jake suggestions w3c/wcag#711.
-
Failure technique for 2.5.2 w3c/wcag#815.
-
G131 w3c/wcag#830.
-
Tech providing single point control sliders w3c/wcag#760.
-
Tech failure doorslam w3c/wcag#790.
-
CSS doorslam technique rewrite w3c/wcag#822.
-
Tech control orientation w3c/wcag#794.
-
Update control-orientation.html w3c/wcag#821.
-
F26 update to address 258 w3c/wcag#776.
-
Technique - Two color focus indicator w3c/wcag#583.
-
Tech failure unmodifiable single key shortcut w3c/wcag#584.
-
Tech hover focus hoverable w3c/wcag#543.
-
-
1 pull request closed.
-
Technique - ensuring single pointer usage w3c/wcag#380.
-
-
16 pull requests received 71 new comments.
-
Tech providing single point control sliders w3c/wcag#760 (11 comments by @alastc, @awkawk, @patrickhlauke)
-
Updating an example for buttons. w3c/wcag#813 (10 comments by @alastc, @aparnapasi, @detlevhfischer, @goodwitch, @mraccess77)
-
Create shortcut-mechanism.html w3c/wcag#836 (9 comments by @alastc, @detlevhfischer, @mbgower, @mraccess77, @patrickhlauke)
-
Update ensuring-single-pointer.html w3c/wcag#823 (4 comments by @detlevhfischer, @mbgower, @patrickhlauke)
-
JS error in script-expand-links working example, issue 817 w3c/wcag#818 (3 comments by @maxstarkenburg, @patrickhlauke)
-
w3c/coga
-
2 issues opened.
-
Duplicate bullet point w3c/coga#96, by @sheribyrne.
-
Persona/index contains broken links w3c/coga#95, by @chrisosaurus.
-
-
3 issues closed.
-
References to Research item 41 is misformatted w3c/coga#2.
-
w3c.github.io/coga/templates link broken w3c/coga#27.
-
Incorrect heading for ADHD w3c/coga#60.
-
-
5 issues received 10 new comments.
-
1 pull request opened.
-
1 pull request received 2 new comments.
-
Fixing markup, duplicate text, invalid urls, and minor typos. w3c/coga#97 (2 comments by @SteveALee)
-
w3c/wcag-act
-
3 issues opened.
-
Discuss rule maintenance w3c/wcag-act#412, by @WilcoFiers.
-
Add Mary Jo and Shadi as editors to WG Note w3c/wcag-act#411, by @moekraft.
-
change 'inapplicable' to 'not applicable' (from David McDonald) w3c/wcag-act#405, by @nitedog.
-
-
29 issues closed.
-
change 'inapplicable' to 'not applicable' (from David McDonald) w3c/wcag-act#405.
-
Intention to submit feedback and implementation report w3c/wcag-act#365.
-
Feedback Lisa Louise Davis w3c/wcag-act#363.
-
CR Feedback Fernanda Bonnin w3c/wcag-act#364.
-
Add example for External Accessibility Requirements mapping w3c/wcag-act#329.
-
Editorial updates w3c/wcag-act#356.
-
Unintended "should" in background section w3c/wcag-act#355.
-
Optional items under MUST keyword w3c/wcag-act#357.
-
"Unique identifier" scope w3c/wcag-act#358.
-
Expectations for Composite Rules w3c/wcag-act#359.
-
Rule's date and version number w3c/wcag-act#360.
-
Examples 3 and 4 in Appendix 1 are identical w3c/wcag-act#362.
-
Level Access Feedback: General w3c/wcag-act#366.
-
Level Access Feedback: ACT Rule Types w3c/wcag-act#367.
-
Level Access Feedback: Atomic rules w3c/wcag-act#368.
-
Level Access Feedback: Rule Input w3c/wcag-act#369.
-
Level Access Feedback: Unspecified Input Aspects w3c/wcag-act#370.
-
feedback of Orange accessibility team w3c/wcag-act#371.
-
Unintended "must" in Introduction w3c/wcag-act#372.
-
Unintended "may" in Examples 17 w3c/wcag-act#373.
-
Capitalize "Web" used as a noun w3c/wcag-act#374.
-
Feedback: Audrey Maniez (Access42) w3c/wcag-act#375.
-
Update example references from auto-wcag to ACT-R w3c/wcag-act#378.
-
Change mark up of must / should / may w3c/wcag-act#390.
-
Make rule examples consistent across composite rule examples. w3c/wcag-act#348.
-
Failure techniques relationship to ACT Rules and conformance (Anne) w3c/wcag-act#268.
-
elaborate on complex aggregation w3c/wcag-act#335.
-
Investigate how to use EARL with ACT RF w3c/wcag-act#229.
-
15 issues received 18 new comments.
-
change 'inapplicable' to 'not applicable' (from David McDonald) w3c/wcag-act#405 (1 comment by @nitedog)
-
Add example for External Accessibility Requirements mapping w3c/wcag-act#329 (1 comment by @nitedog)
-
Failure techniques relationship to ACT Rules and conformance (Anne) w3c/wcag-act#268 (1 comment by @nitedog)
-
Issue with the "Conformance level" part of Accessibility Requirements Mapping w3c/wcag-act#384 (1 comment by @nitedog)
-
19 pull requests opened.
-
Creating updated WG Note w3c/wcag-act#410, by @moekraft.
-
fixing validation error w3c/wcag-act#409, by @nitedog.
-
Clarify Appendix 3 is non-normative w3c/wcag-act#408, by @WilcoFiers.
-
Update gh-pages w3c/wcag-act#407, by @WilcoFiers.
-
Add "and higher" to required for conformance example w3c/wcag-act#406, by @WilcoFiers.
-
fix typos identified by David McDonald w3c/wcag-act#404, by @nitedog.
-
fixed broken link w3c/wcag-act#403, by @nitedog.
-
fixing broken link w3c/wcag-act#402, by @nitedog.
-
fixed link w3c/wcag-act#401, by @nitedog.
-
fixed typo w3c/wcag-act#400, by @bruce-usab.
-
Change “common failures” link w3c/wcag-act#399, by @bruce-usab.
-
Delete static text. w3c/wcag-act#398, by @bruce-usab.
-
Change History w3c/wcag-act#397, by @nitedog.
-
Proposed rec w3c/wcag-act#396, by @WilcoFiers.
-
Put RFC2119 key words in styles w3c/wcag-act#395, by @WilcoFiers.
-
relationship to failures w3c/wcag-act#394, by @nitedog.
-
clariying note on complex aggregation w3c/wcag-act#393, by @nitedog.
-
align all examples w3c/wcag-act#392, by @nitedog.
-
Prepare Implementation Report w3c/wcag-act#391, by @nitedog.
-
-
25 pull requests merged.
-
Creating updated WG Note w3c/wcag-act#410.
-
fixing validation error w3c/wcag-act#409.
-
Clarify Appendix 3 is non-normative w3c/wcag-act#408.
-
Update gh-pages w3c/wcag-act#407.
-
Change “common failures” link w3c/wcag-act#399.
-
fixed typo w3c/wcag-act#400.
-
fixed link w3c/wcag-act#401.
-
fixing broken link w3c/wcag-act#402.
-
fixed broken link w3c/wcag-act#403.
-
Add "and higher" to required for conformance example w3c/wcag-act#406.
-
fix typos identified by David McDonald w3c/wcag-act#404.
-
Change History w3c/wcag-act#397.
-
Proposed rec w3c/wcag-act#396.
-
update Appendix 1 w3c/wcag-act#389.
-
Edits to clarify Input Aspects w3c/wcag-act#383.
-
align all examples w3c/wcag-act#392.
-
Put RFC2119 key words in styles w3c/wcag-act#395.
-
relationship to failures w3c/wcag-act#394.
-
clariying note on complex aggregation w3c/wcag-act#393.
-
Optional items under must w3c/wcag-act#382.
-
Made various editorial changes w3c/wcag-act#381.
-
Should explainer w3c/wcag-act#380.
-
Fixed capitalization in 3 places w3c/wcag-act#379.
-
updated abstract w3c/wcag-act#376.
-
Prepare Implementation Report w3c/wcag-act#391.
-
-
1 pull request closed.
-
Delete static text. w3c/wcag-act#398.
-
-
6 pull requests received 43 new comments.
-
Delete static text. w3c/wcag-act#398 (11 comments by @annethyme, @bruce-usab, @michael-n-cooper, @nitedog)
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
2 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Duplicate bullet point w3c/coga#96, by @sheribyrne.
-
Persona/index contains broken links w3c/coga#95, by @chrisosaurus.
-
-
3 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
References to Research item 41 is misformatted w3c/coga#2.
-
w3c.github.io/coga/templates link broken w3c/coga#27.
-
Incorrect heading for ADHD w3c/coga#60.
-
-
5 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 10 new comments.
-
1 pull request opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
1 pull request in the Cognitive and Learning Disabilities Accessibility Task Force received 2 new comments.
-
Fixing markup, duplicate text, invalid urls, and minor typos. w3c/coga#97 (2 comments by @SteveALee)
-
Participants
-
3 participants joined.
-
Rachael Bradley Montgomery (Library of Congress) joined.
-
Andrew Somers (W3C Invited Experts) joined.
-
Hidde de Vries (W3C) joined.
-
GitHub
w3c/wcag
-
21 issues opened.
-
Section missing from Understanding Conformance w3c/wcag#807, by @alastc.
-
Typo in Understanding 1.4.11 w3c/wcag#805, by @honoka-h.
-
Understanding SC 1.4.11 - Incorrect alt text w3c/wcag#804, by @honoka-h.
-
Typo Non text contrast ... understanding w3c/wcag#803, by @DavidMacDonald.
-
typo in understanding not text contrast w3c/wcag#802, by @DavidMacDonald.
-
Success Criterion reference error w3c/wcag#801, by @cmuncharaz.
-
Screen, Display, Reflow, Adaptive and Responsive w3c/wcag#799, by @jake-abma.
-
404 errors on internal links due to linking to version w3c/wcag#797, by @joppekroon.
-
Inconsistent SCs that use "media alternative" in Guideline 1.2 w3c/wcag#796, by @bruce-usab.
-
Typo in Understanding SC 1.4.11 w3c/wcag#789, by @honoka-h.
-
typo in 'understanding success criteria 2.4.5' w3c/wcag#785, by @electronicwoft.
-
Revisiting Transcripts and Audio Description (SC 1.2.3/5/8) w3c/wcag#782, by @bruce-usab.
-
text techniques should not be in 1.4.11 non-text contrast w3c/wcag#781, by @mbgower.
-
Editorial change Example 5: Piano - 1.3.4: Orientation w3c/wcag#771, by @jake-abma.
-
Deprecating SC 4.1.1 w3c/wcag#770, by @WilcoFiers.
-
Simple videos need place to host them w3c/wcag#768, by @camusamta.
-
H57, H58 and xml:lang w3c/wcag#759, by @dd8.
-
-
46 issues closed.
-
Add link to HTML5 Autocomplete w3c/wcag#335.
-
Examples link: to HTML5 OR to normative list? w3c/wcag#333.
-
Link to Personas w3c/wcag#332.
-
Small wording update "a people..." w3c/wcag#331.
-
Link to 4.1.2 can be added w3c/wcag#330.
-
Recommendation of EARL w3c/wcag#307.
-
Typo in Understanding 1.4.11 w3c/wcag#805.
-
Understanding SC 1.4.11 - Incorrect alt text w3c/wcag#804.
-
Typo Non text contrast ... understanding w3c/wcag#803.
-
404 errors on internal links due to linking to version w3c/wcag#797.
-
typo in understanding not text contrast w3c/wcag#802.
-
Success Criterion reference error w3c/wcag#801.
-
Contrast questions w3c/wcag#675.
-
Understanding Success Criterion 1.3.4: Orientation w3c/wcag#416.
-
Include font weight for color contrast tests w3c/wcag#665.
-
Typo in Understanding SC 1.4.11 w3c/wcag#789.
-
Tech C38 example not working w3c/wcag#679.
-
typo in 'understanding success criteria 2.4.5' w3c/wcag#785.
-
Typo in SC 3.2.3 w3c/wcag#294.
-
Where is there markup rule of XML sources? w3c/wcag#290.
-
Typo (ARIA1)? w3c/wcag#287.
-
Referring old notes (SCR38) w3c/wcag#285.
-
Improvement of Applicability on F77 w3c/wcag#283.
-
typo on F24? w3c/wcag#281.
-
Weird hr styling in the understanding document. w3c/wcag#299.
-
Update description of tabindex value on H4 w3c/wcag#274.
-
Remove IE6 mention from C20 w3c/wcag#271.
-
Accessiblity Issue with "show # results" w3c/wcag#266.
-
ARIA2 example 3 is invalid w3c/wcag#251.
-
Advisory techniques - general text in "Expected results" w3c/wcag#234.
-
Outline a way to deal with 'definition changes'. w3c/wcag#198.
-
ARIA6 and ARIA11: Content updates for HTML5 required w3c/wcag#155.
-
ARIA4/5: Clarification of a user interface component w3c/wcag#150.
-
The examples for aria-expanded differ in the Wiki.... w3c/wcag#126.
-
89 issues received 292 new comments.
-
Revisiting Transcripts and Audio Description (SC 1.2.3/5/8) w3c/wcag#782 (49 comments by @alastc, @awkawk, @bruce-usab, @jake-abma, @johnfoliot, @lauracarlson, @mbgower, @mraccess77, @patrickhlauke, @Ryladog)
-
Deprecating SC 4.1.1 w3c/wcag#770 (35 comments by @awkawk, @bramd, @bruce-usab, @DavidMacDonald, @dd8, @jake-abma, @johnfoliot, @mraccess77, @patrickhlauke, @Ryladog, @WilcoFiers)
-
1.4.11 if a button has a background less than 3:1 and no border does it pass w3c/wcag#800 (23 comments by @abijames, @alastc, @awkawk, @DavidMacDonald, @jake-abma, @mraccess77)
-
Screen, Display, Reflow, Adaptive and Responsive w3c/wcag#799 (15 comments by @alastc, @jake-abma, @mraccess77)
-
add definition for “path-based gesture” for 2.2 w3c/wcag#758 (9 comments by @alastc, @jake-abma, @mraccess77, @patrickhlauke)
-
Include font weight for color contrast tests w3c/wcag#665 (9 comments by @alastc, @awkawk, @jake-abma, @Myndex, @patrickhlauke, @WayneEDick)
-
Clarify the meaning of "is also available" in step #3 of F3 test w3c/wcag#80 (9 comments by @alastc, @lauracarlson, @mraccess77)
-
Using color ALONE as focus indicator w3c/wcag#757 (7 comments by @alastc, @aparnapasi, @awkawk, @johnfoliot, @mraccess77)
-
Weird hr styling in the understanding document. w3c/wcag#299 (6 comments by @alastc, @patrickhlauke)
-
"single pointer" definition not quite accurate? w3c/wcag#749 (4 comments by @alastc, @jake-abma, @patrickhlauke)
-
2.4.7 Focus Visible - explanation/understanding addition about "mode of operation"? w3c/wcag#301 (4 comments by @alastc, @patrickhlauke)
-
Glossary links are missing from Success Criteria in the QuickRef document w3c/wcag#762 (4 comments by @alastc, @awkawk, @yatil)
-
2.4.6 Headings and Labels - inappropriate "Specific benefits" bullets? w3c/wcag#303 (3 comments by @alastc, @patrickhlauke)
-
Inconsistent SCs that use "media alternative" in Guideline 1.2 w3c/wcag#796 (3 comments by @alastc, @bruce-usab)
-
Cursor as sole focus indicator of inputs sufficient to meet 1.4.11? w3c/wcag#680 (3 comments by @alastc, @jake-abma)
-
Notifications - UI component contrast understanding 1.4.11 w3c/wcag#713 (3 comments by @alastc, @StommePoes)
-
text techniques should not be in 1.4.11 non-text contrast w3c/wcag#781 (2 comments by @alastc, @patrickhlauke)
-
What is DHTML roadmap techniques (Understanding SC 4.1.2)? w3c/wcag#289 (2 comments by @alastc, @michael-n-cooper)
-
4.1.1 Parsing - Duplicate attributes with no user impact cause a conformance failure w3c/wcag#542 (2 comments by @awkawk, @WilcoFiers)
-
Non-sRGB color spaces, outdated sRGB threshold, and other issues in the "relative luminance" definition w3c/wcag#360 (2 comments by @Myndex, @WayneEDick)
-
Criterion 4.1.1 Parsing - Ambiguity regarding specification-conform nesting of HTML elements w3c/wcag#761 (2 comments by @awkawk, @MichaelKetting)
-
iOS and Android not part of examples for WCAG, should be deleted 2.5.2: Pointer Cancellation w3c/wcag#706 (1 comment by @jake-abma)
-
Add a nuance in wording for not generalizing the cognitive group w3c/wcag#329 (1 comment by @jake-abma)
-
Link to "Input Purposes for User Interface Components section" not working w3c/wcag#327 (1 comment by @jake-abma)
-
re-write "zooming into a vertically scrolling page should not cause content to be hidden" w3c/wcag#326 (1 comment by @jake-abma)
-
Clarification on "language versions" within definition of "set of web pages" w3c/wcag#310 (1 comment by @alastc)
-
3.2.4 Consistent Identification - understanding should include "accessible name" concept? w3c/wcag#300 (1 comment by @alastc)
-
1.4.12 Text Spacing - Clarify `text-overflow: ellipsis` applicability, as well as acceptability w3c/wcag#728 (1 comment by @patrickhlauke)
-
SC 1.3.5 Identify Input Purpose - autocomplete technique VS Privacy/Security w3c/wcag#407 (1 comment by @alastc)
-
Consider language changes in Sufficient Techniques section of 1.3.2 SC for item 1 w3c/wcag#243 (1 comment by @alastc)
-
Add some actionable advice to "Large scale (text) > Note 1" in the glossary w3c/wcag#228 (1 comment by @alastc)
-
failure for not identify required fields and input format before submit w3c/wcag#121 (1 comment by @alastc)
-
SCR19: This can cover onchange on checkbox / radio besides select controls w3c/wcag#109 (1 comment by @alastc)
-
Update PDF14 to be in sync with PDF/UA and also ensure footer information is available in other means. w3c/wcag#99 (1 comment by @alastc)
-
Draft technique "Providing a control slider that offers single point activation" w3c/wcag#741 (1 comment by @alastc)
-
Have the Advisory techniques that had no text been removed from WCAG 2.1? w3c/wcag#369 (1 comment by @alastc)
-
2.5.1 Pointer Gestures: clarity on path-based language in Understanding document w3c/wcag#522 (1 comment by @alastc)
-
-
29 pull requests opened.
-
Expand understanding to include concept of accessible name w3c/wcag#810, by @patrickhlauke.
-
Expand/clarify "single pointer" definition w3c/wcag#809, by @patrickhlauke.
-
Add clarifications to understanding 3.1.2 w3c/wcag#808, by @patrickhlauke.
-
Initial draft to address syc-media #796 w3c/wcag#806, by @alastc.
-
Issue 797 internal 404 w3c/wcag#798, by @joppekroon.
-
Tech control orientation w3c/wcag#794, by @awkawk.
-
Tech no reliance on path or multipoint w3c/wcag#793, by @alastc.
-
Wcag22 requirements update w3c/wcag#792, by @alastc.
-
Example doorslam w3c/wcag#791, by @jake-abma.
-
Tech failure doorslam w3c/wcag#790, by @jake-abma.
-
Reword piano example w3c/wcag#787, by @patrickhlauke.
-
Adding security considerations to H98 w3c/wcag#784, by @alastc.
-
Prepping the new technique better w3c/wcag#783, by @alastc.
-
Removing application as a landmark from ARIA11 w3c/wcag#780, by @alastc.
-
Removing DHTML note from 4.1.2 w3c/wcag#779, by @alastc.
-
Updating pause-stop-hide-understanding w3c/wcag#778, by @alastc.
-
Glossary definition for "images of text", from #264 w3c/wcag#777, by @alastc.
-
F26 update to address 258 w3c/wcag#776, by @alastc.
-
Updating 3rd example in H80 w3c/wcag#775, by @alastc.
-
Adding suggestion from 228 w3c/wcag#774, by @alastc.
-
Initial updates for 2.2 w3c/wcag#772, by @awkawk.
-
Remove WAI glossary text on Charter w3c/wcag#769, by @shawna-slh.
-
Fixes for Understanding 1.3.3 Sensory Characteristics w3c/wcag#767, by @patrickhlauke.
-
De-XMLifying H57 and H58 lang techniques w3c/wcag#766, by @alastc.
-
Create css-two-color-focus w3c/wcag#765, by @DavidMacDonald.
-
Revert "Revert "general techniques for label in name"" w3c/wcag#764, by @awkawk.
-
Revert "general techniques for label in name" w3c/wcag#763, by @awkawk.
-
Tech providing single point control sliders w3c/wcag#760, by @alastc.
-
-
24 pull requests merged.
-
Issue 797 internal 404 w3c/wcag#798.
-
Wcag22 requirements update w3c/wcag#792.
-
Sort out figure labels w3c/wcag#688.
-
Technique for device motion actuation w3c/wcag#669.
-
Updates for issue 416, inc normative note w3c/wcag#724.
-
Adding security considerations to H98 w3c/wcag#784.
-
Remove WAI glossary text on Charter w3c/wcag#769.
-
Changes to address Issue #165 w3c/wcag#604.
-
Technique: Native controls for up event w3c/wcag#726.
-
Update pointer-gestures understanding doc w3c/wcag#714.
-
Prepping the new technique better w3c/wcag#783.
-
corrections to Character key shorts and Reflow w3c/wcag#606.
-
Initial updates for 2.2 w3c/wcag#772.
-
Short cuts addendum w3c/wcag#692.
-
Failure technique for 2.5.6 Concurrent Input Mechanisms w3c/wcag#690.
-
Bypass blocks issue 404 w3c/wcag#721.
-
Update motion-actuation.html w3c/wcag#693.
-
Update reflow.html w3c/wcag#715.
-
Revert "Revert "general techniques for label in name"" w3c/wcag#764.
-
Revert "general techniques for label in name" w3c/wcag#763.
-
general techniques for label in name w3c/wcag#649.
-
Label in Name Understanindg edits for consistency w3c/wcag#732.
-
-
3 pull requests closed.
-
Example doorslam w3c/wcag#791.
-
Pointer gestures understanding drag changes - detlev w3c/wcag#736.
-
Create css-two-color-focus w3c/wcag#765.
-
-
21 pull requests received 78 new comments.
-
Update pointer-gestures understanding doc w3c/wcag#714 (22 comments by @alastc, @awkawk, @detlevhfischer)
-
Fixes for Understanding 1.3.3 Sensory Characteristics w3c/wcag#767 (11 comments by @alastc, @awkawk, @patrickhlauke)
-
w3c/coga
-
3 issues closed.
-
do webby stuff w3c/coga#86.
-
2 issues received 4 new comments.
-
Broken link to latest published version in the Techniques document w3c/coga#88 (3 comments by @SteveALee)
-
-
6 pull requests opened.
-
Add missing sections and fix markup errors w3c/coga#94, by @SteveALee.
-
Editorial Changes to design guide w3c/coga#93, by @SteveALee.
-
Fix a couple of pattern names w3c/coga#92, by @lseeman.
-
Design doc transfer review2 w3c/coga#91, by @lseeman.
-
Design doc transfer w3c/coga#90, by @SteveALee.
-
Content usable rbreview w3c/coga#89, by @lseeman.
-
-
5 pull requests merged.
-
Add missing sections and fix markup errors w3c/coga#94.
-
Editorial Changes to design guide w3c/coga#93.
-
Fix a couple of pattern names w3c/coga#92.
-
Design doc transfer review2 w3c/coga#91.
-
Content usable rbreview w3c/coga#89.
-
-
1 pull request closed.
-
Design doc transfer w3c/coga#90.
-
-
5 pull requests received 13 new comments.
w3c/wcag-act
-
3 issues opened.
-
Change mark up of must / should / may w3c/wcag-act#390, by @WilcoFiers.
-
Issue with the "Conformance level" part of Accessibility Requirements Mapping w3c/wcag-act#384, by @annethyme.
-
Update example references from auto-wcag to ACT-R w3c/wcag-act#378, by @nitedog.
-
-
1 issue closed.
-
Reference to specific vendor w3c/wcag-act#361.
-
-
22 issues received 36 new comments.
-
Level Access Feedback: Unspecified Input Aspects w3c/wcag-act#370 (4 comments by @annethyme, @maryjom, @WilcoFiers)
-
Process proposal: Publishing ACT Rules on w3.org/WAI w3c/wcag-act#353 (2 comments by @bruce-usab, @maryjom)
-
-
12 pull requests opened.
-
update Appendix 1 w3c/wcag-act#389, by @nitedog.
-
Remove unintended must & may w3c/wcag-act#388, by @WilcoFiers.
-
Fix "rule type" link in section 4 w3c/wcag-act#387, by @WilcoFiers.
-
Change "vue" reference to "web component" w3c/wcag-act#386, by @WilcoFiers.
-
Add inline definition for unique identifier w3c/wcag-act#385, by @WilcoFiers.
-
Edits to clarify Input Aspects w3c/wcag-act#383, by @maryjom.
-
Optional items under must w3c/wcag-act#382, by @maryjom.
-
Made various editorial changes w3c/wcag-act#381, by @maryjom.
-
Should explainer w3c/wcag-act#380, by @maryjom.
-
Fixed capitalization in 3 places w3c/wcag-act#379, by @maryjom.
-
updated Example 3 in Annex 1 w3c/wcag-act#377, by @nitedog.
-
updated abstract w3c/wcag-act#376, by @nitedog.
-
-
5 pull requests merged.
-
Change "vue" reference to "web component" w3c/wcag-act#386.
-
Fix "rule type" link in section 4 w3c/wcag-act#387.
-
Remove unintended must & may w3c/wcag-act#388.
-
Add inline definition for unique identifier w3c/wcag-act#385.
-
updated Example 3 in Annex 1 w3c/wcag-act#377.
-
-
8 pull requests received 44 new comments.
w3c/wcag3
-
2 issues opened.
-
1.4.5 / 1.4.9 Image of Text and <text> inside SVGs w3c/wcag3#190, by @patrickhlauke.
-
3 issues received 34 new comments.
-
Revisiting imbalance between 1.2.4 Captions (Live) (AA) and 1.2.9 Audio-only (Live) (AAA) w3c/wcag3#189 (28 comments by @alastc, @awkawk, @bruce-usab, @johnfoliot, @mraccess77, @patrickhlauke)
-
Contrast Ratio Math and Related Visual Issues w3c/wcag3#192 (5 comments by @bruce-usab, @Myndex, @Ryladog)
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
3 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
do webby stuff w3c/coga#86.
-
2 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 4 new comments.
-
Broken link to latest published version in the Techniques document w3c/coga#88 (3 comments by @SteveALee)
-
-
6 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Add missing sections and fix markup errors w3c/coga#94, by @SteveALee.
-
Editorial Changes to design guide w3c/coga#93, by @SteveALee.
-
Fix a couple of pattern names w3c/coga#92, by @lseeman.
-
Design doc transfer review2 w3c/coga#91, by @lseeman.
-
Design doc transfer w3c/coga#90, by @SteveALee.
-
Content usable rbreview w3c/coga#89, by @lseeman.
-
-
5 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Add missing sections and fix markup errors w3c/coga#94.
-
Editorial Changes to design guide w3c/coga#93.
-
Fix a couple of pattern names w3c/coga#92.
-
Design doc transfer review2 w3c/coga#91.
-
Content usable rbreview w3c/coga#89.
-
-
1 pull request closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Design doc transfer w3c/coga#90.
-
-
5 pull requests in the Cognitive and Learning Disabilities Accessibility Task Force received 13 new comments.
Low Vision Accessibility Task Force
GitHub
w3c/low-vision-a11y-tf
-
1 pull request opened in the Low Vision Accessibility Task Force.
-
Jim edits w3c/low-vision-a11y-tf#83, by @allanj-uaag.
-
-
1 pull request closed in the Low Vision Accessibility Task Force.
-
Jim edits w3c/low-vision-a11y-tf#83.
-
Participants
-
1 organization left.
-
New Zealand Government left.
-
GitHub
w3c/wcag
-
28 issues opened.
-
add definition for “path-based gesture” for 2.2 w3c/wcag#758, by @jake-abma.
-
Using color ALONE as focus indicator w3c/wcag#757, by @aparnapasi.
-
Bad/incomplete example for Understanding 3.3.2 w3c/wcag#755, by @patrickhlauke.
-
Understanding 4.1.2: wrong anchor w3c/wcag#751, by @audreymaniez.
-
Ambiguity in understanding for 1.3.3 sensory characteristics w3c/wcag#750, by @patrickhlauke.
-
"single pointer" definition not quite accurate? w3c/wcag#749, by @patrickhlauke.
-
"(future link)" Vs. "GXXX:" (SC 2.5.1) w3c/wcag#748, by @jake-abma.
-
explanation of "path-based gestures" for "single pointer" w3c/wcag#746, by @jake-abma.
-
links broken 2.5.3: Label in Name | single Vs. plural w3c/wcag#745, by @jake-abma.
-
Found a undiscovered "future link" in 3.2.5 - Change on Request w3c/wcag#743, by @jake-abma.
-
New placement of Understanding link w3c/wcag#742, by @DavidMacDonald.
-
Explanation for Benefit nr.3 SC 3.2.5: Change on Request w3c/wcag#740, by @jake-abma.
-
3.2.5: Change on Request Understanding update w3c/wcag#738, by @jake-abma.
-
"changes of context" definition complete? w3c/wcag#737, by @jake-abma.
-
Typo Understanding 2.5.3 Label in name w3c/wcag#731, by @audreymaniez.
-
Motion actuation (2.5.4) question on exception w3c/wcag#727, by @alastc.
-
Applicability/testability of 1.3.5 for native apps w3c/wcag#720, by @patrickhlauke.
-
ARIA authoring pratices design pattern to conform WCAG ? w3c/wcag#718, by @goetsu.
-
ARIA in HTML conformance to conform WCAG ? w3c/wcag#717, by @goetsu.
-
-
24 issues closed.
-
typo w3c/wcag#756.
-
links broken 2.5.3: Label in Name | single Vs. plural w3c/wcag#745.
-
"(future link)" Vs. "GXXX:" (SC 2.5.1) w3c/wcag#748.
-
Understanding 4.1.2: wrong anchor w3c/wcag#751.
-
Link to "Related resources" w3c/wcag#334.
-
Add META tag for viewport at examples w3c/wcag#480.
-
Typo Understanding 2.5.3 Label in name w3c/wcag#731.
-
Small text change to Examples: 2.5.4: Motion Actuation w3c/wcag#710.
-
2.4.7 Focus Visible - what counts as "visible"? w3c/wcag#302.
-
Small adjustment to link "How to Meet WCAG 2.1" w3c/wcag#412.
-
1.4.3 - CSS4 Variable Fonts - What is bold? w3c/wcag#341.
-
Applicability/testability of 1.3.5 for native apps w3c/wcag#720.
-
Live form controls in understanding non text contrast w3c/wcag#405.
-
Second thoughts on pointer gestures and drag-and-drop w3c/wcag#403.
-
Carry out editorial review for consistent structure w3c/wcag#398.
-
Understanding SC 1.4.11 - Mistake w3c/wcag#397.
-
-
70 issues received 277 new comments.
-
Include font weight for color contrast tests w3c/wcag#665 (29 comments by @alastc, @Myndex, @patrickhlauke)
-
1.4.4 - Clarification needed for Success Criterion for mobile browsers w3c/wcag#730 (18 comments by @alastc, @clshortfuse, @jha11y, @patrickhlauke)
-
2.5.3: Must the visible label of site logos linking to the start page be included in the accName? w3c/wcag#722 (15 comments by @awkawk, @detlevhfischer, @jake-abma, @patrickhlauke)
-
interpreting non-text contrast for isometric illustrations w3c/wcag#700 (13 comments by @alastc, @awkawk, @mbgower, @mraccess77, @Myndex)
-
Bad/incomplete example for Understanding 3.3.2 w3c/wcag#755 (12 comments by @awkawk, @goetsu, @mraccess77, @patrickhlauke)
-
Notifications - UI component contrast understanding 1.4.11 w3c/wcag#713 (12 comments by @alastc, @awkawk, @Myndex, @patrickhlauke, @petewoodhouse-rg)
-
"changes of context" definition complete? w3c/wcag#737 (11 comments by @awkawk, @jake-abma, @mraccess77, @patrickhlauke)
-
"single pointer" definition not quite accurate? w3c/wcag#749 (10 comments by @detlevhfischer, @jake-abma, @patrickhlauke)
-
Reflow Understanding text hard to parse when it talks about 1.4.4 w3c/wcag#658 (8 comments by @alastc, @DavidMacDonald, @MikeElledge, @mraccess77, @patrickhlauke)
-
ARIA authoring pratices design pattern to conform WCAG ? w3c/wcag#718 (8 comments by @awkawk, @DavidMacDonald, @mraccess77, @patrickhlauke, @scottaohara)
-
Applicability/testability of 1.3.5 for native apps w3c/wcag#720 (8 comments by @alastc, @detlevhfischer, @johnfoliot, @mraccess77, @patrickhlauke)
-
New placement of Understanding link w3c/wcag#742 (7 comments by @alastc, @jake-abma, @mraccess77, @patrickhlauke)
-
Motion actuation (2.5.4) question on exception w3c/wcag#727 (7 comments by @alastc, @jake-abma, @patrickhlauke)
-
Explanation for Benefit nr.3 SC 3.2.5: Change on Request w3c/wcag#740 (6 comments by @alastc, @jake-abma, @mraccess77)
-
ARIA in HTML conformance to conform WCAG ? w3c/wcag#717 (6 comments by @awkawk, @goetsu, @jake-abma, @mraccess77, @patrickhlauke, @stevefaulkner)
-
Draft technique "Not relying on path or multipoint gestures for operation" w3c/wcag#739 (5 comments by @alastc, @detlevhfischer, @goetsu, @mraccess77, @patrickhlauke)
-
Failure Technique around page regions (Header, Footer, Nav, Main etc.) w3c/wcag#340 (5 comments by @ghost, @jake-abma, @mraccess77)
-
SC Understanding update: "What it is about" Vs. "What it isn't about" w3c/wcag#744 (4 comments by @alastc, @jake-abma, @patrickhlauke)
-
3.2.5: Change on Request Understanding update w3c/wcag#738 (4 comments by @alastc, @jake-abma, @patrickhlauke)
-
SC language for Content on Hover or Focus could be misinterpreted w3c/wcag#687 (4 comments by @alastc, @jake-abma, @mraccess77)
-
explanation of "path-based gestures" for "single pointer" w3c/wcag#746 (4 comments by @detlevhfischer, @patrickhlauke)
-
Key terms have word "new" preceding definition, 2.5.2: Pointer Cancellation w3c/wcag#708 (4 comments by @jake-abma, @patrickhlauke)
-
1.4.12 Text Spacing - Clarify `text-overflow: ellipsis` applicability, as well as acceptability w3c/wcag#728 (4 comments by @alastc, @cscrosati, @patrickhlauke)
-
WCAG F85: Clarify guidance about where the focus should go when the modal dialog is closed w3c/wcag#518 (3 comments by @electronicwoft, @jake-abma)
-
1.4.13 Content on Hover or Focus - need some clarifications on two points w3c/wcag#605 (3 comments by @alastc)
-
SC 1.3.5 Technique "Use type attribute on fields in simple login forms"? w3c/wcag#504 (3 comments by @patrickhlauke)
-
Expand 1.4.10 to apply 'down to' instead of 'at' w3c/wcag#698 (3 comments by @alastc, @patrickhlauke, @WayneEDick)
-
Non-sRGB color spaces, outdated sRGB threshold, and other issues in the "relative luminance" definition w3c/wcag#360 (3 comments by @Myndex, @svgeesus)
-
2.5.1 Pointer Gestures: clarity on path-based language in Understanding document w3c/wcag#522 (2 comments by @detlevhfischer, @goetsu)
-
Draft technique "Providing a control slider that offers single point activation" w3c/wcag#741 (2 comments by @alastc, @jake-abma)
-
Ambiguity in understanding for 1.3.3 sensory characteristics w3c/wcag#750 (2 comments by @awkawk, @patrickhlauke)
-
Have the Advisory techniques that had no text been removed from WCAG 2.1? w3c/wcag#369 (2 comments by @alastc, @jake-abma)
-
Demonstration videos need captions and descriptions w3c/wcag#689 (2 comments by @alastc, @mraccess77)
-
Cursor as sole focus indicator of inputs sufficient to meet 1.4.11? w3c/wcag#680 (1 comment by @electronicwoft)
-
4.1.1 Parsing - Duplicate attributes with no user impact cause a conformance failure w3c/wcag#542 (1 comment by @awkawk)
-
Benefits 2.5.1: split benefit and remove redundant one (for other SC) w3c/wcag#747 (1 comment by @patrickhlauke)
-
Sections in Understanding docs without content should be adjusted w3c/wcag#705 (1 comment by @jake-abma)
-
Include details on user interface components in 1.4.3 & 1.4.6 Understanding w3c/wcag#481 (1 comment by @alastc)
-
Sentence Advisory Techniques for 2.4.7: Focus Visible need adjustments w3c/wcag#729 (1 comment by @jake-abma)
-
exempt or not covered, and exempt not needed - SC 2.5.4: Motion Actuation w3c/wcag#709 (1 comment by @jake-abma)
-
Duplicate paragraph in the "Status of This Document" section of WCAG 2.1 w3c/wcag#410 (1 comment by @alastc)
-
SC 1.3.5 Identify Input Purpose - autocomplete technique VS Privacy/Security w3c/wcag#407 (1 comment by @alastc)
-
Understanding Non-Text contrast needs update to reflect consensus. w3c/wcag#406 (1 comment by @alastc)
-
-
13 pull requests opened.
-
Change on Request update for issue #738 w3c/wcag#754, by @alastc.
-
Tech icon font img role v3 w3c/wcag#753, by @alastc.
-
Tech icon font img role v2 w3c/wcag#752, by @alastc.
-
Pointer gestures understanding drag changes - detlev w3c/wcag#736, by @alastc.
-
Understanding pointer gestures df changes w3c/wcag#735, by @detlevhfischer.
-
Added href value w3c/wcag#734, by @svinkle.
-
Motion actuation errata from issue 727 w3c/wcag#733, by @alastc.
-
Label in Name Understanindg edits for consistency w3c/wcag#732, by @mbgower.
-
Technique: Native controls for up event w3c/wcag#726, by @alastc.
-
Updates based on #714 discussion w3c/wcag#725, by @alastc.
-
Updates for issue 416, inc normative note w3c/wcag#724, by @alastc.
-
Hover-focus, typo and additional paragraph w3c/wcag#723, by @alastc.
-
Bypass blocks issue 404 w3c/wcag#721, by @alastc.
-
-
2 pull requests merged.
-
Tech icon font img role v3 w3c/wcag#753.
-
Hover-focus, typo and additional paragraph w3c/wcag#723.
-
-
5 pull requests closed.
-
Added href value w3c/wcag#734.
-
Tech icon font img role v2 w3c/wcag#752.
-
Technique - setting role of img on icon fonts w3c/wcag#531.
-
Understanding pointer gestures df changes w3c/wcag#735.
-
Updates based on #714 discussion w3c/wcag#725.
-
-
19 pull requests received 70 new comments.
-
Failure technique for 2.5.6 Concurrent Input Mechanisms w3c/wcag#690 (16 comments by @alastc, @jake-abma, @mbgower, @patrickhlauke, @Ryladog)
-
Update pointer-gestures understanding doc w3c/wcag#714 (14 comments by @alastc, @detlevhfischer, @jake-abma, @mbgower, @patrickhlauke)
-
Technique: Native controls for up event w3c/wcag#726 (3 comments by @alastc, @detlevhfischer, @patrickhlauke)
-
Change to normative text of 1.4.12: at least > up to w3c/wcag#637 (3 comments by @detlevhfischer, @jake-abma, @patrickhlauke)
-
w3c/wcag-act
-
21 issues opened.
-
Feedback: Audrey Maniez (Access42) w3c/wcag-act#375, by @WilcoFiers.
-
Capitalize "Web" used as a noun w3c/wcag-act#374, by @nitedog.
-
Unintended "may" in Examples 17 w3c/wcag-act#373, by @nitedog.
-
Unintended "must" in Introduction w3c/wcag-act#372, by @nitedog.
-
feedback of Orange accessibility team w3c/wcag-act#371, by @Aniort.
-
Level Access Feedback: Unspecified Input Aspects w3c/wcag-act#370, by @WilcoFiers.
-
Level Access Feedback: Rule Input w3c/wcag-act#369, by @WilcoFiers.
-
Level Access Feedback: Atomic rules w3c/wcag-act#368, by @WilcoFiers.
-
Level Access Feedback: ACT Rule Types w3c/wcag-act#367, by @WilcoFiers.
-
Level Access Feedback: General w3c/wcag-act#366, by @WilcoFiers.
-
Intention to submit feedback and implementation report w3c/wcag-act#365, by @cptvitamin.
-
CR Feedback Fernanda Bonnin w3c/wcag-act#364, by @WilcoFiers.
-
Feedback Lisa Louise Davis w3c/wcag-act#363, by @WilcoFiers.
-
Examples 3 and 4 in Appendix 1 are identical w3c/wcag-act#362, by @carlosapaduarte.
-
Reference to specific vendor w3c/wcag-act#361, by @carlosapaduarte.
-
Rule's date and version number w3c/wcag-act#360, by @carlosapaduarte.
-
Expectations for Composite Rules w3c/wcag-act#359, by @carlosapaduarte.
-
"Unique identifier" scope w3c/wcag-act#358, by @carlosapaduarte.
-
Optional items under MUST keyword w3c/wcag-act#357, by @carlosapaduarte.
-
Editorial updates w3c/wcag-act#356, by @carlosapaduarte.
-
Unintended "should" in background section w3c/wcag-act#355, by @WilcoFiers.
-
-
1 issue closed.
-
Update the CSS reference in the Common Input Aspects note w3c/wcag-act#333.
-
-
11 issues received 16 new comments.
-
Process proposal: Publishing ACT Rules on w3.org/WAI w3c/wcag-act#353 (4 comments by @annethyme, @mraccess77, @WilcoFiers)
-
w3c/coga
-
2 issues opened.
-
Possible typo in title and main header of Techniques document w3c/coga#87, by @jfhector.
w3c/wcag3
-
1 issue opened.
-
Description for Icons w3c/wcag3#191, by @MarcHaunschild.
-
-
1 issue reopened.
-
Description for Icons w3c/wcag3#191, by @MarcHaunschild.
-
-
2 issues received 29 new comments.
-
Contrast Ratio Math and Related Visual Issues w3c/wcag3#192 (20 comments by @alastc, @mraccess77, @Myndex, @patrickhlauke)
-
Description for Icons w3c/wcag3#191 (9 comments by @alastc, @awkawk, @detlevhfischer, @LJWatson, @MarcHaunschild)
-
w3c/earl
-
1 pull request opened.
-
fix: update Axe report w3c/earl#2, by @jeeyyy.
-
-
1 pull request merged.
-
fix: update Axe report w3c/earl#2.
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
2 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Possible typo in title and main header of Techniques document w3c/coga#87, by @jfhector.
TR publications
-
2 documents published.
-
Accessibility Conformance Testing (ACT) Rules Format 1.0 published as a Candidate Recommendation Snapshot. History of Accessibility Conformance Testing (ACT) Rules Format 1.0
-
Participants
-
2 participants joined.
-
David Fazio (W3C Invited Experts) joined.
-
Chris Loiselle (Oracle Corporation) joined.
-
-
1 participant left.
-
Joshue O'Connor (W3C Invited Experts) left.
-
-
1 organization joined.
-
Dyno Mapper joined.
-
GitHub
w3c/wcag
-
20 issues opened.
-
Notifications - UI component contrast understanding 1.4.11 w3c/wcag#713, by @petewoodhouse-rg.
-
Small text change to Examples: 2.5.4: Motion Actuation w3c/wcag#710, by @jake-abma.
-
Sections in Understanding docs without content should be adjusted w3c/wcag#705, by @jake-abma.
-
Typo in "Understanding SC 1.3.6" w3c/wcag#703, by @ptrin.
-
interpreting non-text contrast for isometric illustrations w3c/wcag#700, by @mbgower.
-
5.2.2 Full pages 3rd Note has redundant text "New" w3c/wcag#699, by @jake-abma.
-
Expand 1.4.10 to apply 'down to' instead of 'at' w3c/wcag#698, by @patrickhlauke.
-
Overlap between 3.3.1 and 4.1.2? w3c/wcag#696, by @patrickhlauke.
-
Demonstration videos need captions and descriptions w3c/wcag#689, by @mbgower.
-
SC language for Content on Hover or Focus could be misinterpreted w3c/wcag#687, by @mbgower.
-
Understanding 2.5.5: Target Size - broken links to definitions w3c/wcag#684, by @patrickhlauke.
-
Potential failure techniques (or at least checks) for Text Spacing? w3c/wcag#683, by @mbgower.
-
Technique C36 missing content? w3c/wcag#682, by @mbgower.
-
-
19 issues closed.
-
Typo in "Understanding SC 1.3.6" w3c/wcag#703.
-
5.2.2 Full pages 3rd Note has redundant text "New" w3c/wcag#699.
-
Understanding Reflow "out of the flow" w3c/wcag#390.
-
Understanding document - SC 1.4.12 Text Spacing w3c/wcag#378.
-
SC 1.1.1 Situation D - ARIA 6 & ARIA 10 w3c/wcag#503.
-
use of color example in Non-Text Contrast w3c/wcag#492.
-
Understanding Status Changes w3c/wcag#359.
-
Understanding Motion Actuation w3c/wcag#358.
-
Understanding Pointer Gestures w3c/wcag#354.
-
Understanding Pointer Cancellation w3c/wcag#355.
-
Mobile browser reflow language potentially confusing w3c/wcag#660.
-
Large text definition should include more font weights w3c/wcag#671.
-
Technique G134: Outdated Links w3c/wcag#657.
-
54 issues received 237 new comments.
-
Expand 1.4.10 to apply 'down to' instead of 'at' w3c/wcag#698 (46 comments by @alastc, @detlevhfischer, @jake-abma, @mraccess77, @patrickhlauke, @stephenhay, @WayneEDick)
-
Cursor as sole focus indicator of inputs sufficient to meet 1.4.11? w3c/wcag#680 (40 comments by @awkawk, @detlevhfischer, @jake-abma, @mbgower, @mraccess77, @patrickhlauke)
-
Failure technique F94 (1.4.4 resize text): remove "1280 pixels wide" step in test procedure w3c/wcag#704 (25 comments by @alastc, @detlevhfischer, @mraccess77, @patrickhlauke)
-
2.4.7 Focus Visible - what counts as "visible"? w3c/wcag#302 (13 comments by @alastc, @fstorr, @johnfoliot, @mraccess77, @patrickhlauke, @StommePoes)
-
2.5.1 Pointer Gestures: clarity on path-based language in Understanding document w3c/wcag#522 (9 comments by @alastc, @awkawk, @detlevhfischer, @mbgower)
-
Non-sRGB color spaces, outdated sRGB threshold, and other issues in the "relative luminance" definition w3c/wcag#360 (9 comments by @alastc, @Myndex, @svgeesus)
-
Overlap between 3.3.1 and 4.1.2? w3c/wcag#696 (9 comments by @DavidMacDonald, @detlevhfischer, @mraccess77, @patrickhlauke)
-
SC language for Content on Hover or Focus could be misinterpreted w3c/wcag#687 (6 comments by @detlevhfischer, @jake-abma, @steverep)
-
SC 1.3.5 Technique "Use type attribute on fields in simple login forms"? w3c/wcag#504 (5 comments by @alastc, @detlevhfischer, @jake-abma, @patrickhlauke)
-
1.3.2. Advisory Technique recommends using justified text. Shouldn't it be left/right-aligned? w3c/wcag#697 (4 comments by @alastc, @michael-n-cooper, @mraccess77, @Myndex)
-
interpreting non-text contrast for isometric illustrations w3c/wcag#700 (4 comments by @mbgower, @Myndex)
-
Understanding Success Criterion 1.3.4: Orientation w3c/wcag#416 (4 comments by @awkawk, @mbgower, @StefanSTS)
-
Sections in Understanding docs without content should be adjusted w3c/wcag#705 (3 comments by @jake-abma, @mbgower, @michael-n-cooper)
-
Key terms have word "new" preceding definition, 2.5.2: Pointer Cancellation w3c/wcag#708 (2 comments by @mbgower, @michael-n-cooper)
-
Notifications - UI component contrast understanding 1.4.11 w3c/wcag#713 (2 comments by @patrickhlauke, @petewoodhouse-rg)
-
iOS and Android not part of examples for WCAG, should be deleted 2.5.2: Pointer Cancellation w3c/wcag#706 (2 comments by @mbgower)
-
Understanding 2.5.4 Motion Actuation's "Related Resources" are irrelevant. w3c/wcag#652 (2 comments by @awkawk)
-
Are Reflow, Text Size and Orientation cumulative? w3c/wcag#391 (2 comments by @alastc, @patrickhlauke)
-
4.1.1 Parsing - Duplicate attributes with no user impact cause a conformance failure w3c/wcag#542 (2 comments by @alastc, @WilcoFiers)
-
Potential failure techniques (or at least checks) for Text Spacing? w3c/wcag#683 (2 comments by @nitedog, @WayneEDick)
-
Conflict between glossary definition of label and H65 sufficient technique for 3.3.2 w3c/wcag#101 (1 comment by @alastc)
-
exempt or not covered, and exempt not needed - SC 2.5.4: Motion Actuation w3c/wcag#709 (1 comment by @mbgower)
-
2.5.2: Pointer Cancellation mentions failure for 2.5.3, editorial issue w3c/wcag#707 (1 comment by @mbgower)
-
1.4.13 Content on Hover or Focus - need some clarifications on two points w3c/wcag#605 (1 comment by @detlevhfischer)
-
Reflow Understanding text hard to parse when it talks about 1.4.4 w3c/wcag#658 (1 comment by @detlevhfischer)
-
2.5.4 Concurrent Input Mechanism: Add mouse/keyboard menu example w3c/wcag#363 (1 comment by @alastc)
-
Can browser dev tools > device toggle be used to test SC 1.4.10 Reflow w3c/wcag#520 (1 comment by @patrickhlauke)
-
Making 1.4.1 use of color info on state requirements for 1.4.11 into new sufficient and failure techniques w3c/wcag#402 (1 comment by @mbgower)
-
Understanding 2.5.5: Target Size - broken links to definitions w3c/wcag#684 (1 comment by @michael-n-cooper)
-
-
14 pull requests opened.
-
Update reflow.html w3c/wcag#715, by @mbgower.
-
Update pointer-gestures understanding doc w3c/wcag#714, by @mbgower.
-
Motion actuation editorial jake w3c/wcag#712, by @mbgower.
-
Pointer cancellation jake suggestions w3c/wcag#711, by @mbgower.
-
Update status-messages.html w3c/wcag#694, by @mbgower.
-
Update motion-actuation.html w3c/wcag#693, by @mbgower.
-
Short cuts addendum w3c/wcag#692, by @mbgower.
-
Pointer gestures typos w3c/wcag#691, by @mbgower.
-
Failure technique for 2.5.6 Concurrent Input Mechanisms w3c/wcag#690, by @patrickhlauke.
-
Sort out figure labels w3c/wcag#688, by @michael-n-cooper.
-
Non-text contast - Adjacent colors and example clarifications. w3c/wcag#681, by @alastc.
-
-
8 pull requests merged.
-
Motion actuation editorial jake w3c/wcag#712.
-
Tech failure orientation lock w3c/wcag#545.
-
Tech drag drop cancel w3c/wcag#456.
-
Update reflow.html w3c/wcag#659.
-
fixes per #657 w3c/wcag#678.
-
Pointer gestures typos w3c/wcag#691.
-
-
16 pull requests received 60 new comments.
-
Failure technique for 2.5.6 Concurrent Input Mechanisms w3c/wcag#690 (15 comments by @awkawk, @DavidMacDonald, @detlevhfischer, @jake-abma, @mbgower, @mraccess77, @patrickhlauke)
-
Update motion-actuation.html w3c/wcag#693 (9 comments by @awkawk, @detlevhfischer, @mbgower, @patrickhlauke)
-
general techniques for label in name w3c/wcag#649 (6 comments by @MakotoUeki, @mbgower, @patrickhlauke)
-
Technique - setting role of img on icon fonts w3c/wcag#531 (4 comments by @jake-abma, @lauracarlson)
-
Non-text contast - Adjacent colors and example clarifications. w3c/wcag#681 (3 comments by @alastc, @Myndex)
-
In 1.4.11 Understanding text, adds field boundary exception when contrasty placeholder present w3c/wcag#701 (1 comment by @awkawk)
-
Add clarification of "inactive" to user interface component glossary definition w3c/wcag#638 (1 comment by @alastc)
-
w3c/wcag3
-
4 issues opened.
-
Contrast Ratio Math and Related Visual Issues w3c/wcag3#192, by @Myndex.
-
Contrast Ratio Math and Related Visual Issues w3c/wcag3#196, by @Myndex.
-
Contrast Ratio Math and Related Visual Issues w3c/wcag3#195, by @Myndex.
-
Draft SC "States Discernable" w3c/wcag3#193, by @detlevhfischer.
-
-
4 issues received 73 new comments.
-
Contrast Ratio Math and Related Visual Issues w3c/wcag3#192 (44 comments by @alastc, @bruce-usab, @mraccess77, @Myndex, @patrickhlauke, @svgeesus, @xi)
-
Draft SC "Label gaps" w3c/wcag3#194 (15 comments by @alastc, @detlevhfischer, @jake-abma, @patrickhlauke)
-
Reflow: Fixed Position Fields w3c/wcag3#198 (8 comments by @alastc, @jake-abma, @mraccess77, @patrickhlauke, @StommePoes)
-
w3c/wcag-act
-
2 issues opened.
-
Remove Conformance section from WG note w3c/wcag-act#354, by @moekraft.
-
Process proposal: Publishing ACT Rules on w3.org/WAI w3c/wcag-act#353, by @WilcoFiers.
-
-
4 issues closed.
-
List of features for exit critiera w3c/wcag-act#224.
-
Issue with Example 11 w3c/wcag-act#342.
-
Cleanup balance between WCAG 2.0 and WCAG 2.1 w3c/wcag-act#323.
-
-
1 issue received 5 new comments.
-
Process proposal: Publishing ACT Rules on w3.org/WAI w3c/wcag-act#353 (5 comments by @aglevelaccess, @alastc, @maryjom, @nitedog)
-
-
1 pull request merged.
-
added Exit Criteria w3c/wcag-act#352.
-
-
1 pull request received 1 new comment.
w3c/earl
-
1 pull request opened.
-
Set repo-type to others and remove association with WG w3c/earl#1, by @dontcallmedom.
-
Participants
-
1 organization joined.
-
Thomson Reuters Corp. joined.
-
GitHub
w3c/wcag
-
25 issues opened.
-
Tech C38 example not working w3c/wcag#679, by @jake-abma.
-
minor issues with working example w3c/wcag#677, by @mbgower.
-
Contrast questions w3c/wcag#675, by @awkawk.
-
Broken link in 2.1 w3c/wcag#672, by @DavidMacDonald.
-
Large text definition should include more font weights w3c/wcag#671, by @cyns.
-
2.5.2 Pointer cancellation - are both mouse buttons included? w3c/wcag#670, by @detlevhfischer.
-
Reflow and diverging content behaviour desktop vs. mobile w3c/wcag#668, by @detlevhfischer.
-
Add 'label in name' warning to ARIA8 w3c/wcag#667, by @alastc.
-
Include font weight for color contrast tests w3c/wcag#665, by @alastc.
-
Technique G146: outdated URL w3c/wcag#663, by @cstrobbe.
-
Mobile browser reflow language potentially confusing w3c/wcag#660, by @mbgower.
-
Technique G134: Outdated Links w3c/wcag#657, by @cstrobbe.
-
G206 seems to be allowing a failure to exist w3c/wcag#656, by @mbgower.
-
H42 missing appropriate hierarchical level condition w3c/wcag#655, by @goetsu.
-
The wording of 3.1.2 does not include a requirement for accuracy w3c/wcag#651, by @mbgower.
-
H59: outdated links w3c/wcag#650, by @cstrobbe.
-
Testing options for 2.5.1 Pointer gestures w3c/wcag#647, by @detlevhfischer.
-
G209: The technique "IS" referenced from an Understanding doc w3c/wcag#646, by @jake-abma.
-
G207: Image missing "Orange icon on white background" w3c/wcag#645, by @jake-abma.
-
Testing options for orientation without mobile device w3c/wcag#643, by @detlevhfischer.
-
-
16 issues closed.
-
minor issues with working example w3c/wcag#677.
-
H42 missing appropriate hierarchical level condition w3c/wcag#655.
-
The "ZAP" example for CR 5 contradicts itself w3c/wcag#632.
-
Clarification on 2.5.3 Label in Name interpretation w3c/wcag#592.
-
Broken link in 2.1 w3c/wcag#672.
-
Technique G146: outdated URL w3c/wcag#663.
-
Scoping of 2.5.3 Label in Name w3c/wcag#591.
-
H59: outdated links w3c/wcag#650.
-
G207: Image missing "Orange icon on white background" w3c/wcag#645.
-
-
42 issues received 189 new comments.
-
4.1.1 Parsing - Duplicate attributes with no user impact cause a conformance failure w3c/wcag#542 (37 comments by @alastc, @awkawk, @DavidMacDonald, @dylanb, @jared-w-smith, @mraccess77, @nitedog, @patrickhlauke, @stevefaulkner, @WilcoFiers, @zcorpan)
-
If field asks for input about "your organization" is that covered under SC 1.3.5? w3c/wcag#642 (16 comments by @alastc, @awkawk, @johnfoliot, @mraccess77)
-
Reflow Understanding text hard to parse when it talks about 1.4.4 w3c/wcag#658 (13 comments by @alastc, @detlevhfischer, @mbgower, @patrickhlauke, @WayneEDick)
-
WCAG 2.1 2.1.4 Character Key Shortcuts - does it include SPACE/ENTER ? w3c/wcag#666 (11 comments by @alastc, @detlevhfischer, @KimPatch, @mbgower, @patrickhlauke)
-
H42 missing appropriate hierarchical level condition w3c/wcag#655 (11 comments by @alastc, @awkawk, @DavidMacDonald, @goetsu, @patrickhlauke)
-
Testing 1.4.10 Reflow: No equivalence of testing at 320px or 1280px with 400% zoom? w3c/wcag#648 (8 comments by @detlevhfischer, @mraccess77, @patrickhlauke)
-
Reflow and diverging content behaviour desktop vs. mobile w3c/wcag#668 (7 comments by @detlevhfischer, @patrickhlauke)
-
Are Reflow, Text Size and Orientation cumulative? w3c/wcag#391 (7 comments by @guyhickling, @mraccess77, @patrickhlauke)
-
Testing options for orientation without mobile device w3c/wcag#643 (7 comments by @detlevhfischer, @mraccess77, @patrickhlauke)
-
Clarification on user interface components for 2.5.3 Label in name w3c/wcag#593 (5 comments by @alastc, @awkawk, @mraccess77)
-
"at least" should be "at most" in WCAG 2.1 SC 1.4.12 w3c/wcag#635 (5 comments by @alastc, @patrickhlauke)
-
Add 'label in name' warning to ARIA8 w3c/wcag#667 (4 comments by @awkawk, @detlevhfischer, @jake-abma, @mbgower)
-
The wording of 3.1.2 does not include a requirement for accuracy w3c/wcag#651 (4 comments by @alastc, @awkawk, @patrickhlauke)
-
Do we need to clarify inactive user interface component w3c/wcag#636 (4 comments by @alastc, @patrickhlauke)
-
Clarify the meaning of "is also available" in step #3 of F3 test w3c/wcag#80 (4 comments by @detlevhfischer, @lauracarlson, @mbgower, @mraccess77)
-
Understanding 2.5.4 Motion Actuation's "Related Resources" are irrelevant. w3c/wcag#652 (4 comments by @awkawk, @mraccess77, @patrickhlauke)
-
Large text definition should include more font weights w3c/wcag#671 (3 comments by @awkawk, @jake-abma, @patrickhlauke)
-
Applicability of 1.4.12 text spacing to data tables in web applications w3c/wcag#641 (3 comments by @awkawk, @jake-abma)
-
Include font weight for color contrast tests w3c/wcag#665 (3 comments by @jake-abma, @patrickhlauke, @WayneEDick)
-
2.5.2 Pointer cancellation - are both mouse buttons included? w3c/wcag#670 (2 comments by @awkawk, @patrickhlauke)
-
2.5.1 Pointer Gestures: clarity on path-based language in Understanding document w3c/wcag#522 (2 comments by @detlevhfischer, @mbgower)
-
1.3.4 Orientation - applicability to native apps w3c/wcag#613 (2 comments by @mraccess77, @patrickhlauke)
-
Exception for use of symbols as visible label in regard to 2.5.3 Label in Name w3c/wcag#598 (1 comment by @mbgower)
-
WCAG 2.1 Understanding 2.3.1 - missing/vague dimension definitions w3c/wcag#585 (1 comment by @patrickhlauke)
-
References to a Failure for 2.5.2 Pointer Cancellation is out of date w3c/wcag#372 (1 comment by @awkawk)
-
DOCUMENT NOT FOUND - 2.4.7 Focus Visible link in SC 1.4.11: Non-text Contrast w3c/wcag#644 (1 comment by @awkawk)
-
-
9 pull requests opened.
-
fixes per #657 w3c/wcag#678, by @awkawk.
-
Update index.html w3c/wcag#676, by @mbgower.
-
Technique for device motion actuation w3c/wcag#669, by @alastc.
-
small fix to align H42 and ARIA12 w3c/wcag#664, by @awkawk.
-
Update ARIA13.xml w3c/wcag#662, by @RababGomaa.
-
Update reflow.html w3c/wcag#659, by @mbgower.
-
Motion Actuation Success Techniques and Working Example w3c/wcag#653, by @rachaelbradley.
-
general techniques for label in name w3c/wcag#649, by @mbgower.
-
-
4 pull requests merged.
-
Update index.html w3c/wcag#676.
-
small fix to align H42 and ARIA12 w3c/wcag#664.
-
ZAP Issue w3c/wcag#654.
-
Label in name understanding doc update, large w3c/wcag#614.
-
-
3 pull requests closed.
-
Motion Actuation Success Techniques and Working Example w3c/wcag#653.
-
updates to address AWK's concerns and placeholder w3c/wcag#615.
-
Edits for PR614 for review w3c/wcag#639.
-
-
12 pull requests received 35 new comments.
-
Technique - setting role of img on icon fonts w3c/wcag#531 (4 comments by @jake-abma, @lauracarlson)
-
Add clarification of "inactive" to user interface component glossary definition w3c/wcag#638 (3 comments by @awkawk, @patrickhlauke)
-
Motion Actuation Success Techniques and Working Example w3c/wcag#653 (2 comments by @awkawk, @rachaelbradley)
w3c/coga
-
1 issue opened.
-
do webby stuff w3c/coga#86, by @SteveALee.
-
-
1 issue received 1 new comment.
w3c/wcag-act
-
4 issues opened.
-
Make rule examples consistent across composite rule examples. w3c/wcag-act#348, by @moekraft.
-
Issue with Example 11 w3c/wcag-act#342, by @awkawk.
-
"test aspects" confusing w3c/wcag-act#341, by @awkawk.
-
Under Acknowledgements mention "Community Group for incubation"? w3c/wcag-act#340, by @annethyme.
-
-
9 issues closed.
-
Add an example or two of applicability w3c/wcag-act#330.
-
Add examples to Applicability w3c/wcag-act#298.
-
Wrong references to WAI-ARIA 1.1 w3c/wcag-act#222.
-
Add an example for expectations w3c/wcag-act#331.
-
Add links to Outcome definition w3c/wcag-act#315.
-
Update the link to EPUB spec in "Input Aspects" w3c/wcag-act#338.
-
Need better example of permanent change log w3c/wcag-act#98.
-
"test aspects" confusing w3c/wcag-act#341.
-
-
6 issues received 10 new comments.
-
Under Acknowledgements mention "Community Group for incubation"? w3c/wcag-act#340 (2 comments by @nitedog, @WilcoFiers)
-
Use consistent case and styling for outcomes: failed, passed, inapplicable w3c/wcag-act#316 (1 comment by @maryjom)
-
9 pull requests opened.
-
added Exit Criteria w3c/wcag-act#352, by @nitedog.
-
Fix styling, capitalization of outcomes w3c/wcag-act#351, by @maryjom.
-
Made WCAG references consistent w3c/wcag-act#350, by @maryjom.
-
Issue 342 Example of HTML Input Element Accessible Name w3c/wcag-act#349, by @moekraft.
-
edit: Better changelog example w3c/wcag-act#347, by @WilcoFiers.
-
edit: Add 2 applicability examples w3c/wcag-act#346, by @WilcoFiers.
-
edit: Update use of outcome definition w3c/wcag-act#345, by @WilcoFiers.
-
edit: More examples for expectations w3c/wcag-act#344, by @WilcoFiers.
-
edit: Change test aspect to input aspect w3c/wcag-act#343, by @WilcoFiers.
-
-
9 pull requests merged.
-
Made WCAG references consistent w3c/wcag-act#350.
-
Issue 342 Example of HTML Input Element Accessible Name w3c/wcag-act#349.
-
Fix styling, capitalization of outcomes w3c/wcag-act#351.
-
edit: Add 2 applicability examples w3c/wcag-act#346.
-
edit: More examples for expectations w3c/wcag-act#344.
-
edit: Update use of outcome definition w3c/wcag-act#345.
-
Update an EPUB reference to the latest spec URL w3c/wcag-act#339.
-
edit: Better changelog example w3c/wcag-act#347.
-
edit: Change test aspect to input aspect w3c/wcag-act#343.
-
-
9 pull requests received 23 new comments.
-
edit: Add 2 applicability examples w3c/wcag-act#346 (10 comments by @annethyme, @kasperisager, @nitedog, @rdeltour, @WilcoFiers)
-
w3c/wcag3
-
2 issues opened.
-
Draft SC "Label gaps" w3c/wcag3#194, by @detlevhfischer.
-
-
2 issues received 16 new comments.
-
Draft SC "Label gaps" w3c/wcag3#194 (15 comments by @alastc, @awkawk, @detlevhfischer, @mraccess77, @patrickhlauke)
-
Future Success Criteria: Require disabled icon for disabled UI interface elements w3c/wcag3#197 (1 comment by @bkimmel)
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
1 issue opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
do webby stuff w3c/coga#86, by @SteveALee.
-
-
1 issue in the Cognitive and Learning Disabilities Accessibility Task Force received 1 new comment.
Participants
-
3 organizations joined.
-
eyeo GmbH joined.
-
Salesforce joined.
-
Cyxtera Technologies, Inc. joined.
-
-
2 organizations left.
-
Readspeaker left.
-
Kaplan Publishing left.
-
GitHub
w3c/wcag
-
23 issues opened.
-
Do we need to clarify inactive user interface component w3c/wcag#636, by @DavidMacDonald.
-
"at least" should be "at most" in WCAG 2.1 SC 1.4.12 w3c/wcag#635, by @jrpool.
-
Example text is not distinguished from definition text w3c/wcag#634, by @mitchellevan.
-
The "ZAP" example for CR 5 contradicts itself w3c/wcag#632, by @mitchellevan.
-
Unavailable external resources in Understanding WCAG 2.0/2.1 w3c/wcag#628, by @momdo.
-
Criteria for erratum not present w3c/wcag#626, by @jake-abma.
-
Do issues with Windows high contrast mode fall under WCAG 2.1? w3c/wcag#623, by @mraccess77.
-
inconsistent anchors and pointers w3c/wcag#622, by @mbgower.
-
Understanding Conformance page is still 2.0 labelled w3c/wcag#621, by @mbgower.
-
1.4.12 Text Spacing and navigation mechanisms w3c/wcag#620, by @detlevhfischer.
-
definition of presentation in SC 1.3.1 w3c/wcag#618, by @goetsu.
-
User Agent Support notes w3c/wcag#617, by @awkawk.
-
Typo in 0.5.2 Numbering in WCAG 2.1 w3c/wcag#616, by @eduardo-olivares1.
-
1.3.4 Orientation - applicability to native apps w3c/wcag#613, by @detlevhfischer.
-
Editorial: More correctly link in §0.1 on WCAG 2.1 w3c/wcag#608, by @momdo.
-
28 issues closed.
-
Some wording questions for 1.3.5: Identify Input Purpose w3c/wcag#537.
-
Is it the purpose or not the purpose? w3c/wcag#536.
-
C7 - change needed in CSS code for example w3c/wcag#131.
-
1.4.12 Text Spacing and navigation mechanisms w3c/wcag#620.
-
Reference to WCAG 2.0 instead WCAG 2.1 w3c/wcag#382.
-
1.3.4 Orientation - applicability to native apps w3c/wcag#613.
-
definition of presentation in SC 1.3.1 w3c/wcag#618.
-
Generate valid HTML5 with XSLT w3c/wcag#253.
-
Word order is wrong on H74? w3c/wcag#280.
-
Technique proposal - Issue 296 - Reminder w3c/wcag#547.
-
inconsistent anchors and pointers w3c/wcag#622.
-
Understanding Conformance page is still 2.0 labelled w3c/wcag#621.
-
Typo in 0.5.2 Numbering in WCAG 2.1 w3c/wcag#616.
-
Test #1 of H39 for table caption needs re-wording w3c/wcag#165.
-
Editorial: More correctly link in §0.1 on WCAG 2.1 w3c/wcag#608.
-
Spacing Override Technique w3c/wcag#384.
-
Broken Link in F89 w3c/wcag#505.
-
fix CSS padding on understanding pages w3c/wcag#528.
-
42 issues received 200 new comments.
-
Do issues with Windows high contrast mode fall under WCAG 2.1? w3c/wcag#623 (20 comments by @alastc, @jake-abma, @lauracarlson, @mraccess77, @patrickhlauke, @StommePoes)
-
1.3.4 Orientation - applicability to native apps w3c/wcag#613 (17 comments by @alastc, @awkawk, @detlevhfischer, @goetsu, @jake-abma, @patrickhlauke)
-
Misleading info in "Understanding 2.4.4: Link Purpose (In Context)" w3c/wcag#581 (15 comments by @alastc, @awkawk, @goodwitch, @mraccess77, @patrickhlauke)
-
Is using the track element to provide audio descriptions sufficient? w3c/wcag#599 (15 comments by @alastc, @awkawk, @DavidMacDonald, @gkatsev, @lauracarlson, @OwenEdwards, @silviapfeiffer)
-
Test #1 of H39 for table caption needs re-wording w3c/wcag#165 (12 comments by @awkawk, @goetsu, @OlivierNourry)
-
Do we need to clarify inactive user interface component w3c/wcag#636 (9 comments by @awkawk, @DavidMacDonald, @jake-abma, @mraccess77, @patrickhlauke)
-
4.1.1 Parsing - Duplicate attributes with no user impact cause a conformance failure w3c/wcag#542 (9 comments by @alastc, @awkawk, @cwadamsoforacle, @dd8, @mraccess77, @patrickhlauke)
-
definition of presentation in SC 1.3.1 w3c/wcag#618 (8 comments by @alastc, @awkawk, @goetsu, @mraccess77, @patrickhlauke)
-
Example text is not distinguished from definition text w3c/wcag#634 (6 comments by @alastc, @awkawk, @jake-abma, @michael-n-cooper, @mitchellevan)
-
Some wording questions for 1.3.5: Identify Input Purpose w3c/wcag#537 (6 comments by @awkawk, @marcjohlic, @patrickhlauke)
-
C7 - change needed in CSS code for example w3c/wcag#131 (5 comments by @alastc, @awkawk, @patrickhlauke)
-
"at least" should be "at most" in WCAG 2.1 SC 1.4.12 w3c/wcag#635 (5 comments by @awkawk, @jrpool, @mraccess77, @patrickhlauke)
-
Is ALT text part of the visible label for 2.5.3 Label in Name? w3c/wcag#602 (4 comments by @awkawk, @bruce-usab, @mraccess77)
-
Editorial: Glossary section of WCAG 2.1 has phrase "WCAG Working Group" w3c/wcag#609 (3 comments by @awkawk)
-
1.4.13 Content on Hover or Focus - hoverable requirement, clarification of point "persistent" w3c/wcag#582 (3 comments by @alastc, @detlevhfischer, @mbgower)
-
Clarify if modal dialog on page load is a failure of SC 3.2.1 + 3.2.5 w3c/wcag#538 (2 comments by @jake-abma, @JamesCatt)
-
labelled navigation landmarks should be added to sufficient techniques for 2.4.4 w3c/wcag#619 (2 comments by @alastc)
-
Applicability of 1.4.12 text spacing to data tables in web applications w3c/wcag#641 (1 comment by @patrickhlauke)
-
Links point to nonexistent IDs in Understanding Success Criterion 4.1.3: Status Messages w3c/wcag#640 (1 comment by @awkawk)
-
Conflict between glossary definition of label and H65 sufficient technique for 3.3.2 w3c/wcag#101 (1 comment by @awkawk)
-
Tech H98 - autocomplete - should test also include check of wrong application of autocomplete? w3c/wcag#544 (1 comment by @awkawk)
-
-
16 pull requests opened.
-
Edits for PR614 for review w3c/wcag#639, by @awkawk.
-
Change to normative text of 1.4.12: at least > up to w3c/wcag#637, by @patrickhlauke.
-
Issues 536 & 537 Understanding Identify Input Purpose updates w3c/wcag#631, by @marcjohlic.
-
Updating CSS for C7 w3c/wcag#630, by @alastc.
-
Update identify-input-purpose.html w3c/wcag#629, by @marcjohlic.
-
Updates to H65 in response to #101 w3c/wcag#627, by @awkawk.
-
implemented Alastair's suggestions w3c/wcag#625, by @awkawk.
-
Possible re-update to H96 w3c/wcag#624, by @awkawk.
-
updates to address AWK's concerns and placeholder w3c/wcag#615, by @awkawk.
-
Label in name understanding doc update, large w3c/wcag#614, by @mbgower.
-
Fixes to WCAG 2.1 Understanding 2.4.6 and 3.3.2 w3c/wcag#612, by @patrickhlauke.
-
fix for issue #609 w3c/wcag#611, by @awkawk.
-
Correct links to the WAI-ARIA spec. w3c/wcag#607, by @alastc.
-
corrections to Character key shorts and Reflow w3c/wcag#606, by @mbgower.
-
Changes to address Issue #165 w3c/wcag#604, by @awkawk.
-
-
10 pull requests merged.
-
Updating CSS for C7 w3c/wcag#630.
-
Updates to H65 in response to #101 w3c/wcag#627.
-
Removing F52 from on-focus w3c/wcag#590.
-
Technique - Boundary contrast w3c/wcag#576.
-
fix for issue #609 w3c/wcag#611.
-
implemented Alastair's suggestions w3c/wcag#625.
-
Fixes to WCAG 2.1 Understanding 2.4.6 and 3.3.2 w3c/wcag#612.
-
Possible re-update to H96 w3c/wcag#624.
-
Correct links to the WAI-ARIA spec. w3c/wcag#607.
-
1 pull request closed.
-
Update identify-input-purpose.html w3c/wcag#629.
-
-
13 pull requests received 54 new comments.
-
corrections to Character key shorts and Reflow w3c/wcag#606 (14 comments by @alastc, @awkawk, @detlevhfischer, @marcjohlic, @mbgower)
-
Label in name understanding doc update, large w3c/wcag#614 (12 comments by @awkawk, @mbgower, @mraccess77, @patrickhlauke)
-
Fixes to WCAG 2.1 Understanding 2.4.6 and 3.3.2 w3c/wcag#612 (12 comments by @awkawk, @patrickhlauke)
-
Add clarification of "inactive" to user interface component glossary definition w3c/wcag#638 (1 comment by @michael-n-cooper)
-
w3c/wcag-act
-
6 issues opened.
-
Update the link to EPUB spec in "Input Aspects" w3c/wcag-act#338, by @rdeltour.
-
elaborate on complex aggregation w3c/wcag-act#335, by @nitedog.
-
Update the CSS reference in the Common Input Aspects note w3c/wcag-act#333, by @rdeltour.
-
Add an example for expectations w3c/wcag-act#331, by @maryjom.
-
Add an example or two of applicability w3c/wcag-act#330, by @maryjom.
-
Add example for External Accessibility Requirements mapping w3c/wcag-act#329, by @maryjom.
-
-
14 issues closed.
-
Consider a new section on "Evaluating a Rule"? w3c/wcag-act#139.
-
Rule Description: Example needed (Shadi) w3c/wcag-act#249.
-
Add an explanation about why to include the outcome definition w3c/wcag-act#285.
-
Write an explainer for the spec w3c/wcag-act#291.
-
Clarify that test subjects have only one outcome w3c/wcag-act#299.
-
Add definition for Accessibility Requirements document. w3c/wcag-act#317.
-
replace "failure condition" w3c/wcag-act#327.
-
Proposal to (slightly) rearange the spec outline w3c/wcag-act#284.
-
Add an example to Accessibility Support w3c/wcag-act#296.
-
Add a test case example w3c/wcag-act#297.
-
Add example for composed rules using other composed rules w3c/wcag-act#320.
-
Composed rule applicability not just a UNION w3c/wcag-act#321.
-
Common aspects doc needs an abstract and introduction w3c/wcag-act#318.
-
-
11 issues received 11 new comments.
-
Add example that applicability can include the page as a whole or the root node of a document w3c/wcag-act#288 (1 comment by @WilcoFiers)
-
Add example for composed rules using other composed rules w3c/wcag-act#320 (1 comment by @WilcoFiers)
-
6 pull requests opened.
-
Update an EPUB reference to the latest spec URL w3c/wcag-act#339, by @rdeltour.
-
Fix broken anchor, #rule-accuracy w3c/wcag-act#337, by @moekraft.
-
Create Editor's Draft for AG WG w3c/wcag-act#336, by @moekraft.
-
Updating WG Note on Common Input Aspects w3c/wcag-act#334, by @moekraft.
-
Created a change history for the document. w3c/wcag-act#332, by @maryjom.
-
Candidate recommendation proposal w3c/wcag-act#328, by @maryjom.
-
-
6 pull requests merged.
-
Fix broken anchor, #rule-accuracy w3c/wcag-act#337.
-
Create Editor's Draft for AG WG w3c/wcag-act#336.
-
Created a change history for the document. w3c/wcag-act#332.
-
Candidate recommendation proposal w3c/wcag-act#328.
-
Updating WG Note on Common Input Aspects w3c/wcag-act#334.
-
updated Abstract and Introduction w3c/wcag-act#326.
-
-
1 pull request closed.
-
Updates for CR w3c/wcag-act#322.
-
-
3 pull requests received 126 new comments.
-
Candidate recommendation proposal w3c/wcag-act#328 (108 comments by @annethyme, @cpandhi, @kengdoj, @maryjom, @rdeltour, @tbostic32, @WilcoFiers)
-
w3c/wcag3
-
1 issue received 1 new comment.
Participants
-
1 participant joined.
-
Stephen Repsher (W3C Invited Experts) joined.
-
-
3 organizations joined.
-
Wells Fargo Bank N.A. joined.
-
TetraLogical Services Ltd joined.
-
NYC Department of Education joined.
-
GitHub
w3c/wcag
-
19 issues opened.
-
Is ALT text part of the visible label for 2.5.3 Label in Name? w3c/wcag#602, by @mbgower.
-
Example page lacks images Images for C37 w3c/wcag#601, by @jake-abma.
-
This page is not functional at 320CSS px w3c/wcag#596, by @WayneEDick.
-
Need links to Understanding docs for guidelines w3c/wcag#595, by @mmeller75.
-
Clarification on user interface components for 2.5.3 Label in name w3c/wcag#593, by @cpandhi.
-
Clarification on 2.5.3 Label in Name interpretation w3c/wcag#592, by @mbgower.
-
Scoping of 2.5.3 Label in Name w3c/wcag#591, by @detlevhfischer.
-
Minor editorial issue (duplicate content) in Understanding 3.2.1 w3c/wcag#587, by @plannero.
-
Missing matching </div> w3c/wcag#580, by @jofatmofn.
-
Uniform look for sub-headings (Grouping of Techniques) w3c/wcag#578, by @jofatmofn.
-
Use of "or" in text as against "OR" for alternative techniques w3c/wcag#577, by @jofatmofn.
-
Relation of 200% text resize requirement and 1.4.10 Reflow w3c/wcag#574, by @detlevhfischer.
-
-
18 issues closed.
-
Example page lacks images Images for C37 w3c/wcag#601.
-
missing opening parenthesis on F73 w3c/wcag#282.
-
Small editorial issue with "new" note w3c/wcag#561.
-
Missing matching </div> w3c/wcag#580.
-
SC 1.4.11 contrast on hover included or not w3c/wcag#400.
-
"Notes" not present in Understanding docs w3c/wcag#571.
-
Technique C7 in WCAG 21 is missing the css code example w3c/wcag#566.
-
Uniform look for sub-headings (Grouping of Techniques) w3c/wcag#578.
-
1.4.3 Resource is not exist w3c/wcag#476.
-
-
39 issues received 146 new comments.
-
1.4.13 Content on Hover or Focus - hoverable requirement, clarification of point "persistent" w3c/wcag#582 (15 comments by @alastc, @detlevhfischer, @jake-abma, @mbgower, @mraccess77, @steverep)
-
Clarification on 2.5.3 Label in Name interpretation w3c/wcag#592 (13 comments by @alastc, @awkawk, @mbgower, @mraccess77)
-
Does SC 1.4.11 require comparing focused and non-focused states w3c/wcag#541 (10 comments by @alastc, @mbgower, @mraccess77, @patrickhlauke)
-
Scoping of 2.5.3 Label in Name w3c/wcag#591 (10 comments by @alastc, @detlevhfischer, @KimPatch, @mbgower, @mraccess77)
-
Non-sRGB color spaces, outdated sRGB threshold, and other issues in the "relative luminance" definition w3c/wcag#360 (10 comments by @alastc, @awkawk, @svgeesus)
-
Understanding Label in Name w3c/wcag#352 (10 comments by @alastc, @awkawk, @detlevhfischer, @patrickhlauke)
-
Exception for use of symbols as visible label in regard to 2.5.3 Label in Name w3c/wcag#598 (9 comments by @alastc, @mbgower, @mraccess77)
-
Need links to Understanding docs for guidelines w3c/wcag#595 (7 comments by @awkawk, @michael-n-cooper, @mmeller75, @patrickhlauke)
-
Clarify if modal dialog on page load is a failure of SC 3.2.1 + 3.2.5 w3c/wcag#538 (5 comments by @alastc, @detlevhfischer, @JamesCatt)
-
Do the biggest sites fail Success Criterion 2.1.4 (Character Key Shortcuts)? w3c/wcag#597 (4 comments by @alastc, @awkawk, @simevidas)
-
Is using the track element to provide audio descriptions sufficient? w3c/wcag#599 (4 comments by @awkawk, @johnfoliot, @mraccess77, @OwenEdwards)
-
Clarification on user interface components for 2.5.3 Label in name w3c/wcag#593 (4 comments by @alastc, @awkawk, @mbgower)
-
Tech H98 - autocomplete - should test also include check of wrong application of autocomplete? w3c/wcag#544 (3 comments by @alastc, @mraccess77)
-
WCAG 2.1 Understanding 2.3.1 - missing/vague dimension definitions w3c/wcag#585 (3 comments by @alastc, @awkawk)
-
Technique C7 in WCAG 21 is missing the css code example w3c/wcag#566 (2 comments by @alastc, @michael-n-cooper)
-
Understanding SC 1.4.11 Active User Interface Components button examples text contrast w3c/wcag#551 (2 comments by @alastc, @detlevhfischer)
-
Misleading info in "Understanding 2.4.4: Link Purpose (In Context)" w3c/wcag#581 (2 comments by @awkawk, @mraccess77)
-
Minor editorial issue (duplicate content) in Understanding 3.2.1 w3c/wcag#587 (1 comment by @alastc)
-
Proposal for new WCAG 2.2 SC 'States discernible' (a more limited aspect of affordance) w3c/wcag#559 (1 comment by @alastc)
-
-
10 pull requests opened.
-
Update content-on-hover-or-focus.html w3c/wcag#603, by @mbgower.
-
Cleanup of reflow techniques. w3c/wcag#600, by @alastc.
-
Removing F52 from on-focus w3c/wcag#590, by @alastc.
-
Update for issue 588 w3c/wcag#589, by @alastc.
-
Fixed invalid HTML example w3c/wcag#588, by @whoisak.
-
Adding pre tags for C7 w3c/wcag#586, by @alastc.
-
Tech failure unmodifiable single key shortcut w3c/wcag#584, by @detlevhfischer.
-
Technique - Two color focus indicator w3c/wcag#583, by @alastc.
-
Technique - Boundary contrast w3c/wcag#576, by @alastc.
-
Fix typos in 'The relation of Reflow to... Resize Text' w3c/wcag#575, by @mitchellevan.
-
-
10 pull requests merged.
-
Tech visible labels match names w3c/wcag#455.
-
Fix typos in 'The relation of Reflow to... Resize Text' w3c/wcag#575.
-
Update for issue 588 w3c/wcag#589.
-
Adding pre tags for C7 w3c/wcag#586.
-
Non-text contrast updates w3c/wcag#550.
-
Technique and example for reducing motion sc.2.3.3 w3c/wcag#556.
-
Updating accname link references. w3c/wcag#555.
-
updated anchors and supplied new link targets w3c/wcag#489.
-
Changes to H91 to add HTML5 changes w3c/wcag#179.
-
-
4 pull requests closed.
-
Fix format of w3c.json contact and add repo-type w3c/wcag#564.
-
updates in response to MBgower comments w3c/wcag#565.
-
Fixed invalid HTML example w3c/wcag#588.
-
Alternative method of explaining focus states. w3c/wcag#557.
-
-
16 pull requests received 51 new comments.
-
Non-text contrast updates w3c/wcag#550 (24 comments by @alastc, @awkawk, @jared-w-smith, @mraccess77)
-
Technique - Boundary contrast w3c/wcag#576 (5 comments by @alastc, @detlevhfischer, @jake-abma, @rachaelbradley)
-
Technique and example for reducing motion sc.2.3.3 w3c/wcag#556 (4 comments by @alastc, @jake-abma, @nschonni)
-
Fix typos in 'The relation of Reflow to... Resize Text' w3c/wcag#575 (3 comments by @alastc, @mitchellevan, @mraccess77)
-
Removed G139 from Situation B techniques for Status Messages Understanding doc w3c/wcag#568 (1 comment by @awkawk)
-
w3c/wcag-act
-
9 issues opened.
-
replace "failure condition" w3c/wcag-act#327, by @nitedog.
-
Look at using RDF for the ACT Rules Format w3c/wcag-act#324, by @WilcoFiers.
-
Cleanup balance between WCAG 2.0 and WCAG 2.1 w3c/wcag-act#323, by @moekraft.
-
Composed rule applicability not just a UNION w3c/wcag-act#321, by @WilcoFiers.
-
Add example for composed rules using other composed rules w3c/wcag-act#320, by @WilcoFiers.
-
Common aspects doc needs an abstract and introduction w3c/wcag-act#318, by @WilcoFiers.
-
Add definition for Accessibility Requirements document. w3c/wcag-act#317, by @moekraft.
-
Use consistent case and styling for outcomes: failed, passed, inapplicable w3c/wcag-act#316, by @moekraft.
-
Add links to Outcome definition w3c/wcag-act#315, by @moekraft.
-
-
5 issues closed.
-
Create introduction to "What is an ACT rule?" in the spec w3c/wcag-act#292.
-
Recent use cases w3c/wcag-act#301.
-
Consider restricting requirement mapping w3c/wcag-act#290.
-
Consider if composite rules can use results of other composite rules w3c/wcag-act#289.
-
Normative or Informative w3c/wcag-act#282.
-
-
8 issues received 9 new comments.
-
4 pull requests opened.
-
updated Abstract and Introduction w3c/wcag-act#326, by @nitedog.
-
revising document structure w3c/wcag-act#325, by @nitedog.
-
Updates for CR w3c/wcag-act#322, by @WilcoFiers.
-
Edits to allow composite-composite rules. w3c/wcag-act#319, by @maryjom.
-
-
4 pull requests merged.
-
revising document structure w3c/wcag-act#325.
-
What is act rule w3c/wcag-act#314.
-
Edits to allow composite-composite rules. w3c/wcag-act#319.
-
Accessibility requirements mapping rewrite w3c/wcag-act#313.
-
-
3 pull requests closed.
-
Proposal of RDF schema for ACT w3c/wcag-act#307.
-
Accessibility References w3c/wcag-act#295.
-
Proposal: new accessibility requirements mapping w3c/wcag-act#306.
-
-
7 pull requests received 153 new comments.
-
Updates for CR w3c/wcag-act#322 (88 comments by @annethyme, @maryjom, @moekraft, @nitedog, @WilcoFiers)
-
updated Abstract and Introduction w3c/wcag-act#326 (21 comments by @annethyme, @maryjom, @moekraft, @nitedog, @tbostic32)
-
Accessibility requirements mapping rewrite w3c/wcag-act#313 (19 comments by @annethyme, @moekraft, @WilcoFiers)
-
Edits to allow composite-composite rules. w3c/wcag-act#319 (13 comments by @annethyme, @maryjom, @WilcoFiers)
-
w3c/coga
-
2 pull requests opened.
-
Lisa working on janinas resucture w3c/coga#85, by @lseeman.
-
Separate tables w3c/coga#84, by @ruoxiran.
-
-
2 pull requests merged.
-
Lisa working on janinas resucture w3c/coga#85.
-
Separate tables w3c/coga#84.
-
-
1 pull request received 1 new comment.
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
2 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Lisa working on janinas resucture w3c/coga#85, by @lseeman.
-
Separate tables w3c/coga#84, by @ruoxiran.
-
-
2 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Lisa working on janinas resucture w3c/coga#85.
-
Separate tables w3c/coga#84.
-
-
1 pull request in the Cognitive and Learning Disabilities Accessibility Task Force received 1 new comment.