Accessibility Guidelines Working Group - Activity in 2018
No matches.
TR publications
-
2 documents published.
-
Cognitive Accessibility Roadmap and Gap Analysis published as a Working Draft. History of Cognitive Accessibility Roadmap and Gap Analysis
-
Making Content Usable for People with Cognitive and Learning Disabilities published as a First Public Working Draft. History of Making Content Usable for People with Cognitive and Learning Disabilities
-
Participants
-
1 participant joined.
-
Keyonda Smith (W3C Invited Experts) joined.
-
GitHub
w3c/wcag
-
12 issues opened.
-
"Notes" not present in Understanding docs w3c/wcag#571, by @jake-abma.
-
"examples" fail 1.4.1 Use of Color in WCAG 2.1 document w3c/wcag#570, by @jake-abma.
-
Bug: In understanding docs the SC defintitions are missing w3c/wcag#569, by @jake-abma.
-
Technique C7 in WCAG 21 is missing the css code example w3c/wcag#566, by @DavidMacDonald.
-
Link in 2.1 failing F73 w3c/wcag#562, by @alastc.
-
Small editorial issue with "new" note w3c/wcag#561, by @jake-abma.
-
Problems with WCAG 2.0 Flash Definition w3c/wcag#553, by @dd8.
-
Minor issue: duplicate h2 on understanding landing page w3c/wcag#548, by @tasnook.
-
Technique proposal - Issue 296 - Reminder w3c/wcag#547, by @KerstinProbiesch.
-
-
3 issues closed.
-
"examples" fail 1.4.1 Use of Color in WCAG 2.1 document w3c/wcag#570.
-
Minor issue: duplicate h2 on understanding landing page w3c/wcag#548.
-
-
14 issues received 40 new comments.
-
Does SC 1.4.11 require comparing focused and non-focused states w3c/wcag#541 (13 comments by @alastc, @detlevhfischer, @jake-abma, @johnfoliot, @mbgower, @patrickhlauke)
-
Proposal for new WCAG 2.2 SC 'States discernible' (a more limited aspect of affordance) w3c/wcag#559 (12 comments by @alastc, @awkawk, @detlevhfischer, @gianwild, @mbgower, @mraccess77)
-
Understanding docs and Technique docs are not identified at non-normative w3c/wcag#508 (2 comments by @alastc, @mbgower)
-
"examples" fail 1.4.1 Use of Color in WCAG 2.1 document w3c/wcag#570 (1 comment by @michael-n-cooper)
-
SC 1.3.5 Technique "Use type attribute on fields in simple login forms"? w3c/wcag#504 (1 comment by @alastc)
-
Understanding SC 1.4.11 Active User Interface Components button examples text contrast w3c/wcag#551 (1 comment by @alastc)
-
-
15 pull requests opened.
-
updates in response to MBgower comments w3c/wcag#565, by @awkawk.
-
Fix format of w3c.json contact and add repo-type w3c/wcag#564, by @dontcallmedom.
-
bunch of editorial changes w3c/wcag#563, by @awkawk.
-
Updating hrefs for new techniques in the changelog w3c/wcag#560, by @alastc.
-
Tech icon contrast: editorial edits and some non-editorial w3c/wcag#558, by @awkawk.
-
Alternative method of explaining focus states. w3c/wcag#557, by @alastc.
-
Technique and example for reducing motion sc.2.3.3 w3c/wcag#556, by @anevins12.
-
Updating accname link references. w3c/wcag#555, by @alastc.
-
Removing duplicate TOC H2 in understanding index w3c/wcag#554, by @alastc.
-
Non-text contrast updates w3c/wcag#550, by @alastc.
-
fix: Move data-include-replace to TOC element w3c/wcag#549, by @nschonni.
-
Technique - icon contrast w3c/wcag#546, by @alastc.
-
Tech failure orientation lock w3c/wcag#545, by @awkawk.
-
3 pull requests merged.
-
Technique - icon contrast w3c/wcag#546.
-
-
5 pull requests closed.
-
bunch of editorial changes w3c/wcag#563.
-
Updating hrefs for new techniques in the changelog w3c/wcag#560.
-
fix: Move data-include-replace to TOC element w3c/wcag#549.
-
Removing duplicate TOC H2 in understanding index w3c/wcag#554.
-
-
15 pull requests received 70 new comments.
-
Non-text contrast updates w3c/wcag#550 (22 comments by @alastc, @allanj-uaag, @awkawk, @jared-w-smith, @mraccess77)
-
Tech failure orientation lock w3c/wcag#545 (9 comments by @alastc, @awkawk, @brooksienoodlesoup, @detlevhfischer, @jake-abma, @mbgower)
-
Technique - setting role of img on icon fonts w3c/wcag#531 (8 comments by @alastc, @allanj-uaag, @detlevhfischer, @jake-abma, @marcjohlic, @mraccess77)
-
Technique - icon contrast w3c/wcag#546 (7 comments by @alastc, @allanj-uaag, @detlevhfischer, @mbgower, @michael-n-cooper)
-
Tech hover focus hoverable w3c/wcag#543 (5 comments by @alastc, @detlevhfischer, @jake-abma, @mraccess77)
-
Removed G139 from Situation B techniques for Status Messages Understanding doc w3c/wcag#568 (2 comments by @mbgower, @michael-n-cooper)
-
Alternative method of explaining focus states. w3c/wcag#557 (2 comments by @alastc, @detlevhfischer)
-
List skip-link and landmark techniques as related to each other w3c/wcag#552 (1 comment by @lkmorlan)
-
List skip-link and landmark techniques as related to each other w3c/wcag#319 (1 comment by @michael-n-cooper)
-
w3c/wcag-act
-
3 issues closed.
-
Add changelog and issues list to structure section w3c/wcag-act#286.
-
-
5 issues received 8 new comments.
-
Proposal to (slightly) rearange the spec outline w3c/wcag-act#284 (3 comments by @moekraft, @rdeltour)
-
Mapping "Background" and "Assumptions" sections from Auto-WCAG to ACT Rules Format w3c/wcag-act#293 (1 comment by @moekraft)
-
-
4 pull requests opened.
-
What is act rule w3c/wcag-act#314, by @maryjom.
-
Accessibility requirements mapping rewrite w3c/wcag-act#313, by @WilcoFiers.
-
Updating CSS Biblio Tag w3c/wcag-act#312, by @moekraft.
-
Merging PR 304, 305 & 308 w3c/wcag-act#311, by @moekraft.
-
-
5 pull requests merged.
-
Updating CSS Biblio Tag w3c/wcag-act#312.
-
Merging PR 304, 305 & 308 w3c/wcag-act#311.
-
Added Acknowledgments section w3c/wcag-act#308.
-
"Optional items" section + renaming "Assumptions" w3c/wcag-act#305.
-
Remove formal syntax w3c/wcag-act#304.
-
-
1 pull request closed.
-
What is an ACT rule - Issue 292 w3c/wcag-act#310.
-
-
1 pull request reopened.
-
Proposal: new accessibility requirements mapping w3c/wcag-act#306, by @moekraft.
-
-
5 pull requests received 8 new comments.
Participants
-
2 participants joined.
-
Steve Lee (W3C) joined.
-
Makoto Ueki (W3C Invited Experts) joined.
-
-
2 participants left.
-
Steve Lee (W3C) left.
-
John Kirkwood (W3C Invited Experts) left.
-
GitHub
w3c/wcag
-
9 issues opened.
-
Does SC 1.4.11 require comparing focused and non-focused states w3c/wcag#541, by @mraccess77.
-
Issues for SC 1.3.6 Identify Purpose w3c/wcag#539, by @jake-abma.
-
Some wording questions for 1.3.5: Identify Input Purpose w3c/wcag#537, by @jake-abma.
-
Is it the purpose or not the purpose? w3c/wcag#536, by @jake-abma.
-
5 issues closed.
-
typo in third note on Conformance Requirement 2 w3c/wcag#524.
-
flexbox branch still present w3c/wcag#498.
-
Bad link in G158 w3c/wcag#523.
-
-
16 issues received 51 new comments.
-
1.4.11 seems to include the ACTIVE state of links and buttons. w3c/wcag#517 (9 comments by @alastc, @awkawk, @mbgower, @mraccess77, @patrickhlauke)
-
New Technique draft "Making content on focus or hover hoverable, dissmissible and permanent" w3c/wcag#529 (8 comments by @alastc, @detlevhfischer, @mraccess77)
-
Tech H98 - autocomplete - should test also include check of wrong application of autocomplete? w3c/wcag#544 (6 comments by @alastc, @detlevhfischer, @johnfoliot, @mraccess77)
-
Does SC 1.4.11 require comparing focused and non-focused states w3c/wcag#541 (5 comments by @alastc, @detlevhfischer, @patrickhlauke)
-
4.1.1 Parsing - Duplicate attributes with no user impact cause a conformance failure w3c/wcag#542 (3 comments by @alastc, @dd8)
-
WCAG F85: Clarify guidance about where the focus should go when the modal dialog is closed w3c/wcag#518 (3 comments by @awkawk, @iamrafan, @jnurthen)
-
Can browser dev tools > device toggle be used to test SC 1.4.10 Reflow w3c/wcag#520 (1 comment by @alastc)
-
-
7 pull requests opened.
-
Tech hover focus hoverable w3c/wcag#543, by @detlevhfischer.
-
First draft technique changelog for review. w3c/wcag#535, by @alastc.
-
Removed the link. w3c/wcag#534, by @alastc.
-
Adding a basic css file for previewing techniques/understanding w3c/wcag#533, by @alastc.
-
Tech - Using type attribute for purpose w3c/wcag#532, by @alastc.
-
Technique - setting role of img on icon fonts w3c/wcag#531, by @alastc.
-
changes to address #517 w3c/wcag#530, by @awkawk.
-
-
18 pull requests merged.
-
Tech failure name not label text w3c/wcag#457.
-
Tech failure content hover focus not hoverable w3c/wcag#506.
-
Tech fitting labels inputs viewport w3c/wcag#509.
-
First draft technique changelog for review. w3c/wcag#535.
-
Example css sticky w3c/wcag#500.
-
changes to address #517 w3c/wcag#530.
-
Removed the link. w3c/wcag#534.
-
Example fitting images viewport w3c/wcag#495.
-
Tech fitting images viewport w3c/wcag#494.
-
Tech spacing override w3c/wcag#386.
-
Tech media queries sticky w3c/wcag#389.
-
prevent breaking grid 1fr to minmax(0, 1fr) w3c/wcag#497.
-
prevent breaking grid 1fr to minmax(0, 1fr) w3c/wcag#496.
-
em to rem for consistency w3c/wcag#514.
-
em to rem for consistency w3c/wcag#513.
-
em to rem for consistency w3c/wcag#512.
-
em to rem for consistency w3c/wcag#511.
-
-
5 pull requests closed.
-
Example css fitting inputs w3c/wcag#510.
-
Tech ensuring single pointer deltev w3c/wcag#454.
-
Tech - Using type attribute for purpose w3c/wcag#532.
-
Tech failure hover focus content not dismissable w3c/wcag#450.
-
Pointer gestures amendment w3c/wcag#379.
-
-
19 pull requests received 83 new comments.
-
Tech - Using type attribute for purpose w3c/wcag#532 (42 comments by @alastc, @awkawk, @detlevhfischer, @johnfoliot, @mraccess77)
-
Adding a basic css file for previewing techniques/understanding w3c/wcag#533 (2 comments by @alastc)
-
w3c/wcag-act
-
3 issues opened.
-
Editorial: Make clear the ACT Rule Format list minimum requirements for ACT Rules w3c/wcag-act#302, by @annethyme.
-
Recent use cases w3c/wcag-act#301, by @WilcoFiers.
-
Clarify that test subjects have only one outcome w3c/wcag-act#299, by @WilcoFiers.
-
-
2 issues closed.
-
"ACT Rules" or "ACT rules"? w3c/wcag-act#278.
-
7. Accessibility Requirements - Improvement suggestion w3c/wcag-act#231.
-
-
9 issues received 17 new comments.
-
Mapping "Background" and "Assumptions" sections from Auto-WCAG to ACT Rules Format w3c/wcag-act#293 (3 comments by @annethyme, @skotkjerra)
-
10.1. Applicability for Atomic Rules: Remove the "formal syntax MAY be used" w3c/wcag-act#294 (1 comment by @moekraft)
-
9 pull requests opened.
-
What is an ACT rule - Issue 292 w3c/wcag-act#310, by @maryjom.
-
Create new editor's draft 11-28-18 w3c/wcag-act#309, by @moekraft.
-
Added Acknowledgments section w3c/wcag-act#308, by @nitedog.
-
Proposal of RDF schema for ACT w3c/wcag-act#307, by @josehilera.
-
Proposal: new accessibility requirements mapping w3c/wcag-act#306, by @annethyme.
-
"Optional items" section + renaming "Assumptions" w3c/wcag-act#305, by @annethyme.
-
Remove formal syntax w3c/wcag-act#304, by @moekraft.
-
Consistent use of ACT Rules w3c/wcag-act#303, by @moekraft.
-
Fix a typo w3c/wcag-act#300, by @mfairchild365.
-
-
4 pull requests merged.
-
Create new editor's draft 11-28-18 w3c/wcag-act#309.
-
Consistent use of ACT Rules w3c/wcag-act#303.
-
Typos and minor editorial tweaks w3c/wcag-act#287.
-
Fix a typo w3c/wcag-act#300.
-
-
9 pull requests received 38 new comments.
-
"Optional items" section + renaming "Assumptions" w3c/wcag-act#305 (17 comments by @annethyme, @nitedog, @skotkjerra, @WilcoFiers)
-
Participants
-
1 participant joined.
-
Juli-Ann Rowsell (W3C Invited Experts) joined.
-
-
5 participants left.
-
Makoto Ueki (W3C Invited Experts) left.
-
Christophe Strobbe (W3C Invited Experts) left.
-
Adam Solomon (W3C Invited Experts) left.
-
Marla Runyan (W3C Invited Experts) left.
-
Chris Loiselle (Oracle Corporation) left.
-
-
1 organization left.
-
Interactive Accessibility left.
-
GitHub
w3c/wcag
-
19 issues opened.
-
fix CSS padding on understanding pages w3c/wcag#528, by @Veyfeyken.
-
Advisory techniques vs Recommended techniques w3c/wcag#527, by @StefanSTS.
-
Outdated tabindex technique w3c/wcag#526, by @alastc.
-
typo in third note on Conformance Requirement 2 w3c/wcag#524, by @DavidMacDonald.
-
Bad link in G158 w3c/wcag#523, by @awkawk.
-
Decorative vs Meaningful images w3c/wcag#521, by @iamrafan.
-
Clarify Understanding for SC 1.1.1 Non-Text Content w3c/wcag#519, by @mraccess77.
-
Broken Link in F89 w3c/wcag#505, by @KerstinProbiesch.
-
SC 1.1.1 Situation D - ARIA 6 & ARIA 10 w3c/wcag#503, by @ghost.
-
Example link within example code block clear enough? w3c/wcag#499, by @jake-abma.
-
flexbox branch still present w3c/wcag#498, by @jake-abma.
-
Document outline not correct for techniques w3c/wcag#493, by @jake-abma.
-
use of color example in Non-Text Contrast w3c/wcag#492, by @mbgower.
-
-
6 issues closed.
-
Stylish had analytics and data collection implemented w3c/wcag#478.
-
Document outline not correct for techniques w3c/wcag#493.
-
Technique SCR29 needs updating w3c/wcag#468.
-
-
23 issues received 86 new comments.
-
Outdated tabindex technique w3c/wcag#526 (12 comments by @alastc, @detlevhfischer, @johnfoliot, @patrickhlauke, @Ryladog)
-
2.5.1 Pointer Gestures: clarity on path-based language in Understanding document w3c/wcag#522 (6 comments by @detlevhfischer, @mbgower)
-
SC 1.3.5 Technique "Use type attribute on fields in simple login forms"? w3c/wcag#504 (6 comments by @detlevhfischer, @mraccess77, @patrickhlauke)
-
Non-sRGB color spaces, outdated sRGB threshold, and other issues in the "relative luminance" definition w3c/wcag#360 (5 comments by @alastc, @patrickhlauke, @svgeesus)
-
WCAG F85: Clarify guidance about where the focus should go when the modal dialog is closed w3c/wcag#518 (5 comments by @awkawk, @jnurthen)
-
Minor link errors in Understanding 1.4.12 Text spacing w3c/wcag#443 (3 comments by @alastc, @michael-n-cooper)
-
1.4.11 seems to include the ACTIVE state of links and buttons. w3c/wcag#517 (2 comments by @awkawk, @mraccess77)
-
Should the failure to implement Sufficient Technique in the right way be treated as a WCAG failure w3c/wcag#318 (2 comments by @alastc, @iamrafan)
-
Failure technique F87 contradicts the Accessible name and desc algorithm w3c/wcag#433 (1 comment by @awkawk)
-
Include details on user interface components in 1.4.3 & 1.4.6 Understanding w3c/wcag#481 (1 comment by @awkawk)
-
16 pull requests opened.
-
fix: Close paragraph for validation w3c/wcag#516, by @nschonni.
-
Fix: Correct broken link w3c/wcag#515, by @raven-wills.
-
em to rem for consistency w3c/wcag#514, by @jake-abma.
-
em to rem for consistency w3c/wcag#513, by @jake-abma.
-
em to rem for consistency w3c/wcag#512, by @jake-abma.
-
em to rem for consistency w3c/wcag#511, by @jake-abma.
-
Example css fitting inputs w3c/wcag#510, by @jake-abma.
-
Tech fitting labels inputs viewport w3c/wcag#509, by @jake-abma.
-
Tech failure content hover focus not hoverable w3c/wcag#506, by @detlevhfischer.
-
Added video style to additional.css w3c/wcag#502, by @alastc.
-
Additional paragraph about compliance standards. w3c/wcag#501, by @alastc.
-
Example css sticky w3c/wcag#500, by @jake-abma.
-
prevent breaking grid 1fr to minmax(0, 1fr) w3c/wcag#497, by @jake-abma.
-
prevent breaking grid 1fr to minmax(0, 1fr) w3c/wcag#496, by @jake-abma.
-
Example fitting images viewport w3c/wcag#495, by @jake-abma.
-
Tech fitting images viewport w3c/wcag#494, by @jake-abma.
-
-
8 pull requests merged.
-
fix: Close paragraph for validation w3c/wcag#516.
-
Technique: Reflow for long URLs w3c/wcag#486.
-
Updating the stylish / stylus reference. w3c/wcag#487.
-
Added video style to additional.css w3c/wcag#502.
-
Example aria role log w3c/wcag#436.
-
Tech using role log w3c/wcag#435.
-
editorial changes to existing 1.4.11 understanding doc w3c/wcag#491.
-
-
1 pull request closed.
-
EXAMPLE: ACT Rules as techniques w3c/wcag#381.
-
-
14 pull requests received 45 new comments.
-
Technique: Reflow for long URLs w3c/wcag#486 (10 comments by @alastc, @awkawk, @KerstinProbiesch, @mraccess77, @WayneEDick)
-
Tech failure name not label text w3c/wcag#457 (7 comments by @alastc, @goodwitch, @jake-abma, @mbgower, @mraccess77, @patrickhlauke, @Ryladog)
-
editorial changes to existing 1.4.11 understanding doc w3c/wcag#491 (4 comments by @alastc, @awkawk, @mbgower)
-
Tech failure hover focus content not dismissable w3c/wcag#450 (2 comments by @alastc, @detlevhfischer)
-
w3c/wcag-act
-
16 issues opened.
-
Add examples to Applicability w3c/wcag-act#298, by @annethyme.
-
Add a test case example w3c/wcag-act#297, by @WilcoFiers.
-
Add an example to Accessibility Support w3c/wcag-act#296, by @WilcoFiers.
-
10.1. Applicability for Atomic Rules: Remove the "formal syntax MAY be used" w3c/wcag-act#294, by @annethyme.
-
Mapping "Background" and "Assumptions" sections from Auto-WCAG to ACT Rules Format w3c/wcag-act#293, by @annethyme.
-
Create introduction to "What is an ACT rule?" in the spec w3c/wcag-act#292, by @annethyme.
-
Write an explainer for the spec w3c/wcag-act#291, by @rdeltour.
-
Consider restricting requirement mapping w3c/wcag-act#290, by @WilcoFiers.
-
Consider if composite rules can use results of other composite rules w3c/wcag-act#289, by @WilcoFiers.
-
Add changelog and issues list to structure section w3c/wcag-act#286, by @WilcoFiers.
-
Add an explanation about why to include the outcome definition w3c/wcag-act#285, by @WilcoFiers.
-
Proposal to (slightly) rearange the spec outline w3c/wcag-act#284, by @rdeltour.
-
Normative or Informative w3c/wcag-act#282, by @goodwitch.
-
Scope sections states ACT rules should not be used for conformance w3c/wcag-act#281, by @moekraft.
-
Mark all Informative sections as such w3c/wcag-act#280, by @moekraft.
-
-
21 issues closed.
-
Rule Identifier: Example needed (Shadi) w3c/wcag-act#248.
-
Test cases for composed rules w3c/wcag-act#251.
-
Examples need to be identified accessibly w3c/wcag-act#187.
-
Outcomes of atomic tests w3c/wcag-act#235.
-
15.2. Accuracy Benchmarking - Update definition w3c/wcag-act#236.
-
Section “13. Accessibility Support” unclear w3c/wcag-act#221.
-
ACT i18n checks w3c/wcag-act#226.
-
"Failed" / "Passed" or "Fail"/"Pass"? w3c/wcag-act#279.
-
Mark all Informative sections as such w3c/wcag-act#280.
-
Scope sections states ACT rules should not be used for conformance w3c/wcag-act#281.
-
Need a definition of Test Target w3c/wcag-act#271.
-
Clear split between requirements for rule authors vs. rule implementers w3c/wcag-act#272.
-
Accessibility Requirements: Updates requested (Shadi) w3c/wcag-act#250.
-
16. Rule Aggregation - Add Requirement w3c/wcag-act#252.
-
Require Rule ID's in Atomic Rule List w3c/wcag-act#261.
-
Clarify the output format definition w3c/wcag-act#162.
-
Clarify the definition of Rule Aggregation w3c/wcag-act#165.
-
ACT security checks w3c/wcag-act#225.
-
Test subject is inconsistent with EARL language w3c/wcag-act#275.
-
-
9 issues received 20 new comments.
-
Test subject is inconsistent with EARL language w3c/wcag-act#275 (3 comments by @annethyme, @kasperisager, @WilcoFiers)
-
3 pull requests opened.
-
Accessibility References w3c/wcag-act#295, by @nitedog.
-
Typos and minor editorial tweaks w3c/wcag-act#287, by @rdeltour.
-
CR Proposal w3c/wcag-act#283, by @WilcoFiers.
-
-
1 pull request merged.
-
CR Proposal w3c/wcag-act#283.
-
-
2 pull requests closed.
-
Update accessibility requirements section w3c/wcag-act#276.
-
Update rule accuracy section w3c/wcag-act#277.
-
-
4 pull requests received 69 new comments.
-
CR Proposal w3c/wcag-act#283 (53 comments by @kengdoj, @maryjom, @nitedog, @rdeltour, @tbostic32, @WilcoFiers)
-
w3c/coga
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Lisas changes such as easyread abstract w3c/coga#83.
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
1 issue in the Cognitive and Learning Disabilities Accessibility Task Force received 1 new comment.
-
1 pull request merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Lisas changes such as easyread abstract w3c/coga#83.
-
Participants
-
2 organizations joined.
-
AKEA Web Solutions, LLC joined.
-
AccessibilityOz joined.
-
GitHub
w3c/wcag
-
11 issues opened.
-
Background/foreground techniques update or remove C23, 25 w3c/wcag#490, by @DavidMacDonald.
-
Add META tag for viewport at examples w3c/wcag#480, by @jake-abma.
-
Stylish had analytics and data collection implemented w3c/wcag#478, by @DavidMacDonald.
-
1.4.3 Resource is not exist w3c/wcag#476, by @jidaikobo-shibata.
-
1.4.3 Broken Link (CSS Values) w3c/wcag#475, by @jidaikobo-shibata.
-
typo in non-text contrast understanding w3c/wcag#472, by @DavidMacDonald.
-
Typo in understanding for Not text contrast w3c/wcag#471, by @DavidMacDonald.
-
Techniques for WCAG 2.1 does not itself follow G141 w3c/wcag#470, by @svgeesus.
-
Contrast ratio for text that is part of inactive UI component w3c/wcag#469, by @iamrafan.
-
-
11 issues closed.
-
Grammatical error in "Understandable"? w3c/wcag#460.
-
WCAG 2.1 Understanding doc does not have SC numbers w3c/wcag#370.
-
1.4.3 Broken Link (CSS Values) w3c/wcag#475.
-
No HTML Landmarks techniques present, only ARIA w3c/wcag#422.
-
Techniques for WCAG 2.1 does not itself follow G141 w3c/wcag#470.
-
typo in non-text contrast understanding w3c/wcag#472.
-
Typo in understanding for Not text contrast w3c/wcag#471.
-
19 issues received 61 new comments.
-
Stylish had analytics and data collection implemented w3c/wcag#478 (14 comments by @alastc, @allanj-uaag, @awkawk, @DavidMacDonald, @detlevhfischer, @jake-abma, @mraccess77)
-
Include details on user interface components in 1.4.3 & 1.4.6 Understanding w3c/wcag#481 (6 comments by @awkawk, @mbgower)
-
Non-sRGB color spaces, outdated sRGB threshold, and other issues in the "relative luminance" definition w3c/wcag#360 (5 comments by @alastc, @svgeesus)
-
Grammatical error in "Understandable"? w3c/wcag#460 (4 comments by @awkawk, @bruce-usab, @johnfoliot)
-
Reflow understanding - Video size & location w3c/wcag#445 (4 comments by @alastc, @shawna-slh, @yatil)
-
Typo in 4. Robust: "...can be interpreted by by a wide variety..." w3c/wcag#488 (3 comments by @awkawk, @JamesDonnelly)
-
Background/foreground techniques update or remove C23, 25 w3c/wcag#490 (3 comments by @jared-w-smith, @mraccess77, @Ryladog)
-
Contrast ratio for text that is part of inactive UI component w3c/wcag#469 (3 comments by @alastc, @awkawk, @iamrafan)
-
Failure technique F87 contradicts the Accessible name and desc algorithm w3c/wcag#433 (2 comments by @alastc, @lauracarlson)
-
Techniques for WCAG 2.1 does not itself follow G141 w3c/wcag#470 (2 comments by @awkawk, @michael-n-cooper)
-
Understanding 1.3.5 - relative link in the SC boxout at the top isn't working w3c/wcag#442 (1 comment by @michael-n-cooper)
-
errata? 1.4.11 does not exempt logos, like 1.4.3 exempts logotypes w3c/wcag#447 (1 comment by @alastc)
-
-
12 pull requests opened.
-
editorial changes to existing 1.4.11 understanding doc w3c/wcag#491, by @mbgower.
-
updated anchors and supplied new link targets w3c/wcag#489, by @mbgower.
-
Updating the stylish / stylus reference. w3c/wcag#487, by @alastc.
-
Technique: Reflow for long URLs w3c/wcag#486, by @alastc.
-
Scr29 example update w3c/wcag#485, by @awkawk.
-
Implemented mbgover' change suggestions. w3c/wcag#483, by @detlevhfischer.
-
Fix typo w3c/wcag#482, by @raven-wills.
-
Fix/meta viewport examples w3c/wcag#479, by @jake-abma.
-
Removed styling that doesn't get used. w3c/wcag#477, by @alastc.
-
reworking with AWK changes w3c/wcag#474, by @awkawk.
-
F87 - removing the with-AT clauses w3c/wcag#473, by @alastc.
-
-
12 pull requests merged.
-
Fix/meta viewport examples w3c/wcag#479.
-
F87 - removing the with-AT clauses w3c/wcag#473.
-
Scr29 example update w3c/wcag#485.
-
reworking with AWK changes w3c/wcag#474.
-
Fix typo w3c/wcag#482.
-
Removed styling that doesn't get used. w3c/wcag#477.
-
Tech autocomplete w3c/wcag#437.
-
Import understanding SC 1.4.13's images into repo w3c/wcag#446.
-
Technique - Failure of viewport units w3c/wcag#417.
-
Tech flexbox reflow w3c/wcag#388.
-
Tech media queries grid reflow w3c/wcag#387.
-
Removing the fixed-text examples w3c/wcag#385.
-
-
2 pull requests closed.
-
Implemented mbgover' change suggestions. w3c/wcag#483.
-
added mousedown complexities w3c/wcag#424.
-
-
17 pull requests received 74 new comments.
-
Tech media queries sticky w3c/wcag#389 (14 comments by @alastc, @jake-abma, @jgrieves, @lauracarlson, @patrickhlauke, @StommePoes, @WayneEDick)
-
Tech failure name not label text w3c/wcag#457 (10 comments by @awkawk, @brooksienoodlesoup, @detlevhfischer, @goodwitch, @jake-abma, @marcjohlic, @mraccess77)
-
editorial changes to existing 1.4.11 understanding doc w3c/wcag#491 (8 comments by @alastc, @awkawk, @mbgower)
-
Technique: Reflow for long URLs w3c/wcag#486 (7 comments by @alastc, @allanj-uaag, @detlevhfischer, @KerstinProbiesch)
-
F87 - removing the with-AT clauses w3c/wcag#473 (7 comments by @alastc, @awkawk, @detlevhfischer, @mraccess77)
-
Tech visible labels match names w3c/wcag#455 (6 comments by @alastc, @awkawk, @brooksienoodlesoup, @KimPatch, @mraccess77)
-
Updating the stylish / stylus reference. w3c/wcag#487 (4 comments by @alastc, @awkawk, @lauracarlson)
-
w3c/wcag-act
-
12 issues opened.
-
"Failed" / "Passed" or "Fail"/"Pass"? w3c/wcag-act#279, by @annethyme.
-
"ACT Rules" or "ACT rules"? w3c/wcag-act#278, by @annethyme.
-
Test subject is inconsistent with EARL language w3c/wcag-act#275, by @WilcoFiers.
-
Clear split between requirements for rule authors vs. rule implementers w3c/wcag-act#272, by @annethyme.
-
Need a definition of Test Target w3c/wcag-act#271, by @moekraft.
-
Failure techniques relationship to ACT Rules and conformance (Anne) w3c/wcag-act#268, by @maryjom.
-
Scrub document to ensure correct use of "should" and "may" (Anne) w3c/wcag-act#267, by @maryjom.
-
Doc references "#output-aggregation" uses different link text each time used w3c/wcag-act#266, by @maryjom.
-
Clarify definition of Aspect under Test needed w3c/wcag-act#264, by @moekraft.
-
Include Rule Identifiers and Rule Description in Atomic Rule List w3c/wcag-act#262, by @moekraft.
-
Require Rule ID's in Atomic Rule List w3c/wcag-act#261, by @kengdoj.
-
Aspects Under Tests - Editorial updates (Shadi) w3c/wcag-act#257, by @moekraft.
-
-
20 issues closed.
-
False negatives definition w3c/wcag-act#239.
-
3. ACT Rule Types - Clarify example w3c/wcag-act#230.
-
4. ACT Rule Structure - Improvement suggestion w3c/wcag-act#232.
-
Concern about stability of test target pointers w3c/wcag-act#220.
-
Clarify definition of Aspect under Test needed w3c/wcag-act#264.
-
Scrub document to ensure correct use of "should" and "may" (Anne) w3c/wcag-act#267.
-
Aspects Under Tests - Editorial updates (Shadi) w3c/wcag-act#257.
-
Structure of the text w3c/wcag-act#238.
-
11.2. Aggregation Expectations - Update example w3c/wcag-act#234.
-
Abstract: Editorial updates (Shadi) w3c/wcag-act#244.
-
Introduction: Editorial updates (Shadi) w3c/wcag-act#245.
-
Scope: Editorial updates (Shadi) w3c/wcag-act#246.
-
Include Rule Identifiers and Rule Description in Atomic Rule List w3c/wcag-act#262.
-
8.1. Common Aspects - Question w3c/wcag-act#233.
-
Review/replace term "aggregation definition" for composed rules w3c/wcag-act#241.
-
16. Rule Aggregation - Improve example w3c/wcag-act#237.
-
Composed or Composite rule? w3c/wcag-act#243.
-
-
1 issue reopened.
-
8.1. Common Aspects - Question w3c/wcag-act#233, by @maryjom.
-
-
26 issues received 48 new comments.
-
Clarify definition of Aspect under Test needed w3c/wcag-act#264 (6 comments by @annethyme, @moekraft, @nitedog, @rdeltour, @WilcoFiers)
-
List of features for exit critiera w3c/wcag-act#224 (4 comments by @annethyme, @nitedog, @tbostic32, @WilcoFiers)
-
Review/replace term "aggregation definition" for composed rules w3c/wcag-act#241 (3 comments by @cpandhi, @moekraft)
-
Scrub document to ensure correct use of "should" and "may" (Anne) w3c/wcag-act#267 (2 comments by @nitedog, @WilcoFiers)
-
Clear split between requirements for rule authors vs. rule implementers w3c/wcag-act#272 (1 comment by @annethyme)
-
Question on 4. Test Subject Types (Input) - like to see more than just html w3c/wcag-act#123 (1 comment by @WilcoFiers)
-
Include Rule Identifiers and Rule Description in Atomic Rule List w3c/wcag-act#262 (1 comment by @maryjom)
-
Failure techniques relationship to ACT Rules and conformance (Anne) w3c/wcag-act#268 (1 comment by @maryjom)
-
-
15 pull requests opened.
-
Update rule accuracy section w3c/wcag-act#277, by @WilcoFiers.
-
Update accessibility requirements section w3c/wcag-act#276, by @WilcoFiers.
-
Updates to Aspects under test w3c/wcag-act#274, by @moekraft.
-
Bunch of editorial edits w3c/wcag-act#273, by @WilcoFiers.
-
Shadi's updates to the Abstract section w3c/wcag-act#270, by @maryjom.
-
Shadi's edits to scope section w3c/wcag-act#269, by @maryjom.
-
Shadi's edits to the Introduction section w3c/wcag-act#265, by @maryjom.
-
Latest draft based off PR 242 & 247 w3c/wcag-act#263, by @moekraft.
-
Add archive date to link text w3c/wcag-act#260, by @moekraft.
-
Create archive version w3c/wcag-act#259, by @moekraft.
-
Add new WG Note w3c/wcag-act#258, by @moekraft.
-
Change composed rule to composite rule w3c/wcag-act#256, by @moekraft.
-
Demo PR for PR Preview w3c/wcag-act#255, by @rdeltour.
-
Fix the PR Preview config w3c/wcag-act#254, by @rdeltour.
-
test PR preview w3c/wcag-act#253, by @nitedog.
-
-
12 pull requests merged.
-
Bunch of editorial edits w3c/wcag-act#273.
-
Shadi's edits to scope section w3c/wcag-act#269.
-
Shadi's updates to the Abstract section w3c/wcag-act#270.
-
Shadi's edits to the Introduction section w3c/wcag-act#265.
-
Latest draft based off PR 242 & 247 w3c/wcag-act#263.
-
Get rid of "Test/Aggregation Definition" w3c/wcag-act#247.
-
Update "8. Aspects under Test" w3c/wcag-act#242.
-
Add archive date to link text w3c/wcag-act#260.
-
Create archive version w3c/wcag-act#259.
-
Add new WG Note w3c/wcag-act#258.
-
Change composed rule to composite rule w3c/wcag-act#256.
-
Fix the PR Preview config w3c/wcag-act#254.
-
-
3 pull requests closed.
-
Updates to Aspects under test w3c/wcag-act#274.
-
Demo PR for PR Preview w3c/wcag-act#255.
-
test PR preview w3c/wcag-act#253.
-
-
1 pull request reopened.
-
Demo PR for PR Preview w3c/wcag-act#255, by @nitedog.
-
-
7 pull requests received 53 new comments.
-
Update rule accuracy section w3c/wcag-act#277 (17 comments by @annethyme, @maryjom, @nitedog, @tbostic32)
-
Update accessibility requirements section w3c/wcag-act#276 (14 comments by @annethyme, @maryjom, @nitedog, @tbostic32)
-
Update "8. Aspects under Test" w3c/wcag-act#242 (11 comments by @annethyme, @maryjom, @moekraft, @nitedog, @tbostic32)
-
w3c/coga
-
1 pull request opened.
-
Lisas changes such as easyread abstract w3c/coga#83, by @lseeman.
-
-
1 pull request closed.
-
Fixed a few minor type-os and grammar w3c/coga#82.
-
-
2 pull requests received 2 new comments.
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
1 pull request opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Lisas changes such as easyread abstract w3c/coga#83, by @lseeman.
-
-
1 pull request closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Fixed a few minor type-os and grammar w3c/coga#82.
-
-
2 pull requests in the Cognitive and Learning Disabilities Accessibility Task Force received 2 new comments.
Participants
-
2 participants joined.
-
Jennifer Delisi (W3C Invited Experts) joined.
-
Thaddeus Cambron (W3C Invited Experts) joined.
-
-
1 organization left.
-
Apex CoVantage left.
-
GitHub
w3c/wcag
-
13 issues opened.
-
Technique SCR29 needs updating w3c/wcag#468, by @alastc.
-
Understanding 4.1.3 - wrong id reference in anchors w3c/wcag#465, by @audreymaniez.
-
Fix whitespace issues to match EditorConfig settings w3c/wcag#464, by @nschonni.
-
Grammatical error in "Robust" w3c/wcag#461, by @LJWatson.
-
Grammatical error in "Understandable"? w3c/wcag#460, by @LJWatson.
-
Duplicate content in ARIA Technique 19 w3c/wcag#452, by @plannero.
-
Html coding error in G83 and other new Technique pages w3c/wcag#451, by @plannero.
-
errata? 1.4.11 does not exempt logos, like 1.4.3 exempts logotypes w3c/wcag#447, by @cyns.
-
Reflow understanding - Video size & location w3c/wcag#445, by @alastc.
-
Image problem in Understanding 1.4.11 Non-text contrast w3c/wcag#444, by @plannero.
-
Minor link errors in Understanding 1.4.12 Text spacing w3c/wcag#443, by @plannero.
-
Success Criterion 1.3.5: Identify Input Purpose w3c/wcag#441, by @LaurenceRLewis.
-
-
13 issues closed.
-
Grammatical error in "Robust" w3c/wcag#461.
-
repeated "by" w3c/wcag#374.
-
H57 and H58 linkrot w3c/wcag#241.
-
Duplicate content in ARIA Technique 19 w3c/wcag#452.
-
Html coding error in G83 and other new Technique pages w3c/wcag#451.
-
Image problem in Understanding 1.4.11 Non-text contrast w3c/wcag#444.
-
Small typo for Note 5.2.2 Full pages w3c/wcag#413.
-
Is there a typo in 1.4.13? w3c/wcag#420.
-
Typo: signiicantly w3c/wcag#325.
-
Success Criterion 1.3.5: Identify Input Purpose w3c/wcag#441.
-
-
22 issues received 60 new comments.
-
Failure technique F87 contradicts the Accessible name and desc algorithm w3c/wcag#433 (14 comments by @alastc, @awkawk, @lauracarlson, @mraccess77, @WayneEDick, @Wildebrew)
-
Image problem in Understanding 1.4.11 Non-text contrast w3c/wcag#444 (7 comments by @alastc, @patrickhlauke, @plannero)
-
Reflow understanding - Video size & location w3c/wcag#445 (6 comments by @alastc, @awkawk, @michael-n-cooper, @WayneEDick, @yatil)
-
Re-write of sentence "It is critical" w3c/wcag#324 (5 comments by @alastc, @awkawk, @detlevhfischer, @lauracarlson)
-
SC 1.3.5 is not restricted to markup languages but SC 1.3.6 is w3c/wcag#425 (3 comments by @johnfoliot, @PhuongHoang1182)
-
Success Criterion 1.3.5: Identify Input Purpose w3c/wcag#441 (2 comments by @awkawk, @LaurenceRLewis)
-
errata? 1.4.11 does not exempt logos, like 1.4.3 exempts logotypes w3c/wcag#447 (1 comment by @alastc)
-
Duplicate paragraph in the "Status of This Document" section of WCAG 2.1 w3c/wcag#410 (1 comment by @awkawk)
-
Missing navigation on https://www.w3.org/WAI/WCAG21/Understanding/reflow w3c/wcag#375 (1 comment by @awkawk)
-
Missing letter on https://www.w3.org/WAI/WCAG21/Understanding/reflow w3c/wcag#376 (1 comment by @awkawk)
-
-
15 pull requests opened.
-
Prevent video from overflowing container element w3c/wcag#463, by @juleskuehn.
-
chore: Run eclint fix for whitespace and indents w3c/wcag#459, by @nschonni.
-
Modification to Understanding doc to synch with new technique w3c/wcag#458, by @mbgower.
-
Tech failure name not label text w3c/wcag#457, by @detlevhfischer.
-
Tech drag drop cancel w3c/wcag#456, by @detlevhfischer.
-
Tech visible labels match names w3c/wcag#455, by @detlevhfischer.
-
Tech ensuring single pointer deltev w3c/wcag#454, by @detlevhfischer.
-
Identify input purpose updates w3c/wcag#453, by @alastc.
-
Tech failure hover focus content not dismissable w3c/wcag#450, by @detlevhfischer.
-
Example aria role status w3c/wcag#449, by @alastc.
-
Tech using role status w3c/wcag#448, by @alastc.
-
Import understanding SC 1.4.13's images into repo w3c/wcag#446, by @EricDunsworth.
-
8 pull requests merged.
-
Identify input purpose updates w3c/wcag#453.
-
Example aria role status w3c/wcag#431.
-
Tech using role status w3c/wcag#432.
-
Example aria role status w3c/wcag#449.
-
Tech using role status w3c/wcag#448.
-
5 pull requests closed.
-
Prevent video from overflowing container element w3c/wcag#463.
-
chore: Run eclint fix for whitespace and indents w3c/wcag#459.
-
Typo fixes for duplicate words w3c/wcag#377.
-
Update autocomplete.html w3c/wcag#439.
-
-
25 pull requests received 76 new comments.
-
Tech failure name not label text w3c/wcag#457 (8 comments by @allanj-uaag, @detlevhfischer, @lauracarlson, @marcjohlic, @patrickhlauke)
-
Tech failure hover focus content not dismissable w3c/wcag#450 (8 comments by @alastc, @detlevhfischer, @mraccess77)
-
Tech media queries grid reflow w3c/wcag#387 (7 comments by @alastc, @allanj-uaag, @detlevhfischer, @jake-abma, @WayneEDick)
-
chore: Run eclint fix for whitespace and indents w3c/wcag#459 (6 comments by @alastc, @michael-n-cooper, @nschonni)
-
status-messages: Fix HTML code issues that impact generation of Understanding as expected w3c/wcag#467 (3 comments by @alastc, @michael-n-cooper)
-
Incorporate changes to status message Understanding post-michael cooper w3c/wcag#462 (2 comments by @alastc, @detlevhfischer)
-
non-text-contrast: Fix HTML code issues that impact generation of Understanding as expected w3c/wcag#466 (2 comments by @alastc, @michael-n-cooper)
-
Import understanding SC 1.4.13's images into repo w3c/wcag#446 (2 comments by @alastc, @EricDunsworth)
-
w3c/wcag-act
-
10 issues opened.
-
16. Rule Aggregation - Add Requirement w3c/wcag-act#252, by @nitedog.
-
Test cases for composed rules w3c/wcag-act#251, by @WilcoFiers.
-
Accessibility Requirements: Updates requested (Shadi) w3c/wcag-act#250, by @moekraft.
-
Rule Description: Example needed (Shadi) w3c/wcag-act#249, by @moekraft.
-
Rule Identifier: Example needed (Shadi) w3c/wcag-act#248, by @moekraft.
-
Scope: Editorial updates (Shadi) w3c/wcag-act#246, by @moekraft.
-
Introduction: Editorial updates (Shadi) w3c/wcag-act#245, by @moekraft.
-
Abstract: Editorial updates (Shadi) w3c/wcag-act#244, by @moekraft.
-
Composed or Composite rule? w3c/wcag-act#243, by @Brynanders.
-
Review/replace term "aggregation definition" for composed rules w3c/wcag-act#241, by @EmmaJP.
-
-
27 issues closed.
-
"Pass" / "fail" terminology use w3c/wcag-act#219.
-
Pointers to nodes in (Shadow) DOM w3c/wcag-act#223.
-
Example 1 and Example 2 are identical w3c/wcag-act#197.
-
Add a glossary w3c/wcag-act#196.
-
Custom Aggregation for Rule Groups w3c/wcag-act#198.
-
DIFI: 1 Introduction and 3.5 Limitations, Assumptions or Exceptions w3c/wcag-act#201.
-
DIFI: 3.4 Accessibility Requirements w3c/wcag-act#202.
-
DIFI: 6.1. Applicability w3c/wcag-act#203.
-
DIFI: 6.2 Expectations w3c/wcag-act#204.
-
DIFI: Rule Grouping w3c/wcag-act#205.
-
DIFI: 8.3. Outcome w3c/wcag-act#207.
-
DIFI: 8.4 Ensure Comparable Results w3c/wcag-act#208.
-
DIFI: 9.3 Rule Aggregation w3c/wcag-act#209.
-
Add rule groups w3c/wcag-act#193.
-
Rule Groups and examples required w3c/wcag-act#189.
-
Propose tickets to update the examples w3c/wcag-act#177.
-
Review process comments Detlev Fischer w3c/wcag-act#174.
-
Better define how to test the applicability part of a rule w3c/wcag-act#164.
-
Output data format for rule groups w3c/wcag-act#116.
-
Investigate Va11yS to see if testcases can be updated w3c/wcag-act#89.
-
Define proposal on how to best leverage existing testcases w3c/wcag-act#76.
-
Clarify that ACT Framework Requirements is not about ACT Rules w3c/wcag-act#6.
-
DIFI: ACT Rule Data Format w3c/wcag-act#206.
-
Consistent linking / highlighting of defined terms in rules format w3c/wcag-act#185.
-
SC cannot be evaluate to inapplicable ? w3c/wcag-act#240.
-
-
39 issues received 55 new comments.
-
Accessibility Requirements: Updates requested (Shadi) w3c/wcag-act#250 (3 comments by @maryjom, @WilcoFiers)
-
Review/replace term "aggregation definition" for composed rules w3c/wcag-act#241 (3 comments by @annethyme, @cpandhi, @moekraft)
-
Question on 4. Test Subject Types (Input) - like to see more than just html w3c/wcag-act#123 (2 comments by @WilcoFiers)
-
Clarify how to do "Implementation validation" and "accuracy benchmarking" for manual or semi-automated rules w3c/wcag-act#163 (2 comments by @maryjom, @WilcoFiers)
-
clarifying the relationship between rule application and accessibility conformance w3c/wcag-act#227 (2 comments by @moekraft, @WilcoFiers)
-
Communicating the need for additional input for rules that may require such w3c/wcag-act#176 (2 comments by @kasperisager, @WilcoFiers)
-
Ensure Comparable Results section seems redundant to ACT Data Format (Output Data) section w3c/wcag-act#183 (1 comment by @WilcoFiers)
-
Define proposal on how to best leverage existing testcases w3c/wcag-act#76 (1 comment by @WilcoFiers)
-
Clarify that ACT Framework Requirements is not about ACT Rules w3c/wcag-act#6 (1 comment by @WilcoFiers)
-
Consistent linking / highlighting of defined terms in rules format w3c/wcag-act#185 (1 comment by @moekraft)
-
2 pull requests opened.
-
Get rid of "Test/Aggregation Definition" w3c/wcag-act#247, by @annethyme.
-
Update "8. Aspects under Test" w3c/wcag-act#242, by @annethyme.
-
-
2 pull requests received 5 new comments.
-
Get rid of "Test/Aggregation Definition" w3c/wcag-act#247 (4 comments by @annethyme, @maryjom, @moekraft)
-
w3c/coga
-
3 pull requests opened.
-
Fixed a few minor type-os and grammar w3c/coga#82, by @SteveALee.
-
New titles and intros w3c/coga#81, by @lseeman.
-
separate the usable doc w3c/coga#80, by @lseeman.
-
-
2 pull requests merged.
-
New titles and intros w3c/coga#81.
-
separate the usable doc w3c/coga#80.
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
3 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Fixed a few minor type-os and grammar w3c/coga#82, by @SteveALee.
-
New titles and intros w3c/coga#81, by @lseeman.
-
separate the usable doc w3c/coga#80, by @lseeman.
-
-
2 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
New titles and intros w3c/coga#81.
-
separate the usable doc w3c/coga#80.
-
Low Vision Accessibility Task Force
GitHub
w3c/low-vision-a11y-tf
-
1 issue opened in the Low Vision Accessibility Task Force.
-
The Reflow Criterion from WCAG 2.1 Fails on All Pages w3c/low-vision-a11y-tf#82, by @WayneEDick.
-
TR publications
-
1 document published.
-
Accessibility Conformance Testing (ACT) Rules Format 1.0 published as a Working Draft. History of Accessibility Conformance Testing (ACT) Rules Format 1.0
-
Participants
-
1 participant joined.
-
Kathy Eng (W3C Invited Experts) joined.
-
-
1 organization joined.
-
Universidad Politécnica de Madrid joined.
-
-
2 organizations left.
-
Unify left.
-
Raising the Floor left.
-
GitHub
w3c/wcag-act
-
21 issues opened.
-
SC cannot be evaluate to inapplicable ? w3c/wcag-act#240, by @audreymaniez.
-
False negatives definition w3c/wcag-act#239, by @audreymaniez.
-
Structure of the text w3c/wcag-act#238, by @annika-FTB.
-
16. Rule Aggregation - Improve example w3c/wcag-act#237, by @annika-FTB.
-
15.2. Accuracy Benchmarking - Update definition w3c/wcag-act#236, by @annika-FTB.
-
Outcomes of atomic tests w3c/wcag-act#235, by @annika-FTB.
-
11.2. Aggregation Expectations - Update example w3c/wcag-act#234, by @annika-FTB.
-
8.1. Common Aspects - Question w3c/wcag-act#233, by @annika-FTB.
-
4. ACT Rule Structure - Improvement suggestion w3c/wcag-act#232, by @annika-FTB.
-
7. Accessibility Requirements - Improvement suggestion w3c/wcag-act#231, by @annika-FTB.
-
3. ACT Rule Types - Clarify example w3c/wcag-act#230, by @annika-FTB.
-
Investigate how to use EARL with ACT RF w3c/wcag-act#229, by @WilcoFiers.
-
clarifying the relationship between rule application and accessibility conformance w3c/wcag-act#227, by @jasonjgw.
-
ACT i18n checks w3c/wcag-act#226, by @WilcoFiers.
-
ACT security checks w3c/wcag-act#225, by @WilcoFiers.
-
List of features for exit critiera w3c/wcag-act#224, by @WilcoFiers.
-
Pointers to nodes in (Shadow) DOM w3c/wcag-act#223, by @kasperisager.
-
Wrong references to WAI-ARIA 1.1 w3c/wcag-act#222, by @nitedog.
-
Section “13. Accessibility Support” unclear w3c/wcag-act#221, by @nitedog.
-
Concern about stability of test target pointers w3c/wcag-act#220, by @kasperisager.
-
-
2 issues closed.
-
Should rule groups be separate entities? w3c/wcag-act#161.
-
Rule groups (or "composed rules"?) w3c/wcag-act#214.
-
-
9 issues received 20 new comments.
-
List of features for exit critiera w3c/wcag-act#224 (5 comments by @annethyme, @cpandhi, @maryjom, @moekraft, @rdeltour)
-
Concern about stability of test target pointers w3c/wcag-act#220 (2 comments by @rdeltour, @WilcoFiers)
-
w3c/wcag
-
8 issues opened.
-
w3c using autoplay on their own videos w3c/wcag#440, by @nschonni.
-
https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0 w3c/wcag#438, by @berghov1941.
-
SC 1.3.5 is not restricted to markup languages but SC 1.3.6 is w3c/wcag#425, by @mraccess77.
-
Enabling code-examples to reflow w3c/wcag#423, by @alastc.
-
No HTML Landmarks techniques present, only ARIA w3c/wcag#422, by @jake-abma.
-
2.2.6: Timeouts - reference to compliance w3c/wcag#421, by @ghost.
-
Is there a typo in 1.4.13? w3c/wcag#420, by @goodwitch.
-
-
2 issues closed.
-
w3c using autoplay on their own videos w3c/wcag#440.
-
https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0 w3c/wcag#438.
-
-
11 issues received 51 new comments.
-
Failure technique F87 contradicts the Accessible name and desc algorithm w3c/wcag#433 (19 comments by @alastc, @awkawk, @lauracarlson, @mbgower, @mraccess77, @Wildebrew)
-
Is there a typo in 1.4.13? w3c/wcag#420 (5 comments by @awkawk, @eadraffan, @johnfoliot, @mbgower, @Ryladog)
-
No HTML Landmarks techniques present, only ARIA w3c/wcag#422 (4 comments by @alastc, @jake-abma, @johnfoliot)
-
SC 1.3.5 is not restricted to markup languages but SC 1.3.6 is w3c/wcag#425 (3 comments by @awkawk, @mbgower)
-
Second thoughts on pointer gestures and drag-and-drop w3c/wcag#403 (2 comments by @alastc, @mbgower)
-
https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0 w3c/wcag#438 (2 comments by @berghov1941, @michael-n-cooper)
-
-
15 pull requests opened.
-
Update autocomplete.html w3c/wcag#439, by @mbgower.
-
Tech autocomplete w3c/wcag#437, by @DavidMacDonald.
-
Example aria role log w3c/wcag#436, by @mbgower.
-
Tech using role log w3c/wcag#435, by @mbgower.
-
Techniques links w3c/wcag#434, by @michael-n-cooper.
-
Tech using role status w3c/wcag#432, by @mbgower.
-
Example aria role status w3c/wcag#431, by @mbgower.
-
Change links from 2.0 Understanding to 2.1 w3c/wcag#430, by @michael-n-cooper.
-
Extraneous note text on reflow. w3c/wcag#429, by @alastc.
-
Correcting two note/examples w3c/wcag#428, by @alastc.
-
Removing ed-note about stable URL w3c/wcag#427, by @alastc.
-
Editorial updates 2.0 - 2.1 w3c/wcag#426, by @alastc.
-
added mousedown complexities w3c/wcag#424, by @detlevhfischer.
-
Updates from issue 382 w3c/wcag#419, by @alastc.
-
Adding xmlns declaration w3c/wcag#418, by @alastc.
-
-
7 pull requests merged.
-
Techniques links w3c/wcag#434.
-
Adding xmlns declaration w3c/wcag#418.
-
Change links from 2.0 Understanding to 2.1 w3c/wcag#430.
-
Extraneous note text on reflow. w3c/wcag#429.
-
Correcting two note/examples w3c/wcag#428.
-
Removing ed-note about stable URL w3c/wcag#427.
-
Editorial updates 2.0 - 2.1 w3c/wcag#426.
-
-
1 pull request closed.
-
Updates from issue 382 w3c/wcag#419.
-
-
13 pull requests received 71 new comments.
-
Tech media queries grid reflow w3c/wcag#387 (17 comments by @alastc, @allanj-uaag, @jake-abma, @lauracarlson, @mbgower, @mraccess77)
-
Technique - Failure of viewport units w3c/wcag#417 (13 comments by @alastc, @allanj-uaag, @detlevhfischer, @lauracarlson, @mraccess77, @Ryladog)
-
Tech media queries sticky w3c/wcag#389 (5 comments by @alastc, @detlevhfischer, @jake-abma, @mbgower)
-
Technique - ensuring single pointer usage w3c/wcag#380 (3 comments by @alastc, @awkawk, @mraccess77)
-
w3c/wcag3
-
1 issue opened.
-
Measurable test coverage: Silver requirement? w3c/wcag3#387, by @WilcoFiers.
-
w3c/coga
-
1 issue opened.
-
[Gap Analysis] Duplicate Bullet Point in Introduction w3c/coga#79, by @yatil.
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
1 issue opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
[Gap Analysis] Duplicate Bullet Point in Introduction w3c/coga#79, by @yatil.
-
TR publications
-
2 documents published.
-
Web Content Accessibility Guidelines (WCAG) 2.1 published as a Recommendation. History of Web Content Accessibility Guidelines (WCAG) 2.1
-
Cognitive Accessibility Roadmap and Gap Analysis published as a Working Draft. History of Cognitive Accessibility Roadmap and Gap Analysis
-
Participants
-
1 organization joined.
-
Media Access Australia joined.
-
GitHub
w3c/wcag
-
84 issues opened.
-
Understanding Success Criterion 1.3.4: Orientation w3c/wcag#416, by @michael-n-cooper.
-
Table of contents missing, big gap Understanding pages w3c/wcag#415, by @michael-n-cooper.
-
small typo where two "cc" are present for the word criteria w3c/wcag#414, by @michael-n-cooper.
-
Small typo for Note 5.2.2 Full pages w3c/wcag#413, by @michael-n-cooper.
-
Small adjustment to link "How to Meet WCAG 2.1" w3c/wcag#412, by @michael-n-cooper.
-
WCAG 2 Layers of Guidance still refers to WCAG 2.0 w3c/wcag#411, by @michael-n-cooper.
-
SC 1.4.10 - Implementation Report - PDF w3c/wcag#408, by @michael-n-cooper.
-
Live form controls in understanding non text contrast w3c/wcag#405, by @michael-n-cooper.
-
Understanding Success Criterion 2.4.1: Bypass Blocks w3c/wcag#404, by @michael-n-cooper.
-
Second thoughts on pointer gestures and drag-and-drop w3c/wcag#403, by @michael-n-cooper.
-
Orientation needs clarification on locking at the OS level w3c/wcag#401, by @michael-n-cooper.
-
SC 1.4.11 contrast on hover included or not w3c/wcag#400, by @michael-n-cooper.
-
Carry out editorial review for consistent structure w3c/wcag#398, by @michael-n-cooper.
-
Understanding SC 1.4.11 - Mistake w3c/wcag#397, by @michael-n-cooper.
-
Formatting the new WCAG 2.1 w3c/wcag#396, by @michael-n-cooper.
-
Polish starts of the Understanding documents w3c/wcag#395, by @michael-n-cooper.
-
single pointer definition includes path-based gestures? w3c/wcag#394, by @michael-n-cooper.
-
Update FAQ to address new SC in non-Web content w3c/wcag#393, by @michael-n-cooper.
-
SC2.2.6 (Timouts) should be for all websites w3c/wcag#392, by @michael-n-cooper.
-
Are Reflow, Text Size and Orientation cumulative? w3c/wcag#391, by @michael-n-cooper.
-
Understanding Reflow "out of the flow" w3c/wcag#390, by @jake-abma.
-
Spacing Override Technique w3c/wcag#384, by @allanj-uaag.
-
Reference to WCAG 2.0 instead WCAG 2.1 w3c/wcag#382, by @rscano.
-
Understanding document - SC 1.4.12 Text Spacing w3c/wcag#378, by @KerstinProbiesch.
-
repeated "by" w3c/wcag#374, by @michael-n-cooper.
-
WCAG 2.1 Understanding doc does not have SC numbers w3c/wcag#370, by @mraccess77.
-
Provide clarification in PDF-Techniques for list of tools w3c/wcag#368, by @KerstinProbiesch.
-
Wrong example: G146: Using liquid layout w3c/wcag#365, by @michael-n-cooper.
-
2.2.6 Timeouts: Understanding Intent section is too long w3c/wcag#362, by @michael-n-cooper.
-
Understanding Status Changes w3c/wcag#359, by @michael-n-cooper.
-
Understanding Motion Actuation w3c/wcag#358, by @michael-n-cooper.
-
Understanding Orientation w3c/wcag#357, by @michael-n-cooper.
-
Understanding Concurrent Input Mechanisms w3c/wcag#356, by @michael-n-cooper.
-
Understanding Pointer Cancellation w3c/wcag#355, by @michael-n-cooper.
-
Understanding Pointer Gestures w3c/wcag#354, by @michael-n-cooper.
-
Understanding Target Size w3c/wcag#353, by @michael-n-cooper.
-
Understanding Label in Name w3c/wcag#352, by @michael-n-cooper.
-
Understanding Character Key Shortcuts w3c/wcag#351, by @michael-n-cooper.
-
Understanding Animation from Interactions w3c/wcag#350, by @michael-n-cooper.
-
Understanding Timeouts w3c/wcag#349, by @michael-n-cooper.
-
Understanding Content on Hover or Focus w3c/wcag#348, by @michael-n-cooper.
-
Understanding Text Spacing w3c/wcag#347, by @michael-n-cooper.
-
Understanding Non-text Contrast w3c/wcag#346, by @michael-n-cooper.
-
Understanding Reflow w3c/wcag#345, by @michael-n-cooper.
-
Understanding Identify Purpose w3c/wcag#344, by @michael-n-cooper.
-
Understanding Identify Common/Input Purpose w3c/wcag#343, by @michael-n-cooper.
-
Problem with Technique G131 w3c/wcag#342, by @michael-n-cooper.
-
1.4.3 - CSS4 Variable Fonts - What is bold? w3c/wcag#341, by @michael-n-cooper.
-
Problem with Technique G131 w3c/wcag#339, by @michael-n-cooper.
-
[Understanding/On Focus] Two wrong URLs w3c/wcag#338, by @yatil.
-
Link to assistive technologies doesn't work w3c/wcag#337, by @jake-abma.
-
Link to user agents doesn't work w3c/wcag#336, by @jake-abma.
-
Add link to HTML5 Autocomplete w3c/wcag#335, by @jake-abma.
-
Link to "Related resources" w3c/wcag#334, by @jake-abma.
-
Examples link: to HTML5 OR to normative list? w3c/wcag#333, by @jake-abma.
-
Link to Personas w3c/wcag#332, by @jake-abma.
-
Small wording update "a people..." w3c/wcag#331, by @jake-abma.
-
Link to 4.1.2 can be added w3c/wcag#330, by @jake-abma.
-
Add a nuance in wording for not generalizing the cognitive group w3c/wcag#329, by @jake-abma.
-
Link to "programmatically determined " not working w3c/wcag#328, by @jake-abma.
-
Typo: signiicantly w3c/wcag#325, by @jake-abma.
-
Re-write of sentence "It is critical" w3c/wcag#324, by @jake-abma.
-
Glossary: definition of "prerecorded" w3c/wcag#323, by @jkshapiro.
-
Editorial issue with Concurrent Input Mechanisms w3c/wcag#322, by @sidnc86.
-
Editorial correction in Understanding Reflow w3c/wcag#321, by @sidnc86.
-
Date-stamping creation and revision dates for techniques w3c/wcag#320, by @awkawk.
-
-
3 issues closed.
-
Problem with Technique G131 w3c/wcag#342.
-
Editorial correction in Understanding Reflow w3c/wcag#321.
-
52 issues received 419 new comments.
-
Failure Technique around page regions (Header, Footer, Nav, Main etc.) w3c/wcag#340 (36 comments by @michael-n-cooper)
-
Second thoughts on pointer gestures and drag-and-drop w3c/wcag#403 (20 comments by @michael-n-cooper)
-
Understanding Content on Hover or Focus w3c/wcag#348 (10 comments by @guyhickling, @michael-n-cooper)
-
SC 1.3.5 Identify Input Purpose - autocomplete technique VS Privacy/Security w3c/wcag#407 (7 comments by @michael-n-cooper)
-
Non-sRGB color spaces, outdated sRGB threshold, and other issues in the "relative luminance" definition w3c/wcag#360 (6 comments by @michael-n-cooper)
-
single pointer definition includes path-based gestures? w3c/wcag#394 (4 comments by @michael-n-cooper)
-
Spacing Override Technique w3c/wcag#384 (4 comments by @emanser, @goodwitch, @johnfoliot, @stevefaulkner)
-
Orientation needs clarification on locking at the OS level w3c/wcag#401 (3 comments by @michael-n-cooper)
-
2.6.2 Orientation: Add vision impairment benefit and example w3c/wcag#364 (3 comments by @michael-n-cooper)
-
SC2.2.6 (Timouts) should be for all websites w3c/wcag#392 (2 comments by @guyhickling, @michael-n-cooper)
-
2.5.4 Concurrent Input Mechanism: Add mouse/keyboard menu example w3c/wcag#363 (2 comments by @michael-n-cooper)
-
incorporate feedback from Review of Understanding Text Spacing w3c/wcag#399 (1 comment by @michael-n-cooper)
-
References to a Failure for 2.5.2 Pointer Cancellation is out of date w3c/wcag#372 (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.2.6 Timeouts: Understanding Intent section is too long w3c/wcag#362 (1 comment by @michael-n-cooper)
-
1.3.5 Identify Purpose: Understanding and Techniques seem unfinished w3c/wcag#361 (1 comment by @michael-n-cooper)
-
Add a nuance in wording for not generalizing the cognitive group w3c/wcag#329 (1 comment by @jake-abma)
-
13 pull requests opened.
-
Technique - Failure of viewport units w3c/wcag#417, by @alastc.
-
Tech media queries sticky w3c/wcag#389, by @alastc.
-
Tech flexbox reflow w3c/wcag#388, by @alastc.
-
Tech media queries grid reflow w3c/wcag#387, by @alastc.
-
Tech spacing override w3c/wcag#386, by @alastc.
-
Removing the fixed-text examples w3c/wcag#385, by @alastc.
-
Minor updates for clarity w3c/wcag#383, by @DavidMacDonald.
-
EXAMPLE: ACT Rules as techniques w3c/wcag#381, by @WilcoFiers.
-
Technique - ensuring single pointer usage w3c/wcag#380, by @alastc.
-
Pointer gestures amendment w3c/wcag#379, by @detlevhfischer.
-
Typo fixes for duplicate words w3c/wcag#377, by @nschonni.
-
Understanding non-text-contrast updates w3c/wcag#373, by @alastc.
-
Point to this repo instead of wcag21 w3c/wcag#367, by @alastc.
-
-
3 pull requests merged.
-
Understanding non-text-contrast updates w3c/wcag#373.
-
Minor updates for clarity w3c/wcag#383.
-
Point to this repo instead of wcag21 w3c/wcag#367.
-
-
3 pull requests received 12 new comments.
-
Understanding non-text-contrast updates w3c/wcag#373 (4 comments by @alastc, @DavidMacDonald, @johnfoliot)
w3c/wcag-act
-
2 issues opened.
-
"Pass" / "fail" terminology use w3c/wcag-act#219, by @WilcoFiers.
-
Need non-versioned biblio reference tags w3c/wcag-act#216, by @moekraft.
-
-
4 issues received 6 new comments.
-
2 pull requests opened.
-
Generating draft with composed rules updates w3c/wcag-act#218, by @moekraft.
-
Add Composed rules w3c/wcag-act#217, by @WilcoFiers.
-
-
3 pull requests merged.
-
Generating draft with composed rules updates w3c/wcag-act#218.
-
Add Composed rules w3c/wcag-act#217.
-
Consistent linking 185 w3c/wcag-act#210.
-
-
1 pull request closed.
-
Update rule grouping section w3c/wcag-act#211.
-
-
3 pull requests received 49 new comments.
-
Add Composed rules w3c/wcag-act#217 (43 comments by @annethyme, @jeeyyy, @maryjom, @moekraft, @rdeltour, @WilcoFiers)
-
w3c/wcag3
-
1 issue opened.
-
Reflow: Fixed Position Fields w3c/wcag3#198, by @michael-n-cooper.
-
-
1 issue received 8 new comments.
GitHub
w3c/wcag
-
1 issue received 1 new comment.
-
Should the failure to implement Sufficient Technique in the right way be treated as a WCAG failure w3c/wcag#318 (1 comment by @alastc)
-
-
1 pull request opened.
-
List skip-link and landmark techniques as related to each other w3c/wcag#319, by @lkmorlan.
-
w3c/wcag-act
-
1 issue opened.
-
Rule groups (or "composed rules"?) w3c/wcag-act#214, by @rdeltour.
-
-
3 issues closed.
-
Example of section 3.4 “Limitations, Assumptions, or Exceptions” w3c/wcag-act#136.
-
Consider stronger normative references in the "Common Aspects" w3c/wcag-act#167.
-
Better example for non-DOM selector? w3c/wcag-act#138.
-
-
12 issues received 17 new comments.
-
Rule groups (or "composed rules"?) w3c/wcag-act#214 (6 comments by @annethyme, @cpandhi, @moekraft, @rdeltour, @WilcoFiers)
-
DIFI: 1 Introduction and 3.5 Limitations, Assumptions or Exceptions w3c/wcag-act#201 (1 comment by @WilcoFiers)
-
-
5 pull requests opened.
-
Add "multiple interpretations" to assumptions w3c/wcag-act#215, by @WilcoFiers.
-
Editorial simplification in 'Common Aspects' w3c/wcag-act#213, by @rdeltour.
-
Improve the example of 'Limitations, Assumptions, or Exceptions' w3c/wcag-act#212, by @rdeltour.
-
Update rule grouping section w3c/wcag-act#211, by @kasperisager.
-
Consistent linking 185 w3c/wcag-act#210, by @moekraft.
-
-
5 pull requests merged.
-
Update Accessibility Support Section w3c/wcag-act#200.
-
Add "multiple interpretations" to assumptions w3c/wcag-act#215.
-
Improve the example of 'Limitations, Assumptions, or Exceptions' w3c/wcag-act#212.
-
Editorial simplification in 'Common Aspects' w3c/wcag-act#213.
-
Update Introduction Section w3c/wcag-act#199.
-
-
4 pull requests received 42 new comments.
-
Consistent linking 185 w3c/wcag-act#210 (28 comments by @githubdam, @kasperisager, @maryjom, @moekraft, @nitedog, @rdeltour, @skotkjerra, @WilcoFiers)
-
Update rule grouping section w3c/wcag-act#211 (7 comments by @annethyme, @kasperisager, @WilcoFiers)
-
Update Accessibility Support Section w3c/wcag-act#200 (4 comments by @kasperisager, @maryjom, @moekraft, @WilcoFiers)
-
Improve the example of 'Limitations, Assumptions, or Exceptions' w3c/wcag-act#212 (3 comments by @annethyme, @maryjom)
-
w3c/coga
-
2 pull requests opened.
-
Change according lisa email w3c/coga#78, by @ruoxiran.
-
Adding the make-usable appendix w3c/coga#77, by @alastc.
-
-
2 pull requests merged.
-
Change according lisa email w3c/coga#78.
-
Adding the make-usable appendix w3c/coga#77.
-
-
2 pull requests received 2 new comments.
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
2 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Change according lisa email w3c/coga#78, by @ruoxiran.
-
Adding the make-usable appendix w3c/coga#77, by @alastc.
-
-
2 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Change according lisa email w3c/coga#78.
-
Adding the make-usable appendix w3c/coga#77.
-
-
2 pull requests in the Cognitive and Learning Disabilities Accessibility Task Force received 2 new comments.
TR publications
-
1 document published.
-
Web Content Accessibility Guidelines (WCAG) 2.1 published as a Proposed Recommendation. History of Web Content Accessibility Guidelines (WCAG) 2.1
-
Participants
-
1 organization joined.
-
Search Engine Optimization Inc joined.
-
GitHub
w3c/coga
-
2 pull requests opened.
-
Transfer usable html ac w3c/coga#76, by @alastc.
-
Jan's summaries for issue papers w3c/coga#75, by @lseeman.
-
-
3 pull requests merged.
-
Transfer usable html ac w3c/coga#76.
-
Jan's summaries for issue papers w3c/coga#75.
-
Redo cleanup links w3c/coga#74.
-
w3c/wcag-act
-
15 issues opened.
-
DIFI: 9.3 Rule Aggregation w3c/wcag-act#209, by @WilcoFiers.
-
DIFI: 8.4 Ensure Comparable Results w3c/wcag-act#208, by @WilcoFiers.
-
DIFI: 8.3. Outcome w3c/wcag-act#207, by @WilcoFiers.
-
DIFI: ACT Rule Data Format w3c/wcag-act#206, by @WilcoFiers.
-
DIFI: Rule Grouping w3c/wcag-act#205, by @WilcoFiers.
-
DIFI: 6.2 Expectations w3c/wcag-act#204, by @WilcoFiers.
-
DIFI: 6.1. Applicability w3c/wcag-act#203, by @WilcoFiers.
-
DIFI: 3.4 Accessibility Requirements w3c/wcag-act#202, by @WilcoFiers.
-
DIFI: 1 Introduction and 3.5 Limitations, Assumptions or Exceptions w3c/wcag-act#201, by @WilcoFiers.
-
Custom Aggregation for Rule Groups w3c/wcag-act#198, by @annethyme.
-
Example 1 and Example 2 are identical w3c/wcag-act#197, by @annethyme.
-
Add a glossary w3c/wcag-act#196, by @WilcoFiers.
-
Define a format for rules and test cases w3c/wcag-act#195, by @WilcoFiers.
-
Add implementation manifest w3c/wcag-act#194, by @WilcoFiers.
-
Add rule groups w3c/wcag-act#193, by @WilcoFiers.
-
-
2 issues closed.
-
Discuss if expectations are "conformance statements" w3c/wcag-act#172.
-
Clarify that a N/A result is a pass. w3c/wcag-act#160.
-
-
6 issues received 10 new comments.
-
Consistent linking / highlighting of defined terms in rules format w3c/wcag-act#185 (1 comment by @moekraft)
-
2 pull requests opened.
-
Update Accessibility Support Section w3c/wcag-act#200, by @anthonyFer.
-
Update Introduction Section w3c/wcag-act#199, by @anthonyFer.
-
-
2 pull requests merged.
-
change: expectation is an assertion w3c/wcag-act#191.
-
Note related to inapplicability w3c/wcag-act#192.
-
-
2 pull requests received 2 new comments.
w3c/wcag
-
2 issues opened.
-
ARIA6 and others: Bad links w3c/wcag#317, by @yatil.
-
1 issue closed.
-
2 issues received 4 new comments.
-
Outdated threshold for sRGB companding in the "relative luminance" definition w3c/wcag#308 (1 comment by @awkawk)
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
2 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Transfer usable html ac w3c/coga#76, by @alastc.
-
Jan's summaries for issue papers w3c/coga#75, by @lseeman.
-
-
3 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Transfer usable html ac w3c/coga#76.
-
Jan's summaries for issue papers w3c/coga#75.
-
Redo cleanup links w3c/coga#74.
-
TR publications
-
1 document published.
-
Accessibility Conformance Testing (ACT) Rules Format 1.0 published as a Working Draft. History of Accessibility Conformance Testing (ACT) Rules Format 1.0
-
Participants
-
1 organization joined.
-
Readspeaker joined.
-
GitHub
w3c/coga
-
5 pull requests opened.
-
Redo cleanup links w3c/coga#74, by @ruoxiran.
-
redo clean up for links w3c/coga#73, by @ruoxiran.
-
Roy edit links w3c/coga#72, by @ruoxiran.
-
Fix all links in 9 tables, removed "§" w3c/coga#71, by @ruoxiran.
-
Lisa updates on the table w3c/coga#70, by @lseeman.
-
-
1 pull request merged.
-
Lisa updates on the table w3c/coga#70.
-
-
3 pull requests closed.
-
redo clean up for links w3c/coga#73.
-
Roy edit links w3c/coga#72.
-
Fix all links in 9 tables, removed "§" w3c/coga#71.
-
-
3 pull requests received 3 new comments.
w3c/wcag-act
-
4 issues opened.
-
Rule Groups and examples required w3c/wcag-act#189, by @gianwild.
-
Examples need to be identified accessibly w3c/wcag-act#187, by @chaals.
-
Consistent linking / highlighting of defined terms in rules format w3c/wcag-act#185, by @WilcoFiers.
-
-
6 issues closed.
-
Migrate to w3c/respec from bikeshed w3c/wcag-act#79.
-
Typo w3c/wcag-act#188.
-
Discuss renaming "test procedure" w3c/wcag-act#158.
-
Should expectations be distinct w3c/wcag-act#173.
-
Correct spelling errors and, in places, syntax w3c/wcag-act#178.
-
-
7 issues received 10 new comments.
-
4 pull requests opened.
-
Note related to inapplicability w3c/wcag-act#192, by @WilcoFiers.
-
change: expectation is an assertion w3c/wcag-act#191, by @WilcoFiers.
-
Generating latest draft w3c/wcag-act#186, by @moekraft.
-
-
4 pull requests merged.
-
Test definitions w3c/wcag-act#182.
-
Generating latest draft w3c/wcag-act#186.
-
Editorial updates, fix spelling errors. w3c/wcag-act#184.
-
4 pull requests received 5 new comments.
-
Fix occurrences of typo using the contraction of 'it is' instead of the possessive 'its'. w3c/wcag-act#190 (1 comment by @WilcoFiers)
w3c/wcag
-
1 issue opened.
-
Common Purpose names should be maintained by WCAG w3c/wcag#316, by @chaals.
-
-
1 issue closed.
-
Common Purpose names should be maintained by WCAG w3c/wcag#316.
-
-
1 issue received 2 new comments.
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
5 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Redo cleanup links w3c/coga#74, by @ruoxiran.
-
redo clean up for links w3c/coga#73, by @ruoxiran.
-
Roy edit links w3c/coga#72, by @ruoxiran.
-
Fix all links in 9 tables, removed "§" w3c/coga#71, by @ruoxiran.
-
Lisa updates on the table w3c/coga#70, by @lseeman.
-
-
1 pull request merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Lisa updates on the table w3c/coga#70.
-
-
3 pull requests closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
redo clean up for links w3c/coga#73.
-
Roy edit links w3c/coga#72.
-
Fix all links in 9 tables, removed "§" w3c/coga#71.
-
-
3 pull requests in the Cognitive and Learning Disabilities Accessibility Task Force received 3 new comments.
GitHub
w3c/wcag-act
-
17 issues opened.
-
Develop rules repository w3c/wcag-act#181, by @WilcoFiers.
-
Create understanding documentation for ACT Rules w3c/wcag-act#180, by @WilcoFiers.
-
Editorial differences between spec and example rules w3c/wcag-act#179, by @maryjom.
-
Correct spelling errors and, in places, syntax w3c/wcag-act#178, by @maryjom.
-
Propose tickets to update the examples w3c/wcag-act#177, by @WilcoFiers.
-
Communicating the need for additional input for rules that may require such w3c/wcag-act#176, by @kasperisager.
-
presenting ACT Rules and implementations w3c/wcag-act#175, by @nitedog.
-
Review process comments Detlev Fischer w3c/wcag-act#174, by @WilcoFiers.
-
Should expectations be distinct w3c/wcag-act#173, by @WilcoFiers.
-
Discuss if expectations are "conformance statements" w3c/wcag-act#172, by @WilcoFiers.
-
Consider stronger normative references in the "Common Aspects" w3c/wcag-act#167, by @rdeltour.
-
Consider linking from the spec to GitHub issues w3c/wcag-act#166, by @rdeltour.
-
Clarify the definition of Rule Aggregation w3c/wcag-act#165, by @rdeltour.
-
Better define how to test the applicability part of a rule w3c/wcag-act#164, by @rdeltour.
-
Clarify the output format definition w3c/wcag-act#162, by @rdeltour.
-
3 issues closed.
-
Need credit section in Rules template w3c/wcag-act#100.
-
Consider linking from the spec to GitHub issues w3c/wcag-act#166.
-
[editorial] Harmonize language on how ACT Rules conformance w3c/wcag-act#134.
-
-
10 issues received 16 new comments.
-
Better define how to test the applicability part of a rule w3c/wcag-act#164 (2 comments by @WilcoFiers)
-
Consider stronger normative references in the "Common Aspects" w3c/wcag-act#167 (1 comment by @WilcoFiers)
-
6 pull requests opened.
-
Editorial updates, fix spelling errors. w3c/wcag-act#184, by @maryjom.
-
Test definitions w3c/wcag-act#182, by @WilcoFiers.
-
Reword the Accessibility Support section w3c/wcag-act#171, by @rdeltour.
-
Normalize the statements on ACT Rules w3c/wcag-act#170, by @rdeltour.
-
Minor editorial simplifications + fixes w3c/wcag-act#169, by @rdeltour.
-
Reword the abstract w3c/wcag-act#168, by @rdeltour.
-
-
4 pull requests merged.
-
Reword the Accessibility Support section w3c/wcag-act#171.
-
Reword the abstract w3c/wcag-act#168.
-
Minor editorial simplifications + fixes w3c/wcag-act#169.
-
Normalize the statements on ACT Rules w3c/wcag-act#170.
-
-
2 pull requests received 7 new comments.
w3c/wcag
-
1 issue opened.
-
2.4.6 Headings and Labels - note regarding 1.3.1 w3c/wcag#315, by @jidaikobo-shibata.
-
TR publications
-
1 document published.
-
Web Content Accessibility Guidelines (WCAG) 2.1 published as a Candidate Recommendation Snapshot. History of Web Content Accessibility Guidelines (WCAG) 2.1
-
GitHub
w3c/wcag-act
-
4 issues opened.
-
Should rule groups be separate entities? w3c/wcag-act#161, by @kasperisager.
-
Clarify that a N/A result is a pass. w3c/wcag-act#160, by @DavidMacDonald.
-
Discuss renaming "test procedure" w3c/wcag-act#158, by @WilcoFiers.
-
Update spec to use applicable / expectations instead of selector / steps w3c/wcag-act#154, by @WilcoFiers.
-
-
25 issues closed.
-
Question on 4. Test Subject Types (Input) and the state of the page w3c/wcag-act#124.
-
Support for recording state in output data w3c/wcag-act#114.
-
Rewrite ACT-R1 with Applicable/Expectations format w3c/wcag-act#150.
-
Rewrite ACT-R3 with Applicable/Expectations format w3c/wcag-act#152.
-
Rewrite ACT-R2 with Applicable/Expectations format w3c/wcag-act#151.
-
Allow for alternative structure in ATT w3c/wcag-act#140.
-
Update spec to use applicable / expectations instead of selector / steps w3c/wcag-act#154.
-
Input types are much too specific and lead to confusion w3c/wcag-act#109.
-
Need to update examples in Appendix to match Earl specificiation w3c/wcag-act#108.
-
Specification does not pass WCAG 2.0 Accessibility requirements w3c/wcag-act#110.
-
Research flowcharting tools w3c/wcag-act#99.
-
Mapping rules to WCAG 2.0 Failure Techniques is problematic. w3c/wcag-act#15.
-
publication requirements needs a first draft w3c/wcag-act#81.
-
Accuracy benchmarking repeats false positives (editorial) w3c/wcag-act#83.
-
Question: How do you indicate tools for manual testing w3c/wcag-act#112.
-
Clarify the purpose of the test procedure w3c/wcag-act#113.
-
Suggestions on 8.4 Test Subject - add state? w3c/wcag-act#128.
-
Clarify what we mean by negative tests w3c/wcag-act#7.
-
Clarify proof of compliance with absence of violation w3c/wcag-act#8.
-
Avoid hard statements about rules not being automated w3c/wcag-act#120.
-
Suggestion for 5.2 Test Cases - List of Common Issue Descriptions? w3c/wcag-act#125.
-
Question on 8.1 Selected Item - pointer w3c/wcag-act#127.
-
Possibly allow meta-rules w3c/wcag-act#141.
-
22 issues received 35 new comments.
-
Rewrite ACT-R3 with Applicable/Expectations format w3c/wcag-act#152 (4 comments by @cpandhi, @WilcoFiers)
-
Rewrite ACT-R1 with Applicable/Expectations format w3c/wcag-act#150 (3 comments by @cpandhi, @WilcoFiers)
-
Rewrite ACT-R2 with Applicable/Expectations format w3c/wcag-act#151 (3 comments by @kasperisager, @WilcoFiers)
-
Input types are much too specific and lead to confusion w3c/wcag-act#109 (3 comments by @kasperisager, @maryjom)
-
Suggestion for 8. ACT Data Format (Output Format) - Sufficient Technique(s) w3c/wcag-act#126 (2 comments by @nitedog)
-
Question on 4. Test Subject Types (Input) and the state of the page w3c/wcag-act#124 (2 comments by @nitedog)
-
Question on 4. Test Subject Types (Input) - like to see more than just html w3c/wcag-act#123 (2 comments by @goodwitch, @kasperisager)
-
Specification does not pass WCAG 2.0 Accessibility requirements w3c/wcag-act#110 (1 comment by @WilcoFiers)
-
Define proposal on how to best leverage existing testcases w3c/wcag-act#76 (1 comment by @WilcoFiers)
-
Should we add a section on user input/interactive steps to the rules format? w3c/wcag-act#104 (1 comment by @WilcoFiers)
-
Suggestion for 5.2 Test Cases - List of Common Issue Descriptions? w3c/wcag-act#125 (1 comment by @WilcoFiers)
-
Update spec to use applicable / expectations instead of selector / steps w3c/wcag-act#154 (1 comment by @WilcoFiers)
-
-
4 pull requests opened.
-
Aspects under test w3c/wcag-act#159, by @WilcoFiers.
-
Add section describing "Aspects Under Test" w3c/wcag-act#157, by @kasperisager.
-
Ensure EARL examples are valid w3c/wcag-act#156, by @WilcoFiers.
-
Replace selector/steps with applicability/expecations w3c/wcag-act#155, by @WilcoFiers.
-
-
4 pull requests merged.
-
Aspects under test w3c/wcag-act#159.
-
Replace selector/steps with applicability/expecations w3c/wcag-act#155.
-
Ensure EARL examples are valid w3c/wcag-act#156.
-
Reword informative prose in the Introduction and Scope sections w3c/wcag-act#131.
-
-
1 pull request closed.
-
Add section describing "Aspects Under Test" w3c/wcag-act#157.
-
-
2 pull requests received 31 new comments.
-
Replace selector/steps with applicability/expecations w3c/wcag-act#155 (20 comments by @annethyme, @cpandhi, @EmmaJP, @kasperisager, @moekraft, @nitedog, @WilcoFiers)
-
Add section describing "Aspects Under Test" w3c/wcag-act#157 (11 comments by @kasperisager, @maryjom, @moekraft, @WilcoFiers)
-
w3c/wcag
-
4 issues opened.
-
Color contrast of 2.37:1 for EDITOR'S NOTE: on WCAG 2.1 w3c/wcag#313, by @goodwitch.
-
metadata needs to be consistent #321 w3c/wcag#311, by @joshueoconnor.
-
-
1 issue received 7 new comments.
-
2.4.7 Focus Visible - what counts as "visible"? w3c/wcag#302 (7 comments by @alastc, @patrickhlauke, @StommePoes)
-
-
1 pull request opened.
-
In G200, list G201 as a related technique w3c/wcag#314, by @lkmorlan.
-