Accessibility Guidelines Working Group - Activity in 2021
No matches.
TR publications
-
2 documents published.
-
W3C Accessibility Guidelines (WCAG) 3.0 published as a Working Draft. History of W3C Accessibility Guidelines (WCAG) 3.0
-
Past meetings
-
10 meetings.
Participants
-
3 participants joined.
-
Suzie Miller (Microsoft Corporation) joined.
-
Meenakshi Das (Microsoft Corporation) joined.
-
Laurence Lewis (Telstra) joined.
-
-
2 participants left.
-
Kepeng Li (Alibaba Group) left.
-
Andrew Somers (W3C Invited Experts) left.
-
-
1 organization joined.
-
Telstra joined.
-
GitHub
w3c/wcag
-
10 issues opened.
-
Opinions on default 403 server page accessibility w3c/wcag#2164, by @jamesjacobs.
-
Use "area" in target spacing (minimum) w3c/wcag#2162, by @WilcoFiers.
-
Consider revision to the definition of Page break locators w3c/wcag#2155, by @mbgower.
-
Contrast of Avatars and Emojis w3c/wcag#2152, by @NeerajChoukseyDeque.
-
@@ in understanding document w3c/wcag#2151, by @yatil.
-
28 issues closed.
-
Consider revision to the definition of Page break locators w3c/wcag#2155.
-
Suggested rewording to normative text of Visible Controls w3c/wcag#1932.
-
Identity w3c/wcag#2167.
-
Opinions on default 403 server page accessibility w3c/wcag#2164.
-
WCAG 2.2 Focus appearance & Visual examples w3c/wcag#2071.
-
3.2.7: Controls that require scrolling to reach w3c/wcag#1875.
-
2.4.13: Query: are slides included? w3c/wcag#1867.
-
3.3.7 Further guidance on 2-factor independent methods w3c/wcag#1965.
-
Adobe Comment on 2.5.7 Dragging Movements w3c/wcag#1886.
-
Contrast of Avatars and Emojis w3c/wcag#2152.
-
@@ in understanding document w3c/wcag#2151.
-
-
32 issues received 137 new comments.
-
Target spacing (minimum): multiple overlapping elements interact oddly with offset w3c/wcag#2159 (50 comments by @alastc, @bruce-usab, @JAWS-test, @mraccess77, @patrickhlauke, @WilcoFiers)
-
Suggested improvement to Understanding 2.2.1: Timing Adjustable w3c/wcag#1814 (19 comments by @bruce-usab, @mraccess77, @patrickhlauke, @robinmetral)
-
Contrast of Avatars and Emojis w3c/wcag#2152 (14 comments by @JAWS-test, @mraccess77, @NeerajChoukseyDeque, @patrickhlauke)
-
Use "area" in target spacing (minimum) w3c/wcag#2162 (6 comments by @alastc, @mraccess77, @patrickhlauke, @WilcoFiers)
-
Does textual information on focus/hover meet visual alternative for SC 1.4.11 w3c/wcag#2157 (6 comments by @alastc, @JAWS-test, @mraccess77, @patrickhlauke)
-
Update H95 TTML and IMSC guidance w3c/wcag#2079 (4 comments by @awkawk, @detlevhfischer, @nigelmegitt)
-
Opinions on default 403 server page accessibility w3c/wcag#2164 (3 comments by @jamesjacobs, @mraccess77, @patrickhlauke)
-
SC 2.4.13 Page break navigation for Web content: overly prescriptive? w3c/wcag#2026 (3 comments by @alastc, @spanchang)
-
Example in SC 2.5.7 seems to imply keyboard functionality acceptable if an on-screen keyboard can be used. w3c/wcag#1978 (3 comments by @mraccess77, @patrickhlauke)
-
[WCAG 2.2 Feedback] Success Criterion 2.5.8 Target Size (Minimum) (Level AA) w3c/wcag#1894 (2 comments by @liacrl, @patrickhlauke)
-
Does the Definition of "Dragging Movements" Intentionally Limit the Scope to Moving Objects/Items? w3c/wcag#1560 (2 comments by @alastc, @SuzanneTaylor)
-
does a control that exposes an incorrect/inappropriate role fail 4.1.2 or not w3c/wcag#2142 (2 comments by @detlevhfischer, @patrickhlauke)
-
aria-roledescription with implicit/explicit roles not read by screen readers w3c/wcag#2168 (1 comment by @patrickhlauke)
-
3.2.7 Visible Controls - The examples provided on the “Understanding” page are not enough w3c/wcag#1443 (1 comment by @gradualclearing)
-
Can large headings be exempt from Success Criterion 1.4.4 Resize text? w3c/wcag#1671 (1 comment by @scottkellum)
-
3.2.7: Subjective judgement is needed, and effort to test and remediate could be quite variable w3c/wcag#1877 (1 comment by @alastc)
-
3.2.7 Visible Controls - The first exception is difficult to understand w3c/wcag#1760 (1 comment by @alastc)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.3.7 Accessible Authentication w3c/wcag#1890 (1 comment by @alastc)
-
SC 2.5.7 Dragging exceptions seems like example of free form paths rather than dragging w3c/wcag#1979 (1 comment by @alastc)
-
Retiring technique H59 Using the link element and navigation tools w3c/wcag#1036 (1 comment by @patrickhlauke)
-
Sufficient technique H63 should incorporate HTML5 and address missing info w3c/wcag#2077 (1 comment by @detlevhfischer)
-
-
9 pull requests opened.
-
[Supporting docs redesign] Change contribution info w3c/wcag#2165, by @hidde.
-
Linking to mechanism w3c/wcag#2163, by @alastc.
-
Michael's page-break def w3c/wcag#2160, by @alastc.
-
Fix typo in consistent help understanding w3c/wcag#2158, by @patrickhlauke.
-
typo in introduction section adds space after link w3c/wcag#2156, by @shawnthompson.
-
Adding exception w3c/wcag#2154, by @alastc.
-
Update H95.html w3c/wcag#2150, by @detlevhfischer.
-
conformance challenges 5aside w3c/wcag#2149, by @JaninaSajka.
-
-
22 pull requests merged.
-
Michael's page-break def w3c/wcag#2160.
-
Initial re-write of SC text w3c/wcag#2019.
-
[Supporting docs redesign] Change contribution info w3c/wcag#2165.
-
conformance challenges 5aside w3c/wcag#2149.
-
Linking to mechanism w3c/wcag#2163.
-
Consistent Help understanding and technique edits w3c/wcag#2092.
-
Outlining non-scoped things. w3c/wcag#2044.
-
Adding suggestion from 2068 w3c/wcag#2115.
-
Paragraph update w3c/wcag#1988.
-
Update visible-controls.html w3c/wcag#2095.
-
Updated SC text w3c/wcag#2145.
-
Adding suggested text w3c/wcag#1989.
-
Update page-break-navigation.html w3c/wcag#2094.
-
Update H99.html w3c/wcag#2130.
-
Adding suggestions from issue #1965 w3c/wcag#2120.
-
Update dragging-movements.html w3c/wcag#2003.
-
Dragging rects and connector lines w3c/wcag#2066.
-
Adding exception w3c/wcag#2154.
-
dragging movements 3rd example w3c/wcag#2009.
-
Update dragging-movements.html w3c/wcag#1961.
-
-
7 pull requests received 10 new comments.
-
Moved some contents out of SC intent and added as additional benefit w3c/wcag#2138 (3 comments by @patrickhlauke)
-
w3c/wcag3
-
1 issue opened.
-
2 issues received 3 new comments.
w3c/coga
-
1 issue opened.
-
SPAM w3c/coga#312, by @Elsokary22.
-
-
1 issue closed.
-
SPAM w3c/coga#312.
-
-
1 issue received 1 new comment.
w3c/wcag-act
-
1 pull request merged.
-
Common aspects: CSS styling, use positive language w3c/wcag-act#524.
-
-
1 pull request received 1 new comment.
Cognitive and Learning Disabilities Accessibility Task Force
Past meetings
-
5 meetings of the Cognitive and Learning Disabilities Accessibility Task Force.
Participants
-
2 participants joined the Cognitive and Learning Disabilities Accessibility Task Force.
-
Shawn Thompson joined.
-
Lē Silveus McNamara joined.
-
GitHub
w3c/coga
-
1 issue opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
SPAM w3c/coga#312, by @Elsokary22.
-
-
1 issue closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
SPAM w3c/coga#312.
-
-
1 issue in the Cognitive and Learning Disabilities Accessibility Task Force received 1 new comment.
Low Vision Accessibility Task Force
Participants
-
1 participant left the Low Vision Accessibility Task Force.
-
Andrew Somers left.
-
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
3 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Participants
-
1 participant joined the Accessibility Conformance Testing (ACT) Task Force.
-
Todd Libby joined.
-
Past meetings
-
9 meetings.
Participants
-
6 participants joined.
-
Todd Libby (W3C Invited Experts) joined.
-
Janina Sajka (Level Access) joined.
-
Suzanne Taylor (Things Entertainment) joined.
-
Helen Burge (W3C Invited Experts) joined.
-
Jennifer Chadwick (Siteimprove) joined.
-
Lē Silveus McNamara (TPGi) joined.
-
-
1 participant left.
-
Angel Li (Alibaba Group) left.
-
-
1 organization joined.
-
Things Entertainment joined.
-
GitHub
w3c/wcag
-
15 issues opened.
-
Question: Unnamed Fieldset and HTML Spec vs WCAG w3c/wcag#2140, by @LaurenceRLewis.
-
Violation of 4.1.1, if with ARIA syntax is correct? w3c/wcag#2135, by @JAWS-test.
-
Technique G74, Title and Examples (SC 1.1.1) w3c/wcag#2129, by @toddmarquisboutin.
-
Technique G73, Example 3 (SC 1.1.1) w3c/wcag#2128, by @toddmarquisboutin.
-
Alt Text Character Limit w3c/wcag#2126, by @cdesrosiers813.
-
Clarifying on conveying several status w3c/wcag#2124, by @gundulaniemann.
-
Keyboard control loophole (2.1.1+2.1.4)? w3c/wcag#2123, by @JAWS-test.
-
Clarification on definition of "scrolling in two dimensions" in 1.4.10 w3c/wcag#2119, by @mra11yx.
-
24 issues closed.
-
3.2.6: Using "should" in the Understanding doc is confusing w3c/wcag#1874.
-
2.5.8: Name Change w3c/wcag#1871.
-
What is a complex shape? w3c/wcag#2050.
-
Outdated links to UNDERSTANDING-WCAG20 in WCAG 2.1 and 2.2 w3c/wcag#1828.
-
Cleanup of the non-linked techniques. w3c/wcag#1245.
-
Question: Unnamed Fieldset and HTML Spec vs WCAG w3c/wcag#2140.
-
Outdated understanding documents still linger around w3c/wcag#1389.
-
2.5.8: Further Examples Required w3c/wcag#1872.
-
2.5.8: Minimum Component Size w3c/wcag#1870.
-
Align Target Size (min) with Target Size (enh) w3c/wcag#1721.
-
SC "level" label doesn't follow the reading order w3c/wcag#1428.
-
Avoid confusion about WCAG versions in the header w3c/wcag#1224.
-
WebauthN and passwordless w3c/wcag#2052.
-
Focus indicators for large editing areas w3c/wcag#2017.
-
Use of the word“state” is not sufficiently consistent w3c/wcag#2049.
-
SC 3.2.7 exception may not align with understanding text w3c/wcag#1980.
-
48 issues received 135 new comments.
-
H39 Using caption elements to associate data table captions with data tables needs a rewritten test w3c/wcag#2136 (14 comments by @alastc, @awkawk, @mbgower, @patrickhlauke)
-
Seeking confirmation that 2.4.6 applies also to headings & labels that are not visible w3c/wcag#2134 (9 comments by @detlevhfischer, @mraccess77, @patrickhlauke)
-
Avoid confusion about WCAG versions in the header w3c/wcag#1224 (9 comments by @alastc, @bruce-usab, @mbgower, @patrickhlauke, @Veyfeyken)
-
does a control that exposes an incorrect/inappropriate role fail 4.1.2 or not w3c/wcag#2142 (8 comments by @awkawk, @JAWS-test, @mraccess77, @patrickhlauke)
-
"Short" and "Long" can be misleading (SC 1.1.1) w3c/wcag#2117 (7 comments by @bruce-usab, @GreggVan, @MakotoUeki, @mraccess77)
-
Adobe Comment on 3.2.7 Visible Controls w3c/wcag#1888 (6 comments by @alastc, @mraccess77, @patrickhlauke)
-
Question: Unnamed Fieldset and HTML Spec vs WCAG w3c/wcag#2140 (4 comments by @JAWS-test, @LaurenceRLewis, @mraccess77, @patrickhlauke)
-
Clarify if SC 2.4.4 requires paragraph to be a P element in HTML w3c/wcag#2109 (4 comments by @detlevhfischer, @mraccess77, @scottaohara)
-
Technique G74, Title and Examples (SC 1.1.1) w3c/wcag#2129 (4 comments by @GreggVan, @mraccess77, @toddmarquisboutin)
-
Can we consider a technique to meet Focus appearance that exposes tooltips? w3c/wcag#2139 (3 comments by @mbgower, @mraccess77, @patrickhlauke)
-
WCAG 2.2 3.2.6 Consistent Help understanding - remove explanation of help mechanisms w3c/wcag#1881 (3 comments by @DavidMacDonald, @patrickhlauke)
-
Find a consistent phrase to use in Understanding documents for recommended approaches w3c/wcag#2148 (2 comments by @mraccess77, @patrickhlauke)
-
[WCAG 2.2 Feedback] Success Criterion 2.5.8 Target Size (Minimum) (Level AA) w3c/wcag#1894 (2 comments by @alastc, @DavidMacDonald)
-
Ensure heading level matches the heading's visual importance/level w3c/wcag#2141 (2 comments by @alastc, @JAWS-test)
-
3.2.7 Visible Controls - The examples provided on the “Understanding” page are not enough w3c/wcag#1443 (2 comments by @alastc, @mbgower)
-
clarifying whether swipe is a path-based gesture w3c/wcag#2116 (2 comments by @detlevhfischer, @patrickhlauke)
-
WCAG2.2: 3.2.7 Visible Controls (AA) - Confirmation on navigation menus w3c/wcag#1845 (2 comments by @alastc, @bruce-usab)
-
3.2.7: Subjective judgement is needed, and effort to test and remediate could be quite variable w3c/wcag#1877 (2 comments by @mbgower)
-
[WCAG 2.2 Draft Feedback] Remaining Review Process/Path to Recommendation? w3c/wcag#1897 (1 comment by @alastc)
-
SC 2.4.11: Make clearer the method of calculating the minimum area w3c/wcag#1883 (1 comment by @alastc)
-
Relationship between Use of colour, Non-text contrast, and Focus visible w3c/wcag#1847 (1 comment by @alastc)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.2.6 Consistent Help (A) w3c/wcag#1892 (1 comment by @alastc)
-
SC 2.5.8 Target Size (Minimum) - Is "24 by 24 CSS pixels” reasonable? w3c/wcag#1831 (1 comment by @alastc)
-
“Conformance Criterion” instead of “Conformance Requirement” used in the WCAG 2.1 Glossary w3c/wcag#1758 (1 comment by @DavidMacDonald)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.3.7 Accessible Authentication w3c/wcag#1890 (1 comment by @alastc)
-
WCAG 2.1 Understanding 2.3.1 - missing/vague dimension definitions w3c/wcag#585 (1 comment by @alastc)
-
Clarification on definition of "scrolling in two dimensions" in 1.4.10 w3c/wcag#2119 (1 comment by @JAWS-test)
-
-
15 pull requests opened.
-
Adding target area w3c/wcag#2147, by @alastc.
-
Yatil's suggestion w3c/wcag#2146, by @alastc.
-
Updated SC text w3c/wcag#2145, by @alastc.
-
Adjust to proposed change. w3c/wcag#2144, by @alastc.
-
update terminology: color blind w3c/wcag#2143, by @shawna-slh.
-
Moved some contents out of SC intent and added as additional benefit w3c/wcag#2138, by @a11ydoer.
-
Update H39.html w3c/wcag#2137, by @mbgower.
-
Update links for old trace.wisc.edu resources w3c/wcag#2132, by @patrickhlauke.
-
Updating technique placeholder w3c/wcag#2131, by @mbgower.
-
Update H99.html w3c/wcag#2130, by @mbgower.
-
Update three-flashes-or-below-threshold.html w3c/wcag#2127, by @mbgower.
-
altering bullet to make components persistent w3c/wcag#2125, by @mbgower.
-
Changes to remove redundancy w3c/wcag#2122, by @mbgower.
-
Updates from the meeting w3c/wcag#2121, by @alastc.
-
Adding suggestions from issue #1965 w3c/wcag#2120, by @fstrr.
-
-
10 pull requests merged.
-
Dragging understanding+tech rewording w3c/wcag#1954.
-
Target Size (Minimum) edits and addition of diagram w3c/wcag#2108.
-
Issue 1874 - removed the word should w3c/wcag#2021.
-
Link updates w3c/wcag#1830.
-
Aligning target size SCs w3c/wcag#2082.
-
target size of obscured targets w3c/wcag#2024.
-
Update links for old trace.wisc.edu resources w3c/wcag#2132.
-
Adding sentence on large text areas w3c/wcag#2081.
-
Updates from the meeting w3c/wcag#2121.
-
Issue1980 visible controls w3c/wcag#1990.
-
-
20 pull requests received 50 new comments.
-
Update three-flashes-or-below-threshold.html w3c/wcag#2127 (11 comments by @alastc, @mbgower, @patrickhlauke)
-
Moved some contents out of SC intent and added as additional benefit w3c/wcag#2138 (5 comments by @patrickhlauke)
-
Update links for old trace.wisc.edu resources w3c/wcag#2132 (3 comments by @alastc, @GreggVan, @patrickhlauke)
-
Target Size (Minimum) edits and addition of diagram w3c/wcag#2108 (2 comments by @detlevhfischer, @patrickhlauke)
-
w3c/wcag-act
-
1 issue closed.
-
Master w3c/wcag-act#523.
-
-
1 pull request opened.
-
Common aspects: CSS styling, use positive language w3c/wcag-act#524, by @WilcoFiers.
-
-
1 pull request received 27 new comments.
-
First attempt at defining implementations w3c/wcag-act#522 (27 comments by @HelenBurge, @Jym77, @kengdoj, @kherr-a11y, @tbostic32, @wcreedle, @WilcoFiers)
-
w3c/coga
-
1 issue opened.
-
Review language specific issues for v2.0 of Content Usable w3c/coga#310, by @rainbreaw.
-
-
2 issues closed.
-
Review Updated Personas w3c/coga#246.
-
Issues in some languages w3c/coga#248.
-
-
3 issues received 3 new comments.
-
Consider adding a persona "non-native speakers with limited language skills w3c/coga#162 (1 comment by @rainbreaw)
w3c/wcag3
-
1 issue opened.
-
Question about specifics in alternative text w3c/wcag3#251, by @rusteinberg.
-
-
3 issues received 3 new comments.
Cognitive and Learning Disabilities Accessibility Task Force
Past meetings
-
4 meetings of the Cognitive and Learning Disabilities Accessibility Task Force.
GitHub
w3c/coga
-
1 issue opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Review language specific issues for v2.0 of Content Usable w3c/coga#310, by @rainbreaw.
-
-
2 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Review Updated Personas w3c/coga#246.
-
Issues in some languages w3c/coga#248.
-
-
3 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 3 new comments.
-
Consider adding a persona "non-native speakers with limited language skills w3c/coga#162 (1 comment by @rainbreaw)
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
4 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Participants
-
3 participants joined the Accessibility Conformance Testing (ACT) Task Force.
-
Helen Burge joined.
-
Jennifer Chadwick joined.
-
Will Creedle joined.
-
Low Vision Accessibility Task Force
Participants
-
1 chair stepped down in the Low Vision Accessibility Task Force.
-
Chris Loiselle stepped down as a chair.
-
-
1 participant left the Low Vision Accessibility Task Force.
-
Chris Loiselle left.
-
Past meetings
-
10 meetings.
Participants
-
5 participants joined.
-
Qing An (Alibaba Group) joined.
-
mancang sun (Alibaba Group) joined.
-
brook sexton (Thomson Reuters Corp.) joined.
-
Will Creedle (Deque Systems, Inc.) joined.
-
Shadi Abou-Zahra (Amazon) joined.
-
-
2 participants left.
-
Hidde de Vries (W3C) left.
-
Monica Wegner (Thomson Reuters Corp.) left.
-
-
1 organization left.
-
Access2online Inc. left.
-
GitHub
w3c/wcag
-
29 issues opened.
-
G82 Technique title (SC 1.1.1) w3c/wcag#2118, by @MakotoUeki.
-
"Short" and "Long" can be misleading (SC 1.1.1) w3c/wcag#2117, by @MakotoUeki.
-
clarifying whether swipe is a path-based gesture w3c/wcag#2116, by @gundulaniemann.
-
SC 2.5.5 Understanding Doc has a typo (WCAG 2.1) w3c/wcag#2112, by @gjccopinga.
-
Clarify if SC 2.4.4 requires paragraph to be a P element in HTML w3c/wcag#2109, by @mraccess77.
-
Typo in Understanding SC 1.4.6 w3c/wcag#2105, by @gjccopinga.
-
MR Peter horvath w3c/wcag#2104, by @peter123Y.
-
Is there an intended minimum viewport size for 1.4.4? w3c/wcag#2101, by @daniel-montalvo.
-
Clarity on passes/fails for SC 3.2.7 Visible Controls w3c/wcag#2100, by @mraccess77.
-
Clarification: APAC being adopted for WCAG 2.x? w3c/wcag#2099, by @yatil.
-
Resolve understanding drafts for conflicts with updates w3c/wcag#2088, by @mbgower.
-
Clarify figure 11 in SC 2.4.11 understanding w3c/wcag#2085, by @mraccess77.
-
What is meant by programmatic markers in SC 2.4.13 w3c/wcag#2084, by @mraccess77.
-
Flashing content and CSS reliance w3c/wcag#2080, by @dd8.
-
Update H95 TTML and IMSC guidance w3c/wcag#2079, by @nigelmegitt.
-
2.5.5 understanding doc has an empty example w3c/wcag#2074, by @mattgarrish.
-
What does "content" mean in SC 1.4.10 Reflow w3c/wcag#2073, by @JAWS-test.
-
Visible controls w3c/wcag#2072, by @DavidMacDonald.
-
WCAG 2.2 Focus appearance & Visual examples w3c/wcag#2071, by @johnfoliot.
-
3.2.6 Consistent Help - Questions to resolve for consistent testing w3c/wcag#2068, by @goodwitch.
-
-
18 issues closed.
-
SC 2.5.5 Understanding Doc has a typo (WCAG 2.1) w3c/wcag#2112.
-
Typo in Understanding SC 1.4.6 w3c/wcag#2105.
-
MR Peter horvath w3c/wcag#2104.
-
Clarity on passes/fails for SC 3.2.7 Visible Controls w3c/wcag#2100.
-
Clarification: APAC being adopted for WCAG 2.x? w3c/wcag#2099.
-
Clarify figure 11 in SC 2.4.11 understanding w3c/wcag#2085.
-
What is meant by programmatic markers in SC 2.4.13 w3c/wcag#2084.
-
Adobe Comment on 2.4.11 Focus Appearance (minimum) w3c/wcag#1887.
-
-
48 issues received 188 new comments.
-
Use of the word“state” is not sufficiently consistent w3c/wcag#2049 (19 comments by @alastc, @bruce-usab, @JAWS-test, @patrickhlauke)
-
Visible Required label and 3.3.2: Labels or Instructions w3c/wcag#1698 (13 comments by @detlevhfischer, @mraccess77, @patrickhlauke)
-
3.2.6 Consistent Help - Questions to resolve for consistent testing w3c/wcag#2068 (12 comments by @alastc, @bruce-usab, @goodwitch, @melaniephilipp, @mraccess77, @patrickhlauke)
-
Can ENTER on seach field be accepted as conforming alternative to inaccessible control (loupe icon)? w3c/wcag#2069 (10 comments by @alastc, @detlevhfischer, @mraccess77, @patrickhlauke, @scottaohara)
-
What does "content" mean in SC 1.4.10 Reflow w3c/wcag#2073 (9 comments by @alastc, @JAWS-test, @mraccess77, @patrickhlauke)
-
1.4.10: If original page must be scrolled and unchanged at 320px - is that a violation of "Reflow"? w3c/wcag#2063 (9 comments by @alastc, @JAWS-test, @mraccess77, @patrickhlauke)
-
Autocomplete for passwords is discouraged for security concerns (WCAG 2.1 Success Criterion 1.3.5) w3c/wcag#2110 (8 comments by @alastc, @mraccess77, @patrickhlauke, @shawnthompson)
-
WCAG 2.2 2.5.8 - adding diagrams that make the reality/consequences of target offset clearer w3c/wcag#1848 (8 comments by @alastc, @colabottles, @detlevhfischer, @patrickhlauke)
-
Clarification: APAC being adopted for WCAG 2.x? w3c/wcag#2099 (7 comments by @bruce-usab, @mraccess77, @Myndex, @yatil)
-
Understanding 1.4.11 - symbolic text characters w3c/wcag#2062 (7 comments by @alastc, @fstrr, @JAWS-test, @patrickhlauke)
-
Focus indicators for large editing areas w3c/wcag#2017 (6 comments by @alastc, @bruce-usab, @mbgower, @mraccess77)
-
Is there an intended minimum viewport size for 1.4.4? w3c/wcag#2101 (6 comments by @alastc, @mraccess77, @patrickhlauke)
-
Figure 1 example 1 implies it passes adjacent contrast but that aspect might not apply to this SC 2.4.11 w3c/wcag#2087 (6 comments by @alastc, @mraccess77)
-
SC 2.4.13 Page break navigation for Web content: overly prescriptive? w3c/wcag#2026 (6 comments by @alastc, @DavidMacDonald, @mraccess77, @spanchang)
-
"Short" and "Long" can be misleading (SC 1.1.1) w3c/wcag#2117 (4 comments by @bruce-usab, @mraccess77, @patrickhlauke)
-
Clarify in understanding SC 2.4.2 Page Title applicability to single page applications w3c/wcag#2102 (4 comments by @mraccess77, @patrickhlauke)
-
F87 and ARIA 24 seem to contradict in the use of CSS content property w3c/wcag#1554 (4 comments by @dd8, @patrickhlauke)
-
Clarify in 3.3.8 Redundant Entry understanding document "available for the user to select." w3c/wcag#1973 (3 comments by @alastc, @mraccess77)
-
Clarify if comparing focus and unfocused state in SC 2.4.11 applies with outset indicators w3c/wcag#2086 (3 comments by @alastc, @mraccess77)
-
Clarity on passes/fails for SC 3.2.7 Visible Controls w3c/wcag#2100 (2 comments by @alastc, @patrickhlauke)
-
What is meant by programmatic markers in SC 2.4.13 w3c/wcag#2084 (2 comments by @alastc, @mraccess77)
-
3.2.2 On Input guidance relating to select change triggering page reload w3c/wcag#2076 (2 comments by @jamesjacobs, @patrickhlauke)
-
incorporate style changes and some readability edits for multiple SCs w3c/wcag#2030 (1 comment by @mbgower)
-
Add some actionable advice to "Large scale (text) > Note 1" in the glossary w3c/wcag#228 (1 comment by @patrickhlauke)
-
Link purpose (2.4.4 and 2.4.9) "ambiguous to users in general" is self-defeating w3c/wcag#1149 (1 comment by @patrickhlauke)
-
Focus Appearance (Minimum) 2.4.11 move from Operable to Perceivable, also 2.4.7 and 2.4.12 w3c/wcag#2037 (1 comment by @alastc)
-
[WCAG 2.2 Feedback] Success Criterion 2.5.8 Target Size (Minimum) (Level AA) w3c/wcag#1894 (1 comment by @alastc)
-
How should 2.4.11 / 2.4.12 be applied to inline elements that wrap over multiple lines? w3c/wcag#1328 (1 comment by @alastc)
-
Sufficient technique H63 should incorporate HTML5 and address missing info w3c/wcag#2077 (1 comment by @patrickhlauke)
-
Minimum Area shape requirement could use attention, Focus Appearance (Minimum) w3c/wcag#1928 (1 comment by @alastc)
-
Does the Definition of "Dragging Movements" Intentionally Limit the Scope to Moving Objects/Items? w3c/wcag#1560 (1 comment by @detlevhfischer)
-
-
24 pull requests opened.
-
Adding suggestion from 2068 w3c/wcag#2115, by @alastc.
-
Correct 2.5.5 understanding with correct SC number w3c/wcag#2114, by @patrickhlauke.
-
Issue2017 editing area wording changes w3c/wcag#2111, by @mbgower.
-
Target Size (Minimum) edits and addition of diagram w3c/wcag#2108, by @colabottles.
-
Adding link for essential w3c/wcag#2103, by @alastc.
-
Update focus-appearance-minimum.html w3c/wcag#2097, by @mbgower.
-
Fix some SCs numbers in Understanding document w3c/wcag#2096, by @Jym77.
-
Update visible-controls.html w3c/wcag#2095, by @mbgower.
-
Update page-break-navigation.html w3c/wcag#2094, by @mbgower.
-
Update focus-appearance-enhanced.html w3c/wcag#2093, by @mbgower.
-
Consistent Help understanding and technique edits w3c/wcag#2092, by @mbgower.
-
Update accessible-authentication.html w3c/wcag#2091, by @mbgower.
-
Wcag22 typos and editorial w3c/wcag#2089, by @alastc.
-
Additions/tweaks to 1.4.3 understanding w3c/wcag#2083, by @patrickhlauke.
-
Aligning target size SCs w3c/wcag#2082, by @alastc.
-
Adding sentence on large text areas w3c/wcag#2081, by @alastc.
-
Shuffling target size files w3c/wcag#2075, by @alastc.
-
focus-apperance alternative proposal w3c/wcag#2070, by @WilcoFiers.
-
Add section on symbolic text characters to 1.4.11 understanding w3c/wcag#2067, by @patrickhlauke.
-
Dragging rects and connector lines w3c/wcag#2066, by @detlevhfischer.
-
Dragging and click lock functionality w3c/wcag#2065, by @detlevhfischer.
-
-
13 pull requests merged.
-
Issue2017 editing area wording changes w3c/wcag#2111.
-
Correct 2.5.5 understanding with correct SC number w3c/wcag#2114.
-
Adding link for essential w3c/wcag#2103.
-
Changing the NTC section w3c/wcag#2060.
-
Update focus-appearance-minimum.html w3c/wcag#2097.
-
Removing complexity w3c/wcag#2051.
-
Update focus-appearance-enhanced.html w3c/wcag#2093.
-
Update accessible-authentication.html w3c/wcag#2091.
-
Wcag22 typos and editorial w3c/wcag#2089.
-
Re-doing the border aspect. w3c/wcag#2040.
-
focus-apperance alternative proposal w3c/wcag#2070.
-
-
2 pull requests closed.
-
Updates from meeting w3c/wcag#2059.
-
17 pull requests received 53 new comments.
-
Target Size (Minimum) edits and addition of diagram w3c/wcag#2108 (24 comments by @colabottles, @detlevhfischer, @patrickhlauke)
-
Add two notes/clarifications to 2.1.1/2.1.3 understanding w3c/wcag#1642 (6 comments by @bruce-usab, @JAWS-test, @patrickhlauke)
-
🎨 Add redesign of Techniques, Understanding templates w3c/wcag#2012 (5 comments by @GreggVan, @hidde, @michael-n-cooper, @mraccess77, @rianrietveld)
-
Correct 2.5.5 understanding with correct SC number w3c/wcag#2114 (2 comments by @alastc, @patrickhlauke)
-
Add explicit mention of SPAs and dynamic changes of title to 2.4.2 understanding w3c/wcag#2107 (2 comments by @mraccess77, @patrickhlauke)
-
Update Link Purpose (in Context) understanding benefits to focus on AT w3c/wcag#1164 (1 comment by @patrickhlauke)
-
w3c/wcag3
-
1 issue received 3 new comments.
-
What is the method for calculating the APCA CONTRAST LOOKUP TABLE, for a given score level / use case w3c/wcag3#253 (3 comments by @Myndex, @sdw32)
-
w3c/wcag-act
-
1 issue opened.
-
Master w3c/wcag-act#523, by @Ken125pig.
-
-
1 pull request opened.
-
First attempt at defining implementations w3c/wcag-act#522, by @WilcoFiers.
-
-
2 pull requests merged.
-
Update CSS Styling input aspect w3c/wcag-act#520.
-
Add note about language w3c/wcag-act#521.
-
-
3 pull requests received 16 new comments.
Low Vision Accessibility Task Force
Participants
-
1 participant joined the Low Vision Accessibility Task Force.
-
Daniele Marano joined.
-
GitHub
w3c/low-vision-a11y-tf
-
1 issue closed in the Low Vision Accessibility Task Force.
-
3 issues in the Low Vision Accessibility Task Force received 6 new comments.
-
Action: Update https://www.w3.org/WAI/GL/low-vision-a11y-tf/work-statement.php w3c/low-vision-a11y-tf#89 (1 comment by @ChrisLoiselle)
-
Determine if the issues listed on https://github.com/w3c/low-vision-a11y-tf/issues stay open or if we can close these issues. w3c/low-vision-a11y-tf#96 (1 comment by @ChrisLoiselle)
-
1 pull request opened in the Low Vision Accessibility Task Force.
-
Assigning proximity to @lauracarlson. w3c/low-vision-a11y-tf#132, by @lauracarlson.
-
-
1 pull request merged in the Low Vision Accessibility Task Force.
-
Assigning proximity to @lauracarlson. w3c/low-vision-a11y-tf#132.
-
-
1 pull request reopened in the Low Vision Accessibility Task Force.
-
[outdated - OK to close?] Added items, descriptions, and author w3c/low-vision-a11y-tf#104, by @shawna-slh.
-
-
1 pull request in the Low Vision Accessibility Task Force received 1 new comment.
-
[outdated - OK to close?] Added items, descriptions, and author w3c/low-vision-a11y-tf#104 (1 comment by @shawna-slh)
-
Cognitive and Learning Disabilities Accessibility Task Force
Past meetings
-
4 meetings of the Cognitive and Learning Disabilities Accessibility Task Force.
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
5 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Past meetings
-
8 meetings.
Participants
-
1 Team contact stepped down.
-
Shadi Abou-Zahra stepped down as a Team contact.
-
-
5 participants joined.
-
Hedda Peters (Arkose Labs, Inc.) joined.
-
Laura Miller (W3C Invited Experts) joined.
-
Jeff Kline (W3C Invited Experts) joined.
-
Carlos Duarte (Universidade de Lisboa - ULisboa) joined.
-
Julie Rawe (Understood.org) joined.
-
-
4 participants left.
-
Shadi Abou-Zahra (Amazon) left.
-
Kasper Isager Dalsgarð (Siteimprove) left.
-
Todd Libby (W3C Invited Experts) left.
-
Allie Bogus (Understood.org) left.
-
-
2 organizations joined.
-
Arkose Labs, Inc. joined.
-
Universidade de Lisboa - ULisboa joined.
-
GitHub
w3c/wcag
-
18 issues opened.
-
Understanding 1.4.11 - symbolic text characters w3c/wcag#2062, by @fstrr.
-
Understanding 1.4.11 - recent additional image incorrect w3c/wcag#2061, by @patrickhlauke.
-
WebauthN and passwordless w3c/wcag#2052, by @alastc.
-
What is a complex shape? w3c/wcag#2050, by @awkawk.
-
Use of the word“state” is not sufficiently consistent w3c/wcag#2049, by @bruce-usab.
-
Using aria-hidden to remove content from the accessibility tree w3c/wcag#2041, by @kherr-a11y.
-
Understanding for Contrast does not call out Color Blindness w3c/wcag#2033, by @bruce-usab.
-
incorporate style changes and some readability edits for multiple SCs w3c/wcag#2030, by @mbgower.
-
SC 2.4.13 Page break navigation for Web content: overly prescriptive? w3c/wcag#2026, by @spanchang.
-
Applicability of map markings to SC 1.4.11 w3c/wcag#2025, by @mraccess77.
-
-
15 issues closed.
-
Focus Appearance (Minimum) Understanding document challenges w3c/wcag#1930.
-
3.3.7 - Defining common objects w3c/wcag#1902.
-
Focus appearance is impresise and fairly complicated w3c/wcag#1718.
-
Update Technique G195 procedure w3c/wcag#1931.
-
2.4.11: Gradient Focus Indicators w3c/wcag#1861.
-
-
47 issues received 170 new comments.
-
Does SC 2.5.3 fail when there is a visual text label but the control has no accessible name? w3c/wcag#2045 (20 comments by @alastc, @bruce-usab, @jake-abma, @mraccess77, @patrickhlauke, @scottaohara)
-
Focus indicators for large editing areas w3c/wcag#2017 (17 comments by @alastc, @anevins12, @bruce-usab, @DavidMacDonald, @mraccess77, @patrickhlauke, @rainbreaw)
-
Use of the word“state” is not sufficiently consistent w3c/wcag#2049 (15 comments by @alastc, @bruce-usab, @mbgower, @mraccess77, @patrickhlauke)
-
Do skeleton loaders fall under “inactive” exemption of 1.4.11 Non-Text Contrast? w3c/wcag#2048 (15 comments by @aardrian, @alastc, @bruce-usab, @mraccess77, @patrickhlauke, @scottaohara)
-
Focus Appearance (Minimum) 2.4.11 move from Operable to Perceivable, also 2.4.7 and 2.4.12 w3c/wcag#2037 (9 comments by @alastc, @jake-abma, @mraccess77, @patrickhlauke)
-
Understanding for Contrast does not call out Color Blindness w3c/wcag#2033 (6 comments by @bruce-usab, @mraccess77, @Myndex)
-
3.3.7 - Defining common objects w3c/wcag#1902 (6 comments by @abijames, @alastc, @ghost, @lseeman, @rachaelbradley)
-
Do toggle buttons not require the aria-pressed attribute in their markup? w3c/wcag#2038 (6 comments by @JAWS-test, @patrickhlauke, @sivakusayan)
-
Text spacing: does it require compatibility with one or all methods? w3c/wcag#975 (5 comments by @AshankGG, @mraccess77, @patrickhlauke)
-
Focus Appearance (Minimum) needs more info on adjacent contrast w3c/wcag#1929 (4 comments by @alastc, @mraccess77)
-
Chromium autocomplete behaviour now incompatible with Input Purpose & security w3c/wcag#2032 (4 comments by @alastc, @JAWS-test, @patrickhlauke)
-
Understanding doc contradicts SC2.4.5 Multiple ways w3c/wcag#1077 (3 comments by @joelanman, @patrickhlauke, @yatil)
-
Conformance WCAG 3: Counting passing issues and documenting is poor use of a company's budget w3c/wcag#2058 (3 comments by @jake-abma, @jongund, @mraccess77)
-
WCAG 2.2 2.5.8: add the (possibly redundant) mention of "pointer inputs" to match 2.5.5 w3c/wcag#1832 (3 comments by @jenstrickland, @patrickhlauke)
-
SC 2.4.13 Page break navigation for Web content: overly prescriptive? w3c/wcag#2026 (3 comments by @alastc, @spanchang)
-
Sanity check focusable items under cookie notification 2.4.11 Focus Appearance (Minimum) w3c/wcag#2015 (3 comments by @alastc, @mraccess77)
-
Language of 1.4.10/Reflow exception seems broader than intended w3c/wcag#1049 (3 comments by @mbgower, @patrickhlauke, @scottaohara)
-
Accessible Authentication needs better techniques w3c/wcag#1916 (3 comments by @JohnRochfordUMMS, @shawnthompson)
-
Align Target Size (min) with Target Size (enh) w3c/wcag#1721 (2 comments by @jenstrickland, @patrickhlauke)
-
Minimum Area shape requirement could use attention, Focus Appearance (Minimum) w3c/wcag#1928 (2 comments by @alastc, @mbgower)
-
Separate requirements from exceptions in 2.2.1 Timing Adjustable w3c/wcag#1971 (2 comments by @bruce-usab, @mattgarrish)
-
Is "Not fully obscured:" from SC 2.4.11 already covered by SC 2.4.7 w3c/wcag#2023 (2 comments by @alastc, @mraccess77)
-
[WCAG 2.2 Feedback] Success Criterion 2.5.8 Target Size (Minimum) (Level AA) w3c/wcag#1894 (1 comment by @jenstrickland)
-
SC 2.5.8 Target Size (Minimum) - Is "24 by 24 CSS pixels” reasonable? w3c/wcag#1831 (1 comment by @jenstrickland)
-
Does only the initial state obscured clause of SC 2.4.11 also apply to SC 2.4.12? w3c/wcag#1982 (1 comment by @alastc)
-
[WCAG 2.2 Feedback] Success Criterion 2.4.11 Focus Appearance (Minimum) (Level AA) w3c/wcag#1896 (1 comment by @alastc)
-
Understanding doc for section headings uses two different meanings of section w3c/wcag#2035 (1 comment by @patrickhlauke)
-
2.4.11: Confusing wording due to unconventional state requirement w3c/wcag#1859 (1 comment by @alastc)
-
Does the Definition of "Dragging Movements" Intentionally Limit the Scope to Moving Objects/Items? w3c/wcag#1560 (1 comment by @SuzanneTaylor)
-
-
16 pull requests opened.
-
Changing the NTC section w3c/wcag#2060, by @alastc.
-
Updates from meeting w3c/wcag#2059, by @alastc.
-
Fix focus appearance typo w3c/wcag#2056, by @WilcoFiers.
-
Removing complexity w3c/wcag#2051, by @awkawk.
-
Removing overlapping content w3c/wcag#2046, by @alastc.
-
Outlining non-scoped things. w3c/wcag#2044, by @alastc.
-
Updates to resolve #1902 w3c/wcag#2042, by @rachaelbradley.
-
Re-doing the border aspect. w3c/wcag#2040, by @alastc.
-
Tweak section headings understanding wording w3c/wcag#2036, by @patrickhlauke.
-
Update contrast-minimum.html w3c/wcag#2034, by @bruce-usab.
-
Update work-statement.php w3c/wcag#2031, by @daniel-montalvo.
-
Update visible-controls.html w3c/wcag#2029, by @mbgower.
-
Non-text contrast update w3c/wcag#2028, by @alastc.
-
Update focus-appearance-minimum.html w3c/wcag#2027, by @mbgower.
-
target size of obscured targets w3c/wcag#2024, by @detlevhfischer.
-
-
9 pull requests merged.
-
Update work-statement.php w3c/wcag#2031.
-
Updates to resolve #1902 w3c/wcag#2042.
-
Updating G195, and separating a technique for focus-app-enh w3c/wcag#2004.
-
Removing overlapping content w3c/wcag#2046.
-
Non-text contrast update w3c/wcag#2028.
-
Focus-appearance min understanding updates w3c/wcag#2000.
-
Update focus-appearance-minimum.html w3c/wcag#2027.
-
Update reflow.html w3c/wcag#1656.
-
Update G219.html w3c/wcag#1975.
-
-
1 pull request closed.
-
G195 test adjustment w3c/wcag#1473.
-
-
20 pull requests received 56 new comments.
-
Update contrast-minimum.html w3c/wcag#2034 (10 comments by @alastc, @bruce-usab, @mbgower, @mraccess77, @Myndex, @patrickhlauke)
-
Review of Understanding documents for consistency and readability w3c/wcag#1834 (8 comments by @mbgower, @patrickhlauke)
-
Updating G195, and separating a technique for focus-app-enh w3c/wcag#2004 (4 comments by @patrickhlauke)
-
2.5.3 - control with label but no accname (understanding note + new failure technique) w3c/wcag#2057 (3 comments by @detlevhfischer, @jake-abma, @mraccess77)
-
w3c/wcag-act
-
2 pull requests opened.
-
Add note about language w3c/wcag-act#521, by @Jym77.
-
Update CSS Styling input aspect w3c/wcag-act#520, by @carlosapaduarte.
-
w3c/wcag3
-
3 issues opened.
-
2.4.6 complicated by works of fiction w3c/wcag3#170, by @mattgarrish.
-
UsableNet Feedback/Input on Representative Sample w3c/wcag3#252, by @UsableNet-WCAG.
-
3 issues received 21 new comments.
-
2.4.6 complicated by works of fiction w3c/wcag3#170 (12 comments by @bruce-usab, @JAWS-test, @mattgarrish, @patrickhlauke, @scottaohara)
-
Form / Input Errors Vs. states Vs. 1.4.11 Non-text Contrast Vs. 2.4.11 Focus Appearance (Minimum) w3c/wcag3#169 (6 comments by @bruce-usab, @jake-abma, @patrickhlauke)
-
Contrast Ratio Math and Related Visual Issues w3c/wcag3#192 (3 comments by @bruce-usab, @GreggVan, @Myndex)
-
w3c/coga
-
2 issues received 2 new comments.
-
Consider adding a persona "non-native speakers with limited language skills w3c/coga#162 (1 comment by @JaninaSajka)
-
1 pull request merged.
-
1 pull request received 1 new comment.
-
Restructured design guide source of content-usable for Web version w3c/coga#309 (1 comment by @SteveALee)
-
Low Vision Accessibility Task Force
Participants
-
1 participant left the Low Vision Accessibility Task Force.
-
Todd Libby left.
-
GitHub
w3c/low-vision-a11y-tf
-
2 issues opened in the Low Vision Accessibility Task Force.
-
Supplemental Guidance Pull Request Question w3c/low-vision-a11y-tf#105, by @Myndex.
-
WCAG 2.2 — Comment on a pending Pull Request w3c/low-vision-a11y-tf#100, by @Myndex.
-
-
1 issue closed in the Low Vision Accessibility Task Force.
-
Supplemental Guidance Pull Request Question w3c/low-vision-a11y-tf#105.
-
-
7 issues in the Low Vision Accessibility Task Force received 12 new comments.
-
Possibly adding SCs to WCAG 2.3 - Lc tool ? w3c/low-vision-a11y-tf#97 (5 comments by @mraccess77, @Myndex)
-
creating an exception for large scale text from having to meet the requirements significantly reduces the usefulness of the SC 1.4.4 Resize Text w3c/low-vision-a11y-tf#98 (1 comment by @Myndex)
-
Determine if the issues listed on https://github.com/w3c/low-vision-a11y-tf/issues stay open or if we can close these issues. w3c/low-vision-a11y-tf#96 (1 comment by @Myndex)
-
Action: Update https://www.w3.org/WAI/GL/low-vision-a11y-tf/work-statement.php w3c/low-vision-a11y-tf#89 (1 comment by @Myndex)
-
-
2 pull requests opened in the Low Vision Accessibility Task Force.
-
Create example.md w3c/low-vision-a11y-tf#113, by @bruce-usab.
-
[outdated - OK to close?] Added items, descriptions, and author w3c/low-vision-a11y-tf#104, by @Myndex.
-
-
1 pull request in the Low Vision Accessibility Task Force received 2 new comments.
-
[outdated - OK to close?] Added items, descriptions, and author w3c/low-vision-a11y-tf#104 (2 comments by @Myndex, @shawna-slh)
-
Mobile Accessibility Task Force
Participants
-
1 participant left the Mobile Accessibility Task Force.
-
Shadi Abou-Zahra left.
-
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
5 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Participants
-
1 Team contact stepped down in the Accessibility Conformance Testing (ACT) Task Force.
-
Shadi Abou-Zahra stepped down as a Team contact.
-
-
2 participants left the Accessibility Conformance Testing (ACT) Task Force.
-
Shadi Abou-Zahra left.
-
Todd Libby left.
-
Cognitive and Learning Disabilities Accessibility Task Force
Past meetings
-
4 meetings of the Cognitive and Learning Disabilities Accessibility Task Force.
Participants
-
1 participant joined the Cognitive and Learning Disabilities Accessibility Task Force.
-
Julie Rawe joined.
-
-
1 participant left the Cognitive and Learning Disabilities Accessibility Task Force.
-
Allie Bogus left.
-
GitHub
w3c/coga
-
2 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 2 new comments.
-
Consider adding a persona "non-native speakers with limited language skills w3c/coga#162 (1 comment by @JaninaSajka)
-
1 pull request merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
1 pull request in the Cognitive and Learning Disabilities Accessibility Task Force received 1 new comment.
-
Restructured design guide source of content-usable for Web version w3c/coga#309 (1 comment by @SteveALee)
-
Past meetings
Participants
-
5 participants joined.
-
Breixo Pastoriza Barcia (Glocal Quality Solutions) joined.
-
Andrew Nevins (TPGi) joined.
-
Bhoomika Bhagchandani (W3C Invited Experts) joined.
-
Alistair Garrison (W3C Invited Experts) joined.
-
Sam Waller (W3C Invited Experts) joined.
-
-
1 participant left.
-
Rupa Jaganathan (SAP SE) left.
-
-
1 organization joined.
-
Glocal Quality Solutions joined.
-
GitHub
w3c/coga
-
6 issues opened.
-
Missing "User Need" heading in Design Guide part of content-usable w3c/coga#308, by @SteveALee.
-
Use GitHub action instead of Travis CI w3c/coga#306, by @plehegar.
-
"high potential" in "B.2 Business Considerations" w3c/coga#305, by @MakotoUeki.
-
Clarification of "a process is in place for acting on it" w3c/coga#304, by @MakotoUeki.
-
"feedback" in "5.5.7 Is there Enough Help and Support?" w3c/coga#303, by @MakotoUeki.
-
-
2 issues received 3 new comments.
-
Missing "User Need" heading in Design Guide part of content-usable w3c/coga#308 (1 comment by @SteveALee)
-
1 pull request opened.
-
Restructured design guide source of content-usable for Web version w3c/coga#309, by @SteveALee.
-
w3c/wcag
-
24 issues opened.
-
Is "Not fully obscured:" from SC 2.4.11 already covered by SC 2.4.7 w3c/wcag#2023, by @mraccess77.
-
Language level and inclusion. 3.1.5 w3c/wcag#2022, by @paul-poupet.
-
Focus indicators for large editing areas w3c/wcag#2017, by @alastc.
-
Do titles have to be unique on a site? w3c/wcag#2013, by @joelanman.
-
Should linked logotypes in headers fulfill 2.5.3 Label in Name? w3c/wcag#2011, by @yatil.
-
Title, headings and language in relation to iframes w3c/wcag#2008, by @medeaoblongata.
-
Video players with controls that auto-dismiss w3c/wcag#2007, by @scottaohara.
-
2.4.11 Editor's note wording w3c/wcag#2006, by @detlevhfischer.
-
Changing the base.css w3c/wcag#2001, by @rukundob451.
-
Understanding SC 4.1.1 mentions SC 1.4.2 'Resize text' w3c/wcag#1999, by @sander-nl.
-
Typo 'contasts' in Understanding SC 1.4.11 (WCAG 2.1) w3c/wcag#1996, by @cstrobbe.
-
Changes needed: ARIA6: Using aria-label to provide labels for objects w3c/wcag#1987, by @spanchang.
-
Changes needed for ARIA8: Using aria-label for link purpose w3c/wcag#1985, by @spanchang.
-
Broken link(s) w3c/wcag#1983, by @shawna-slh.
-
Obscured part of SC 2.4.12 understanding text conflicts with SC w3c/wcag#1981, by @mraccess77.
-
SC 3.2.7 exception may not align with understanding text w3c/wcag#1980, by @mraccess77.
-
-
20 issues closed.
-
2.4.11 Editor's note wording w3c/wcag#2006.
-
2.4.13: Is EPUB Web Content? w3c/wcag#1869.
-
Does redundant entry require saving PII? w3c/wcag#1843.
-
Consistent Help note doesn't make sense to me w3c/wcag#1924.
-
Changing the base.css w3c/wcag#2001.
-
Understanding SC 4.1.1 mentions SC 1.4.2 'Resize text' w3c/wcag#1999.
-
2.4.11: Text below figure figure 11 w3c/wcag#1865.
-
Typo 'contasts' in Understanding SC 1.4.11 (WCAG 2.1) w3c/wcag#1996.
-
2.4.11: Gradient Backgrounds w3c/wcag#1862.
-
2.4.11 and browser default focus indicators w3c/wcag#1854.
-
2.4.11 Focus Appearance (Minimum) (AA) - Minimum Area w3c/wcag#1806.
-
Adobe Comment on 2.5.8 Target Size (Minimum) w3c/wcag#1889.
-
63 issues received 149 new comments.
-
Sanity check focusable items under cookie notification 2.4.11 Focus Appearance (Minimum) w3c/wcag#2015 (15 comments by @alastc, @detlevhfischer, @jake-abma, @mraccess77, @patrickhlauke)
-
Should linked logotypes in headers fulfill 2.5.3 Label in Name? w3c/wcag#2011 (10 comments by @alastc, @detlevhfischer, @jake-abma, @patrickhlauke, @yatil)
-
3.3.7 - Defining common objects w3c/wcag#1902 (7 comments by @alastc, @mraccess77, @rachaelbradley, @rainbreaw)
-
Video players with controls that auto-dismiss w3c/wcag#2007 (6 comments by @mraccess77, @patrickhlauke, @scottaohara)
-
Sanity check 2.4.3 Focus Order and cookie notification at bottom gets first focus w3c/wcag#2016 (5 comments by @jake-abma, @mraccess77, @patrickhlauke)
-
Changes Needed: ARIA14 Using aria-label to provide an invisible label where a visible label cannot be used w3c/wcag#1986 (5 comments by @alastc, @patrickhlauke, @spanchang)
-
1.3.1 and Lists and the notorious "or are available in text" w3c/wcag#1974 (4 comments by @alastc, @bruce-usab, @goodwitch, @patrickhlauke)
-
2.4.11 and browser default focus indicators w3c/wcag#1854 (3 comments by @alastc, @escetic, @mbgower)
-
Title, headings and language in relation to iframes w3c/wcag#2008 (3 comments by @alastc, @medeaoblongata, @mraccess77)
-
Clarify in 3.3.8 Redundant Entry understanding document "available for the user to select." w3c/wcag#1973 (3 comments by @alastc, @mraccess77)
-
Are 'Headings' enough to pass 2.4.1: Bypass Blocks w3c/wcag#1712 (3 comments by @BillDashfield, @MarcHaunschild, @patrickhlauke)
-
Changes needed for ARIA8: Using aria-label for link purpose w3c/wcag#1985 (3 comments by @alastc, @spanchang)
-
Changes needed: ARIA6: Using aria-label to provide labels for objects w3c/wcag#1987 (3 comments by @patrickhlauke, @spanchang)
-
2.4.11: Confusing wording due to unconventional state requirement w3c/wcag#1859 (2 comments by @alastc, @DavidMacDonald)
-
Suggested rewording to normative text of Visible Controls w3c/wcag#1932 (2 comments by @DavidMacDonald, @detlevhfischer)
-
WCAG 2.2 - 3.2.7 Visible Controls (AA) - difficult to understand meaning w3c/wcag#1840 (2 comments by @alastc, @yatil)
-
Does only the initial state obscured clause of SC 2.4.11 also apply to SC 2.4.12? w3c/wcag#1982 (2 comments by @alastc, @mraccess77)
-
Obscured part of SC 2.4.12 understanding text conflicts with SC w3c/wcag#1981 (2 comments by @alastc, @patrickhlauke)
-
SC 2.4.11: Make clearer the method of calculating the minimum area w3c/wcag#1883 (2 comments by @alastc)
-
Accessible Authentication needs better techniques w3c/wcag#1916 (2 comments by @alastc, @shawnthompson)
-
Is a video player considered a single component for purposes of single character shortcuts SC 2.1.4? w3c/wcag#1950 (2 comments by @detlevhfischer, @mraccess77)
-
3.3.8: Ensuring single transactions (from the user's perspective) are covered w3c/wcag#1880 (2 comments by @alastc)
-
SC 2.4.11 Focus Appearance fails to explain why authors are better enbled than UA at solving this w3c/wcag#1911 (2 comments by @alastc, @rainbreaw)
-
Separate requirements from exceptions in 2.2.1 Timing Adjustable w3c/wcag#1971 (2 comments by @alastc, @patrickhlauke)
-
2.4.11: Insufficient requirement for focus indication via enlargement w3c/wcag#1858 (1 comment by @DavidMacDonald)
-
3.2.6: Using "should" in the Understanding doc is confusing w3c/wcag#1874 (1 comment by @DavidMacDonald)
-
WCAG2.2: 3.2.7 Visible Controls (AA) - Confirmation on navigation menus w3c/wcag#1845 (1 comment by @alastc)
-
How should 2.4.11 / 2.4.12 be applied to inline elements that wrap over multiple lines? w3c/wcag#1328 (1 comment by @alastc)
-
Focus Appearance (Minimum) needs more info on adjacent contrast w3c/wcag#1929 (1 comment by @alastc)
-
Link to 'MathML version of the relative luminance definition' directs to a 404 page w3c/wcag#2014 (1 comment by @alastc)
-
3.2.7 Visible Controls - The examples provided on the “Understanding” page are not enough w3c/wcag#1443 (1 comment by @alastc)
-
Contents of language attribute on HTML element missing in Techniques w3c/wcag#2005 (1 comment by @hidde)
-
SC 2.5.7 Dragging exceptions seems like example of free form paths rather than dragging w3c/wcag#1979 (1 comment by @detlevhfischer)
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.4.13: Page Break Navigation (A) w3c/wcag#1893 (1 comment by @alastc)
-
Minimum Area shape requirement could use attention, Focus Appearance (Minimum) w3c/wcag#1928 (1 comment by @alastc)
-
[WCAG 2.2 Feedback] Success Criterion 2.4.11 Focus Appearance (Minimum) (Level AA) w3c/wcag#1896 (1 comment by @alastc)
-
-
22 pull requests opened.
-
Issue 1874 - removed the word should w3c/wcag#2021, by @DavidMacDonald.
-
Issue 1932 Gramatical rewrite of visible controls w3c/wcag#2020, by @DavidMacDonald.
-
Initial re-write of SC text w3c/wcag#2019, by @alastc.
-
Aligning to the SC text w3c/wcag#2018, by @alastc.
-
🎨 Add redesign of Techniques, Understanding templates w3c/wcag#2012, by @hidde.
-
Add redesign of Techniques/Understanding templates w3c/wcag#2010, by @hidde.
-
dragging movements 3rd example w3c/wcag#2009, by @detlevhfischer.
-
Updating G195, and separating a technique for focus-app-enh w3c/wcag#2004, by @alastc.
-
Update dragging-movements.html w3c/wcag#2003, by @detlevhfischer.
-
Update base.css w3c/wcag#2002, by @rukundob451.
-
Focus-appearance min understanding updates w3c/wcag#2000, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1998, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1997, by @alastc.
-
Adding pbl scope statement w3c/wcag#1995, by @alastc.
-
Adding scope statement to understanding w3c/wcag#1994, by @alastc.
-
Target Size addition of user agent and equivalent exceptions w3c/wcag#1993, by @mbgower.
-
Removing session, scoping in 3rd party providers w3c/wcag#1992, by @alastc.
-
Keep session, scoping 3rd parties out w3c/wcag#1991, by @alastc.
-
Issue1980 visible controls w3c/wcag#1990, by @alastc.
-
Adding suggested text w3c/wcag#1989, by @alastc.
-
Paragraph update w3c/wcag#1988, by @alastc.
-
Consistent help 1924 w3c/wcag#1984, by @rachaelbradley.
-
-
12 pull requests merged.
-
Aligning to the SC text w3c/wcag#2018.
-
Adding pbl scope statement w3c/wcag#1995.
-
Adding scope statement to understanding w3c/wcag#1994.
-
Removing session, scoping in 3rd party providers w3c/wcag#1992.
-
Update consistent-help.html w3c/wcag#1968.
-
Consistent help 1924 w3c/wcag#1984.
-
Wcag22 typos and editorial w3c/wcag#1998.
-
Wcag22 typos and editorial w3c/wcag#1997.
-
David's suggested update w3c/wcag#1967.
-
Updating min area w3c/wcag#1966.
-
Target size min legal exception w3c/wcag#1955.
-
-
2 pull requests closed.
-
Add redesign of Techniques/Understanding templates w3c/wcag#2010.
-
Keep session, scoping 3rd parties out w3c/wcag#1991.
-
-
8 pull requests received 12 new comments.
-
Target Size addition of user agent and equivalent exceptions w3c/wcag#1993 (4 comments by @detlevhfischer, @mraccess77, @patrickhlauke)
-
w3c/wcag3
-
5 issues opened.
-
Trusted Tester comment on WCAG3 draft: Conformance Levels w3c/wcag3#254, by @kengdoj.
-
Trusted Tester sampling guidance w3c/wcag3#255, by @kengdoj.
-
Measures for "clear words" w3c/wcag3#247, by @JonathanPaulKatz.
-
Glossary Terms in Methods (Normative versus Non-Normative) w3c/wcag3#256, by @johnfoliot.
-
2 issues received 2 new comments.
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
6 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Missing "User Need" heading in Design Guide part of content-usable w3c/coga#308, by @SteveALee.
-
Use GitHub action instead of Travis CI w3c/coga#306, by @plehegar.
-
"high potential" in "B.2 Business Considerations" w3c/coga#305, by @MakotoUeki.
-
Clarification of "a process is in place for acting on it" w3c/coga#304, by @MakotoUeki.
-
"feedback" in "5.5.7 Is there Enough Help and Support?" w3c/coga#303, by @MakotoUeki.
-
-
2 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 3 new comments.
-
Missing "User Need" heading in Design Guide part of content-usable w3c/coga#308 (1 comment by @SteveALee)
-
1 pull request opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Restructured design guide source of content-usable for Web version w3c/coga#309, by @SteveALee.
-
Low Vision Accessibility Task Force
Participants
-
4 participants joined the Low Vision Accessibility Task Force.
-
Bhoomika Bhagchandani joined.
-
Bruce Bailey joined.
-
Todd Libby joined.
-
Sam Waller joined.
-
GitHub
w3c/low-vision-a11y-tf
-
1 issue opened in the Low Vision Accessibility Task Force.
-
Proposed Meeting Agenda Items Sept 2021 w3c/low-vision-a11y-tf#99, by @Myndex.
-
-
2 issues closed in the Low Vision Accessibility Task Force.
-
Determine planning meeting time cadence w3c/low-vision-a11y-tf#95.
-
Confirm Meeting time with Task Force participants w3c/low-vision-a11y-tf#94.
-
-
2 issues in the Low Vision Accessibility Task Force received 2 new comments.
-
Confirm Meeting time with Task Force participants w3c/low-vision-a11y-tf#94 (1 comment by @shawna-slh)
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
1 meeting of the Accessibility Conformance Testing (ACT) Task Force.
Past meetings
Participants
-
1 chair appointed.
-
Rachael Bradley Montgomery became a chair.
-
-
1 chair stepped down.
-
Rachael Bradley Montgomery stepped down as a chair.
-
-
3 participants joined.
-
Rachael Bradley Montgomery (Library of Congress) joined.
-
Shawn Thompson (W3C Invited Experts) joined.
-
Gregg Vanderheiden (W3C Invited Experts) joined.
-
-
6 participants left.
-
Rachael Bradley Montgomery (Library of Congress) left.
-
Justine Pascalides (Amazon) left.
-
Matthew Orr (Fiserv) left.
-
Tomas Sefcovic (Fiserv) left.
-
Jim Griesemer (Level Access) left.
-
Alistair Garrison (W3C Invited Experts) left.
-
-
1 organization joined.
-
Library of Congress joined.
-
-
1 organization left.
-
Fiserv left.
-
GitHub
w3c/wcag
-
14 issues opened.
-
2.5.8 Target size (minimum) lacks 'Alternative' exception w3c/wcag#1976, by @mbgower.
-
1.3.1 and Lists and the notorious "or are available in text" w3c/wcag#1974, by @goodwitch.
-
Separate requirements from exceptions in 2.2.1 Timing Adjustable w3c/wcag#1971, by @mattgarrish.
-
[Glossary] Region w3c/wcag#1970, by @yatil.
-
3.3.7 Further guidance on 2-factor independent methods w3c/wcag#1965, by @abijames.
-
How can you use aria-required with checkboxes? w3c/wcag#1963, by @mbgower.
-
Related resource links in SC 2.4.2 understanding are 404 or not found w3c/wcag#1962, by @mraccess77.
-
2.4.9 phone number links w3c/wcag#1949, by @rwapp.
-
1.1.1 test rule links w3c/wcag#1948, by @rwapp.
-
cards, dashboards, and non-text contrast w3c/wcag#1945, by @gundulaniemann.
-
-
29 issues closed.
-
Broken link in Understanding 2.4.2 doc w3c/wcag#1906.
-
3.3.7: Ensuring copy-paste is not blocked w3c/wcag#1878.
-
Adobe Comment on 3.3.7 Accessible Authentication w3c/wcag#1885.
-
Use GitHub actions instead of Travis CI w3c/wcag#1937.
-
3.3.7 Clarification on USB-based 2FA w3c/wcag#1903.
-
Broken link on documentation page w3c/wcag#913.
-
Update date is not shown w3c/wcag#1088.
-
Links TBD w3c/wcag#1102.
-
broken links in Understanding w3c/wcag#1283.
-
broken link(s) in Technique w3c/wcag#1286.
-
WCAG 2.2 Understanding Documents AGAIN at the WCAG 2.1 URL w3c/wcag#1820.
-
WCAG 2.1 techniques contain links and references to WCAG 2.2 w3c/wcag#1919.
-
Empty Key Terms sections in understanding docs w3c/wcag#1841.
-
3.3.7: Other Methods w3c/wcag#1879.
-
Carousels fail 2.2.1: Timing Adjustable ?! w3c/wcag#1658.
-
65 issues received 150 new comments.
-
SC 3.3.7 Accessible Authentication - add requirement / control to "show password" for end-users w3c/wcag#1912 (17 comments by @alastc, @JohnRochfordUMMS, @patrickhlauke, @philljenkins, @rainbreaw)
-
cards, dashboards, and non-text contrast w3c/wcag#1945 (14 comments by @alastc, @detlevhfischer, @gundulaniemann, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
How can you use aria-required with checkboxes? w3c/wcag#1963 (9 comments by @fstrr, @JAWS-test, @mbgower, @patrickhlauke)
-
Is a video player considered a single component for purposes of single character shortcuts SC 2.1.4? w3c/wcag#1950 (7 comments by @bskibinski, @mraccess77, @patrickhlauke, @scottaohara)
-
2.5.8 Target size (minimum) lacks 'Alternative' exception w3c/wcag#1976 (6 comments by @mbgower, @mraccess77)
-
1.3.1 and Lists and the notorious "or are available in text" w3c/wcag#1974 (6 comments by @bruce-usab, @goodwitch, @mraccess77, @patrickhlauke, @scottaohara)
-
Dragging Movements needs some attention w3c/wcag#1917 (5 comments by @detlevhfischer, @mbgower, @mraccess77, @norarose)
-
2.4.11: Text below figure figure 11 w3c/wcag#1865 (4 comments by @alastc, @DavidMacDonald, @GreggVan, @mraccess77)
-
Page Break Navigation uses undefined term to define a term, and needs to clarify w3c/wcag#1927 (3 comments by @alastc, @aubbink1)
-
3.3.1 Error identification and the required attribute w3c/wcag#1944 (3 comments by @anevins12, @jamesjacobs, @JAWS-test)
-
WCAG 2.2 2.5.8 - adding diagrams that make the reality/consequences of target offset clearer w3c/wcag#1848 (3 comments by @detlevhfischer, @patrickhlauke)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.3.7 Accessible Authentication w3c/wcag#1890 (2 comments by @philljenkins, @rainbreaw)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.2.6 Consistent Help (A) w3c/wcag#1892 (2 comments by @alastc, @rachaelbradley)
-
Minimum Area shape requirement could use attention, Focus Appearance (Minimum) w3c/wcag#1928 (2 comments by @alastc, @mraccess77)
-
2.4.11: Confusing wording due to unconventional state requirement w3c/wcag#1859 (2 comments by @alastc, @DavidMacDonald)
-
2.4.7 Focus Visible: WCAG 2.1 Understanding has wrong level (A instead of AA) w3c/wcag#1178 (2 comments by @alastc, @guyhickling)
-
WCAG Techniques "Official version" link appears to be incorrect w3c/wcag#1740 (2 comments by @alastc, @jribbens)
-
3.3.8: Ensuring single transactions (from the user's perspective) are covered w3c/wcag#1880 (2 comments by @awkawk, @DavidMacDonald)
-
Suggested rewording to normative text of Visible Controls w3c/wcag#1932 (2 comments by @DavidMacDonald)
-
What is an "input field"? (1.3.5 Identify Input Purpose) w3c/wcag#1652 (2 comments by @komali2, @patrickhlauke)
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.4.13: Page Break Navigation (A) w3c/wcag#1893 (1 comment by @alastc)
-
3.2.7: Subjective judgement is needed, and effort to test and remediate could be quite variable w3c/wcag#1877 (1 comment by @lseeman)
-
SC 2.4.11 Focus Appearance fails to explain why authors are better enbled than UA at solving this w3c/wcag#1911 (1 comment by @alastc)
-
[WCAG 2.2 Feedback] Success Criterion 2.4.11 Focus Appearance (Minimum) (Level AA) w3c/wcag#1896 (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 @alastc)
-
Link for Understanding Conformance goes to 2.0 version, NOT the 2.1 w3c/wcag#968 (1 comment by @alastc)
-
Understanding document for “Pointer Target Spacing”, a non-existent WCAG 2.2 SC, is still available w3c/wcag#1833 (1 comment by @alastc)
-
Understanding document for “Dragging”, a non-existent WCAG 2.2 SC, is still available w3c/wcag#1835 (1 comment by @alastc)
-
Does 3.3.2 mandate forms that have required/optional fields indicate this visually? w3c/wcag#923 (1 comment by @mraccess77)
-
WCAG 2.1 techniques contain links and references to WCAG 2.2 w3c/wcag#1919 (1 comment by @michael-n-cooper)
-
2.4.11: Insufficient requirement for focus indication via enlargement w3c/wcag#1858 (1 comment by @DavidMacDonald)
-
2.4.13: Query: are pages with print CSS that includes page breaks excepted? w3c/wcag#1868 (1 comment by @DavidMacDonald)
-
3.2.6: Using "should" in the Understanding doc is confusing w3c/wcag#1874 (1 comment by @DavidMacDonald)
-
2.5.1 Pointer Gestures: clarity on path-based language in Understanding document w3c/wcag#522 (1 comment by @anevins12)
-
-
17 pull requests opened.
-
Update G219.html w3c/wcag#1975, by @mbgower.
-
Update consistent-help.html w3c/wcag#1968, by @rachaelbradley.
-
David's suggested update w3c/wcag#1967, by @alastc.
-
Updating min area w3c/wcag#1966, by @alastc.
-
Target size minimum: conforming alternate version w3c/wcag#1964, by @detlevhfischer.
-
Update dragging-movements.html w3c/wcag#1961, by @detlevhfischer.
-
Refining password blocking text w3c/wcag#1960, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1959, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1958, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1957, by @alastc.
-
Target size min styling w3c/wcag#1956, by @detlevhfischer.
-
Target size min legal exception w3c/wcag#1955, by @detlevhfischer.
-
Dragging understanding+tech rewording w3c/wcag#1954, by @detlevhfischer.
-
Page Break Nav terminology clarity w3c/wcag#1952, by @aubbink1.
-
Scha14 issue 1321 w3c/wcag#1951, by @alastc.
-
removed benefits that don't rely on AT w3c/wcag#1947, by @DavidMacDonald.
-
Rewrite h69 d macdonald w3c/wcag#1946, by @DavidMacDonald.
-
-
12 pull requests merged.
-
Fix for #1350 w3c/wcag#1353.
-
Fix understanding images w3c/wcag#1549.
-
Page Break Nav terminology clarity w3c/wcag#1952.
-
Refining password blocking text w3c/wcag#1960.
-
Adding paragraph about password visibility w3c/wcag#1940.
-
Adding site-specific to understanding w3c/wcag#1909.
-
Wcag22 typos and editorial w3c/wcag#1959.
-
Wcag22 typos and editorial w3c/wcag#1958.
-
Wcag22 typos and editorial w3c/wcag#1957.
-
1.4.11 Understanding - slight rewording w3c/wcag#1672.
-
Update time-limits-required-behaviors.xml w3c/wcag#1688.
-
-
3 pull requests closed.
-
Replacing the image-recognition example w3c/wcag#1407.
-
Scha14 issue 1321 w3c/wcag#1951.
-
removed benefits that don't rely on AT w3c/wcag#1947.
-
-
10 pull requests received 27 new comments.
-
Target size min styling w3c/wcag#1956 (6 comments by @alastc, @detlevhfischer, @scottaohara, @WilcoFiers)
-
Dragging understanding+tech rewording w3c/wcag#1954 (5 comments by @alastc, @detlevhfischer, @patrickhlauke)
-
Target size minimum: conforming alternate version w3c/wcag#1964 (2 comments by @detlevhfischer, @scottaohara)
-
WCAG 2.2 3.3.7: Accessible Authentication - disambiguate "paste" and "password managers" w3c/wcag#1898 (1 comment by @patrickhlauke)
-
w3c/coga
-
3 issues opened.
-
5.4.1 "the General Population" w3c/coga#302, by @MakotoUeki.
-
"number 0" in 3.6.3 Voice Menus (User Story) w3c/coga#301, by @MakotoUeki.
-
Clarification for ”Introduction” w3c/coga#300, by @MakotoUeki.
-
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 participant joined the Cognitive and Learning Disabilities Accessibility Task Force.
-
Rachael Bradley Montgomery joined.
-
-
3 participants left the Cognitive and Learning Disabilities Accessibility Task Force.
-
Rachael Bradley Montgomery left.
-
Justine Pascalides left.
-
Jim Griesemer left.
-
GitHub
w3c/coga
-
3 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
5.4.1 "the General Population" w3c/coga#302, by @MakotoUeki.
-
"number 0" in 3.6.3 Voice Menus (User Story) w3c/coga#301, by @MakotoUeki.
-
Clarification for ”Introduction” w3c/coga#300, by @MakotoUeki.
-
Accessibility Conformance Testing (ACT) Task Force
Participants
-
2 participants joined the Accessibility Conformance Testing (ACT) Task Force.
-
Rachael Bradley Montgomery joined.
-
Karen Herr joined.
-
-
2 participants left the Accessibility Conformance Testing (ACT) Task Force.
-
Rachael Bradley Montgomery left.
-
Alistair Garrison left.
-
Low Vision Accessibility Task Force
Participants
-
1 participant joined the Low Vision Accessibility Task Force.
-
Rachael Bradley Montgomery joined.
-
-
1 participant left the Low Vision Accessibility Task Force.
-
Rachael Bradley Montgomery left.
-
GitHub
w3c/low-vision-a11y-tf
-
12 issues opened in the Low Vision Accessibility Task Force.
-
Possibly adding SCs to WCAG 2.3 - Lc tool ? w3c/low-vision-a11y-tf#97, by @ChrisLoiselle.
-
Determine planning meeting time cadence w3c/low-vision-a11y-tf#95, by @ChrisLoiselle.
-
Confirm Meeting time with Task Force participants w3c/low-vision-a11y-tf#94, by @ChrisLoiselle.
-
Input into WCAG 3 w3c/low-vision-a11y-tf#93, by @ChrisLoiselle.
-
Action: Update https://www.w3.org/WAI/GL/low-vision-a11y-tf/work-statement.php w3c/low-vision-a11y-tf#89, by @ChrisLoiselle.
-
Action: Update https://www.w3.org/WAI/GL/low-vision-a11y-tf/ w3c/low-vision-a11y-tf#88, by @ChrisLoiselle.
-
test w3c/low-vision-a11y-tf#87, by @ChrisLoiselle.
-
1 issue closed in the Low Vision Accessibility Task Force.
-
test w3c/low-vision-a11y-tf#87.
-
Mobile Accessibility Task Force
Participants
-
1 participant joined the Mobile Accessibility Task Force.
-
Rachael Bradley Montgomery joined.
-
-
2 participants left the Mobile Accessibility Task Force.
-
Rachael Bradley Montgomery left.
-
Alistair Garrison left.
-
TR publications
-
1 document published.
-
W3C Accessibility Guidelines (WCAG) 3.0 published as a Working Draft. History of W3C Accessibility Guidelines (WCAG) 3.0
-
Participants
-
4 participants joined.
-
Jen Goulden (Crawford Technologies) joined.
-
Kenny Dunsin (Crawford Technologies) joined.
-
Bernard Wang (Wikimedia Foundation) joined.
-
Christopher Merrington (Gain) joined.
-
-
1 participant left.
-
Juliette Alexandria (Access2online Inc.) left.
-
-
1 organization joined.
-
Wikimedia Foundation joined.
-
GitHub
w3c/wcag
-
89 issues opened.
-
3.3.1 Error identification and the required attribute w3c/wcag#1944, by @jamesjacobs.
-
2.2.2 Pause, Stop, Hide - Definition of term "Parallel" needed w3c/wcag#1943, by @anevins12.
-
Contrast and video w3c/wcag#1939, by @fstrr.
-
Use GitHub actions instead of Travis CI w3c/wcag#1937, by @plehegar.
-
2.5.3: how strict does the match between label and name need to be? w3c/wcag#1936, by @Jym77.
-
Suggested rewording to normative text of Visible Controls w3c/wcag#1932, by @mbgower.
-
Update Technique G195 procedure w3c/wcag#1931, by @mbgower.
-
Focus Appearance (Minimum) Understanding document challenges w3c/wcag#1930, by @mbgower.
-
Focus Appearance (Minimum) needs more info on adjacent contrast w3c/wcag#1929, by @mbgower.
-
Consistent Help note doesn't make sense to me w3c/wcag#1924, by @mbgower.
-
WCAG 2.1 techniques contain links and references to WCAG 2.2 w3c/wcag#1919, by @mitchellevan.
-
Dragging Movements needs some attention w3c/wcag#1917, by @mbgower.
-
Accessible Authentication needs better techniques w3c/wcag#1916, by @mbgower.
-
H44: additional benefit statement: replace "or" with "for" w3c/wcag#1914, by @spanchang.
-
Broken link found on H97 (Techniques for WCAG 2.1) w3c/wcag#1913, by @caztcha.
-
1.2.1 language to be used in media-alternatives for sign-language videos w3c/wcag#1910, by @ebalink.
-
Definition of video-only and synchronized media w3c/wcag#1908, by @ebalink.
-
Broken link in Understanding 2.4.2 doc w3c/wcag#1906, by @susanatx.
-
3.2.7 clarifications and a user-agent example w3c/wcag#1905, by @JamesCatt.
-
Target size and user-agent components that can't be styled w3c/wcag#1904, by @JamesCatt.
-
3.3.7 Clarification on USB-based 2FA w3c/wcag#1903, by @JamesCatt.
-
3.3.7 - Defining common objects w3c/wcag#1902, by @ghost.
-
[WCAG 2.2 Draft Feedback] 3.2.7 Visible Controls (Level AA) w3c/wcag#1895, by @dshoukry.
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.2.6 Consistent Help (A) w3c/wcag#1892, by @dshoukry.
-
[WCAG 2.2 Draft Feedback] SC 2.5.7: Dragging Movements (AA) w3c/wcag#1891, by @dshoukry.
-
Adobe Comment on 2.5.8 Target Size (Minimum) w3c/wcag#1889, by @awkawk.
-
Adobe Comment on 3.2.7 Visible Controls w3c/wcag#1888, by @awkawk.
-
Adobe Comment on 2.4.11 Focus Appearance (minimum) w3c/wcag#1887, by @awkawk.
-
Adobe Comment on 2.5.7 Dragging Movements w3c/wcag#1886, by @awkawk.
-
Adobe Comment on 3.3.7 Accessible Authentication w3c/wcag#1885, by @awkawk.
-
Clarifying scope of 4.1.3 w3c/wcag#1884, by @ajanec01.
-
SC 2.4.11: Make clearer the method of calculating the minimum area w3c/wcag#1883, by @momdo.
-
3.3.7: Other Methods w3c/wcag#1879, by @benja11y.
-
3.3.7: Ensuring copy-paste is not blocked w3c/wcag#1878, by @benja11y.
-
3.2.7: Controls that are always hidden for everyone w3c/wcag#1876, by @benja11y.
-
3.2.7: Controls that require scrolling to reach w3c/wcag#1875, by @benja11y.
-
3.2.6: Using "should" in the Understanding doc is confusing w3c/wcag#1874, by @benja11y.
-
2.5.8: Typo in the Figure description w3c/wcag#1873, by @benja11y.
-
2.5.8: Further Examples Required w3c/wcag#1872, by @benja11y.
-
2.5.8: Name Change w3c/wcag#1871, by @benja11y.
-
2.5.8: Minimum Component Size w3c/wcag#1870, by @benja11y.
-
2.4.13: Is EPUB Web Content? w3c/wcag#1869, by @benja11y.
-
2.4.13: Query: are slides included? w3c/wcag#1867, by @benja11y.
-
2.4.12: Adjacent Links w3c/wcag#1866, by @benja11y.
-
2.4.11: Text below figure figure 11 w3c/wcag#1865, by @benja11y.
-
2.4.11: Text below figure 3 w3c/wcag#1864, by @benja11y.
-
2.4.11: Text below figure 2 w3c/wcag#1863, by @benja11y.
-
2.4.11: Gradient Backgrounds w3c/wcag#1862, by @benja11y.
-
2.4.11: Gradient Focus Indicators w3c/wcag#1861, by @benja11y.
-
2.4.11: Typos in the text below Figure 18 w3c/wcag#1860, by @benja11y.
-
2.4.11: Confusing wording due to unconventional state requirement w3c/wcag#1859, by @benja11y.
-
2.4.11: Insufficient requirement for focus indication via enlargement w3c/wcag#1858, by @benja11y.
-
SC 1.3.4 Orientation - how to test w3c/wcag#1856, by @kengdoj.
-
2.4.11 and browser default focus indicators w3c/wcag#1854, by @JamesCatt.
-
WCAG 2.2: 2.5.8 understanding - "magnifying glass" vs "loupe" w3c/wcag#1846, by @patrickhlauke.
-
WCAG2.2: 3.2.7 Visible Controls (AA) - Confirmation on navigation menus w3c/wcag#1845, by @emleml.
-
"Redundant entry" should be title case w3c/wcag#1844, by @mattgarrish.
-
Does redundant entry require saving PII? w3c/wcag#1843, by @priyankad7.
-
2.4.11 Focus Appearance complexity w3c/wcag#1842, by @priyankad7.
-
Empty Key Terms sections in understanding docs w3c/wcag#1841, by @mattgarrish.
-
Understanding for 1.4.10 redefines normative requirement for 1.4.4 w3c/wcag#1839, by @patrickhlauke.
-
Understanding doc for 1.2.9 mentions video w3c/wcag#1836, by @mattgarrish.
-
-
22 issues closed.
-
"Changes of color" applied to motion definition w3c/wcag#1535.
-
Programtically parse wcag2.1 spec w3c/wcag#1729.
-
Can text buttons fail 1.1.1 and 3.3.2? w3c/wcag#985.
-
"Redundant entry" should be title case w3c/wcag#1844.
-
2.4.11: Typos in the text below Figure 18 w3c/wcag#1860.
-
2.4.11: Text below figure 2 w3c/wcag#1863.
-
2.4.11: Text below figure 3 w3c/wcag#1864.
-
2.4.12: Adjacent Links w3c/wcag#1866.
-
Broken link found on H97 (Techniques for WCAG 2.1) w3c/wcag#1913.
-
Clarifying scope of 4.1.3 w3c/wcag#1884.
-
3.2.7: Controls that are always hidden for everyone w3c/wcag#1876.
-
2.5.8: Typo in the Figure description w3c/wcag#1873.
-
94 issues received 317 new comments.
-
2.4.11 and browser default focus indicators w3c/wcag#1854 (20 comments by @alastc, @JamesCatt, @JAWS-test, @mraccess77, @PAFaieta, @patrickhlauke)
-
Can large headings be exempt from Success Criterion 1.4.4 Resize text? w3c/wcag#1671 (19 comments by @detlevhfischer, @masi, @mraccess77, @patrickhlauke, @scottkellum)
-
Definition of video-only and synchronized media w3c/wcag#1908 (12 comments by @bruce-usab, @detlevhfischer, @ebalink, @mraccess77, @patrickhlauke)
-
Focus Appearance (Minimum) needs more info on adjacent contrast w3c/wcag#1929 (10 comments by @alastc, @mbgower, @mraccess77, @patrickhlauke)
-
Accessible Authentication needs better techniques w3c/wcag#1916 (9 comments by @alastc, @mbgower, @mraccess77, @patrickhlauke)
-
[WCAG 2.2 Feedback] Success Criterion 2.5.8 Target Size (Minimum) (Level AA) w3c/wcag#1894 (9 comments by @alastc, @eaugustine, @liacrl, @patrickhlauke)
-
Where in WCAG do you record issues in touch swipe focussing and activation of controls? w3c/wcag#1907 (9 comments by @detlevhfischer, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
Adobe Comment on 2.5.7 Dragging Movements w3c/wcag#1886 (7 comments by @alastc, @detlevhfischer, @patrickhlauke)
-
SC 3.3.7 Accessible Authentication - add requirement / control to "show password" for end-users w3c/wcag#1912 (6 comments by @alastc, @eadraffan, @jake-abma, @patrickhlauke, @rainbreaw)
-
Add warning to technique H45 that longdesc is obsolete w3c/wcag#950 (6 comments by @chaals, @kazuhito-kidachi, @LJWatson, @patrickhlauke)
-
3.3.7 Clarification on USB-based 2FA w3c/wcag#1903 (6 comments by @alastc, @JamesCatt, @mraccess77, @patrickhlauke)
-
SC 2.4.11 Focus Appearance fails to explain why authors are better enbled than UA at solving this w3c/wcag#1911 (6 comments by @alastc, @JamesCatt, @mraccess77, @patrickhlauke, @philljenkins)
-
2.5.3: how strict does the match between label and name need to be? w3c/wcag#1936 (5 comments by @alastc, @patrickhlauke)
-
Relationship between Use of colour, Non-text contrast, and Focus visible w3c/wcag#1847 (5 comments by @ajanec01, @JAWS-test, @patrickhlauke)
-
Suggested rewording to normative text of Visible Controls w3c/wcag#1932 (4 comments by @alastc, @mbgower, @mraccess77)
-
Target size and user-agent components that can't be styled w3c/wcag#1904 (4 comments by @detlevhfischer, @jake-abma, @mraccess77, @patrickhlauke)
-
Are 'Headings' enough to pass 2.4.1: Bypass Blocks w3c/wcag#1712 (4 comments by @BillDashfield, @matatk, @xi)
-
"setting all of the following" wording nitpick in normative 1.4.12: Text Spacing w3c/wcag#930 (4 comments by @bruce-usab, @patrickhlauke, @rainbreaw)
-
WCAG 2.2 3.3.7: Accessible Authentication - confusion about "paste" w3c/wcag#1855 (4 comments by @alastc, @patrickhlauke)
-
WCAG 2.2 - 3.2.7 Visible Controls (AA) - difficult to understand meaning w3c/wcag#1840 (4 comments by @LaurenceRLewis, @mraccess77, @yatil)
-
Failure technique F94 (1.4.4 resize text): remove "1280 pixels wide" step in test procedure w3c/wcag#704 (4 comments by @mraccess77, @patrickhlauke)
-
2.2.2 Pause, Stop, Hide - Definition of term "Parallel" needed w3c/wcag#1943 (3 comments by @alastc, @anevins12)
-
Consistent Help normative list should be reviewed for consistent presenation/punctuation w3c/wcag#1925 (3 comments by @alastc, @bruce-usab, @mbgower)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.3.7 Accessible Authentication w3c/wcag#1890 (3 comments by @alastc, @mraccess77)
-
WCAG 2.1 techniques contain links and references to WCAG 2.2 w3c/wcag#1919 (3 comments by @alastc, @hidde)
-
WCAG 2.2 Understanding Documents AGAIN at the WCAG 2.1 URL w3c/wcag#1820 (3 comments by @shawna-slh, @sophieschoice)
-
1.2.1 language to be used in media-alternatives for sign-language videos w3c/wcag#1910 (3 comments by @detlevhfischer, @ebalink, @patrickhlauke)
-
Understanding document for “Dragging”, a non-existent WCAG 2.2 SC, is still available w3c/wcag#1835 (3 comments by @alastc, @shawna-slh, @yatil)
-
3.2.6: Using "should" in the Understanding doc is confusing w3c/wcag#1874 (3 comments by @alastc, @mraccess77, @patrickhlauke)
-
2.4.11: Insufficient requirement for focus indication via enlargement w3c/wcag#1858 (3 comments by @alastc, @benja11y)
-
WCAG 2.2 2.5.8 - adding diagrams that make the reality/consequences of target offset clearer w3c/wcag#1848 (3 comments by @aardrian, @patrickhlauke)
-
Understanding doc for 1.2.9 mentions video w3c/wcag#1836 (3 comments by @mraccess77, @patrickhlauke)
-
SC 2.4.11: Make clearer the method of calculating the minimum area w3c/wcag#1883 (2 comments by @alastc, @momdo)
-
3.3.7 - supporting copy-paste, example with memorable information, and specific characters w3c/wcag#1901 (2 comments by @alastc)
-
WCAG 2.2: 2.5.8 understanding - "magnifying glass" vs "loupe" w3c/wcag#1846 (2 comments by @alastc, @scottaohara)
-
3.3.7 - Are system-level tests out of scope? Are PINs and Passwords synonymous? w3c/wcag#1900 (2 comments by @alastc, @ghost)
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.4.13: Page Break Navigation (A) w3c/wcag#1893 (2 comments by @alastc, @mraccess77)
-
3.2.7: Subjective judgement is needed, and effort to test and remediate could be quite variable w3c/wcag#1877 (2 comments by @alastc, @bruce-usab)
-
To meet SC 1.4.4 with a control what increments if any between 100 and 200 percent must be provided? w3c/wcag#1857 (2 comments by @alastc, @patrickhlauke)
-
WCAG2.2: 3.2.7 Visible Controls (AA) - Confirmation on navigation menus w3c/wcag#1845 (2 comments by @mraccess77, @patrickhlauke)
-
Understanding for 1.4.10 redefines normative requirement for 1.4.4 w3c/wcag#1839 (2 comments by @detlevhfischer, @patrickhlauke)
-
G183: Change mouse Pointer = hovering over the link causes a visual enhancement? w3c/wcag#1761 (1 comment by @kasperisager)
-
Link to technique for Visible Controls not working; whole SC version out of date? w3c/wcag#1933 (1 comment by @alastc)
-
Page Break Navigation uses undefined term to define a term, and needs to clarify w3c/wcag#1927 (1 comment by @alastc)
-
Nr. 2: Problem with 2 statements in 1 SC: 3.3.1: Error Identification w3c/wcag#1774 (1 comment by @bruce-usab)
-
Problem with 2 statements in 1 SC: 3.3.1: Error Identification w3c/wcag#1773 (1 comment by @bruce-usab)
-
Resource link 404s on WCAG 2.1 target-size Understanding document w3c/wcag#1704 (1 comment by @alastc)
-
[WCAG 2.2 Draft Feedback] Remaining Review Process/Path to Recommendation? w3c/wcag#1897 (1 comment by @alastc)
-
3.3.8: Ensuring single transactions (from the user's perspective) are covered w3c/wcag#1880 (1 comment by @alastc)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.2.6 Consistent Help (A) w3c/wcag#1892 (1 comment by @patrickhlauke)
-
2.4.13: Query: are pages with print CSS that includes page breaks excepted? w3c/wcag#1868 (1 comment by @alastc)
-
2.4.11: Confusing wording due to unconventional state requirement w3c/wcag#1859 (1 comment by @alastc)
-
Findable help (3.2.6) demands contact links within PDF's for instance? w3c/wcag#1693 (1 comment by @alastc)
-
(WCAG 2.0) Translations link in header links… not to translations w3c/wcag#1474 (1 comment by @yatil)
-
-
19 pull requests opened.
-
update 1.4.3 and 1.4.5 to include references to text in video w3c/wcag#1942, by @fstrr.
-
Consistency: "Resize text" > "Resize Text" w3c/wcag#1941, by @patrickhlauke.
-
Adding paragraph about password visibility w3c/wcag#1940, by @alastc.
-
Switch from Travis CI to GitHub action w3c/wcag#1938, by @plehegar.
-
Wcag22 typos and editorial w3c/wcag#1935, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1934, by @alastc.
-
Editorial updates from #1890 w3c/wcag#1923, by @alastc.
-
Adding text to accessible-auth understanding w3c/wcag#1922, by @alastc.
-
WCAG 2.1 - removing wcag22 understandings w3c/wcag#1921, by @alastc.
-
Removing wcag22 techniques w3c/wcag#1920, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1918, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1915, by @alastc.
-
Adding site-specific to understanding w3c/wcag#1909, by @alastc.
-
Remove initial window/browser size from F94 test w3c/wcag#1838, by @patrickhlauke.
-
-
14 pull requests merged.
-
Update for #1535, motion animation w3c/wcag#1555.
-
Switch from Travis CI to GitHub action w3c/wcag#1938.
-
Wcag22 typos and editorial w3c/wcag#1935.
-
Wcag22 typos and editorial w3c/wcag#1934.
-
Editorial updates from #1890 w3c/wcag#1923.
-
Expand 3.3.2 Labels or Instructions understanding w3c/wcag#1568.
-
WCAG 2.1 - removing wcag22 understandings w3c/wcag#1921.
-
Removing wcag22 techniques w3c/wcag#1920.
-
Wcag22 typos and editorial w3c/wcag#1918.
-
Wcag22 typos and editorial w3c/wcag#1915.
-
Updating the contrast value w3c/wcag#1780.
-
Target size understanding review mg w3c/wcag#1770.
-
Changes to 2.5.1 Pointer Gestures understanding w3c/wcag#1569.
-
-
2 pull requests closed.
-
12 pull requests received 70 new comments.
-
Rewrite for 3.3.1 Error Identification understanding document w3c/wcag#1651 (27 comments by @alastc, @awkawk, @bruce-usab, @gundulaniemann, @jake-abma, @mraccess77, @patrickhlauke)
-
Target size understanding review mg w3c/wcag#1770 (14 comments by @alastc, @patrickhlauke, @WilcoFiers)
-
Review of Understanding documents for consistency and readability w3c/wcag#1834 (13 comments by @maryjom, @mbgower, @patrickhlauke)
-
Expand 3.3.2 Labels or Instructions understanding w3c/wcag#1568 (4 comments by @alastc, @mraccess77, @patrickhlauke)
-
WCAG 2.2 3.3.7: Accessible Authentication - disambiguate "paste" and "password managers" w3c/wcag#1898 (3 comments by @alastc, @patrickhlauke)
-
Understanding 1.4.12: clarify the intent and author responsibility w3c/wcag#1687 (3 comments by @alastc, @gundulaniemann, @patrickhlauke)
-
WCAG 2.2 2.5.8 understanding: replace "loupe" with "magnifying glass" w3c/wcag#1850 (1 comment by @alastc)
-
w3c/wcag3
-
1 issue opened.
-
Proposal to introduce maximum contrast ratio w3c/wcag3#171, by @cawa-93.
-
-
4 issues received 16 new comments.
-
Affordance for oversized text in WCAG Success Criterion 1.4.4: Resize Text w3c/wcag3#261 (10 comments by @ChrisLoiselle, @Myndex, @scottkellum)
-
Proposal to introduce maximum contrast ratio w3c/wcag3#171 (3 comments by @bruce-usab, @JAWS-test, @mraccess77)
-
How does the guideline ensure text is sufficiently readable for people with CVD (colourblindness) w3c/wcag3#403 (2 comments by @ChrisLoiselle, @sdw32)
-
w3c/coga
-
2 issues opened.
-
new patter sugestion w3c/coga#299, by @lseeman.
-
wording difficult to parse w3c/coga#298, by @shawna-slh.
-
-
1 issue closed.
-
Check that glossary terms work as hyperlinked text w3c/coga#227.
-
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
4 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Participants
-
1 chair appointed in the Accessibility Conformance Testing (ACT) Task Force.
-
Kathy Eng became a chair.
-
-
1 Team contact appointed in the Accessibility Conformance Testing (ACT) Task Force.
-
Daniel Montalvo became a Team contact.
-
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 chair appointed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Rain Breaw Michaels became a chair.
-
GitHub
w3c/coga
-
2 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
new patter sugestion w3c/coga#299, by @lseeman.
-
wording difficult to parse w3c/coga#298, by @shawna-slh.
-
-
1 issue closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Check that glossary terms work as hyperlinked text w3c/coga#227.
-
Mobile Accessibility Task Force
Participants
-
1 Team contact stepped down in the Mobile Accessibility Task Force.
-
Shadi Abou-Zahra stepped down as a Team contact.
-
TR publications
-
2 documents published.
-
Web Content Accessibility Guidelines (WCAG) 2.2 published twice as a Working Draft. History of Web Content Accessibility Guidelines (WCAG) 2.2
-
Participants
-
7 participants joined.
-
Natalie Patrice Tucker (Knowbility) joined.
-
Natalie Patrice Tucker (Knowbility) joined.
-
Todd Libby (W3C Invited Experts) joined.
-
Jennifer Strickland (MITRE Corporation) joined.
-
Kun Zhang (Shenzhen Accessibility Research Association) joined.
-
Aimee Ubbink (Crawford Technologies) joined.
-
Thomas Brunet (IBM Corporation) joined.
-
-
6 participants left.
-
Natalie Patrice Tucker (Knowbility) left.
-
Natalie Patrice Tucker (Knowbility) left.
-
Natalie Patrice Tucker (Knowbility) left.
-
Jennifer Strickland (MITRE Corporation) left.
-
Jerry Lee (Macmillan Learning) left.
-
Kim Graff (Macmillan Learning) left.
-
-
1 organization joined.
-
Crawford Technologies joined.
-
-
1 organization left.
-
Macmillan Learning left.
-
GitHub
w3c/wcag
-
36 issues opened.
-
SC 2.5.8 Target Size (Minimum) - Is "24 by 24 CSS pixels” reasonable? w3c/wcag#1831, by @caztcha.
-
2.4.11 and 2.5.8 - Recommended viewport size for testing? w3c/wcag#1829, by @ghost.
-
Outdated links to UNDERSTANDING-WCAG20 in WCAG 2.1 and 2.2 w3c/wcag#1828, by @patrickhlauke.
-
WCAG 2.2 Understanding Documents AGAIN at the WCAG 2.1 URL w3c/wcag#1820, by @yatil.
-
Description for Sufficient Techniques, like Advisory and Failures w3c/wcag#1815, by @jake-abma.
-
Suggested improvement to Understanding 2.2.1: Timing Adjustable w3c/wcag#1814, by @awkawk.
-
WCAG 2.1 SCs with incomplete/no techniques w3c/wcag#1813, by @patrickhlauke.
-
2.4.11 Focus Appearance (Minimum) (AA) - Minimum Area w3c/wcag#1806, by @dashouse.
-
SC 4.1.1 also for invisible content? w3c/wcag#1805, by @JAWS-test.
-
Referral from ARIA2 to 3.3.3 should be 3.3.1 w3c/wcag#1802, by @jake-abma.
-
ARIA2 is not a Sufficient technique for 3.3.3: Error Suggestion w3c/wcag#1801, by @jake-abma.
-
G83 is not a Sufficient technique for 3.3.3: Error Suggestion w3c/wcag#1800, by @jake-abma.
-
Make Benefits a bulleted list 3.3.3: Error Suggestion w3c/wcag#1798, by @jake-abma.
-
Change 2.0 to 2.2 Intent 3.3.3: Error Suggestion w3c/wcag#1796, by @jake-abma.
-
Sufficient techniques not a fit for 3.3.2: Labels or Instructions w3c/wcag#1795, by @jake-abma.
-
Examples not correct for 3.3.2: Labels or Instructions w3c/wcag#1794, by @jake-abma.
-
add text "or instructions" in Intent for 3.3.2: Labels or Instructions w3c/wcag#1793, by @jake-abma.
-
Requirement and Benefits contradict at 3.3.2: Labels or Instructions w3c/wcag#1791, by @jake-abma.
-
Duplicate content w3c/wcag#1787, by @kristian240.
-
commit history 404 w3c/wcag#1785, by @shawna-slh.
-
[minor] Note and Editor's Note inconsistent w3c/wcag#1784, by @shawna-slh.
-
1.4.1 also relevant if hue is the same but brightness is different? w3c/wcag#1781, by @JAWS-test.
-
10 issues closed.
-
SC 4.1.1 also for invisible content? w3c/wcag#1805.
-
[minor] Note and Editor's Note inconsistent w3c/wcag#1784.
-
How to check 3.1.5: Reading Level? w3c/wcag#1754.
-
2.4.2: Page Titled makes 2.4.8: Location redundant w3c/wcag#1763.
-
Typo in 1.4.11 Understanding doc w3c/wcag#1766.
-
73 issues received 296 new comments.
-
Comment on WCAG 2.2 Draft: please delay adding of new Success Criteria before the current documentation is improved. w3c/wcag#1818 (24 comments by @alastc, @erikkroes, @jake-abma, @joelanman, @masi, @matt-tyas, @mraccess77, @patrickhlauke, @shawna-slh, @StommePoes, @thibaudcolas, @WilcoFiers, @yatil)
-
How to add audio descriptions to videos? w3c/wcag#1768 (17 comments by @alastc, @bruce-usab, @mraccess77, @OwenEdwards, @patrickhlauke)
-
1.4.1 also relevant if hue is the same but brightness is different? w3c/wcag#1781 (15 comments by @alastc, @bruce-usab, @JAWS-test, @mraccess77, @patrickhlauke)
-
Clarify the meaning of "is also available" in step #3 of F3 test w3c/wcag#80 (8 comments by @bruce-usab, @JAWS-test, @mraccess77, @patrickhlauke)
-
!!! Understanding and How to Meet links gone in WCAG 2.2 Latest published version !!! w3c/wcag#1809 (8 comments by @alastc, @bruce-usab, @jake-abma, @patrickhlauke, @yatil)
-
Nr. 2: Problem with 2 statements in 1 SC: 3.3.1: Error Identification w3c/wcag#1774 (8 comments by @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
Can large headings be exempt from Success Criterion 1.4.4 Resize text? w3c/wcag#1671 (6 comments by @masi, @patrickhlauke, @scottkellum)
-
Do issues with Windows high contrast mode fall under WCAG 2.1? w3c/wcag#623 (6 comments by @jake-abma, @patrickhlauke, @StommePoes, @zelliott)
-
Carousels fail 2.2.1: Timing Adjustable ?! w3c/wcag#1658 (6 comments by @alastc, @bruce-usab, @JAWS-test, @patrickhlauke)
-
SC 4.1.1 also for invisible content? w3c/wcag#1805 (6 comments by @JAWS-test, @mraccess77, @scottaohara)
-
example sentence for 3.2.5: Change on Request already covered by 3.2.2: On Input w3c/wcag#1779 (6 comments by @alastc, @jake-abma, @mraccess77)
-
SC 2.5.8 Target Size (Minimum) - Is "24 by 24 CSS pixels” reasonable? w3c/wcag#1831 (5 comments by @caztcha, @mraccess77, @patrickhlauke)
-
Semantic conveyed through Indented UI and Reflow 1.4.10 w3c/wcag#887 (5 comments by @alastc, @mraccess77, @patrickhlauke)
-
Change 2.0 to 2.2 Intent 3.3.3: Error Suggestion w3c/wcag#1796 (5 comments by @jake-abma, @patrickhlauke)
-
Is a search term considered as "Information"? resulting in search failing 3.3.6: Error Prevention (All) w3c/wcag#1755 (5 comments by @alastc, @jake-abma, @patrickhlauke)
-
Outdated links to UNDERSTANDING-WCAG20 in WCAG 2.1 and 2.2 w3c/wcag#1828 (4 comments by @alastc, @patrickhlauke)
-
2.4.11 and 2.5.8 - Recommended viewport size for testing? w3c/wcag#1829 (4 comments by @alastc, @ghost, @jake-abma)
-
Understanding Conformance 2.1 only talks about 2.0 w3c/wcag#967 (4 comments by @jake-abma, @patrickhlauke)
-
add text "or instructions" in Intent for 3.3.2: Labels or Instructions w3c/wcag#1793 (4 comments by @jake-abma, @patrickhlauke)
-
Why does 3.2.4: Consistent Identification has the "AND" in the technique? w3c/wcag#1778 (4 comments by @alastc, @jake-abma)
-
"G153 Making the text easier to read" needs referral to "lower secondary education level"? w3c/wcag#1753 (4 comments by @alastc, @jake-abma)
-
Understanding document for “Pointer Target Spacing”, a non-existent WCAG 2.2 SC, is still available w3c/wcag#1833 (3 comments by @jake-abma, @yatil)
-
Stacked SC: SC 1.4.4: Resize text AND 1.4.3: Contrast Do they have a interrelationship? w3c/wcag#1522 (3 comments by @jake-abma, @masi, @patrickhlauke)
-
"setting all of the following" wording nitpick in normative 1.4.12: Text Spacing w3c/wcag#930 (3 comments by @alastc, @bruce-usab, @patrickhlauke)
-
Mechanism provided by the platform AND stopping 1.4.2: Audio Control w3c/wcag#1533 (3 comments by @jake-abma, @patrickhlauke)
-
Is "preceding heading element" or a region landmark a programmatically determined link context? w3c/wcag#1821 (3 comments by @ajanec01, @patrickhlauke)
-
SC Understanding update: "What it is about" Vs. "What it isn't about" w3c/wcag#744 (3 comments by @jake-abma, @shawna-slh)
-
Location for home pages without a 'visual current home link' a fail for 2.4.8: Location? w3c/wcag#1750 (3 comments by @alastc, @jake-abma)
-
1.4.11 if a button has a background less than 3:1 and no border does it pass w3c/wcag#800 (2 comments by @alliv8, @patrickhlauke)
-
Failure F23 is NOT a failure if you look at the Procedure w3c/wcag#1543 (2 comments by @jake-abma, @patrickhlauke)
-
How does someone view the differences between two "releases" of WCAG 2.2 guidelines? w3c/wcag#1808 (2 comments by @alastc, @OwenEdwards)
-
quickref: Sufficient Techniques & Failures not correct for 1.3.4 Orientation Level AA w3c/wcag#927 (2 comments by @jake-abma, @yatil)
-
re-write "zooming into a vertically scrolling page should not cause content to be hidden" w3c/wcag#326 (2 comments by @jake-abma, @patrickhlauke)
-
Add a nuance in wording for not generalizing the cognitive group w3c/wcag#329 (2 comments by @jake-abma, @patrickhlauke)
-
Suggested improvement to Understanding 2.2.1: Timing Adjustable w3c/wcag#1814 (2 comments by @bruce-usab, @mraccess77)
-
Change 3.3.1: Error Suggestion to 3.3.3: Error Suggestion, 3.3.1: Error Identification w3c/wcag#1797 (2 comments by @patrickhlauke)
-
2.4.11 Clarify whether there is a minimum area requirement for adjacent contrast w3c/wcag#1789 (2 comments by @alastc, @ghost)
-
Sufficient techniques not a fit for 3.3.2: Labels or Instructions w3c/wcag#1795 (2 comments by @jake-abma, @patrickhlauke)
-
Requirement and Benefits contradict at 3.3.2: Labels or Instructions w3c/wcag#1791 (2 comments by @patrickhlauke)
-
“Conformance Criterion” instead of “Conformance Requirement” used in the WCAG 2.1 Glossary w3c/wcag#1758 (2 comments by @alastc, @yatil)
-
2.4.2: Page Titled makes 2.4.8: Location redundant w3c/wcag#1763 (2 comments by @alastc, @jake-abma)
-
Link wrong / broken - Failure due to locking the orientation to landscape or portrait view w3c/wcag#1417 (1 comment by @jake-abma)
-
Extend "programmatically determined" for markup language via A11Y API w3c/wcag#984 (1 comment by @jake-abma)
-
Link for Understanding Conformance goes to 2.0 version, NOT the 2.1 w3c/wcag#968 (1 comment by @jake-abma)
-
Sentence Advisory Techniques for 2.4.7: Focus Visible need adjustments w3c/wcag#729 (1 comment by @jake-abma)
-
Description for Sufficient Techniques, like Advisory and Failures w3c/wcag#1815 (1 comment by @patrickhlauke)
-
Intent vs. Benefits and conformance (with SC 1.2.3 and SC 1.2.5) w3c/wcag#1042 (1 comment by @OwenEdwards)
-
ARIA2 is not a Sufficient technique for 3.3.3: Error Suggestion w3c/wcag#1801 (1 comment by @patrickhlauke)
-
G83 is not a Sufficient technique for 3.3.3: Error Suggestion w3c/wcag#1800 (1 comment by @patrickhlauke)
-
Second example, second nested bullet not correct for 3.3.3: Error Suggestion w3c/wcag#1799 (1 comment by @patrickhlauke)
-
What does nested according to the specification mean in SC 4.1.1 w3c/wcag#978 (1 comment by @patrickhlauke)
-
1.4.12: Text Spacing: Languages and Scripts Results/Exceptions and Content Edit w3c/wcag#1786 (1 comment by @bruce-usab)
-
3.2.7 Visible Controls - The first exception is difficult to understand w3c/wcag#1760 (1 comment by @alastc)
-
21 pull requests opened.
-
Review of Understanding documents for consistency and readability w3c/wcag#1834, by @mbgower.
-
Link updates w3c/wcag#1830, by @alastc.
-
Code fixes to 1.3.5 Identify Input Purpose understanding w3c/wcag#1827, by @patrickhlauke.
-
Reword F23 w3c/wcag#1826, by @patrickhlauke.
-
Rewording of normative text for 1.4.2 Audio Control w3c/wcag#1824, by @patrickhlauke.
-
ARIA9 change "label" to "name" when it refers to accessible name w3c/wcag#1823, by @patrickhlauke.
-
Replacing a dead link with a new tool w3c/wcag#1822, by @awkawk.
-
Tweak 1.4.10 Reflow understanding intent (cut off / zooming) w3c/wcag#1819, by @patrickhlauke.
-
Tweak 1.3.5 Identify Input Purpose understanding intent w3c/wcag#1817, by @patrickhlauke.
-
Tweak 1.4.10 Reflow understanding intent w3c/wcag#1816, by @patrickhlauke.
-
Fix link to GitHub "commit history to WCAG 2.2" in Guidelines w3c/wcag#1812, by @OwenEdwards.
-
Update/correct 3.3.3 understanding w3c/wcag#1804, by @patrickhlauke.
-
Update/correct 3.3.1 understanding w3c/wcag#1803, by @patrickhlauke.
-
Tweak 3.3.2 understanding benefits to align with intent w3c/wcag#1792, by @patrickhlauke.
-
Tweak understanding for 1.2.3 and 1.2.5 w3c/wcag#1790, by @patrickhlauke.
-
Changes to 1.4.1 Use of Color understanding w3c/wcag#1788, by @patrickhlauke.
-
Update target-size-minimum.html w3c/wcag#1783, by @detlevhfischer.
-
Updating the contrast value w3c/wcag#1780, by @alastc.
-
Conformance requirements, not criteria w3c/wcag#1777, by @alastc.
-
-
6 pull requests merged.
-
Replacing a dead link with a new tool w3c/wcag#1822.
-
Ignore output w3c/wcag#1514.
-
Update target-size-minimum.html w3c/wcag#1783.
-
Minor 1.4.11 understanding tweaks w3c/wcag#1767.
-
18 pull requests received 43 new comments.
-
Rewrite for 3.3.1 Error Identification understanding document w3c/wcag#1651 (7 comments by @bruce-usab, @mraccess77, @patrickhlauke)
-
Updating the contrast value w3c/wcag#1780 (7 comments by @alastc, @bruce-usab, @mraccess77, @patrickhlauke)
-
Rewording of normative text for 1.4.2 Audio Control w3c/wcag#1824 (6 comments by @detlevhfischer, @mraccess77, @patrickhlauke)
-
New ARIA technique for the aria-current attribute w3c/wcag#1707 (4 comments by @JAWS-test, @OwenEdwards)
-
Changes to 2.5.1 Pointer Gestures understanding w3c/wcag#1569 (2 comments by @mbgower, @patrickhlauke)
-
Alternative rewording of the normative text for 1.4.2 Audio control w3c/wcag#1825 (1 comment by @patrickhlauke)
-
Fix a link to the "Visible Controls" SC in the Change Log of the Guidelines w3c/wcag#1811 (1 comment by @alastc)
-
Understanding 1.4.12: clarify the intent and author responsibility w3c/wcag#1687 (1 comment by @patrickhlauke)
-
ARIA9 change "label" to "name" when it refers to accessible name w3c/wcag#1823 (1 comment by @detlevhfischer)
-
w3c/coga
-
2 issues opened.
-
Pattern for hover menus w3c/coga#297, by @SteveALee.
-
Language is complex and hard to understand w3c/coga#295, by @vavroom.
-
-
2 issues received 9 new comments.
-
Language is complex and hard to understand w3c/coga#295 (8 comments by @alastc, @brothercake, @jpascalides, @michaelAusbun, @shawnthompson, @vavroom)
-
-
1 pull request opened.
-
Update Web Design Guide from published content w3c/coga#296, by @SteveALee.
-
-
1 pull request merged.
-
Update Web Design Guide from published content w3c/coga#296.
-
w3c/wcag3
-
1 issue opened.
-
Receiving focus is A, but removing is AAA w3c/wcag3#172, by @erikkroes.
-
-
3 issues received 17 new comments.
-
Receiving focus is A, but removing is AAA w3c/wcag3#172 (15 comments by @alastc, @erikkroes, @JAWS-test, @mraccess77, @patrickhlauke)
-
UsableNet - WCAG Team comment - Consider the legal and practical importance of conformance. w3c/wcag3#258 (1 comment by @jpascalides)
-
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 participant joined the Cognitive and Learning Disabilities Accessibility Task Force.
-
Markku Hakkinen joined.
-
GitHub
w3c/coga
-
2 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Pattern for hover menus w3c/coga#297, by @SteveALee.
-
Language is complex and hard to understand w3c/coga#295, by @vavroom.
-
-
2 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 9 new comments.
-
Language is complex and hard to understand w3c/coga#295 (8 comments by @alastc, @brothercake, @jpascalides, @michaelAusbun, @shawnthompson, @vavroom)
-
-
1 pull request opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Update Web Design Guide from published content w3c/coga#296, by @SteveALee.
-
-
1 pull request merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Update Web Design Guide from published content w3c/coga#296.
-
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
1 meeting of the Accessibility Conformance Testing (ACT) Task Force.
Participants
-
1 participant joined the Accessibility Conformance Testing (ACT) Task Force.
-
Todd Libby joined.
-
TR publications
-
1 document published.
Participants
-
8 participants joined.
-
Jeff Bernier (Pearson plc) joined.
-
Sathish Kumar (Deque Systems, Inc.) joined.
-
Daniele Marano (Hilfsgemeinschaft der Blinden und Sehschwachen Österreichs) joined.
-
Fridolin Wild (The Open University) joined.
-
Vijaya Gowri Perumal (Newgen Knowledgeworks) joined.
-
Regina Sanchez (Navy Federal Credit Union) joined.
-
Alisa Smith (AudioEye, Inc.) joined.
-
Dominic Varacalli (AudioEye, Inc.) joined.
-
-
3 participants left.
-
Alisa Smith (AudioEye, Inc.) left.
-
Dominic Varacalli (AudioEye, Inc.) left.
-
Daniele Marano (Hilfsgemeinschaft der Blinden und Sehschwachen Österreichs) left.
-
-
5 organizations joined.
-
Hilfsgemeinschaft der Blinden und Sehschwachen Österreichs joined.
-
The Open University joined.
-
Newgen Knowledgeworks joined.
-
Shenzhen Accessibility Research Association joined.
-
AudioEye, Inc. joined.
-
-
2 organizations left.
-
AudioEye, Inc. left.
-
Hilfsgemeinschaft der Blinden und Sehschwachen Österreichs left.
-
GitHub
w3c/wcag
-
37 issues opened.
-
Nr. 2: Problem with 2 statements in 1 SC: 3.3.1: Error Identification w3c/wcag#1774, by @jake-abma.
-
Problem with 2 statements in 1 SC: 3.3.1: Error Identification w3c/wcag#1773, by @jake-abma.
-
Why is ARIA2 part of Sufficient 3.3.3: Error Suggestion w3c/wcag#1772, by @jake-abma.
-
Are there exceptions for 3.1.4: Abbreviations? w3c/wcag#1771, by @jake-abma.
-
Mark mandatory fields as incorrect on blur? (G83) w3c/wcag#1769, by @JAWS-test.
-
How to add audio descriptions to videos? w3c/wcag#1768, by @guyhickling.
-
Typo in 1.4.11 Understanding doc w3c/wcag#1766, by @susanatx.
-
2.4.2: Page Titled makes 2.4.8: Location redundant w3c/wcag#1763, by @jake-abma.
-
“Pointer Input” not well defined in Glossary w3c/wcag#1762, by @yatil.
-
3.2.7 Visible Controls - The first exception is difficult to understand w3c/wcag#1760, by @ghost.
-
How to check 3.1.5: Reading Level? w3c/wcag#1754, by @jake-abma.
-
Some sufficient techniques don't fulfil whole SC w3c/wcag#1752, by @jake-abma.
-
Commonly used image buttons FAIL 1.4.5: Images of Text? w3c/wcag#1748, by @jake-abma.
-
Add Read Aloud AT to Understanding WCAG for SC 3.1.6 w3c/wcag#1747, by @JaninaSajka.
-
SC 3.1.6 is nonsensical w3c/wcag#1746, by @JaninaSajka.
-
WCAG Techniques "Official version" link appears to be incorrect w3c/wcag#1740, by @jribbens.
-
Understanding SC WCAG 2.5.8 figures 1, 2, 3 don't match captions w3c/wcag#1738, by @MarcSolo.
-
NON default focusable elements always PASS 3.2.1 On Focus? w3c/wcag#1736, by @jake-abma.
-
Programtically parse wcag2.1 spec w3c/wcag#1729, by @LukeButters.
-
Technique C7 recommends bad practice w3c/wcag#1728, by @guyhickling.
-
UX issue around persistent tooltips w3c/wcag#1727, by @jareko999.
-
Does 1.3.4 Orientation apply to parts of a page or screen? w3c/wcag#1725, by @mitchellevan.
-
Align Target Size (min) with Target Size (enh) w3c/wcag#1721, by @WilcoFiers.
-
Focus appearance is impresise and fairly complicated w3c/wcag#1718, by @WilcoFiers.
-
10 issues closed.
-
Alter note for Redundant Entry w3c/wcag#1660.
-
Add Read Aloud AT to Understanding WCAG for SC 3.1.6 w3c/wcag#1747.
-
Page break locators definition should be revised w3c/wcag#1709.
-
The term "minimum focus indicator area" is confusing w3c/wcag#1544.
-
Active Participants w3c/wcag#1315.
-
-
49 issues received 300 new comments.
-
Are 'Headings' enough to pass 2.4.1: Bypass Blocks w3c/wcag#1712 (65 comments by @alastc, @awkawk, @bruce-usab, @erikkroes, @ghost, @goodwitch, @jake-abma, @JAWS-test, @jenstrickland, @kengdoj, @LJWatson, @MarcHaunschild, @patrickhlauke, @stevefaulkner, @yatil)
-
How to add audio descriptions to videos? w3c/wcag#1768 (22 comments by @awkawk, @bruce-usab, @guyhickling, @mraccess77, @patrickhlauke, @sajkaj)
-
Inconsistent SCs that use "media alternative" in Guideline 1.2 w3c/wcag#796 (17 comments by @alastc, @awkawk, @bruce-usab, @mraccess77, @Ryladog)
-
Clarify if adjacent colors within a component can be used for UI control and focus identification for SC 1.4.11 w3c/wcag#1717 (16 comments by @alastc, @JAWS-test, @mraccess77)
-
Does 1.3.4 Orientation apply to parts of a page or screen? w3c/wcag#1725 (15 comments by @alastc, @awkawk, @goodwitch, @jake-abma, @JAWS-test, @mitchellevan, @mraccess77, @patrickhlauke)
-
Problem with 2 statements in 1 SC: 3.3.1: Error Identification w3c/wcag#1773 (9 comments by @jake-abma, @JAWS-test)
-
Commonly used image buttons FAIL 1.4.5: Images of Text? w3c/wcag#1748 (8 comments by @bruce-usab, @jake-abma, @patrickhlauke, @scottaohara)
-
Link Inside OR Outside the Paragraph - Sanity check 2.4.4: Link Purpose (In Context) w3c/wcag#1745 (8 comments by @bruce-usab, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
NON default focusable elements always PASS 3.2.1 On Focus? w3c/wcag#1736 (8 comments by @alastc, @jake-abma, @patrickhlauke)
-
Page break locators definition should be revised w3c/wcag#1709 (8 comments by @alastc, @mbgower, @mraccess77)
-
Question 1.4.1 Use of Color - Radio button colour with label on focus w3c/wcag#1730 (8 comments by @awkawk, @bruce-usab, @jake-abma, @JAWS-test, @LaurenceRLewis, @mraccess77)
-
No technique using figcaption to meet 1.1.1 Non-text content w3c/wcag#852 (7 comments by @mbgower, @mraccess77, @scottaohara)
-
Focus appearance is impresise and fairly complicated w3c/wcag#1718 (6 comments by @alastc, @ghost, @johnfoliot, @mraccess77)
-
Can large headings be exempt from Success Criterion 1.4.4 Resize text? w3c/wcag#1671 (6 comments by @JAWS-test, @mraccess77, @scottkellum)
-
Logo excepted from 1.4.3 Contrast (Minimum), but does it fail as a link for 1.4.11 Non-text Contrast? w3c/wcag#1739 (5 comments by @alastc, @fstrr, @jake-abma, @JAWS-test)
-
Are there exceptions for 3.1.4: Abbreviations? w3c/wcag#1771 (4 comments by @jake-abma, @patrickhlauke)
-
"changes of context" definition complete? w3c/wcag#737 (4 comments by @alastc, @mbgower, @patrickhlauke)
-
Is a search term considered as "Information"? resulting in search failing 3.3.6: Error Prevention (All) w3c/wcag#1755 (4 comments by @jake-abma, @patrickhlauke)
-
Does 3.3.2 mandate forms that have required/optional fields indicate this visually? w3c/wcag#923 (4 comments by @patrickhlauke, @scroniser)
-
G183: Change mouse Pointer = hovering over the link causes a visual enhancement? w3c/wcag#1761 (3 comments by @patrickhlauke, @yatil)
-
2.4.2: Page Titled makes 2.4.8: Location redundant w3c/wcag#1763 (3 comments by @jake-abma, @patrickhlauke, @yatil)
-
Logo still excepted 1.4.11 Non-text Contrast when colors are not the original brand colors? w3c/wcag#1742 (3 comments by @bruce-usab, @jake-abma, @JAWS-test)
-
Change to minimum focus area of SC 2.4.11 allows for small areas increases with no contrast w3c/wcag#1646 (3 comments by @alastc, @mraccess77)
-
Date input field as conforming alternate version of custom datepicker? w3c/wcag#1723 (3 comments by @alastc, @detlevhfischer, @mraccess77)
-
Mark mandatory fields as incorrect on blur? (G83) w3c/wcag#1769 (2 comments by @JAWS-test, @jorycunningham)
-
1.4.3 Minimum Contrast, 1.5 multiplication factor — from which research paper? w3c/wcag#1705 (2 comments by @huayunh, @jlukosky)
-
Understanding SC WCAG 2.5.8 figures 1, 2, 3 don't match captions w3c/wcag#1738 (2 comments by @MarcSolo, @patrickhlauke)
-
Does 2.5.3 "Label in Name" apply to placeholder (where used as only visible label)? w3c/wcag#1700 (2 comments by @alastc, @ghost)
-
Nr. 2: Problem with 2 statements in 1 SC: 3.3.1: Error Identification w3c/wcag#1774 (1 comment by @mraccess77)
-
Location for home pages without a 'visual current home link' a fail for 2.4.8: Location? w3c/wcag#1750 (1 comment by @jake-abma)
-
3.2.7 Visible Controls - The examples provided on the “Understanding” page are not enough w3c/wcag#1443 (1 comment by @ghost)
-
“Conformance Criterion” instead of “Conformance Requirement” used in the WCAG 2.1 Glossary w3c/wcag#1758 (1 comment by @bruce-usab)
-
Change 1.4.9: Images of Text (No Exception) to 1.4.9: Images of Text (50% Exception) w3c/wcag#1749 (1 comment by @alastc)
-
WCAG Techniques "Official version" link appears to be incorrect w3c/wcag#1740 (1 comment by @alastc)
-
Focus Appearance (Minimum), minumum area, second calculation could be too small w3c/wcag#1684 (1 comment by @alastc)
-
2.4.11 Focus Appearance (Minimum) - the math is difficult to understand and explain w3c/wcag#1439 (1 comment by @alastc)
-
Findable help (3.2.6) demands contact links within PDF's for instance? w3c/wcag#1693 (1 comment by @mraccess77)
-
-
18 pull requests opened.
-
Target size understanding review mg w3c/wcag#1770, by @mbgower.
-
Minor 1.4.11 understanding tweaks w3c/wcag#1767, by @patrickhlauke.
-
Update changes-of-context.html w3c/wcag#1765, by @mbgower.
-
Updating contrast SC docs to ref NTC w3c/wcag#1764, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1757, by @alastc.
-
Adding target offset defintion w3c/wcag#1756, by @alastc.
-
Target size minimum understanding rev w3c/wcag#1751, by @alastc.
-
Redundent entry security note alterative w3c/wcag#1741, by @alastc.
-
Decision policy update w3c/wcag#1737, by @alastc.
-
LVTF page on WAI website - update April 2021 w3c/wcag#1735, by @shawna-slh.
-
fixed typo: `the the` and `of of` w3c/wcag#1734, by @grgr-dkrk.
-
Wcag22 typos and editorial w3c/wcag#1731, by @alastc.
-
typo w3c/wcag#1724, by @mitchellevan.
-
Wcag22 typos and editorial w3c/wcag#1722, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1720, by @alastc.
-
Updating based on AA version w3c/wcag#1719, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1716, by @alastc.
-
Focus appearance updates from the google doc w3c/wcag#1715, by @alastc.
-
-
12 pull requests merged.
-
LVTF page on WAI website - update April 2021 w3c/wcag#1735.
-
Decision policy update w3c/wcag#1737.
-
Wcag22 typos and editorial w3c/wcag#1757.
-
Adding target offset defintion w3c/wcag#1756.
-
Redundent entry security note alterative w3c/wcag#1741.
-
Updating based on AA version w3c/wcag#1719.
-
Wcag22 typos and editorial w3c/wcag#1731.
-
Wcag22 typos and editorial w3c/wcag#1722.
-
Wcag22 typos and editorial w3c/wcag#1720.
-
Target size minimum understanding rev w3c/wcag#1708.
-
Focus appearance updates from the google doc w3c/wcag#1715.
-
Wcag22 typos and editorial w3c/wcag#1716.
-
-
1 pull request closed.
-
Redundent entry update from @mbgower w3c/wcag#1659.
-
-
7 pull requests received 12 new comments.
-
Expand 3.3.2 Labels or Instructions understanding w3c/wcag#1568 (3 comments by @bruce-usab, @patrickhlauke)
-
LVTF page on WAI website - update April 2021 w3c/wcag#1735 (3 comments by @ChrisLoiselle, @shawna-slh)
-
w3c/coga
-
2 issues opened.
-
Change from APA w3c/coga#287, by @rachaelbradley.
-
Explore further integrating points from Amanda Lazar and Emma w3c/coga#282, by @rachaelbradley.
-
-
36 issues closed.
-
Change from APA w3c/coga#287.
-
Objective content is inconsistent w3c/coga#149.
-
"More Details" may not be necessary w3c/coga#151.
-
Easy to read definition w3c/coga#144.
-
Suggested corrections and edits for Summary section w3c/coga#176.
-
EO comment: 4.8. QA review and copy edit w3c/coga#223.
-
Plain language - Passive sentences w3c/coga#182.
-
Provide guidance for working with local language experts w3c/coga#159.
-
Suggestions re icons and other aspects of the summary w3c/coga#180.
-
Comments from EO w3c/coga#199.
-
4.7.3.3 How it Helps (typo/unclear) w3c/coga#190.
-
Review use of judgemental terms w3c/coga#140.
-
comments from PhD student Emma Dixon and Amanda Lazar w3c/coga#198.
-
Comment re 3.8.1 User Story: Adapt w3c/coga#169.
-
EO comments: Specific suggestions to improve usability w3c/coga#210.
-
-
32 issues received 35 new comments.
-
Provide guidance for working with local language experts w3c/coga#159 (2 comments by @r12a, @rachaelbradley)
-
Cognitive accessibility definition and other groups that benefit from it w3c/coga#145 (1 comment by @rachaelbradley)
-
Suggested edits to 3.4.1 User Story: Assistance and support w3c/coga#158 (1 comment by @rachaelbradley)
-
Suggested additions to 3.3.2 User Story: Visual Presentation w3c/coga#157 (1 comment by @rachaelbradley)
-
Suggestion re User Stories About Findability, Searchability and Navigation w3c/coga#156 (1 comment by @rachaelbradley)
-
EO comments: Focus Content Usable on designers, developers, and writers w3c/coga#202 (1 comment by @rachaelbradley)
-
EO comments: 2.3. Building the User into the Development Process and Usability Testing w3c/coga#205 (1 comment by @rachaelbradley)
-
EO comments: 2.2. Background about People with Learning and Cognitive Disabilities and the Web w3c/coga#204 (1 comment by @rachaelbradley)
-
Thoughts on "Object permanence" and "Motor automaticity" with AAC (from Ajit via Google) w3c/coga#143 (1 comment by @rachaelbradley)
-
Include sensitivity to sound and complex patterns in 3.6 Help Users to Maintain Focus w3c/coga#132 (1 comment by @rachaelbradley)
-
Write in plain English, Use Plain Language Guideline (positive sentences) w3c/coga#186 (1 comment by @rachaelbradley)
-
EO comments: Appendix B: Considerations for Uptake in Different Contexts and Policies w3c/coga#208 (1 comment by @rachaelbradley)
-
11 pull requests opened.
-
glossary fixed w3c/coga#294, by @ruoxiran.
-
Final check - changes from plan call w3c/coga#293, by @ruoxiran.
-
Final check - comments from Rachael and Lisa w3c/coga#292, by @ruoxiran.
-
final check needed w3c/coga#291, by @ruoxiran.
-
symbol fix and change log update w3c/coga#290, by @rachaelbradley.
-
fixed section of what to do css style issue w3c/coga#289, by @ruoxiran.
-
added Changelog and terms w3c/coga#288, by @ruoxiran.
-
changed lisa's name w3c/coga#286, by @ruoxiran.
-
Lisa 07042021 w3c/coga#285, by @lseeman.
-
Issue 170, glossary synch, and other edits w3c/coga#284, by @rachaelbradley.
-
Issue wrap up w3c/coga#283, by @rachaelbradley.
-
-
13 pull requests merged.
-
glossary fixed w3c/coga#294.
-
Final check - changes from plan call w3c/coga#293.
-
Final check - comments from Rachael and Lisa w3c/coga#292.
-
final check needed w3c/coga#291.
-
symbol fix and change log update w3c/coga#290.
-
fixed section of what to do css style issue w3c/coga#289.
-
added Changelog and terms w3c/coga#288.
-
Lisa 07042021 w3c/coga#285.
-
changed lisa's name w3c/coga#286.
-
Consistency checks w3c/coga#249.
-
Issue 170, glossary synch, and other edits w3c/coga#284.
-
DRAFT Updates from AG Meeting w3c/coga#281.
-
Issue wrap up w3c/coga#283.
-
w3c/wcag3
-
5 issues opened.
-
Comment on WCAG 3.0 w3c/wcag3#257, by @fsasaki.
-
-
3 issues received 6 new comments.
-
Affordance for oversized text in WCAG Success Criterion 1.4.4: Resize Text w3c/wcag3#261 (4 comments by @JAWS-test, @Myndex, @scottkellum)
-
Email: Siteimprove Comments on WCAG 3.0 Draft (2 - Testing is difficult to carry out efficiently) w3c/wcag3#260 (1 comment by @cwadamsoforacle)
-
w3c/wcag-act
-
3 issues opened.
-
Better organize the All ACT rules page w3c/wcag-act#519, by @WilcoFiers.
-
Add paragraph to About ACT rules on "proposed rules" w3c/wcag-act#518, by @WilcoFiers.
-
Remove acknowledgements on About ACT rules w3c/wcag-act#517, by @WilcoFiers.
-
-
1 pull request opened.
-
Create act-state-proposal.md w3c/wcag-act#516, by @WilcoFiers.
-
-
1 pull request merged.
-
Update wcag-ruleset-review-process.md w3c/wcag-act#515.
-
-
1 pull request received 5 new comments.
-
Update wcag-ruleset-review-process.md w3c/wcag-act#515 (5 comments by @daniel-montalvo, @WilcoFiers)
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
2 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Change from APA w3c/coga#287, by @rachaelbradley.
-
Explore further integrating points from Amanda Lazar and Emma w3c/coga#282, by @rachaelbradley.
-
-
36 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Change from APA w3c/coga#287.
-
Objective content is inconsistent w3c/coga#149.
-
"More Details" may not be necessary w3c/coga#151.
-
Easy to read definition w3c/coga#144.
-
Suggested corrections and edits for Summary section w3c/coga#176.
-
EO comment: 4.8. QA review and copy edit w3c/coga#223.
-
Plain language - Passive sentences w3c/coga#182.
-
Provide guidance for working with local language experts w3c/coga#159.
-
Suggestions re icons and other aspects of the summary w3c/coga#180.
-
Comments from EO w3c/coga#199.
-
4.7.3.3 How it Helps (typo/unclear) w3c/coga#190.
-
Review use of judgemental terms w3c/coga#140.
-
comments from PhD student Emma Dixon and Amanda Lazar w3c/coga#198.
-
Comment re 3.8.1 User Story: Adapt w3c/coga#169.
-
EO comments: Specific suggestions to improve usability w3c/coga#210.
-
-
32 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 35 new comments.
-
Provide guidance for working with local language experts w3c/coga#159 (2 comments by @r12a, @rachaelbradley)
-
Cognitive accessibility definition and other groups that benefit from it w3c/coga#145 (1 comment by @rachaelbradley)
-
Suggested edits to 3.4.1 User Story: Assistance and support w3c/coga#158 (1 comment by @rachaelbradley)
-
Suggested additions to 3.3.2 User Story: Visual Presentation w3c/coga#157 (1 comment by @rachaelbradley)
-
Suggestion re User Stories About Findability, Searchability and Navigation w3c/coga#156 (1 comment by @rachaelbradley)
-
EO comments: Focus Content Usable on designers, developers, and writers w3c/coga#202 (1 comment by @rachaelbradley)
-
EO comments: 2.3. Building the User into the Development Process and Usability Testing w3c/coga#205 (1 comment by @rachaelbradley)
-
EO comments: 2.2. Background about People with Learning and Cognitive Disabilities and the Web w3c/coga#204 (1 comment by @rachaelbradley)
-
Thoughts on "Object permanence" and "Motor automaticity" with AAC (from Ajit via Google) w3c/coga#143 (1 comment by @rachaelbradley)
-
Include sensitivity to sound and complex patterns in 3.6 Help Users to Maintain Focus w3c/coga#132 (1 comment by @rachaelbradley)
-
Write in plain English, Use Plain Language Guideline (positive sentences) w3c/coga#186 (1 comment by @rachaelbradley)
-
EO comments: Appendix B: Considerations for Uptake in Different Contexts and Policies w3c/coga#208 (1 comment by @rachaelbradley)
-
11 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
glossary fixed w3c/coga#294, by @ruoxiran.
-
Final check - changes from plan call w3c/coga#293, by @ruoxiran.
-
Final check - comments from Rachael and Lisa w3c/coga#292, by @ruoxiran.
-
final check needed w3c/coga#291, by @ruoxiran.
-
symbol fix and change log update w3c/coga#290, by @rachaelbradley.
-
fixed section of what to do css style issue w3c/coga#289, by @ruoxiran.
-
added Changelog and terms w3c/coga#288, by @ruoxiran.
-
changed lisa's name w3c/coga#286, by @ruoxiran.
-
Lisa 07042021 w3c/coga#285, by @lseeman.
-
Issue 170, glossary synch, and other edits w3c/coga#284, by @rachaelbradley.
-
Issue wrap up w3c/coga#283, by @rachaelbradley.
-
-
13 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
glossary fixed w3c/coga#294.
-
Final check - changes from plan call w3c/coga#293.
-
Final check - comments from Rachael and Lisa w3c/coga#292.
-
final check needed w3c/coga#291.
-
symbol fix and change log update w3c/coga#290.
-
fixed section of what to do css style issue w3c/coga#289.
-
added Changelog and terms w3c/coga#288.
-
Lisa 07042021 w3c/coga#285.
-
changed lisa's name w3c/coga#286.
-
Consistency checks w3c/coga#249.
-
Issue 170, glossary synch, and other edits w3c/coga#284.
-
DRAFT Updates from AG Meeting w3c/coga#281.
-
Issue wrap up w3c/coga#283.
-
Low Vision Accessibility Task Force
Participants
-
1 participant left the Low Vision Accessibility Task Force.
-
Daniele Marano left.
-
Participants
-
5 participants joined.
-
Jennifer Strickland (MITRE Corporation) joined.
-
Melissa Douros (Discover Financial Services LLC) joined.
-
Jaunita Flessas (W3C Invited Experts) joined.
-
Marcos Franco Murillo (Understood.org) joined.
-
Ela Gorla (TetraLogical Services Ltd) joined.
-
-
1 participant left.
-
Jey Nandakumar (Deque Systems, Inc.) left.
-
-
3 organizations joined.
-
Discover Financial Services LLC joined.
-
Navy Federal Credit Union joined.
-
Tenon.io joined.
-
GitHub
w3c/wcag
-
28 issues opened.
-
Are 'Headings' enough to pass 2.4.1: Bypass Blocks w3c/wcag#1712, by @jake-abma.
-
Page break locators definition should be revised w3c/wcag#1709, by @mbgower.
-
Resource link 404s on WCAG 2.1 target-size Understanding document w3c/wcag#1704, by @dotjay.
-
Visible Required label and 3.3.2: Labels or Instructions w3c/wcag#1698, by @LaurenceRLewis.
-
Are compound autocomplete tokens conforming? w3c/wcag#1697, by @DavidMacDonald.
-
Test procedure for Technique H2 may have a typo that makes it invalid w3c/wcag#1694, by @mraccess77.
-
Findable help (3.2.6) demands contact links within PDF's for instance? w3c/wcag#1693, by @ShadowBB.
-
Editorial grammar/logical error in exception for Redundant entry w3c/wcag#1690, by @DavidMacDonald.
-
If an action within a process is NOT required, is it a process at all? w3c/wcag#1685, by @jake-abma.
-
"Page break" or "pagebreak"? w3c/wcag#1683, by @plannero.
-
Benefit 'lists' not applicable 2.4.1: Bypass Blocks w3c/wcag#1678, by @jake-abma.
-
Second benefit at 2.2.5: Re-authenticating wrong w3c/wcag#1675, by @jake-abma.
-
Can large headings be exempt from Success Criterion 1.4.4 Resize text? w3c/wcag#1671, by @simevidas.
-
Pointer targets and continuous areas w3c/wcag#1661, by @alastc.
-
Alter note for Redundant Entry w3c/wcag#1660, by @mbgower.
-
Carousels fail 2.2.1: Timing Adjustable ?! w3c/wcag#1658, by @jake-abma.
-
-
29 issues closed.
-
Understanding Text Spacing w3c/wcag#347.
-
SC 3.3.8 Re-entering usually isn't essential w3c/wcag#1346.
-
"Page break" or "pagebreak"? w3c/wcag#1683.
-
Translations URLs pointing to folders rather than documents w3c/wcag#1319.
-
I18N Self-Review w3c/wcag#1349.
-
"How to Meet" Links in WCAG 2.2 All Return 404 Errors w3c/wcag#1421.
-
2.4.13 Fixed reference points needs definitions w3c/wcag#1426.
-
Pointer targets and continuous areas w3c/wcag#1661.
-
SC 3.2.6 Findable Help - Goal of Criterion Ambiguous w3c/wcag#1435.
-
Wrong linking Understanding pages WCAG 2.1 w3c/wcag#966.
-
Broken links in Understanding Contrast (Minimum) w3c/wcag#973.
-
Invalid Links in Key Terms w3c/wcag#883.
-
What is meant by "a set of web pages"? w3c/wcag#1367.
-
SC 3.3.8 Redundant Entry and User Frustration w3c/wcag#1431.
-
1.4.11 and video scrubbing controls w3c/wcag#1655.
-
60 issues received 320 new comments.
-
Are 'Headings' enough to pass 2.4.1: Bypass Blocks w3c/wcag#1712 (54 comments by @aardrian, @awkawk, @bruce-usab, @detlevhfischer, @ericwbailey, @erikkroes, @jake-abma, @JAWS-test, @MarcHaunschild, @mitchellevan, @mraccess77, @patrickhlauke, @stevefaulkner, @yatil, @ZoeBijl)
-
Carousels fail 2.2.1: Timing Adjustable ?! w3c/wcag#1658 (51 comments by @alastc, @awkawk, @bruce-usab, @detlevhfischer, @jake-abma, @JAWS-test, @jongund, @mraccess77)
-
Do icons / images without visible text fail 2.4.6 Headings and Labels, always? w3c/wcag#1695 (30 comments by @awkawk, @bruce-usab, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke, @scottaohara)
-
What is an "input field"? (1.3.5 Identify Input Purpose) w3c/wcag#1652 (18 comments by @alastc, @awkawk, @JAWS-test, @johnfoliot, @mraccess77, @patrickhlauke)
-
Validity of independent review (retitled) w3c/wcag#1622 (13 comments by @alastc, @bruce-usab, @johnfoliot, @jspellman, @sajkaj)
-
"setting all of the following" wording nitpick in normative 1.4.12: Text Spacing w3c/wcag#930 (9 comments by @alastc, @JAWS-test, @patrickhlauke)
-
Findable help (3.2.6) demands contact links within PDF's for instance? w3c/wcag#1693 (8 comments by @alastc, @mraccess77, @ShadowBB)
-
Text spacing: does it require compatibility with one or all methods? w3c/wcag#975 (8 comments by @alastc, @ernistkg, @JAWS-test, @patrickhlauke)
-
Focus Appearance (Minimum), minumum area, second calculation could be too small w3c/wcag#1684 (8 comments by @alastc, @JAWS-test, @mbgower, @mraccess77)
-
Does 2.5.3 "Label in Name" apply to placeholder (where used as only visible label)? w3c/wcag#1700 (7 comments by @alastc, @awkawk, @jake-abma, @JAWS-test, @jlukosky)
-
G63: Providing a site map is NOT a Sufficient technique for 2.4.8: Location w3c/wcag#1696 (7 comments by @alastc, @bruce-usab, @erikkroes, @jake-abma, @mraccess77)
-
2.5.4 understanding - suggestion to remove the "user gestures towards device" angle w3c/wcag#1464 (6 comments by @detlevhfischer, @patrickhlauke)
-
Test procedure for Technique H2 may have a typo that makes it invalid w3c/wcag#1694 (5 comments by @awkawk, @JAWS-test, @mraccess77)
-
Can large headings be exempt from Success Criterion 1.4.4 Resize text? w3c/wcag#1671 (5 comments by @alastc, @JAWS-test, @mitchellevan, @mraccess77)
-
Does the image of WCAG1.4.11 'Dynamic Examples' satisfy WCAG 1.4.11? w3c/wcag#1670 (5 comments by @bruce-usab, @detlevhfischer, @JAWS-test, @sukoyakarizumu)
-
Visible Required label and 3.3.2: Labels or Instructions w3c/wcag#1698 (4 comments by @JAWS-test, @LaurenceRLewis)
-
If an action within a process is NOT required, is it a process at all? w3c/wcag#1685 (4 comments by @alastc, @detlevhfischer, @jake-abma)
-
Add the use of aria-current as a sufficient technique for Info And Relationships? w3c/wcag#1681 (4 comments by @alastc, @detlevhfischer, @fstrr, @JAWS-test)
-
Understanding WCAG 2.1 docs still incorrectly say WCAG 2.0 w3c/wcag#1068 (3 comments by @missmatsuko, @yatil)
-
Benefit 'lists' not applicable 2.4.1: Bypass Blocks w3c/wcag#1678 (3 comments by @bruce-usab, @jake-abma, @JAWS-test)
-
Using CSS letter-spacing to control spacing within a word w3c/wcag#918 (2 comments by @alastc, @patrickhlauke)
-
Editorial grammar/logical error in exception for Redundant entry w3c/wcag#1690 (2 comments by @alastc)
-
2.5.8 User Agent exception should be about the target with its spacing, not just the target w3c/wcag#1682 (2 comments by @alastc, @mitchellevan)
-
2.4.7 Focus Visible: WCAG 2.1 Understanding has wrong level (A instead of AA) w3c/wcag#1178 (2 comments by @alastc, @yatil)
-
SC 3.2.6 Findable Help - Goal of Criterion Ambiguous w3c/wcag#1435 (2 comments by @alastc, @rachaelbradley)
-
2.3.2: Three Flashes: Blink can overlap flash, sentence need part deleted or updated, contradiction! w3c/wcag#1677 (2 comments by @bruce-usab, @jake-abma)
-
Change to minimum focus area of SC 2.4.11 allows for small areas increases with no contrast w3c/wcag#1646 (1 comment by @alastc)
-
2.4.11 Focus Appearance (Minimum) - the math is difficult to understand and explain w3c/wcag#1439 (1 comment by @alastc)
-
Do issues with Windows high contrast mode fall under WCAG 2.1? w3c/wcag#623 (1 comment by @jlukosky)
-
Translations URLs pointing to folders rather than documents w3c/wcag#1319 (1 comment by @michael-n-cooper)
-
"How to Meet" Links in WCAG 2.2 All Return 404 Errors w3c/wcag#1421 (1 comment by @michael-n-cooper)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.2.6 Findable Help w3c/wcag#1448 (1 comment by @alastc)
-
Findable help term web page at the end of the phrase is confusing w3c/wcag#1574 (1 comment by @rachaelbradley)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.3.8 Redundant entry w3c/wcag#1453 (1 comment by @alastc)
-
SC 3.2.6 Findable Help - Definition for "Set of Web Pages" Needs Refinement w3c/wcag#1436 (1 comment by @alastc)
-
SC 2.5.8 Pointer Target Spacing - Suggested reformulation of pointer clearance calculation w3c/wcag#1444 (1 comment by @alastc)
-
SC 2.5.8 Pointer Target Spacing – Shouldn’t this SC require a minimum target size and spacing requirements? w3c/wcag#1433 (1 comment by @alastc)
-
Pointer Target Spacing (2.5.8), user agent defaults, and lists of links/controls w3c/wcag#1384 (1 comment by @alastc)
-
2.5.8 Larger target sizes could conflict with people needing page zoom w3c/wcag#1381 (1 comment by @alastc)
-
Pointer Target Spacing (2.5.8): Unintentional incentive to reduce target size to pass criterion w3c/wcag#1361 (1 comment by @alastc)
-
-
28 pull requests opened.
-
Consistent help, stray quote mark w3c/wcag#1714, by @alastc.
-
Tweak bypass blocks understanding w3c/wcag#1713, by @patrickhlauke.
-
Page break locator update w3c/wcag#1711, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1710, by @alastc.
-
Target size minimum understanding rev w3c/wcag#1708, by @detlevhfischer.
-
New ARIA technique for the aria-current attribute w3c/wcag#1707, by @fstrr.
-
Update URL to HTML Accessibility Mappings w3c/wcag#1706, by @fstrr.
-
Wcag22 typos and editorial w3c/wcag#1703, by @alastc.
-
Wcag22 typos and editorial w3c/wcag#1701, by @alastc.
-
Aria22 modification for aria-atomic w3c/wcag#1699, by @detlevhfischer.
-
Wcag22 typos and editorial w3c/wcag#1692, by @alastc.
-
Redundant entry: Grammar update w3c/wcag#1691, by @alastc.
-
Update time-limits-required-behaviors.xml w3c/wcag#1688, by @bruce-usab.
-
Understanding 1.4.12: clarify the intent and author responsibility w3c/wcag#1687, by @patrickhlauke.
-
Pointer target spacing to target size w3c/wcag#1680, by @alastc.
-
Implementing changes from 2021-03-09 w3c/wcag#1679, by @alastc.
-
Target size Understanding variant-no new exceptions w3c/wcag#1674, by @detlevhfischer.
-
Target Size (Minimum): updates w3c/wcag#1673, by @detlevhfischer.
-
1.4.11 Understanding - slight rewording w3c/wcag#1672, by @detlevhfischer.
-
Findable help understanding march 21 w3c/wcag#1669, by @rachaelbradley.
-
Findable help understanding w3c/wcag#1668, by @rachaelbradley.
-
Target spacing - add continuous region exception (2) w3c/wcag#1667, by @alastc.
-
Target spacing - adding alternatives exception w3c/wcag#1666, by @alastc.
-
Renaming target-size SCs w3c/wcag#1665, by @alastc.
-
Target-spacing: Adding equivalent function exception w3c/wcag#1664, by @alastc.
-
Target spacing - add continuous region exception w3c/wcag#1663, by @alastc.
-
Findable help updates w3c/wcag#1662, by @alastc.
-
Redundent entry update from @mbgower w3c/wcag#1659, by @alastc.
-
-
16 pull requests merged.
-
Consistent help, stray quote mark w3c/wcag#1714.
-
Page break locator update w3c/wcag#1711.
-
Wcag22 typos and editorial w3c/wcag#1710.
-
Wcag22 typos and editorial w3c/wcag#1703.
-
Wcag22 typos and editorial w3c/wcag#1701.
-
Wcag22 typos and editorial w3c/wcag#1692.
-
Redundant entry: Grammar update w3c/wcag#1691.
-
Visible controls - Updates to examples from Rain w3c/wcag#1648.
-
Dragging movement understanding - Sarah's update w3c/wcag#1649.
-
Aligning focus-vis-enhanced with new min-version w3c/wcag#1623.
-
Pointer target spacing to target size w3c/wcag#1680.
-
Pointer target spacing update w3c/wcag#1608.
-
Implementing changes from 2021-03-09 w3c/wcag#1679.
-
Target size Understanding variant-no new exceptions w3c/wcag#1674.
-
Redundant entry updates w3c/wcag#1639.
-
Adding link to W3C captcha page from "process" w3c/wcag#1640.
-
-
13 pull requests closed.
-
Pointer target spacing understanding revised w3c/wcag#1641.
-
Renaming target-size SCs w3c/wcag#1665.
-
Target Size (Minimum): updates w3c/wcag#1673.
-
Target spacing - add continuous region exception (2) w3c/wcag#1667.
-
Target spacing - adding alternatives exception w3c/wcag#1666.
-
Findable help understanding march 21 w3c/wcag#1669.
-
Correct a citation under Themes from Research w3c/wcag#1629.
-
correct typo 4.2.1 to 4.1.2 w3c/wcag#1589.
-
Findable help understanding w3c/wcag#1668.
-
Target spacing - add continuous region exception w3c/wcag#1663.
-
Target-spacing: Adding equivalent function exception w3c/wcag#1664.
-
decision-policy CWA w3c/wcag#1653.
-
-
18 pull requests received 58 new comments.
-
Target size minimum understanding rev w3c/wcag#1708 (22 comments by @alastc, @detlevhfischer, @patrickhlauke)
-
more clarity on reasonable objections w3c/wcag#1596 (9 comments by @alastc, @awkawk, @bruce-usab, @mbgower)
-
New ARIA technique for the aria-current attribute w3c/wcag#1707 (5 comments by @detlevhfischer, @fstrr, @JAWS-test)
-
Understanding 1.4.12: clarify the intent and author responsibility w3c/wcag#1687 (4 comments by @JAWS-test, @patrickhlauke)
-
Target-spacing: Adding equivalent function exception w3c/wcag#1664 (4 comments by @alastc, @detlevhfischer)
-
w3c/wcag-act
-
2 issues opened.
-
ACT rules and machine learning w3c/wcag-act#512, by @WilcoFiers.
-
2 issues received 2 new comments.
-
2 pull requests opened.
-
Update wcag-ruleset-review-process.md w3c/wcag-act#515, by @WilcoFiers.
-
Create act-publication-process.md w3c/wcag-act#514, by @WilcoFiers.
-
-
1 pull request closed.
-
Create act-publication-process.md w3c/wcag-act#514.
-
-
2 pull requests received 49 new comments.
-
Update wcag-ruleset-review-process.md w3c/wcag-act#515 (38 comments by @annethyme, @daniel-montalvo, @johnhix, @Jym77, @maryjom, @tbostic32, @WilcoFiers)
-
w3c/wcag3
-
16 issues opened.
-
Email: IBM Comments on WCAG 3.0 Draft (6 - Terminology & Naming) w3c/wcag3#263, by @cwadamsoforacle.
-
New SC for audio quality of canned video/audio? w3c/wcag3#173, by @detlevhfischer.
-
Email: Comments on WCAG 3.0 draft (11 - Clear Words w3c/wcag3#264, by @jspellman.
-
Email: Comments on WCAG 3.0 draft (9 - "users") w3c/wcag3#265, by @jspellman.
-
Email: Intopia Feedback - WCAG 3.0 FPWD (5 - Processes) w3c/wcag3#280, by @jspellman.
-
Email: Intopia Feedback - WCAG 3.0 FPWD (4 - Testing) w3c/wcag3#281, by @jspellman.
-
Update the APC Algorithm to be compatible with RGBA colors w3c/wcag3#285, by @SFM61319.
-
Email: WCAG 3.0 public comment (15 - open vs closed captions w3c/wcag3#298, by @jspellman.
-
Consider switching to bikeshed for a11y reasons w3c/wcag3#299, by @WilcoFiers.
-
Content Must Be Automatically Translatable w3c/wcag3#300, by @MakotoUeki.
-
Way of Gathering Feedback from Users w3c/wcag3#383, by @MakotoUeki.
-
22 issues received 36 new comments.
-
New SC for audio quality of canned video/audio? w3c/wcag3#173 (6 comments by @alastc, @detlevhfischer, @mraccess77, @patrickhlauke)
-
Update the APC Algorithm to be compatible with RGBA colors w3c/wcag3#285 (5 comments by @bruce-usab, @ChrisLoiselle, @jspellman, @Myndex)
-
How does the guideline ensure text is sufficiently readable for people with CVD (colourblindness) w3c/wcag3#403 (1 comment by @ChrisLoiselle)
-
Email: IBM Comments on WCAG 3.0 Draft (8 - Plain language summaries) w3c/wcag3#262 (1 comment by @cwadamsoforacle)
-
Email: IBM Comments on WCAG 3.0 Draft (6 - Terminology & Naming) w3c/wcag3#263 (1 comment by @cwadamsoforacle)
-
Mapping to WCAG2 (via email: ITI Comments on First Public Working Draft) w3c/wcag3#284 (1 comment by @jspellman)
-
Email: WCAG 3.0 public comment (15 - open vs closed captions w3c/wcag3#298 (1 comment by @jspellman)
-
Interactive Content? Escaping the linear Page/Form/linear media paradigm. w3c/wcag3#381 (1 comment by @jspellman)
-
w3c/coga
-
1 issue opened.
-
Explore spatial representations w3c/coga#279, by @rachaelbradley.
-
-
31 issues closed.
-
EO comments: Put the Introduction first. w3c/coga#214.
-
list punctuation - copyedit and consistency edit w3c/coga#235.
-
Change examples to active tense w3c/coga#116.
-
Summary headings and content w3c/coga#118.
-
Persona diversity w3c/coga#131.
-
Persona names w3c/coga#135.
-
Suggested updates to the Summary w3c/coga#138.
-
More Pattern examples w3c/coga#153.
-
Having names of users from various cultural backgrounds w3c/coga#161.
-
Suggested edits for 3.6.3 User Story: Voice Menus w3c/coga#165.
-
Consistency: "short-term memory" and "short term memory" w3c/coga#191.
-
Suggestions for streamlining the table of contents w3c/coga#193.
-
EO comments: Draft idea for section 5 text w3c/coga#207.
-
EO comments: Move “Following the advice in this document w3c/coga#211.
-
EO comments: Headings repetition w3c/coga#221.
-
COGA icon review suggestions w3c/coga#231.
-
Comment from Ceapat (Spain) Use of numbers. 4.4.13 w3c/coga#238.
-
Are you a designer? w3c/coga#224.
-
2 issues reopened.
-
EO comment: 4.8. QA review and copy edit w3c/coga#223, by @rachaelbradley.
-
44 issues received 75 new comments.
-
EO comments: Summary, Appendix A: Mapping User Needs, Persona and Patterns, Introduction, Objectives w3c/coga#213 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Change “Summary” to something like “Objectives and Overview”. w3c/coga#215 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Draft idea for section 5 text w3c/coga#207 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Provide the information in a more consumable way than a single TR doc w3c/coga#209 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Move “Following the advice in this document w3c/coga#211 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: In the tables, also link the User Stories and Design Patterns. w3c/coga#216 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Please change some persona names so diverse ethnicities are included. w3c/coga#222 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: From the Summary - “I had difficulty understanding objectives 1 and 3. w3c/coga#220 (2 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Specific suggestions to improve usability w3c/coga#210 (2 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Appendix B: Considerations for Uptake in Different Contexts and Policies w3c/coga#208 (2 comments by @rachaelbradley, @shawna-slh)
-
EO comments: 2.3. Building the User into the Development Process and Usability Testing w3c/coga#205 (2 comments by @rachaelbradley, @shawna-slh)
-
Comment from Ceapat (Spain) Use of numbers. 4.4.13 w3c/coga#238 (2 comments by @claraceapat, @rachaelbradley)
-
8 suggestions to clarify the 2nd chapter ("Introduction") and make it easier to digest w3c/coga#195 (1 comment by @jpascalides)
-
Consider adding a persona "non-native speakers with limited language skills w3c/coga#162 (1 comment by @rachaelbradley)
-
Suggest adding another example to 4.3.3. Pattern: Use a Clear and Understandable Page Structure w3c/coga#171 (1 comment by @rachaelbradley)
-
Suggested changes to the Anna (dyslexia) persona and scenarios w3c/coga#177 (1 comment by @rachaelbradley)
-
Suggested changes to Jonathan (dyscalculia) persona and scenarios w3c/coga#179 (1 comment by @rachaelbradley)
-
Consistency: "short-term memory" and "short term memory" w3c/coga#191 (1 comment by @rachaelbradley)
-
EO comments: Focus Content Usable on designers, developers, and writers w3c/coga#202 (1 comment by @shawna-slh)
-
EO comments: 2.2. Background about People with Learning and Cognitive Disabilities and the Web w3c/coga#204 (1 comment by @shawna-slh)
-
EO comments: Integrate content into existing WAI website resources w3c/coga#201 (1 comment by @shawna-slh)
-
Comment from Ceapat (Spain), related to: 4.4.1 Pattern: Use Clear Words w3c/coga#233 (1 comment by @rachaelbradley)
-
-
32 pull requests opened.
-
DRAFT Updates from AG Meeting w3c/coga#281, by @rachaelbradley.
-
Semantic markup in sum, visually styled as paras w3c/coga#280, by @rainbreaw.
-
Update design.html - fix HTML5 link in 4.9.4.5 w3c/coga#276, by @rainbreaw.
-
Update design.html - extra characters in 4.8.6.3 How it Helps w3c/coga#272, by @rainbreaw.
-
Update design.html - missing period in 4.7.3.3 How it Helps w3c/coga#271, by @rainbreaw.
-
Update design.html - typo in 4.7.2.2 w3c/coga#270, by @rainbreaw.
-
Update design.html - copying or coping w3c/coga#269, by @rainbreaw.
-
Update design.html - typos in 4.6.4.3 w3c/coga#268, by @rainbreaw.
-
Update design.html - typos in 4.6.3.2 and 4.6.3.3 w3c/coga#267, by @rainbreaw.
-
Update design.html - removing extra word in 4.5.9.5 w3c/coga#266, by @rainbreaw.
-
Update design.html - typos in 4.5.9.3 How it Helps w3c/coga#265, by @rainbreaw.
-
Update design.html - fixing a typo in 4.5.6.4 More Details w3c/coga#264, by @rainbreaw.
-
Update design.html fixing typos in 4.5.4.4 More Details w3c/coga#263, by @rainbreaw.
-
Update design.html - misplaced p tag in 4.5 objective 4 w3c/coga#262, by @rainbreaw.
-
Update design.html fixing typos under 4.4.9.4 w3c/coga#261, by @rainbreaw.
-
Update design.html add missing period and small markup fix w3c/coga#260, by @rainbreaw.
-
Update design.html - fix typo in 4.3.5.4 w3c/coga#259, by @rainbreaw.
-
Update to address issue 211 w3c/coga#258, by @rachaelbradley.
-
Issue 206 w3c/coga#257, by @rachaelbradley.
-
Move usability scoping statement w3c/coga#256, by @rachaelbradley.
-
Update design.html w3c/coga#255, by @rainbreaw.
-
Update index.html w3c/coga#254, by @rainbreaw.
-
Update index.html w3c/coga#253, by @rainbreaw.
-
Update index.html fixing "section" words in lines 252-255 w3c/coga#252, by @rainbreaw.
-
Update index.html to fix broken line item tag w3c/coga#251, by @rainbreaw.
-
Update index.html - remove double "cognitive" w3c/coga#250, by @rainbreaw.
-
Consistency checks w3c/coga#249, by @jpascalides.
-
-
27 pull requests merged.
-
Semantic markup in sum, visually styled as paras w3c/coga#280.
-
Update design.html - fix HTML5 link in 4.9.4.5 w3c/coga#276.
-
Update design.html - typo in 4.7.2.2 w3c/coga#270.
-
Update design.html - copying or coping w3c/coga#269.
-
Update design.html - typos in 4.6.4.3 w3c/coga#268.
-
Update design.html - removing extra word in 4.5.9.5 w3c/coga#266.
-
Update design.html - typos in 4.5.9.3 How it Helps w3c/coga#265.
-
Update design.html fixing typos in 4.5.4.4 More Details w3c/coga#263.
-
Update design.html - misplaced p tag in 4.5 objective 4 w3c/coga#262.
-
Update design.html fixing typos under 4.4.9.4 w3c/coga#261.
-
Update design.html - fix typo in 4.3.5.4 w3c/coga#259.
-
typo: then -> than w3c/coga#148.
-
Update to address issue 211 w3c/coga#258.
-
Move usability scoping statement w3c/coga#256.
-
Update index.html - remove double "cognitive" w3c/coga#250.
-
Update index.html to fix broken line item tag w3c/coga#251.
-
Update index.html w3c/coga#253.
-
Update index.html w3c/coga#254.
-
Update design.html w3c/coga#255.
-
merge Part 2a and 2b to main branch w3c/coga#247.
-
-
7 pull requests closed.
-
Update design.html - typos in 4.6.3.2 and 4.6.3.3 w3c/coga#267.
-
"not" repeated twice. w3c/coga#146.
-
Issue 206 w3c/coga#257.
-
6 pull requests received 6 new comments.
-
Update index.html - missing period in second line item under glossary: memory impairments w3c/coga#277 (1 comment by @michael-n-cooper)
-
Update design.html - unintentional characters in 4.9.3.3 How it Helps w3c/coga#274 (1 comment by @michael-n-cooper)
-
Update design.html - extra characters in 4.8.6.3 How it Helps w3c/coga#272 (1 comment by @michael-n-cooper)
-
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 participant joined the Cognitive and Learning Disabilities Accessibility Task Force.
-
Marcos Franco Murillo joined.
-
GitHub
w3c/coga
-
1 issue opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Explore spatial representations w3c/coga#279, by @rachaelbradley.
-
-
31 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
EO comments: Put the Introduction first. w3c/coga#214.
-
list punctuation - copyedit and consistency edit w3c/coga#235.
-
Change examples to active tense w3c/coga#116.
-
Summary headings and content w3c/coga#118.
-
Persona diversity w3c/coga#131.
-
Persona names w3c/coga#135.
-
Suggested updates to the Summary w3c/coga#138.
-
More Pattern examples w3c/coga#153.
-
Having names of users from various cultural backgrounds w3c/coga#161.
-
Suggested edits for 3.6.3 User Story: Voice Menus w3c/coga#165.
-
Consistency: "short-term memory" and "short term memory" w3c/coga#191.
-
Suggestions for streamlining the table of contents w3c/coga#193.
-
EO comments: Draft idea for section 5 text w3c/coga#207.
-
EO comments: Move “Following the advice in this document w3c/coga#211.
-
EO comments: Headings repetition w3c/coga#221.
-
COGA icon review suggestions w3c/coga#231.
-
Comment from Ceapat (Spain) Use of numbers. 4.4.13 w3c/coga#238.
-
Are you a designer? w3c/coga#224.
-
2 issues reopened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
EO comment: 4.8. QA review and copy edit w3c/coga#223, by @rachaelbradley.
-
44 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 75 new comments.
-
EO comments: Summary, Appendix A: Mapping User Needs, Persona and Patterns, Introduction, Objectives w3c/coga#213 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Change “Summary” to something like “Objectives and Overview”. w3c/coga#215 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Draft idea for section 5 text w3c/coga#207 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Provide the information in a more consumable way than a single TR doc w3c/coga#209 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Move “Following the advice in this document w3c/coga#211 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: In the tables, also link the User Stories and Design Patterns. w3c/coga#216 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Please change some persona names so diverse ethnicities are included. w3c/coga#222 (3 comments by @rachaelbradley, @shawna-slh)
-
EO comments: From the Summary - “I had difficulty understanding objectives 1 and 3. w3c/coga#220 (2 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Specific suggestions to improve usability w3c/coga#210 (2 comments by @rachaelbradley, @shawna-slh)
-
EO comments: Appendix B: Considerations for Uptake in Different Contexts and Policies w3c/coga#208 (2 comments by @rachaelbradley, @shawna-slh)
-
EO comments: 2.3. Building the User into the Development Process and Usability Testing w3c/coga#205 (2 comments by @rachaelbradley, @shawna-slh)
-
Comment from Ceapat (Spain) Use of numbers. 4.4.13 w3c/coga#238 (2 comments by @claraceapat, @rachaelbradley)
-
8 suggestions to clarify the 2nd chapter ("Introduction") and make it easier to digest w3c/coga#195 (1 comment by @jpascalides)
-
Consider adding a persona "non-native speakers with limited language skills w3c/coga#162 (1 comment by @rachaelbradley)
-
Suggest adding another example to 4.3.3. Pattern: Use a Clear and Understandable Page Structure w3c/coga#171 (1 comment by @rachaelbradley)
-
Suggested changes to the Anna (dyslexia) persona and scenarios w3c/coga#177 (1 comment by @rachaelbradley)
-
Suggested changes to Jonathan (dyscalculia) persona and scenarios w3c/coga#179 (1 comment by @rachaelbradley)
-
Consistency: "short-term memory" and "short term memory" w3c/coga#191 (1 comment by @rachaelbradley)
-
EO comments: Focus Content Usable on designers, developers, and writers w3c/coga#202 (1 comment by @shawna-slh)
-
EO comments: 2.2. Background about People with Learning and Cognitive Disabilities and the Web w3c/coga#204 (1 comment by @shawna-slh)
-
EO comments: Integrate content into existing WAI website resources w3c/coga#201 (1 comment by @shawna-slh)
-
Comment from Ceapat (Spain), related to: 4.4.1 Pattern: Use Clear Words w3c/coga#233 (1 comment by @rachaelbradley)
-
-
32 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
DRAFT Updates from AG Meeting w3c/coga#281, by @rachaelbradley.
-
Semantic markup in sum, visually styled as paras w3c/coga#280, by @rainbreaw.
-
Update design.html - fix HTML5 link in 4.9.4.5 w3c/coga#276, by @rainbreaw.
-
Update design.html - extra characters in 4.8.6.3 How it Helps w3c/coga#272, by @rainbreaw.
-
Update design.html - missing period in 4.7.3.3 How it Helps w3c/coga#271, by @rainbreaw.
-
Update design.html - typo in 4.7.2.2 w3c/coga#270, by @rainbreaw.
-
Update design.html - copying or coping w3c/coga#269, by @rainbreaw.
-
Update design.html - typos in 4.6.4.3 w3c/coga#268, by @rainbreaw.
-
Update design.html - typos in 4.6.3.2 and 4.6.3.3 w3c/coga#267, by @rainbreaw.
-
Update design.html - removing extra word in 4.5.9.5 w3c/coga#266, by @rainbreaw.
-
Update design.html - typos in 4.5.9.3 How it Helps w3c/coga#265, by @rainbreaw.
-
Update design.html - fixing a typo in 4.5.6.4 More Details w3c/coga#264, by @rainbreaw.
-
Update design.html fixing typos in 4.5.4.4 More Details w3c/coga#263, by @rainbreaw.
-
Update design.html - misplaced p tag in 4.5 objective 4 w3c/coga#262, by @rainbreaw.
-
Update design.html fixing typos under 4.4.9.4 w3c/coga#261, by @rainbreaw.
-
Update design.html add missing period and small markup fix w3c/coga#260, by @rainbreaw.
-
Update design.html - fix typo in 4.3.5.4 w3c/coga#259, by @rainbreaw.
-
Update to address issue 211 w3c/coga#258, by @rachaelbradley.
-
Issue 206 w3c/coga#257, by @rachaelbradley.
-
Move usability scoping statement w3c/coga#256, by @rachaelbradley.
-
Update design.html w3c/coga#255, by @rainbreaw.
-
Update index.html w3c/coga#254, by @rainbreaw.
-
Update index.html w3c/coga#253, by @rainbreaw.
-
Update index.html fixing "section" words in lines 252-255 w3c/coga#252, by @rainbreaw.
-
Update index.html to fix broken line item tag w3c/coga#251, by @rainbreaw.
-
Update index.html - remove double "cognitive" w3c/coga#250, by @rainbreaw.
-
Consistency checks w3c/coga#249, by @jpascalides.
-
-
27 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Semantic markup in sum, visually styled as paras w3c/coga#280.
-
Update design.html - fix HTML5 link in 4.9.4.5 w3c/coga#276.
-
Update design.html - typo in 4.7.2.2 w3c/coga#270.
-
Update design.html - copying or coping w3c/coga#269.
-
Update design.html - typos in 4.6.4.3 w3c/coga#268.
-
Update design.html - removing extra word in 4.5.9.5 w3c/coga#266.
-
Update design.html - typos in 4.5.9.3 How it Helps w3c/coga#265.
-
Update design.html fixing typos in 4.5.4.4 More Details w3c/coga#263.
-
Update design.html - misplaced p tag in 4.5 objective 4 w3c/coga#262.
-
Update design.html fixing typos under 4.4.9.4 w3c/coga#261.
-
Update design.html - fix typo in 4.3.5.4 w3c/coga#259.
-
typo: then -> than w3c/coga#148.
-
Update to address issue 211 w3c/coga#258.
-
Move usability scoping statement w3c/coga#256.
-
Update index.html - remove double "cognitive" w3c/coga#250.
-
Update index.html to fix broken line item tag w3c/coga#251.
-
Update index.html w3c/coga#253.
-
Update index.html w3c/coga#254.
-
Update design.html w3c/coga#255.
-
merge Part 2a and 2b to main branch w3c/coga#247.
-
-
7 pull requests closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Update design.html - typos in 4.6.3.2 and 4.6.3.3 w3c/coga#267.
-
"not" repeated twice. w3c/coga#146.
-
Issue 206 w3c/coga#257.
-
6 pull requests in the Cognitive and Learning Disabilities Accessibility Task Force received 6 new comments.
-
Update index.html - missing period in second line item under glossary: memory impairments w3c/coga#277 (1 comment by @michael-n-cooper)
-
Update design.html - unintentional characters in 4.9.3.3 How it Helps w3c/coga#274 (1 comment by @michael-n-cooper)
-
Update design.html - extra characters in 4.8.6.3 How it Helps w3c/coga#272 (1 comment by @michael-n-cooper)
-
Low Vision Accessibility Task Force
Participants
-
2 chairs appointed in the Low Vision Accessibility Task Force.
-
Chris Loiselle became a chair.
-
Jonathan Avila became a chair.
-
-
1 chair stepped down in the Low Vision Accessibility Task Force.
-
Jim Allan stepped down as a chair.
-
-
1 participant joined the Low Vision Accessibility Task Force.
-
Chris Loiselle joined.
-
GitHub
w3c/low-vision-a11y-tf
-
1 issue opened in the Low Vision Accessibility Task Force.
-
Test issue for LVTF w3c/low-vision-a11y-tf#86, by @ChrisLoiselle.
-
-
1 issue closed in the Low Vision Accessibility Task Force.
-
Test issue for LVTF w3c/low-vision-a11y-tf#86.
-
-
1 issue in the Low Vision Accessibility Task Force received 1 new comment.
Participants
-
7 participants joined.
-
Christos Petrou (Centre for Inclusive Design) joined.
-
Albert Kim (W3C Invited Experts) joined.
-
Ian Smith (codeMantra U.S. LLC) joined.
-
Daniele Marano (Hilfsgemeinschaft der Blinden und Sehschwachen Österreichs) joined.
-
Allie Bogus (Understood.org) joined.
-
Rain Breaw Michaels (Google LLC) joined.
-
Richard Boardman (Salesforce) joined.
-
-
4 organizations joined.
-
Centre for Inclusive Design joined.
-
codeMantra U.S. LLC joined.
-
Hilfsgemeinschaft der Blinden und Sehschwachen Österreichs joined.
-
Understood.org joined.
-
GitHub
w3c/wcag3
-
7 issues opened.
-
WCAG 3 for personal and small business websites w3c/wcag3#388, by @WilcoFiers.
-
Suggesting testing tools / templates w3c/wcag3#404, by @rtenbrink-x.
-
How-Tos should be an Overview w3c/wcag3#405, by @danhendersonede-old.
-
Peer review of color contrast research w3c/wcag3#307, by @mfairchild365.
-
-
3 issues received 7 new comments.
-
Peer review of color contrast research w3c/wcag3#307 (5 comments by @alastc, @mfairchild365, @Myndex, @patrickhlauke)
-
How does the guideline ensure text is sufficiently readable for people with CVD (colourblindness) w3c/wcag3#403 (1 comment by @Myndex)
-
w3c/coga
-
5 issues opened.
-
Issues in some languages w3c/coga#248, by @xfq.
-
Review Updated Personas w3c/coga#246, by @rachaelbradley.
-
Add to Section 3.7.3 Directions w3c/coga#244, by @rachaelbradley.
-
Ability to make reminders loud w3c/coga#243, by @rachaelbradley.
-
-
20 issues closed.
-
Comments from Ceapat (Spain). Related to font w3c/coga#237.
-
Suggested addition to 3.7.5 User Story: Task Management w3c/coga#168.
-
Use of Person First Language for Autism. w3c/coga#139.
-
4.4.5.3 How it Helps (ADD) w3c/coga#188.
-
4.2.2.4 More Details - typo w3c/coga#184.
-
[minor] match outline numbering with Objective numbering w3c/coga#181.
-
Typo w3c/coga#147.
-
Appreciation w3c/coga#142.
-
Glossary w3c/coga#130.
-
Consider dropping Appendix C and others w3c/coga#121.
-
Venn Diagram Interpretation w3c/coga#129.
-
Repeated words (text typos) w3c/coga#183.
-
Typo - "nine personas" should be "ten personas" w3c/coga#166.
-
Comment from Ceapat (Spain) related to: 4.4.3.4 Examples w3c/coga#234.
-
EO comments: Icons in Summary w3c/coga#217.
-
Math Abbreviation w3c/coga#141.
-
-
1 issue reopened.
-
COGA icon review suggestions w3c/coga#231, by @lseeman.
-
-
32 issues received 52 new comments.
-
Comments from Ceapat (Spain). Related to font w3c/coga#237 (3 comments by @claraceapat, @lseeman, @rachaelbradley)
-
[minor] match outline numbering with Objective numbering w3c/coga#181 (2 comments by @rachaelbradley, @ruoxiran)
-
4.4.9.3 How it Helps (don't understand sentence, may need punctuation) w3c/coga#189 (2 comments by @rachaelbradley, @ruoxiran)
-
Write in plain English, Use Plain Language Guideline (Omit superfluous words)) w3c/coga#187 (1 comment by @ruoxiran)
-
Suggest adding more examples to 3.5.1 User Story: Distractions w3c/coga#164 (1 comment by @jpascalides)
-
Comment from Ceapat (Spain), related to: 4.4.1 Pattern: Use Clear Words w3c/coga#233 (1 comment by @jpascalides)
-
Two suggested changes to 5.4.1 Differences from Usability Testing with the General Population w3c/coga#175 (1 comment by @jpascalides)
-
Suggest adding "attention" to wayfinding list in 4.8.6 Pattern: Provide Help with Directions w3c/coga#174 (1 comment by @jpascalides)
-
Three suggested changes to 4.5. Objective 4: Help Users Avoid Mistakes or Correct Them w3c/coga#173 (1 comment by @jpascalides)
-
Four suggested changes to 4.4 Objective 3: Use Clear and Understandable Content w3c/coga#172 (1 comment by @jpascalides)
-
5 pull requests opened.
-
merge Part 2a and 2b to main branch w3c/coga#247, by @ruoxiran.
-
Language use w3c/coga#242, by @rachaelbradley.
-
Issue 118 Add "key topics" to summary w3c/coga#241, by @jpascalides.
-
Add "Mathematics" in parens - issue 141 w3c/coga#240, by @jpascalides.
-
Changes from issues w3c/coga#239, by @rachaelbradley.
-
-
6 pull requests merged.
-
Language use w3c/coga#242.
-
Add "Mathematics" in parens - issue 141 w3c/coga#240.
-
Issue 118 Add "key topics" to summary w3c/coga#241.
-
Changes from issues w3c/coga#239.
-
Changes from wording meeting w3c/coga#236.
-
correct reference to document w3c/coga#229.
-
-
6 pull requests received 9 new comments.
w3c/wcag
-
13 issues opened.
-
1.4.11 and video scrubbing controls w3c/wcag#1655, by @fstrr.
-
What is an "input field"? (1.3.5 Identify Input Purpose) w3c/wcag#1652, by @JAWS-test.
-
Skip links failing 1.4.13 content on hover/focus w3c/wcag#1650, by @alastc.
-
Images of text when text is on page w3c/wcag#1647, by @selfthinker.
-
Dragging SC text update w3c/wcag#1633, by @alastc.
-
Validity of independent review (retitled) w3c/wcag#1622, by @DavidMacDonald.
-
F99 - What does "STR key" mean? w3c/wcag#1620, by @8845musign.
-
Are subtitles baked into a video a failure of 1.4.5: Images of Text? w3c/wcag#1615, by @jake-abma.
-
If the technologies being used Vs. 'not mentioning' 1.4.5 Vs. 1.4.9 w3c/wcag#1614, by @jake-abma.
-
-
35 issues closed.
-
Issues for SC 1.3.6 Identify Purpose w3c/wcag#539.
-
[WCAG 2.2 Draft Feedback] 2.5.8 Pointer Target Spacing w3c/wcag#1456.
-
Skip links failing 1.4.13 content on hover/focus w3c/wcag#1650.
-
[WCAG 2.2 Draft Feedback] 3.2.7 Hidden Controls w3c/wcag#1455.
-
WCAG 2.2 2.5.7 Dragging and its reference to single pointer w3c/wcag#1225.
-
C41 does not fulfil SC 2.4.12 w3c/wcag#1306.
-
Dragging SC text update w3c/wcag#1633.
-
SC 3.3.8 Redundant entry, term "step" is ambiguous w3c/wcag#1345.
-
SC 2.4.13: Fixed Reference Points "on the same page" w3c/wcag#1302.
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.5.7 Dragging w3c/wcag#1454.
-
2.5.7: Dragging - essential example w3c/wcag#1336.
-
F99 - What does "STR key" mean? w3c/wcag#1620.
-
"user interface component" lowercase fixes w3c/wcag#1284.
-
2.4.13 Term "electronic publication" not needed w3c/wcag#1429.
-
Future simplification="important" technique w3c/wcag#1282.
-
-
51 issues received 124 new comments.
-
Images of text when text is on page w3c/wcag#1647 (9 comments by @bruce-usab, @JAWS-test, @mraccess77, @patrickhlauke, @selfthinker)
-
Skip links failing 1.4.13 content on hover/focus w3c/wcag#1650 (9 comments by @alastc, @awkawk, @bruce-usab, @innoticFR, @mraccess77, @patrickhlauke)
-
SC 1.4.11 applicability when focus indicator is a color swap and touches the adjacent background. w3c/wcag#1613 (7 comments by @alastc, @goodwitch, @JAWS-test, @mraccess77)
-
WCAG 2.2 2.5.7 Dragging and its reference to single pointer w3c/wcag#1225 (6 comments by @alastc, @DavidMacDonald, @patrickhlauke)
-
F99 - What does "STR key" mean? w3c/wcag#1620 (5 comments by @8845musign, @alastc, @detlevhfischer, @JAWS-test)
-
The term "minimum focus indicator area" is confusing w3c/wcag#1544 (4 comments by @alastc, @DavidMacDonald, @joesaiyang)
-
If the technologies being used Vs. 'not mentioning' 1.4.5 Vs. 1.4.9 w3c/wcag#1614 (4 comments by @alastc, @bruce-usab, @jake-abma, @JAWS-test)
-
Change to minimum focus area of SC 2.4.11 allows for small areas increases with no contrast w3c/wcag#1646 (3 comments by @alastc, @mraccess77)
-
Does the Definition of "Dragging Movements" Intentionally Limit the Scope to Moving Objects/Items? w3c/wcag#1560 (3 comments by @alastc, @detlevhfischer)
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.4.12 Focus Appearance (Minimum) w3c/wcag#1450 (3 comments by @alastc, @dshoukry)
-
Are subtitles baked into a video a failure of 1.4.5: Images of Text? w3c/wcag#1615 (3 comments by @bruce-usab, @jake-abma, @JAWS-test)
-
SC 2.5.8 Pointer Target Spacing - Minimum pointer clearance needs better empirical backing w3c/wcag#1445 (2 comments by @alastc)
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.4.12 Focus Appearance (Enhanced) w3c/wcag#1451 (2 comments by @alastc)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.3.8 Redundant entry w3c/wcag#1453 (2 comments by @alastc, @dshoukry)
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.4.13 Fixed Reference Points w3c/wcag#1449 (2 comments by @alastc)
-
2.4.11 Focus appearance (min) - complex requirement makes it difficult to write test instructions w3c/wcag#1460 (2 comments by @alastc, @ghost)
-
2.4.7: Focus Visible - verbiage to discourage low contrast implementations w3c/wcag#1588 (2 comments by @alastc, @chlane)
-
Findable help term web page at the end of the phrase is confusing w3c/wcag#1574 (1 comment by @mbgower)
-
Language of 1.4.10/Reflow exception seems broader than intended w3c/wcag#1049 (1 comment by @mbgower)
-
Understanding 3.3.1: Error Identification slightly unfocused/mixes up various concepts w3c/wcag#977 (1 comment by @patrickhlauke)
-
Suggest including the first note provided with SC 2.4.11 (AA) on SC 2.4.12 (AAA) as well. w3c/wcag#1405 (1 comment by @alastc)
-
2.5.4 Motion Actuation and camera access (for QR codes etc, not actual "gesturing towards the device") w3c/wcag#1404 (1 comment by @patrickhlauke)
-
Recommend working group provide guidance on calculating contrast of rgba w3c/wcag#1637 (1 comment by @alastc)
-
H99 test procedure only tests for navigation aspect of page breaks and not locators w3c/wcag#1592 (1 comment by @alastc)
-
3.2.7 Hidden Controls – What qualifies as progress or completing a process? w3c/wcag#1442 (1 comment by @alastc)
-
"3.2.7 Hidden Controls" Suggest Clarifying statement about "multiple controls ... in a single location" w3c/wcag#1402 (1 comment by @alastc)
-
3.2.7: Hidden Controls - what happens with optional / on-demand controls w3c/wcag#1400 (1 comment by @alastc)
-
Hidden Controls (3.2.7): clarify definition of process and controls needed to progress or complete a process w3c/wcag#1360 (1 comment by @alastc)
-
Hidden controls SC3.2.7 - Does this cover invisible form fields? w3c/wcag#1243 (1 comment by @alastc)
-
Hidden controls SC3.2.7 - case where the hover is over a related component w3c/wcag#1241 (1 comment by @alastc)
-
SC 2.5.8 Pointer Target Spacing - Clarification: Overlapping Spacing w3c/wcag#1312 (1 comment by @alastc)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.2.6 Findable Help w3c/wcag#1448 (1 comment by @alastc)
-
-
31 pull requests opened.
-
Update findable-help.html w3c/wcag#1657, by @mbgower.
-
Update reflow.html w3c/wcag#1656, by @mbgower.
-
decision-policy CWA w3c/wcag#1653, by @cwadamsoforacle.
-
Rewrite for 3.3.1 Error Identification understanding document w3c/wcag#1651, by @patrickhlauke.
-
Dragging movement understanding - Sarah's update w3c/wcag#1649, by @alastc.
-
Visible controls - Updates to examples from Rain w3c/wcag#1648, by @alastc.
-
Pointer target spacing - Wilco update w3c/wcag#1645, by @alastc.
-
Add two notes/clarifications to 2.1.1/2.1.3 understanding w3c/wcag#1642, by @patrickhlauke.
-
Pointer target spacing understanding revised w3c/wcag#1641, by @detlevhfischer.
-
Adding link to W3C captcha page from "process" w3c/wcag#1640, by @alastc.
-
Redundant entry updates w3c/wcag#1639, by @alastc.
-
reformulation of dragging/pointer gesture difference w3c/wcag#1638, by @detlevhfischer.
-
David macdonald patch drag pointer w3c/wcag#1636, by @DavidMacDonald.
-
Pointer target spacing understanding revised w3c/wcag#1635, by @detlevhfischer.
-
Operated to acheived w3c/wcag#1634, by @alastc.
-
Update pointer-target-spacing-understanding.html w3c/wcag#1632, by @detlevhfischer.
-
Change STR to Ctrl w3c/wcag#1631, by @detlevhfischer.
-
Correct a citation under Themes from Research w3c/wcag#1629, by @bruce-usab.
-
Idea for dealing with 1544 w3c/wcag#1628, by @alastc.
-
G195 update, removing mouse aspect w3c/wcag#1627, by @alastc.
-
Updating the contrast requirement w3c/wcag#1626, by @alastc.
-
Adding note suggested in 1405 w3c/wcag#1625, by @alastc.
-
Editorial update to the 1st benefit w3c/wcag#1624, by @alastc.
-
Aligning focus-vis-enhanced with new min-version w3c/wcag#1623, by @alastc.
-
New pointer target image dropdown menu w3c/wcag#1621, by @detlevhfischer.
-
Issue1449 fixed ref points2 w3c/wcag#1619, by @alastc.
-
Wcag22 fixed ref points updates 2021 jan w3c/wcag#1618, by @alastc.
-
Examples updates w3c/wcag#1617, by @alastc.
-
Suggestion from 1282 w3c/wcag#1616, by @alastc.
-
Adding essential examples. w3c/wcag#1612, by @alastc.
-
-
19 pull requests merged.
-
Pointer target spacing - Wilco update w3c/wcag#1645.
-
Updating the contrast requirement w3c/wcag#1626.
-
David macdonald patch drag pointer w3c/wcag#1636.
-
reformulation of dragging/pointer gesture difference w3c/wcag#1638.
-
Operated to acheived w3c/wcag#1634.
-
G195 update, removing mouse aspect w3c/wcag#1627.
-
Adding note suggested in 1405 w3c/wcag#1625.
-
Editorial update to the 1st benefit w3c/wcag#1624.
-
Credits update w3c/wcag#1545.
-
Issue 1219 non-text-contrast.html typo fix w3c/wcag#1220.
-
Change STR to Ctrl w3c/wcag#1631.
-
Examples updates w3c/wcag#1617.
-
Issue1449 fixed ref points2 w3c/wcag#1619.
-
Added captcha text to intent w3c/wcag#1611.
-
Adding essential examples. w3c/wcag#1612.
-
Issue 1284 w3c/wcag#1469.
-
Wcag22 fixed ref points updates 2021 jan w3c/wcag#1618.
-
Suggestion from 1282 w3c/wcag#1616.
-
Wcag22 visible controls update w3c/wcag#1606.
-
-
6 pull requests closed.
-
Idea for dealing with 1544 w3c/wcag#1628.
-
New pointer target image dropdown menu w3c/wcag#1621.
-
Update pointer-target-spacing-understanding.html w3c/wcag#1632.
-
Pointer target spacing understanding revised w3c/wcag#1635.
-
Minor re-arrangement of the intent section. w3c/wcag#1580.
-
Editorial updates from dshoukry w3c/wcag#1582.
-
-
18 pull requests received 40 new comments.
-
Dragging movement understanding - Sarah's update w3c/wcag#1649 (2 comments by @detlevhfischer, @gradualclearing)
-
Add clarification in 2.4.4 and 2.4.9 understanding that link text is/includes accessible name w3c/wcag#1570 (2 comments by @bruce-usab, @dd8)
w3c/wcag-act
-
3 issues opened.
-
Understanding Prerequisites for Test Rules w3c/wcag-act#511, by @lwolberg.
-
Resolve "Heading has non-empty accessible name" w3c/wcag-act#510, by @nitedog.
-
Updated rule: Links with identical accessible names have equivalent purpose w3c/wcag-act#509, by @HelenBurge.
-
-
1 issue closed.
-
Updated rule: Image filename is accessible name for image w3c/wcag-act#480.
-
-
9 issues received 9 new comments.
-
Updated rule: Links with identical accessible names have equivalent purpose w3c/wcag-act#509 (1 comment by @maryjom)
-
Updated rule: Image filename is accessible name for image w3c/wcag-act#480 (1 comment by @WilcoFiers)
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
3 participants joined the Cognitive and Learning Disabilities Accessibility Task Force.
-
Allie Bogus joined.
-
Albert Kim joined.
-
Rain Breaw Michaels joined.
-
GitHub
w3c/coga
-
5 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Issues in some languages w3c/coga#248, by @xfq.
-
Review Updated Personas w3c/coga#246, by @rachaelbradley.
-
Add to Section 3.7.3 Directions w3c/coga#244, by @rachaelbradley.
-
Ability to make reminders loud w3c/coga#243, by @rachaelbradley.
-
-
20 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Comments from Ceapat (Spain). Related to font w3c/coga#237.
-
Suggested addition to 3.7.5 User Story: Task Management w3c/coga#168.
-
Use of Person First Language for Autism. w3c/coga#139.
-
4.4.5.3 How it Helps (ADD) w3c/coga#188.
-
4.2.2.4 More Details - typo w3c/coga#184.
-
[minor] match outline numbering with Objective numbering w3c/coga#181.
-
Typo w3c/coga#147.
-
Appreciation w3c/coga#142.
-
Glossary w3c/coga#130.
-
Consider dropping Appendix C and others w3c/coga#121.
-
Venn Diagram Interpretation w3c/coga#129.
-
Repeated words (text typos) w3c/coga#183.
-
Typo - "nine personas" should be "ten personas" w3c/coga#166.
-
Comment from Ceapat (Spain) related to: 4.4.3.4 Examples w3c/coga#234.
-
EO comments: Icons in Summary w3c/coga#217.
-
Math Abbreviation w3c/coga#141.
-
-
1 issue reopened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
COGA icon review suggestions w3c/coga#231, by @lseeman.
-
-
32 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 52 new comments.
-
Comments from Ceapat (Spain). Related to font w3c/coga#237 (3 comments by @claraceapat, @lseeman, @rachaelbradley)
-
[minor] match outline numbering with Objective numbering w3c/coga#181 (2 comments by @rachaelbradley, @ruoxiran)
-
4.4.9.3 How it Helps (don't understand sentence, may need punctuation) w3c/coga#189 (2 comments by @rachaelbradley, @ruoxiran)
-
Write in plain English, Use Plain Language Guideline (Omit superfluous words)) w3c/coga#187 (1 comment by @ruoxiran)
-
Suggest adding more examples to 3.5.1 User Story: Distractions w3c/coga#164 (1 comment by @jpascalides)
-
Comment from Ceapat (Spain), related to: 4.4.1 Pattern: Use Clear Words w3c/coga#233 (1 comment by @jpascalides)
-
Two suggested changes to 5.4.1 Differences from Usability Testing with the General Population w3c/coga#175 (1 comment by @jpascalides)
-
Suggest adding "attention" to wayfinding list in 4.8.6 Pattern: Provide Help with Directions w3c/coga#174 (1 comment by @jpascalides)
-
Three suggested changes to 4.5. Objective 4: Help Users Avoid Mistakes or Correct Them w3c/coga#173 (1 comment by @jpascalides)
-
Four suggested changes to 4.4 Objective 3: Use Clear and Understandable Content w3c/coga#172 (1 comment by @jpascalides)
-
5 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
merge Part 2a and 2b to main branch w3c/coga#247, by @ruoxiran.
-
Language use w3c/coga#242, by @rachaelbradley.
-
Issue 118 Add "key topics" to summary w3c/coga#241, by @jpascalides.
-
Add "Mathematics" in parens - issue 141 w3c/coga#240, by @jpascalides.
-
Changes from issues w3c/coga#239, by @rachaelbradley.
-
-
6 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Language use w3c/coga#242.
-
Add "Mathematics" in parens - issue 141 w3c/coga#240.
-
Issue 118 Add "key topics" to summary w3c/coga#241.
-
Changes from issues w3c/coga#239.
-
Changes from wording meeting w3c/coga#236.
-
correct reference to document w3c/coga#229.
-
-
6 pull requests in the Cognitive and Learning Disabilities Accessibility Task Force received 9 new comments.
Accessibility Conformance Testing (ACT) Task Force
Participants
-
1 chair stepped down in the Accessibility Conformance Testing (ACT) Task Force.
-
Mary Jo Mueller stepped down as a chair.
-
-
3 participants left the Accessibility Conformance Testing (ACT) Task Force.
-
Sailesh Panchang left.
-
Sujasree Kurapati left.
-
Jey Nandakumar left.
-
Low Vision Accessibility Task Force
Participants
-
1 participant joined the Low Vision Accessibility Task Force.
-
Daniele Marano joined.
-
TR publications
-
2 documents published.
-
Requirements for WCAG 3.0 published as a First Public Working Draft. History of Requirements for WCAG 3.0
-
W3C Accessibility Guidelines (WCAG) 3.0 published as a First Public Working Draft. History of W3C Accessibility Guidelines (WCAG) 3.0
-
Participants
-
3 participants joined.
-
Karen Herr (UnitedHealth Group) joined.
-
Charu Pandhi (TPGi) joined.
-
Ben Tillyer (University of Oxford) joined.
-
-
3 participants left.
-
Charu Pandhi (IBM Corporation) left.
-
Melina Moehnle (IRT Institut fuer Rundfunktechnik) left.
-
Garenne Bigby (Dyno Mapper) left.
-
-
3 organizations joined.
-
Salesforce joined.
-
UnitedHealth Group joined.
-
Igalia joined.
-
-
2 organizations left.
-
IRT Institut fuer Rundfunktechnik left.
-
Dyno Mapper left.
-
GitHub
w3c/wcag
-
18 issues opened.
-
Update the definition of process w3c/wcag#1605, by @rachaelbradley.
-
Add "sentence" => normative change 1.4.8 Visual Presentation w3c/wcag#1603, by @jake-abma.
-
Applicability Technique G174 - Question w3c/wcag#1602, by @KerstinProbiesch.
-
SC 1.3.6 Identify Purpose w3c/wcag#1591, by @therobertrich.
-
SC 1.3.6 Identify Purpose: Incorrectly cites SC 4.1.2 (typo) w3c/wcag#1590, by @therobertrich.
-
2.4.7 Focus Visible verbiage w3c/wcag#1587, by @chlane.
-
G195 - Test procedure #6 conflicts with test results w3c/wcag#1586, by @chlane.
-
Archive of task force conversations? w3c/wcag#1584, by @robfentress.
-
Add IDs to conformance level definitions w3c/wcag#1575, by @mattgarrish.
-
Findable help term web page at the end of the phrase is confusing w3c/wcag#1574, by @DavidMacDonald.
-
Static content in tab order - failure of 2.4.3 or not? w3c/wcag#4634, by @patrickhlauke.
-
-
41 issues closed.
-
3.3.7 Accessible Authentication queries on personal info w3c/wcag#1320.
-
Clarification on the definition of electronic publication w3c/wcag#1299.
-
3.3.8: Redundant entry - session term w3c/wcag#1335.
-
Challenges: Moving Beyond the Page w3c/wcag#1171.
-
Should the conformance model challenges mention mitigations? w3c/wcag#1135.
-
Challenges: Multi-language support w3c/wcag#1221.
-
Challenges: Guideline 1.4.4 and Adaptive Design w3c/wcag#1222.
-
SC 2.4.11 Unclear use of thickness, other questions w3c/wcag#1290.
-
Understanding 2.4.11 minimum area clarification w3c/wcag#1552.
-
SC 1.3.6 Identify Purpose w3c/wcag#1591.
-
SC 1.3.6 Identify Purpose: Incorrectly cites SC 4.1.2 (typo) w3c/wcag#1590.
-
Clarity for 1.3.3: Sensory Characteristics needed w3c/wcag#1532.
-
Language of Findable Help 3.2.6 is contradictory w3c/wcag#1368.
-
2.4.7 Focus Visible verbiage w3c/wcag#1587.
-
Archive of task force conversations? w3c/wcag#1584.
-
confusing wording in dfn-pagebreak-locator w3c/wcag#1317.
-
Comment from IBM: Make border a defined term in 2.4.11 w3c/wcag#1373.
-
Add IDs to conformance level definitions w3c/wcag#1575.
-
Delete Technique G183 (hover) w3c/wcag#1118.
-
Discrepancy between F73 and G183 w3c/wcag#1272.
-
Findable Help: Some suggested editorial changes for clarity w3c/wcag#1462.
-
SC2.2.6 (Timouts) should be for all websites w3c/wcag#392.
-
67 issues received 199 new comments.
-
Do issues with Windows high contrast mode fall under WCAG 2.1? w3c/wcag#623 (12 comments by @jake-abma, @JAWS-test, @medeaoblongata, @patrickhlauke)
-
SC2.4.13 Fixed Reference Points needs another technique w3c/wcag#1226 (11 comments by @bruce-usab, @DavidMacDonald, @guyhickling, @mattgarrish, @mraccess77)
-
2.4.11 Focus appearance (min) - complex requirement makes it difficult to write test instructions w3c/wcag#1460 (10 comments by @alastc, @ghost, @mraccess77)
-
2.4.7: Focus Visible - verbiage to discourage low contrast implementations w3c/wcag#1588 (9 comments by @alastc, @bruce-usab, @chlane, @mraccess77)
-
G195 - Test procedure #6 conflicts with test results w3c/wcag#1586 (9 comments by @alastc, @chlane, @mraccess77)
-
Adding disclaimer at the top of techniques? w3c/wcag#1567 (8 comments by @alastc, @hidde, @Myndex, @patrickhlauke)
-
Static content in tab order - failure of 2.4.3 or not? w3c/wcag#4634 (8 comments by @alastc, @awkawk, @detlevhfischer, @mraccess77, @patrickhlauke)
-
Clearance/Change for Understanding 1.4.8: Visual Presentation Vs. 1.4.10: Reflow w3c/wcag#1604 (7 comments by @detlevhfischer, @jake-abma, @JAWS-test, @mraccess77)
-
2.4.11 Unusual scenario: two 'visible indicators' within the same hit area w3c/wcag#1337 (6 comments by @alastc, @mraccess77)
-
2.4.11: How to calculate exactly AND 8 pixels along the shortest side PROBLEM w3c/wcag#1531 (5 comments by @alastc, @mraccess77)
-
2.4.13 Term "electronic publication" not needed w3c/wcag#1429 (5 comments by @alastc, @bruce-usab, @DavidMacDonald, @mraccess77)
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.4.13 Fixed Reference Points w3c/wcag#1449 (5 comments by @alastc, @dshoukry, @mraccess77)
-
SC 3.3.8 Redundant entry, term "step" is ambiguous w3c/wcag#1345 (4 comments by @alastc, @Helixopp, @rachaelbradley)
-
2.4.11 Focus Appearance (Minimum) - adjacent contrast and unobscured clauses w3c/wcag#1399 (4 comments by @alastc, @mraccess77)
-
2.4.11 Unobscured bullet will fail the common chatboxes widgets w3c/wcag#1502 (4 comments by @alastc, @mraccess77)
-
Non-sRGB color spaces, outdated sRGB threshold, and other issues in the "relative luminance" definition w3c/wcag#360 (4 comments by @alastc, @bruce-usab, @Myndex, @patrickhlauke)
-
Findable help term web page at the end of the phrase is confusing w3c/wcag#1574 (4 comments by @alastc, @DavidMacDonald, @mraccess77, @scottaohara)
-
Links ambiguous to AT users only can pass 2.4.4 and 2.4.9 w3c/wcag#1202 (4 comments by @dd8, @patrickhlauke)
-
Comment from IBM: Redundant Entry needs to be more tightly scoped in the SC language w3c/wcag#1410 (3 comments by @alastc, @Helixopp)
-
SC 3.3.8 Redundant entry -- problem scenario is not inherently blocking, should be AA or AAA w3c/wcag#1446 (3 comments by @alastc, @Helixopp)
-
F87 and ARIA 24 seem to contradict in the use of CSS content property w3c/wcag#1554 (3 comments by @alastc, @JAWS-test, @patrickhlauke)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.3.7 Accessible Authentication w3c/wcag#1452 (2 comments by @alastc, @dshoukry)
-
What types of electronic publications are intended to be covered by 2.4.13 Fixed Reference Points? w3c/wcag#1422 (2 comments by @alastc)
-
Fixed Reference Points - Potential editorial updates to the SC text w3c/wcag#1461 (2 comments by @alastc)
-
SC 2.5.8 Pointer Target Spacing - Clarification: Overlapping Spacing w3c/wcag#1312 (2 comments by @bruskowski, @scha14)
-
SC 3.2.6 Findable Help - Definition for "Set of Web Pages" Needs Refinement w3c/wcag#1436 (2 comments by @scha14)
-
2.4.2 Page Titled incorrectly ties programmatic requirements with content SC w3c/wcag#1598 (2 comments by @JAWS-test, @mbgower)
-
2.4.11: Focus Appearance - Clarification with 1.4.11 Understanding Non-Text Contrast relationship w3c/wcag#1378 (2 comments by @alastc, @ghost)
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.4.12 Focus Appearance (Minimum) w3c/wcag#1450 (2 comments by @alastc, @dshoukry)
-
Does the Definition of "Dragging Movements" Intentionally Limit the Scope to Moving Objects/Items? w3c/wcag#1560 (2 comments by @detlevhfischer, @SuzanneTaylor)
-
2.4.11 Focus Appearance (Minimum) (AA) - clarification needed w3c/wcag#1341 (2 comments by @alastc, @patrickhlauke)
-
WCAG 2.2 Accessible Authentication: clarification on whether this includes CAPTCHAs w3c/wcag#1256 (1 comment by @alastc)
-
G15 - link to Trace Center Photosensitive Epilepsy Analysis Tool (PEAT) doesn't work w3c/wcag#1600 (1 comment by @alastc)
-
SC2.4.13 Fixed Reference Points - a point for the Understanding doc w3c/wcag#1227 (1 comment by @guyhickling)
-
2.4.7/2.4.11/2.4.12 Must a focus indicator always be displayed? w3c/wcag#1387 (1 comment by @alastc)
-
2.4.11 Unusual scenario: Very short links with a thick underline focus state w3c/wcag#1329 (1 comment by @alastc)
-
H99 test procedure only tests for navigation aspect of page breaks and not locators w3c/wcag#1592 (1 comment by @alastc)
-
Benefits 2.5.1: split benefit and remove redundant one (for other SC) w3c/wcag#747 (1 comment by @jake-abma)
-
What does “Sufficient as a way to meet an unwritten technique” mean ? w3c/wcag#1585 (1 comment by @alastc)
-
Would like to see a working model of a sticky header and sticky footer that passes w3c/wcag#1518 (1 comment by @alastc)
-
2.4.7 limits focus visible to keyboard. 1.4.11 doesn't appear to have the same limitation w3c/wcag#1401 (1 comment by @alastc)
-
3.2.6 Findable Help - Does this SC really apply to "single page" web applications? w3c/wcag#1427 (1 comment by @alastc)
-
-
22 pull requests opened.
-
Added captcha text to intent w3c/wcag#1611, by @alastc.
-
Wcag22 visible controls update3 w3c/wcag#1610, by @alastc.
-
Visible controls using 'controls' w3c/wcag#1609, by @alastc.
-
Pointer target spacing update w3c/wcag#1608, by @scha14.
-
control to component term swap w3c/wcag#1607, by @alastc.
-
Wcag22 visible controls update w3c/wcag#1606, by @rachaelbradley.
-
Clarify ambiguous bullet in decision policy w3c/wcag#1601, by @michael-n-cooper.
-
update resource links in G15 w3c/wcag#1599, by @scottaohara.
-
new paragraph in redundant entry w3c/wcag#1597, by @rachaelbradley.
-
more clarity on reasonable objections w3c/wcag#1596, by @michael-n-cooper.
-
Moving updates to the correct SC file. w3c/wcag#1595, by @alastc.
-
Wcag22 focus appearance size update w3c/wcag#1594, by @alastc.
-
4.2.1 typo in Identify Purpose w3c/wcag#1593, by @alastc.
-
correct typo 4.2.1 to 4.1.2 w3c/wcag#1589, by @therobertrich.
-
Updates to resolve #1461 w3c/wcag#1583, by @alastc.
-
Editorial updates from dshoukry w3c/wcag#1582, by @alastc.
-
Grammar fixes from #1317 w3c/wcag#1581, by @alastc.
-
Minor re-arrangement of the intent section. w3c/wcag#1580, by @alastc.
-
Adding comment about other forms of nav w3c/wcag#1579, by @alastc.
-
Issue1531 focus appearance size calc w3c/wcag#1578, by @alastc.
-
Understanding 2.4.11 minimum area clarification w3c/wcag#1577, by @alastc.
-
Adding ID's to conformance levels w3c/wcag#1576, by @awkawk.
-
-
15 pull requests merged.
-
Replace "ACT Rules" with "Test Rules" w3c/wcag#1526.
-
Issue 1229 Clarity on self-help option w3c/wcag#1376.
-
new paragraph in redundant entry w3c/wcag#1597.
-
control to component term swap w3c/wcag#1607.
-
update resource links in G15 w3c/wcag#1599.
-
Moving updates to the correct SC file. w3c/wcag#1595.
-
Wcag22 focus appearance size update w3c/wcag#1594.
-
Adding comment about other forms of nav w3c/wcag#1579.
-
Understanding 2.4.11 minimum area clarification w3c/wcag#1577.
-
4.2.1 typo in Identify Purpose w3c/wcag#1593.
-
Grammar fixes from #1317 w3c/wcag#1581.
-
Adding ID's to conformance levels w3c/wcag#1576.
-
G183: Removing hover/focus steps from procedure w3c/wcag#1553.
-
Example 2 update. w3c/wcag#1571.
-
-
6 pull requests closed.
-
Updates to resolve #1461 w3c/wcag#1583.
-
Visible controls using 'controls' w3c/wcag#1609.
-
Issue 1229 clarity on self help draft w3c/wcag#1375.
-
Update redundant-entry.html w3c/wcag#1487.
-
Issue 1374 clarity around "or" w3c/wcag#1471.
-
Issue 1242 SC text clarity w3c/wcag#1482.
-
-
14 pull requests received 36 new comments.
-
G183: Removing hover/focus steps from procedure w3c/wcag#1553 (14 comments by @alastc, @awkawk, @mbgower, @mraccess77, @patrickhlauke, @yatil)
-
Wcag22 focus appearance size update w3c/wcag#1594 (4 comments by @alastc, @detlevhfischer, @JAWS-test)
-
Trivial: remove unnecessary space before tag closing bracket w3c/wcag#1507 (3 comments by @patrickhlauke)
-
Focus-appearance 2.4.11 SC & Understanding rewording suggestions w3c/wcag#1501 (3 comments by @alastc, @mbgower)
-
Add clarification in 2.4.4 and 2.4.9 understanding that link text is/includes accessible name w3c/wcag#1570 (1 comment by @patrickhlauke)
-
w3c/wcag-act
-
8 issues opened.
-
New rule: Menuitem has non-empty accessible name w3c/wcag-act#508, by @SameeraKamra.
-
Resolve "ARIA required context role" survey comments w3c/wcag-act#507, by @maryjom.
-
Resolve "audio or video avoids automatically playing audio" w3c/wcag-act#506, by @daniel-montalvo.
-
Resolve "meta element has no refresh delay" w3c/wcag-act#505, by @tbostic32.
-
Resolve "Element marked as decorative is not exposed" feedback w3c/wcag-act#504, by @kengdoj.
-
Minor update to the background section w3c/wcag-act#502, by @WilcoFiers.
-
Resolve "autocomplete has valid value" w3c/wcag-act#501, by @nitedog.
-
-
2 issues closed.
-
Resolve "Image has non-empty accessible name" feedback w3c/wcag-act#465.
-
Updated rule: "role attribute has valid value" w3c/wcag-act#487.
-
-
14 issues received 16 new comments.
-
Resolve "Visible label is part of accessible name" feedback w3c/wcag-act#491 (3 comments by @maryjom, @WilcoFiers)
-
Resolve "Object element rendering non-text content has non-empty accessible name" feedback w3c/wcag-act#479 (1 comment by @maryjom)
-
New rule: headers attribute specified on a cell refers to cells in the same table element w3c/wcag-act#503 (1 comment by @maryjom)
-
Resolve "Element with lang attribute has valid language" feedback w3c/wcag-act#431 (1 comment by @kengdoj)
-
w3c/coga
-
7 issues opened.
-
Comment from Ceapat (Spain) Use of numbers. 4.4.13 w3c/coga#238, by @claraceapat.
-
Comments from Ceapat (Spain). Related to font w3c/coga#237, by @claraceapat.
-
list punctuation - copyedit and consistency edit w3c/coga#235, by @shawna-slh.
-
Comment from Ceapat (Spain) related to: 4.4.3.4 Examples w3c/coga#234, by @claraceapat.
-
COGA icon review suggestions w3c/coga#231, by @r12a.
-
-
8 issues closed.
-
Continue Discussion of Framing Language w3c/coga#123.
-
minor copy edit suggestion w3c/coga#120.
-
4.5.3.2 How it Helps (confusing sentence) w3c/coga#192.
-
Editorial Pass on the Design Guide w3c/coga#154.
-
12 issues received 16 new comments.
-
Review visual processing for inclusion in Content Usable w3c/coga#137 (1 comment by @rachaelbradley)
-
Suggested changes to the Carolyn (ADHD) persona and scenarios w3c/coga#178 (1 comment by @rachaelbradley)
-
Editorial suggestions in Introduction from Wordsmithing Meeting w3c/coga#122 (1 comment by @rachaelbradley)
-
Ensure all information from the Abstract is included in the document w3c/coga#119 (1 comment by @rachaelbradley)
-
Suggested changes for Pattern 4.2.5 Clearly Identify Controls and Their Use w3c/coga#167 (1 comment by @SteveALee)
-
2 pull requests opened.
-
Changes from wording meeting w3c/coga#236, by @rachaelbradley.
-
Added part1 comparison to content-usable in master branch w3c/coga#230, by @ruoxiran.
-
-
1 pull request merged.
w3c/wcag3
-
1 issue opened.
-
Changing disability model from medical to social w3c/wcag3#382, by @KBDevelops.
-
-
1 issue received 3 new comments.
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 participant joined the Cognitive and Learning Disabilities Accessibility Task Force.
-
Kris Anne Kinney joined.
-
GitHub
w3c/coga
-
7 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Comment from Ceapat (Spain) Use of numbers. 4.4.13 w3c/coga#238, by @claraceapat.
-
Comments from Ceapat (Spain). Related to font w3c/coga#237, by @claraceapat.
-
list punctuation - copyedit and consistency edit w3c/coga#235, by @shawna-slh.
-
Comment from Ceapat (Spain) related to: 4.4.3.4 Examples w3c/coga#234, by @claraceapat.
-
COGA icon review suggestions w3c/coga#231, by @r12a.
-
-
8 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Continue Discussion of Framing Language w3c/coga#123.
-
minor copy edit suggestion w3c/coga#120.
-
4.5.3.2 How it Helps (confusing sentence) w3c/coga#192.
-
Editorial Pass on the Design Guide w3c/coga#154.
-
12 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 16 new comments.
-
Review visual processing for inclusion in Content Usable w3c/coga#137 (1 comment by @rachaelbradley)
-
Suggested changes to the Carolyn (ADHD) persona and scenarios w3c/coga#178 (1 comment by @rachaelbradley)
-
Editorial suggestions in Introduction from Wordsmithing Meeting w3c/coga#122 (1 comment by @rachaelbradley)
-
Ensure all information from the Abstract is included in the document w3c/coga#119 (1 comment by @rachaelbradley)
-
Suggested changes for Pattern 4.2.5 Clearly Identify Controls and Their Use w3c/coga#167 (1 comment by @SteveALee)
-
2 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Changes from wording meeting w3c/coga#236, by @rachaelbradley.
-
Added part1 comparison to content-usable in master branch w3c/coga#230, by @ruoxiran.
-
-
1 pull request merged in the Cognitive and Learning Disabilities Accessibility Task Force.
Accessibility Conformance Testing (ACT) Task Force
Participants
-
1 participant left the Accessibility Conformance Testing (ACT) Task Force.
-
Charu Pandhi left.
-