Accessibility Guidelines Working Group - Activity in 2020
No matches.
TR publications
-
1 document published.
Participants
-
4 participants joined.
-
Kris Anne Kinney (Educational Testing Service) joined.
-
Rupa Jaganathan (SAP SE) joined.
-
Sukriti Chadha (W3C Invited Experts) joined.
-
John Foliot (W3C Invited Experts) joined.
-
-
1 participant left.
-
John Foliot (W3C Invited Experts) left.
-
GitHub
w3c/wcag
-
12 issues opened.
-
Adding disclaimer at the top of techniques? w3c/wcag#1567, by @patrickhlauke.
-
F82 is example 1 is NOT a failure of 3.3.2: Labels or Instructions w3c/wcag#1565, by @jake-abma.
-
An accessible name needs to be added to the procedure of G167 w3c/wcag#1564, by @jake-abma.
-
Change 'label' for 'name' in ARIA9 w3c/wcag#1563, by @jake-abma.
-
Need to clean up references in techniques for use of title attribute w3c/wcag#1561, by @spanchang.
-
F87 and ARIA 24 seem to contradict in the use of CSS content property w3c/wcag#1554, by @mraccess77.
-
Understanding 2.4.11 minimum area clarification w3c/wcag#1552, by @abijames.
-
1.4.10: Reflow exception for an interactive e-book w3c/wcag#1550, by @mikahayk.
-
-
14 issues closed.
-
Understanding Use of Colour and Non Text Contrast w3c/wcag#1370.
-
Findable Help SC3.2.6 - all changes together w3c/wcag#1242.
-
3.2.6 Findable Help, confusing use of "page" and "web page" w3c/wcag#1347.
-
SC 3.2.6 Findable Help - Help Mechanism Priority w3c/wcag#1434.
-
SC 3.2.6 Findable Help - Declaring Human Contact Details w3c/wcag#1437.
-
Term definition cross-links in understanding don't work w3c/wcag#1541.
-
45 issues received 108 new comments.
-
Definition and example for 'role' are confusing w3c/wcag#1476 (9 comments by @alastc, @awkawk, @bruce-usab, @mraccess77, @patrickhlauke)
-
3.2.6 Findable Help, confusing use of "page" and "web page" w3c/wcag#1347 (7 comments by @alastc, @jake-abma, @scottaohara)
-
"Changes of color" applied to motion definition w3c/wcag#1535 (7 comments by @alastc, @jake-abma, @patrickhlauke)
-
1.4.12 Letter Spacing: does "word spacing" (and letter spacing) refers to the CSS property or the actual space? w3c/wcag#1556 (5 comments by @alastc, @JAWS-test, @Jym77, @mraccess77)
-
1.4.10: Reflow exception for an interactive e-book w3c/wcag#1550 (4 comments by @alastc, @bruce-usab, @patrickhlauke, @Veyfeyken)
-
Accessible Authentication (3.3.7): clarify whether copy/paste is a cognitive function test w3c/wcag#1359 (3 comments by @alastc, @patrickhlauke)
-
F87 and ARIA 24 seem to contradict in the use of CSS content property w3c/wcag#1554 (3 comments by @JAWS-test, @mraccess77, @patrickhlauke)
-
Does G183 only apply to "links and controls" with additional requirements or in general? w3c/wcag#871 (2 comments by @alastc)
-
Links ambiguous to AT users only can pass 2.4.4 and 2.4.9 w3c/wcag#1202 (2 comments by @patrickhlauke)
-
Does the Definition of "Dragging Movements" Intentionally Limit the Scope to Moving Objects/Items? w3c/wcag#1560 (2 comments by @detlevhfischer, @SuzanneTaylor)
-
1.3.1 Info and Relationships Vs. 1.3.2 Meaningful Sequence w3c/wcag#1519 (2 comments by @alastc, @jake-abma)
-
Are there exceptions for "without requiring specific timings for individual keystrokes" (SC 2.1.1)? w3c/wcag#1539 (2 comments by @alastc)
-
3.2.6 Findable Help - Does this SC really apply to "single page" web applications? w3c/wcag#1427 (1 comment by @alastc)
-
Note and benefits contradict each other in 1.4.1 (Use of color) w3c/wcag#1032 (1 comment by @alastc)
-
2.4.11 Focus Appearance (Minimum) (AA) - clarification needed w3c/wcag#1341 (1 comment by @patrickhlauke)
-
Benefits 2.5.1: split benefit and remove redundant one (for other SC) w3c/wcag#747 (1 comment by @patrickhlauke)
-
1.3.4 Orientation - F97 (Locking orientation) - screen size irrelevant in testing? w3c/wcag#877 (1 comment by @patrickhlauke)
-
Informative Techniques pages are loaded with normative RFC-2119 terms like MUST w3c/wcag#1150 (1 comment by @patrickhlauke)
-
Does 3.3.2 mandate forms that have required/optional fields indicate this visually? w3c/wcag#923 (1 comment by @patrickhlauke)
-
Understanding 3.3.1: Error Identification slightly unfocused/mixes up various concepts w3c/wcag#977 (1 comment by @patrickhlauke)
-
F82 is example 1 is NOT a failure of 3.3.2: Labels or Instructions w3c/wcag#1565 (1 comment by @alastc)
-
Stacked SC: 1.4.12: Text Spacing AND 1.4.3: Contrast Do they have a interrelationship? w3c/wcag#1524 (1 comment by @alastc)
-
2.5.4 understanding - suggestion to remove the "user gestures towards device" angle w3c/wcag#1464 (1 comment by @patrickhlauke)
-
Status of aria-hidden on Unicode characters technique from wiki w3c/wcag#1386 (1 comment by @alastc)
-
2.4.7 Focus Visible: WCAG 2.1 Understanding has wrong level (A instead of AA) w3c/wcag#1178 (1 comment by @alastc)
-
3.2.6 Findable Help - overlap with 3.3.3 consistent navigation and other comments w3c/wcag#1394 (1 comment by @alastc)
-
9 pull requests opened.
-
Example 2 update. w3c/wcag#1571, by @alastc.
-
Changes to 2.5.1 Pointer Gestures understanding w3c/wcag#1569, by @patrickhlauke.
-
Expand 3.3.2 Labels or Instructions understanding w3c/wcag#1568, by @patrickhlauke.
-
Wcag22 visible controls updates - JF w3c/wcag#1559, by @alastc.
-
Changed name to visible controls w3c/wcag#1558, by @alastc.
-
Updates based on the meeting 8th Dec 2020 w3c/wcag#1557, by @alastc.
-
Update for #1535, motion animation w3c/wcag#1555, by @alastc.
-
G183: Removing hover/focus steps from procedure w3c/wcag#1553, by @alastc.
-
-
7 pull requests merged.
-
Fixes for Understanding 1.3.3 Sensory Characteristics w3c/wcag#767.
-
Wcag22 visible controls updates - JF w3c/wcag#1559.
-
Changed name to visible controls w3c/wcag#1558.
-
Updates based on the meeting 8th Dec 2020 w3c/wcag#1557.
-
Finable help SPA clarification w3c/wcag#1538.
-
Versioning w3c/wcag#1240.
-
1 pull request closed.
-
Understanding Use of Color (SC 1.4.1) w3c/wcag#1020.
-
-
13 pull requests received 36 new comments.
-
G183: Removing hover/focus steps from procedure w3c/wcag#1553 (8 comments by @alastc, @patrickhlauke, @yatil)
-
Rework understanding for 1.4.1 to be firmly only about visual aspect w3c/wcag#1500 (7 comments by @alastc, @awkawk, @patrickhlauke, @StommePoes)
-
Fixes for Understanding 1.3.3 Sensory Characteristics w3c/wcag#767 (3 comments by @alastc, @awkawk, @patrickhlauke)
-
Expand 3.3.2 Labels or Instructions understanding w3c/wcag#1568 (2 comments by @detlevhfischer, @patrickhlauke)
-
Add clarification in 2.4.4 and 2.4.9 understanding that link text is/includes accessible name w3c/wcag#1570 (2 comments by @detlevhfischer, @patrickhlauke)
-
Tweak understanding for 1.2.6: Sign Language (Prerecorded) w3c/wcag#1517 (1 comment by @patrickhlauke)
-
w3c/coga
-
2 pull requests opened.
-
correct reference to document w3c/coga#229, by @shawna-slh.
-
Add glossary to publish updating working draft w3c/coga#228, by @ruoxiran.
-
-
2 pull requests merged.
-
Use expected format for w3c.json contacts w3c/coga#196.
-
Add glossary to publish updating working draft w3c/coga#228.
-
-
1 pull request closed.
-
Editoral review issues fix w3c/coga#226.
-
-
1 pull request received 2 new comments.
w3c/wcag-act
-
5 issues received 5 new comments.
-
Resolve "Element with lang attribute has valid language" feedback w3c/wcag-act#431 (1 comment by @maryjom)
w3c/wcag3
-
1 issue received 1 new comment.
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 participant left the Cognitive and Learning Disabilities Accessibility Task Force.
-
John Foliot left.
-
GitHub
w3c/coga
-
2 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
correct reference to document w3c/coga#229, by @shawna-slh.
-
Add glossary to publish updating working draft w3c/coga#228, by @ruoxiran.
-
-
2 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Use expected format for w3c.json contacts w3c/coga#196.
-
Add glossary to publish updating working draft w3c/coga#228.
-
-
1 pull request closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Editoral review issues fix w3c/coga#226.
-
-
1 pull request in the Cognitive and Learning Disabilities Accessibility Task Force received 2 new comments.
Mobile Accessibility Task Force
Participants
-
1 participant joined the Mobile Accessibility Task Force.
-
Sukriti Chadha joined.
-
-
1 participant left the Mobile Accessibility Task Force.
-
John Foliot left.
-
Participants
-
4 participants joined.
-
Daniel Hark SOHN (SCE Korea, Inc.) joined.
-
Daniel Hark SOHN (SCE Korea, Inc.) joined.
-
Kasper Isager Dalsgarð (Siteimprove) joined.
-
Tobias Nyhuus Jensen (Siteimprove) joined.
-
-
3 participants left.
-
Sukriti Chadha (W3C Invited Experts) left.
-
Daniel Hark SOHN (SCE Korea, Inc.) left.
-
Kasper Isager Dalsgarð (Siteimprove) left.
-
-
1 organization joined.
-
SCE Korea, Inc. joined.
-
GitHub
w3c/wcag
-
33 issues opened.
-
Contents of language attribute on HTML element missing in Techniques w3c/wcag#2005, by @hidde.
-
SC 1.4.8 Visual Presentation - Examples Seem to be Missing Images w3c/wcag#1548, by @Grunet.
-
The term "minimum focus indicator area" is confusing w3c/wcag#1544, by @DavidMacDonald.
-
Failure F23 is NOT a failure if you look at the Procedure w3c/wcag#1543, by @jake-abma.
-
Term definition cross-links in understanding don't work w3c/wcag#1541, by @patrickhlauke.
-
"Changes of color" applied to motion definition w3c/wcag#1535, by @jake-abma.
-
SC 1.3.3: Sensory Characteristics w3c/wcag#1534, by @erikkroes.
-
Mechanism provided by the platform AND stopping 1.4.2: Audio Control w3c/wcag#1533, by @jake-abma.
-
Clarity for 1.3.3: Sensory Characteristics needed w3c/wcag#1532, by @jake-abma.
-
Text already present in input makes 1.4.11: Non-text Contrast pass? w3c/wcag#1530, by @jake-abma.
-
Definitions do not work at 3.1.3: Unusual Words w3c/wcag#1525, by @jake-abma.
-
1.3.1 Info and Relationships Vs. 1.3.2 Meaningful Sequence w3c/wcag#1519, by @jake-abma.
-
Pre recorded Vs. Live in 1.2.6: Sign Language (Prerecorded) w3c/wcag#1515, by @jake-abma.
-
Pointer Cancellation - Clarification on Abort and Undo w3c/wcag#1513, by @ghost.
-
WCAG 3.3.1 fulfilled with disabled submit button? w3c/wcag#1512, by @JAWS-test.
-
I think the forward slash is missing w3c/wcag#1506, by @Sylvie123.
-
2.4.11 Unobscured bullet will fail the common chatboxes widgets w3c/wcag#1502, by @DavidMacDonald.
-
-
29 issues closed.
-
Clarity on Understanding 1.4.11 regarding hue w3c/wcag#868.
-
1.3.1 Info and Relationships Vs. 1.3.2 Meaningful Sequence w3c/wcag#1519.
-
Definitions do not work at 3.1.3: Unusual Words w3c/wcag#1525.
-
Focus-appearance and Non-text-contrast relationship w3c/wcag#1490.
-
Example 2 for G195 is too inaccurate w3c/wcag#1305.
-
Does a change of background pass Focus Appearance (Minimum) w3c/wcag#1278.
-
SC 3.3.7 Accessible Authentication w3c/wcag#1318.
-
3.3.7 Accessible Authentication - Add mechanism text w3c/wcag#1418.
-
Non-modal dialogues and Unobscured 2.4.11: Focus Appearance w3c/wcag#1352.
-
2.4.11 Focus Appearance requires contrast for aliased pixels w3c/wcag#1348.
-
2.4.7/2.4.11/2.4.12 Focus: should indicator be unique? w3c/wcag#1383.
-
-
73 issues received 289 new comments.
-
WCAG 2.2 2.5.7 Dragging and its reference to single pointer w3c/wcag#1225 (15 comments by @alastc, @guyhickling, @mraccess77, @patrickhlauke)
-
Stacked SC: 1.4.12: Text Spacing AND 1.4.3: Contrast Do they have a interrelationship? w3c/wcag#1524 (14 comments by @alastc, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
3.2.6 Findable Help - Does this SC really apply to "single page" web applications? w3c/wcag#1427 (14 comments by @bruce-usab, @jake-abma, @mfairchild365, @patrickhlauke, @scha14, @scottaohara)
-
WCAG 3.3.1 fulfilled with disabled submit button? w3c/wcag#1512 (13 comments by @awkawk, @bruce-usab, @gradualclearing, @JAWS-test, @mraccess77, @patrickhlauke)
-
2.4.7 Focus Visible: WCAG 2.1 Understanding has wrong level (A instead of AA) w3c/wcag#1178 (12 comments by @bruce-usab, @detlevhfischer, @guyhickling, @jake-abma, @karlgroves, @patrickhlauke, @yatil)
-
2.4.11 Unobscured bullet will fail the common chatboxes widgets w3c/wcag#1502 (12 comments by @alastc, @DavidMacDonald, @mraccess77)
-
Clearance on unnecessary redundant semantic elements used and WCAG Failures w3c/wcag#1540 (11 comments by @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
Does a video with a transcript fail SC 1.2.5 in light of "Full pages" conformance requirement? w3c/wcag#1537 (10 comments by @bruce-usab, @mraccess77, @patrickhlauke, @Ryladog)
-
Applicability of 2.5.3 Label in Name when no label is present (or just placeholder) w3c/wcag#855 (9 comments by @awkawk, @mraccess77, @patrickhlauke, @srinivasuchakravarthula)
-
SC 1.3.3: Sensory Characteristics w3c/wcag#1534 (8 comments by @alastc, @awkawk, @bruce-usab, @erikkroes, @jake-abma, @mraccess77, @patrickhlauke)
-
Mechanism provided by the platform AND stopping 1.4.2: Audio Control w3c/wcag#1533 (8 comments by @bruce-usab, @jake-abma, @mraccess77, @patrickhlauke)
-
1.3.1 Info and Relationships Vs. 1.3.2 Meaningful Sequence w3c/wcag#1519 (8 comments by @alastc, @erikkroes, @jake-abma, @JAWS-test, @patrickhlauke)
-
input type="number" spinner increase/decrease fail/pass AND 2.5.2: Pointer Cancellation w3c/wcag#1529 (8 comments by @jake-abma, @patrickhlauke)
-
1.4.1: Use of Color - understanding document needs to be clear if it's about "visual" or more w3c/wcag#1076 (7 comments by @JAWS-test, @mraccess77, @Myndex, @patrickhlauke)
-
2.4.7/2.4.11/2.4.12 Must a focus indicator always be displayed? w3c/wcag#1387 (6 comments by @alastc, @detlevhfischer, @jake-abma, @mbgower)
-
Failure F23 is NOT a failure if you look at the Procedure w3c/wcag#1543 (5 comments by @awkawk, @bruce-usab, @jake-abma, @patrickhlauke)
-
Non-text contrast - clarify meaning of "active user interface components" w3c/wcag#1521 (5 comments by @alastc, @dashouse, @patrickhlauke)
-
Bookmarklet for testing character key shortcuts (SC 2.1.4) w3c/wcag#833 (5 comments by @detlevhfischer, @JAWS-test, @patrickhlauke)
-
"Changes of color" applied to motion definition w3c/wcag#1535 (5 comments by @alastc, @jake-abma, @patrickhlauke)
-
Focus-appearance and Non-text-contrast relationship w3c/wcag#1490 (5 comments by @alastc, @DavidMacDonald, @JAWS-test)
-
Clarity for 1.3.3: Sensory Characteristics needed w3c/wcag#1532 (4 comments by @alastc, @bruce-usab, @patrickhlauke)
-
2.4.11: How to calculate exactly AND 8 pixels along the shortest side PROBLEM w3c/wcag#1531 (4 comments by @alastc, @bruce-usab, @jake-abma, @patrickhlauke)
-
3.2.6 Findable Help, confusing use of "page" and "web page" w3c/wcag#1347 (4 comments by @alastc, @jake-abma, @scha14)
-
Stacked SC: SC 1.4.4: Resize text AND 1.4.3: Contrast and zoom Native UA elements? w3c/wcag#1523 (4 comments by @jake-abma, @JAWS-test, @patrickhlauke)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.3.7 Accessible Authentication w3c/wcag#1452 (4 comments by @alastc)
-
2.4.11/2.4.12 Focus Appearance: consider distance between component and indicator w3c/wcag#1382 (4 comments by @alastc, @mraccess77, @patrickhlauke)
-
Accessible Authentication (3.3.7) far too fundamentally restrictive for a Level A w3c/wcag#1364 (4 comments by @alastc, @mraccess77, @patrickhlauke)
-
Pointer Cancellation - Clarification on Abort and Undo w3c/wcag#1513 (4 comments by @ghost, @mraccess77, @patrickhlauke)
-
Dotted outline focus indicators in SC2.4.11 - Minimum area bullet w3c/wcag#1369 (4 comments by @alastc, @guyhickling)
-
More narrowly definition of what "function" is in context of 2.5.2 Pointer Cancellation w3c/wcag#1542 (3 comments by @alastc, @patrickhlauke)
-
Term definition cross-links in understanding don't work w3c/wcag#1541 (3 comments by @alastc, @jake-abma, @patrickhlauke)
-
Stacked SC: SC 1.4.4: Resize text AND 1.4.3: Contrast Do they have a interrelationship? w3c/wcag#1522 (3 comments by @alastc, @jake-abma, @patrickhlauke)
-
Minimum focus indicator definitions for 2.4.11/2.4.12 are ambiguous; example calculations do not account for corners w3c/wcag#1324 (3 comments by @alastc, @mbgower)
-
Does a change of background pass Focus Appearance (Minimum) w3c/wcag#1278 (3 comments by @alastc, @DavidMacDonald, @mbgower)
-
Cases where more than one "Meaningful Sequence" is required for total meaning w3c/wcag#1062 (2 comments by @bruce-usab, @medeaoblongata)
-
Are there exceptions for "without requiring specific timings for individual keystrokes" (SC 2.1.1)? w3c/wcag#1539 (2 comments by @alastc, @patrickhlauke)
-
Would like to see a working model of a sticky header and sticky footer that passes w3c/wcag#1518 (2 comments by @alastc)
-
The term "minimum focus indicator area" is confusing w3c/wcag#1544 (2 comments by @alastc, @mraccess77)
-
'Understanding Findable Help 3.2.6' implicitly recommends unhelpful page formats/headings w3c/wcag#1380 (2 comments by @m-green, @scha14)
-
Text already present in input makes 1.4.11: Non-text Contrast pass? w3c/wcag#1530 (2 comments by @jake-abma, @mraccess77)
-
Update 2.4.12: Focus Appearance (Enhanced) to match 2.4.11: Focus Appearance (Minimum) w3c/wcag#1536 (2 comments by @jake-abma)
-
Pointer Target Spacing (2.5.8), user agent defaults, and lists of links/controls w3c/wcag#1384 (2 comments by @alastc, @patrickhlauke)
-
Discussion of SC 1.4.10 Reflow, 1.4.12 Text Spacing on native mobile apps w3c/wcag#1510 (2 comments by @alastc, @mraccess77)
-
SC 3.3.7 Accessible Authentication & conflict with legal and contractual obligations w3c/wcag#1430 (2 comments by @alastc)
-
Concerns and clarifications with Accessible Authentication 3.3.7 w3c/wcag#1470 (2 comments by @alastc)
-
Pre recorded Vs. Live in 1.2.6: Sign Language (Prerecorded) w3c/wcag#1515 (2 comments by @patrickhlauke)
-
SC 2.4.11 Unclear use of thickness, other questions w3c/wcag#1290 (2 comments by @alastc, @mraccess77)
-
SC 1.4.8 Visual Presentation - Examples Seem to be Missing Images w3c/wcag#1548 (1 comment by @JAWS-test)
-
Status of aria-hidden on Unicode characters technique from wiki w3c/wcag#1386 (1 comment by @kantoche)
-
3.2.6 Findable Help - overlap with 3.3.3 consistent navigation and other comments w3c/wcag#1394 (1 comment by @scha14)
-
SC 3.2.6 Findable Help - Definition for "Set of Web Pages" Needs Refinement w3c/wcag#1436 (1 comment by @scha14)
-
[WCAG 2.2 Draft Feedback] Missing href for Understanding Success Criterion 3.3.7: Accessible Authentication w3c/wcag#1509 (1 comment by @alastc)
-
Accessible Authentication (3.3.7): clarify whether copy/paste is a cognitive function test w3c/wcag#1359 (1 comment by @mraccess77)
-
Comment from IBM: Redundant Entry needs to be more tightly scoped in the SC language w3c/wcag#1410 (1 comment by @mbgower)
-
For purposes of meeting the nested requirements of SC 4.1.1 can ARIA roles be used? w3c/wcag#1511 (1 comment by @patrickhlauke)
-
Relationship/overlap between 2.1's "Pointer Gestures" and 2.2's "Dragging" w3c/wcag#1398 (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 @SuzanneTaylor)
-
-
15 pull requests opened.
-
Fix understanding images w3c/wcag#1549, by @patrickhlauke.
-
Remove 'active' altogether from 1.4.11 Understanding w3c/wcag#1547, by @patrickhlauke.
-
Credits update w3c/wcag#1545, by @scha14.
-
Finable help SPA clarification w3c/wcag#1538, by @scha14.
-
G195 Focus Technique Visual Example Update w3c/wcag#1527, by @scha14.
-
Replace "ACT Rules" with "Test Rules" w3c/wcag#1526, by @nitedog.
-
Tweak understanding for 1.2.6: Sign Language (Prerecorded) w3c/wcag#1517, by @patrickhlauke.
-
Ignore output w3c/wcag#1514, by @hidde.
-
Updates from dshoukry's doc w3c/wcag#1508, by @alastc.
-
Trivial: remove unnecessary space before tag closing bracket w3c/wcag#1507, by @patrickhlauke.
-
Updates from 1418 w3c/wcag#1505, by @alastc.
-
Issue1352 focus appearance w3c/wcag#1504, by @alastc.
-
SC update on non-text contrast relationship w3c/wcag#1503, by @alastc.
-
Focus-appearance 2.4.11 SC & Understanding rewording suggestions w3c/wcag#1501, by @mbgower.
-
-
11 pull requests merged.
-
Adding -4 to the measure w3c/wcag#1498.
-
Updates from dshoukry's doc w3c/wcag#1508.
-
Adding comment on default styles w3c/wcag#1497.
-
Adding the hex colour value to an example w3c/wcag#1496.
-
Additional example for understanding doc for #1278 w3c/wcag#1495.
-
Adding copy-paste references w3c/wcag#1419.
-
Updates from 1418 w3c/wcag#1505.
-
Issue1352 focus appearance w3c/wcag#1504.
-
Understanding addition for #1348 w3c/wcag#1493.
-
SC update on non-text contrast relationship w3c/wcag#1503.
-
Issue 1314 1228 Update findable-help.html (Editorial) w3c/wcag#1356.
-
-
2 pull requests closed.
-
Updating the understanding - redundant entry w3c/wcag#1325.
-
Issue 1294 typo w3c/wcag#1295.
-
-
16 pull requests received 53 new comments.
-
Rework understanding for 1.4.1 to be firmly only about visual aspect w3c/wcag#1500 (22 comments by @alastc, @bruce-usab, @carlosapaduarte, @JAWS-test, @mraccess77, @Myndex, @patrickhlauke, @yatil)
-
Focus-appearance 2.4.11 SC & Understanding rewording suggestions w3c/wcag#1501 (11 comments by @alastc, @awkawk, @mbgower)
-
Trivial: remove unnecessary space before tag closing bracket w3c/wcag#1507 (2 comments by @alastc, @patrickhlauke)
-
w3c/wcag-act
-
4 issues opened.
-
New Rule: Heading has non-empty accessible name w3c/wcag-act#500, by @Jym77.
-
New rule: ARIA required context role w3c/wcag-act#499, by @Jym77.
-
Decision process for accessibility support of test cases w3c/wcag-act#497, by @WilcoFiers.
-
-
4 issues closed.
-
Editorial differences between spec and example rules w3c/wcag-act#179.
-
Develop rules repository w3c/wcag-act#181.
-
Resolve "iFrame element has accessible name" feedback w3c/wcag-act#435.
-
-
14 issues received 15 new comments.
-
Resolve "Element with lang attribute has valid language" feedback w3c/wcag-act#431 (1 comment by @WilcoFiers)
-
Resolve "Visible label is part of accessible name" feedback w3c/wcag-act#491 (1 comment by @maryjom)
-
Resolve "Object element rendering non-text content has non-empty accessible name" feedback w3c/wcag-act#479 (1 comment by @maryjom)
-
Updated rule: `audio` or `video` has no audio that plays automatically w3c/wcag-act#490 (1 comment by @maryjom)
-
How to update `audio` or `video` has no audio that plays automatically (80f0bf) w3c/wcag-act#498 (1 comment by @carlosapaduarte)
-
1 pull request opened.
-
addressing comments from @moekraft w3c/wcag-act#496, by @nitedog.
-
-
2 pull requests merged.
-
Update ACT-Task-Force-Decision-Policy.md w3c/wcag-act#494.
-
addressing comments from @moekraft w3c/wcag-act#496.
-
w3c/wcag3
-
2 issues opened.
-
SCs for users of screen magnifiers w3c/wcag3#175, by @JAWS-test.
-
About Bronze - Silver - Gold and scope of views etc. w3c/wcag3#304, by @spanchang.
-
-
3 issues received 3 new comments.
w3c/coga
-
2 issues opened.
-
Check that glossary terms work as hyperlinked text w3c/coga#227, by @bruce-usab.
-
Are you a designer? w3c/coga#224, by @lseeman.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Editoral review issues fix w3c/coga#226, by @rachaelbradley.
-
style summary list icons w3c/coga#225, by @michael-n-cooper.
-
-
2 pull requests merged.
-
style summary list icons w3c/coga#225.
-
Update glossary definition w3c/coga#200.
-
-
1 pull request reopened.
-
Editoral review issues fix w3c/coga#226, by @rachaelbradley.
-
-
1 pull request received 2 new comments.
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
2 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Check that glossary terms work as hyperlinked text w3c/coga#227, by @bruce-usab.
-
Are you a designer? w3c/coga#224, by @lseeman.
-
-
1 issue in the Cognitive and Learning Disabilities Accessibility Task Force received 1 new comment.
-
2 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Editoral review issues fix w3c/coga#226, by @rachaelbradley.
-
style summary list icons w3c/coga#225, by @michael-n-cooper.
-
-
2 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
style summary list icons w3c/coga#225.
-
Update glossary definition w3c/coga#200.
-
-
1 pull request reopened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Editoral review issues fix w3c/coga#226, by @rachaelbradley.
-
-
1 pull request in the Cognitive and Learning Disabilities Accessibility Task Force received 2 new comments.
Mobile Accessibility Task Force
Participants
-
1 participant left the Mobile Accessibility Task Force.
-
Sukriti Chadha left.
-
Accessibility Conformance Testing (ACT) Task Force
Participants
-
1 participant left the Accessibility Conformance Testing (ACT) Task Force.
-
Kasper Isager Dalsgarð left.
-
Participants
-
5 participants joined.
-
Kyle Lachance (ADA Site Compliance) joined.
-
Scott Rubenstein (ADA Site Compliance) joined.
-
Natalie Patrice Tucker (Knowbility) joined.
-
David Middleton (Accessibility Shield) joined.
-
Matthew Orr (Fiserv) joined.
-
-
4 participants left.
-
Stein Erik Skotkjerra (Siteimprove) left.
-
Anne Thyme Nørregaard (Siteimprove) left.
-
Manoj Venkata (Deque Systems, Inc.) left.
-
Brooks Newton (Thomson Reuters Corp.) left.
-
-
1 organization joined.
-
ADA Site Compliance joined.
-
GitHub
w3c/wcag
-
14 issues opened.
-
F17 removal lost important tests w3c/wcag#1492, by @jribbens.
-
F17 being removed has left gaps in WCAG rules w3c/wcag#1491, by @jribbens.
-
Focus-appearance and Non-text-contrast relationship w3c/wcag#1490, by @alastc.
-
Appendix B (non-normative) Guideline 1.4.1 w3c/wcag#1488, by @raebened.
-
Clarification on the meaning of "disabled" and "turn off" w3c/wcag#1480, by @carlosapaduarte.
-
I think there's a typo on w3.org w3c/wcag#1478, by @Sylvie123.
-
Understanding WCAG 1.4.5 references 1.4.4, should be 1.4.9 w3c/wcag#1477, by @kirabug.
-
Definition and example for 'role' are confusing w3c/wcag#1476, by @36degrees.
-
(WCAG 2.0) Translations link in header links… not to translations w3c/wcag#1474, by @yatil.
-
Captions and AD for user-created/uploaded video? w3c/wcag#1472, by @medeaoblongata.
-
Concerns and clarifications with Accessible Authentication 3.3.7 w3c/wcag#1470, by @simonrjones.
-
"Breadcrumbs" not a term understood by users w3c/wcag#1468, by @guyhickling.
-
-
17 issues closed.
-
F17 being removed has left gaps in WCAG rules w3c/wcag#1491.
-
Appendix B (non-normative) Guideline 1.4.1 w3c/wcag#1488.
-
Adding the word "Pointer" to "2.5.7 Dragging" w3c/wcag#1397.
-
Dragging on mobile apps w3c/wcag#1307.
-
Understanding WCAG 1.4.5 references 1.4.4, should be 1.4.9 w3c/wcag#1477.
-
Cross behavior between focus and hover (1.4.13) w3c/wcag#1196.
-
SC 3.2.6 Finding Help SC text w3c/wcag#1314.
-
Findable Help SC3.2.6 - access to at least one option? w3c/wcag#1231.
-
Findable Help SC3.2.6 - what is self-help? w3c/wcag#1229.
-
I think there's a typo on w3.org w3c/wcag#1478.
-
Findable Help SC3.2.6 - available or provided? w3c/wcag#1232.
-
"Breadcrumbs" not a term understood by users w3c/wcag#1468.
-
-
59 issues received 172 new comments.
-
F17 removal lost important tests w3c/wcag#1492 (19 comments by @awkawk, @JAWS-test, @jribbens, @mraccess77, @patrickhlauke)
-
SC 2.5.8 Pointer Target Spacing - How do input labels impact spacing requirements? w3c/wcag#1432 (13 comments by @alastc, @bruce-usab, @DavidMacDonald, @JAWS-test, @mraccess77, @patrickhlauke)
-
Looking for definitive clarification regarding 1.4.1 w3c/wcag#1467 (12 comments by @aardrian, @alastc, @erikkroes, @patrickhlauke, @scottaohara, @yatil)
-
2.4.11 Focus appearance (min) - complex requirement makes it difficult to write test instructions w3c/wcag#1460 (9 comments by @alastc, @ghost, @mbgower, @mraccess77)
-
Text spacing: does it require compatibility with one or all methods? w3c/wcag#975 (9 comments by @goyalvarun601, @JAWS-test, @mraccess77, @patrickhlauke)
-
2.4.11 Focus Appearance (Minimum) (AA) - clarification needed w3c/wcag#1341 (7 comments by @alastc, @mbgower, @mraccess77)
-
SC 2.4.11 Unclear use of thickness, other questions w3c/wcag#1290 (5 comments by @alastc, @mraccess77, @yatil)
-
Dotted outline focus indicators in SC2.4.11 - Minimum area bullet w3c/wcag#1369 (5 comments by @alastc, @ghost, @guyhickling)
-
Understanding for 1.4.10 and mobile browsers - absolve content authors ("not applicable") w3c/wcag#1483 (5 comments by @alastc, @jake-abma, @patrickhlauke)
-
2.4.11: Focus Appearance - Clarification with 1.4.11 Understanding Non-Text Contrast relationship w3c/wcag#1378 (4 comments by @alastc, @mraccess77)
-
Does a change of background pass Focus Appearance (Minimum) w3c/wcag#1278 (4 comments by @alastc, @lchandelier)
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.4.12 Focus Appearance (Minimum) w3c/wcag#1450 (3 comments by @alastc, @mraccess77)
-
IBM Comment: Make small editorial change to Minimum Area in 2.4.11 w3c/wcag#1374 (3 comments by @alastc, @scha14)
-
2.4.11 Focus Appearance requires contrast for aliased pixels w3c/wcag#1348 (3 comments by @alastc, @guyhickling)
-
SC 2.5.8 Pointer Target Spacing - Suggested reformulation of pointer clearance calculation w3c/wcag#1444 (3 comments by @alastc, @wittjeff)
-
2.4.7 limits focus visible to keyboard. 1.4.11 doesn't appear to have the same limitation w3c/wcag#1401 (2 comments by @alastc)
-
2.4.11 Focus Appearance (Minimum) - adjacent contrast and unobscured clauses w3c/wcag#1399 (2 comments by @alastc)
-
F17 being removed has left gaps in WCAG rules w3c/wcag#1491 (2 comments by @jribbens, @patrickhlauke)
-
Comment from IBM: Reword Focus Appearance (Minimum) to provide clarity w3c/wcag#1372 (2 comments by @alastc)
-
Non-visual status message has wrong language - FAIL in 4.1.3, or elsewhere? w3c/wcag#1342 (2 comments by @medeaoblongata, @patrickhlauke)
-
Understanding WCAG 1.4.5 references 1.4.4, should be 1.4.9 w3c/wcag#1477 (2 comments by @alastc, @scottaohara)
-
Findable Help SC3.2.6 - access to at least one option? w3c/wcag#1231 (2 comments by @guyhickling, @scha14)
-
Does 4.1.3 Status Messages mean every status message needs to have a role="status"/"alert"? w3c/wcag#1475 (2 comments by @mraccess77, @smhigley)
-
Contrast ratio for text that is part of inactive UI component w3c/wcag#469 (2 comments by @Gumnos, @patrickhlauke)
-
Captions and AD for user-created/uploaded video? w3c/wcag#1472 (2 comments by @mraccess77, @patrickhlauke)
-
Accessible Authentication (3.3.7) far too fundamentally restrictive for a Level A w3c/wcag#1364 (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 @rachaelbradley)
-
Cross-reference 2.5.7 Dragging and 2.5.1 Pointer Gestures in Understanding docs w3c/wcag#1316 (1 comment by @alastc)
-
Concerns and clarifications with Accessible Authentication 3.3.7 w3c/wcag#1470 (1 comment by @alastc)
-
2.4.11 Unusual scenario: two 'visible indicators' within the same hit area w3c/wcag#1337 (1 comment by @alastc)
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.3.7 Accessible Authentication w3c/wcag#1452 (1 comment by @cwadamsoforacle)
-
Create new technique for new contrast formula (threshold value) w3c/wcag#1213 (1 comment by @alastc)
-
-
17 pull requests opened.
-
Adding reset loop example w3c/wcag#1499, by @alastc.
-
Adding -4 to the measure w3c/wcag#1498, by @alastc.
-
Adding comment on default styles w3c/wcag#1497, by @alastc.
-
Adding the hex colour value to an example w3c/wcag#1496, by @alastc.
-
Additional example for understanding doc for #1278 w3c/wcag#1495, by @alastc.
-
Link page about avoiding new window links to new window link warning w3c/wcag#1494, by @lkmorlan.
-
Understanding addition for #1348 w3c/wcag#1493, by @alastc.
-
Update redundant-entry.html w3c/wcag#1487, by @mbgower.
-
Change `touch target` to just `target` w3c/wcag#1485, by @patrickhlauke.
-
Updated SC name w3c/wcag#1484, by @alastc.
-
Issue 1242 SC text clarity w3c/wcag#1482, by @scha14.
-
Fixes for #1478 w3c/wcag#1479, by @awkawk.
-
G195 test adjustment w3c/wcag#1473, by @mbgower.
-
Issue 1374 clarity around "or" w3c/wcag#1471, by @scha14.
-
Issue 1284 w3c/wcag#1469, by @scha14.
-
6 pull requests merged.
-
Update focus-appearance-minimum.html w3c/wcag#1403.
-
Updated SC name w3c/wcag#1484.
-
Explain Pointer Gesture vs. dragging movement w3c/wcag#1423.
-
fix link typo in 1.4.4 understanding doc w3c/wcag#1466.
-
Fixes for #1478 w3c/wcag#1479.
-
-
1 pull request closed.
-
Fix: Correct broken link w3c/wcag#515.
-
-
9 pull requests received 12 new comments.
w3c/wcag3
-
1 issue opened.
-
Additional requirement - clarifying responsibilities w3c/wcag3#302, by @alastc.
-
-
1 issue received 4 new comments.
-
1.4.5 / 1.4.9 Image of Text and <text> inside SVGs w3c/wcag3#190 (4 comments by @goodwitch, @JAWS-test)
-
w3c/coga
-
23 issues opened.
-
EO comment: 4.8. QA review and copy edit w3c/coga#223, by @ruoxiran.
-
EO comments: Headings repetition w3c/coga#221, by @ruoxiran.
-
EO comments: Icons in Summary w3c/coga#217, by @ruoxiran.
-
EO comments: Put the Introduction first. w3c/coga#214, by @ruoxiran.
-
EO comments: Move “Following the advice in this document w3c/coga#211, by @ruoxiran.
-
EO comments: Specific suggestions to improve usability w3c/coga#210, by @ruoxiran.
-
EO comments: Draft idea for section 5 text w3c/coga#207, by @ruoxiran.
-
EO comments: Integrate content into existing WAI website resources w3c/coga#201, by @ruoxiran.
-
-
2 issues closed.
-
Editorial suggestions w3c/coga#117.
-
Rename "Description" section in Patterns w3c/coga#150.
-
-
8 issues received 9 new comments.
-
Add patterns section to link to useful resources w3c/coga#152 (2 comments by @rachaelbradley, @SteveALee)
-
Include sensitivity to sound and complex patterns in 3.6 Help Users to Maintain Focus w3c/coga#132 (1 comment by @rachaelbradley)
-
-
1 pull request opened.
-
Update glossary definition w3c/coga#200, by @abijames.
-
w3c/wcag-act
-
5 issues opened.
-
New rule: meta element has no refresh delay w3c/wcag-act#495, by @WilcoFiers.
-
New rule: Element marked as decorative is not exposed w3c/wcag-act#493, by @carlosapaduarte.
-
Resolve "role attribute has valid value" w3c/wcag-act#492, by @cpandhi.
-
Resolve "Visible label is part of accessible name" feedback w3c/wcag-act#491, by @WilcoFiers.
-
Updated rule: `audio` or `video` has no audio that plays automatically w3c/wcag-act#490, by @Jym77.
-
-
4 issues closed.
-
New rule: Text has minimum contrast w3c/wcag-act#475.
-
New rule: Visible label is part of accessible name w3c/wcag-act#482.
-
Resolve "id attribute value is unique" feedback w3c/wcag-act#464.
-
Resolve "HTML page has title" feedback w3c/wcag-act#463.
-
-
8 issues received 9 new comments.
-
Resolve "Object element rendering non-text content has non-empty accessible name" feedback w3c/wcag-act#479 (2 comments by @carlosapaduarte, @maryjom)
-
Updated rule: `audio` or `video` has no audio that plays automatically w3c/wcag-act#490 (1 comment by @maryjom)
-
Resolve "Visible label is part of accessible name" feedback w3c/wcag-act#491 (1 comment by @WilcoFiers)
-
-
1 pull request opened.
-
Update ACT-Task-Force-Decision-Policy.md w3c/wcag-act#494, by @nitedog.
-
-
1 pull request merged.
-
Update wcag-ruleset-review-process.md w3c/wcag-act#486.
-
-
1 pull request received 8 new comments.
-
Update wcag-ruleset-review-process.md w3c/wcag-act#486 (8 comments by @maryjom, @nitedog, @tbostic32, @WilcoFiers)
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
23 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
EO comment: 4.8. QA review and copy edit w3c/coga#223, by @ruoxiran.
-
EO comments: Headings repetition w3c/coga#221, by @ruoxiran.
-
EO comments: Icons in Summary w3c/coga#217, by @ruoxiran.
-
EO comments: Put the Introduction first. w3c/coga#214, by @ruoxiran.
-
EO comments: Move “Following the advice in this document w3c/coga#211, by @ruoxiran.
-
EO comments: Specific suggestions to improve usability w3c/coga#210, by @ruoxiran.
-
EO comments: Draft idea for section 5 text w3c/coga#207, by @ruoxiran.
-
EO comments: Integrate content into existing WAI website resources w3c/coga#201, by @ruoxiran.
-
-
2 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Editorial suggestions w3c/coga#117.
-
Rename "Description" section in Patterns w3c/coga#150.
-
-
8 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 9 new comments.
-
Add patterns section to link to useful resources w3c/coga#152 (2 comments by @rachaelbradley, @SteveALee)
-
Include sensitivity to sound and complex patterns in 3.6 Help Users to Maintain Focus w3c/coga#132 (1 comment by @rachaelbradley)
-
-
1 pull request opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Update glossary definition w3c/coga#200, by @abijames.
-
Accessibility Conformance Testing (ACT) Task Force
Participants
-
3 participants left the Accessibility Conformance Testing (ACT) Task Force.
-
Stein Erik Skotkjerra left.
-
Anne Thyme Nørregaard left.
-
Manoj Venkata left.
-
Participants
-
3 participants joined.
-
Shuxin Ouyang (Huawei) joined.
-
Shuxin Ouyang (Huawei) joined.
-
Juliette Alexandria (Access2online Inc.) joined.
-
-
7 participants left.
-
Wayne Dick (Knowbility) left.
-
Nicolas Steenhout (Knowbility) left.
-
Chris McMeeking (Deque Systems, Inc.) left.
-
Grady Thompson (Intel Corporation) left.
-
Mahita Tovinkere (Intel Corporation) left.
-
Juan LI (Huawei) left.
-
Shuxin Ouyang (Huawei) left.
-
-
1 organization joined.
-
Access2online Inc. joined.
-
GitHub
w3c/wcag
-
74 issues opened.
-
Looking for definitive clarification regarding 1.4.1 w3c/wcag#1467, by @scottaohara.
-
Web-based course - exempted from 1.4.10 Reflow? w3c/wcag#1465, by @detlevhfischer.
-
Findable Help: Some suggested editorial changes for clarity w3c/wcag#1462, by @maryjom.
-
Fixed Reference Points - Potential editorial updates to the SC text w3c/wcag#1461, by @maryjom.
-
[WCAG 2.2 Draft Feedback] 2.5.8 Pointer Target Spacing w3c/wcag#1456, by @dshoukry.
-
[WCAG 2.2 Draft Feedback] 3.2.7 Hidden Controls w3c/wcag#1455, by @dshoukry.
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.5.7 Dragging w3c/wcag#1454, by @dshoukry.
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.3.8 Redundant entry w3c/wcag#1453, by @dshoukry.
-
[WCAG 2.2 Draft Feedback] Success Criterion 3.2.6 Findable Help w3c/wcag#1448, by @dshoukry.
-
[WCAG 2.2 Draft Feedback] Summarized Feedback w3c/wcag#1447, by @dshoukry.
-
SC 3.2.6 Findable Help - Declaring Human Contact Details w3c/wcag#1437, by @omar-bonilla.
-
SC 3.2.6 Findable Help - Goal of Criterion Ambiguous w3c/wcag#1435, by @omar-bonilla.
-
SC 3.2.6 Findable Help - Help Mechanism Priority w3c/wcag#1434, by @omar-bonilla.
-
SC 3.3.8 Redundant Entry and User Frustration w3c/wcag#1431, by @WegnerTR.
-
2.4.13 Term "electronic publication" not needed w3c/wcag#1429, by @kiyochika.
-
SC "level" label doesn't follow the reading order w3c/wcag#1428, by @WilcoFiers.
-
2.4.13 Fixed reference points needs definitions w3c/wcag#1426, by @ghost.
-
Is a time-based token a security concern (timing adjustable) w3c/wcag#1424, by @ajanec01.
-
"How to Meet" Links in WCAG 2.2 All Return 404 Errors w3c/wcag#1421, by @Grunet.
-
Should src36 be mapped to 2.2.2 and not 2.2.1? or perhaps both? w3c/wcag#1420, by @mraccess77.
-
3.3.7 Accessible Authentication - Add mechanism text w3c/wcag#1418, by @awkawk.
-
Long duplicate text in Understanding 1.4.3 w3c/wcag#1406, by @plannero.
-
Adding the word "Pointer" to "2.5.7 Dragging" w3c/wcag#1397, by @SuzanneTaylor.
-
What do "paragraphs" mean in SC 1.4.12? w3c/wcag#1396, by @JAWS-test.
-
Technique SCR39 cut off. w3c/wcag#1395, by @alastc.
-
Hover-dismissable: Use cntl rather than esc w3c/wcag#1393, by @alastc.
-
Editorial fix 2.5.1: Pointer Gestures w3c/wcag#1391, by @jake-abma.
-
Outdated understanding documents still linger around w3c/wcag#1389, by @yatil.
-
2.4.7/2.4.11/2.4.12 Must a focus indicator always be displayed? w3c/wcag#1387, by @JAWS-test.
-
Status of aria-hidden on Unicode characters technique from wiki w3c/wcag#1386, by @kantoche.
-
2.4.7/2.4.11/2.4.12 Focus: should indicator be unique? w3c/wcag#1383, by @Jym77.
-
Timeline for WCAG 2.2 w3c/wcag#1377, by @PICARDBRB.
-
-
22 issues closed.
-
Cognitive function test exception is arbitrary w3c/wcag#1344.
-
Understanding Accessible Authentication 3.3.7 w3c/wcag#1313.
-
3.3.7: Clarify exceptions in definition w3c/wcag#1310.
-
SC 3.3.7: replace "must" by "is" w3c/wcag#1280.
-
Technique SCR39 cut off. w3c/wcag#1395.
-
Editorial fix 2.5.1: Pointer Gestures w3c/wcag#1391.
-
Findable Help SC3.2.6 - same relative order w3c/wcag#1230.
-
SC 2.5.8 Pointer Target Spacing - target size w3c/wcag#1311.
-
Findable Help SC3.2.6 - is one option enough? w3c/wcag#1235.
-
SC 3.2.6 Being responsible for content w3c/wcag#1303.
-
Expand 1.4.10 to apply 'down to' instead of 'at' w3c/wcag#698.
-
small text correction 2.5.8: Pointer Target Spacing w3c/wcag#1355.
-
Findable Help SC3.2.6 hard to understand w3c/wcag#1228.
-
Timeline for WCAG 2.2 w3c/wcag#1377.
-
83 issues received 305 new comments.
-
Pointer Target Spacing (2.5.8), user agent defaults, and lists of links/controls w3c/wcag#1384 (29 comments by @alastc, @detlevhfischer, @jake-abma, @jared-w-smith, @patrickhlauke)
-
Accessible Authentication (3.3.7): clarify whether copy/paste is a cognitive function test w3c/wcag#1359 (17 comments by @alastc, @extra808, @jake-abma, @patrickhlauke, @smhigley, @SteveALee)
-
2.4.7/2.4.11/2.4.12 Focus: should indicator be unique? w3c/wcag#1383 (16 comments by @alastc, @awkawk, @JAWS-test, @Jym77, @mraccess77, @patrickhlauke)
-
WCAG 2.2 Accessible Authentication: clarification on whether this includes CAPTCHAs w3c/wcag#1256 (11 comments by @alastc, @ghost, @mraccess77, @patrickhlauke)
-
Looking for definitive clarification regarding 1.4.1 w3c/wcag#1467 (8 comments by @aardrian, @awkawk, @mraccess77, @patrickhlauke)
-
Hover-dismissable: Use cntl rather than esc w3c/wcag#1393 (8 comments by @alastc, @mraccess77, @patrickhlauke)
-
2.5.8 Larger target sizes could conflict with people needing page zoom w3c/wcag#1381 (8 comments by @alastc, @DanteGagne, @HaTheo, @mraccess77, @patrickhlauke, @smhigley)
-
Can title on links (e.g. linked icon) as sole source of accName ever pass 1.1.1? w3c/wcag#867 (7 comments by @awkawk, @detlevhfischer, @JAWS-test, @patrickhlauke, @stevefaulkner)
-
Adding the word "Pointer" to "2.5.7 Dragging" w3c/wcag#1397 (6 comments by @detlevhfischer, @SuzanneTaylor)
-
Accessible Authentication: Does copy-paste or autofills pass? w3c/wcag#1292 (6 comments by @alastc, @ghost, @mraccess77, @patrickhlauke)
-
2.4.11 Focus Appearance (Minimum) (AA) - clarification needed w3c/wcag#1341 (6 comments by @alastc, @mbgower)
-
What do "paragraphs" mean in SC 1.4.12? w3c/wcag#1396 (6 comments by @JAWS-test, @mraccess77, @patrickhlauke, @scottaohara)
-
2.4.7 limits focus visible to keyboard. 1.4.11 doesn't appear to have the same limitation w3c/wcag#1401 (6 comments by @DavidMacDonald, @patrickhlauke)
-
3.2.7 Hidden Controls – What qualifies as progress or completing a process? w3c/wcag#1442 (5 comments by @CarynPagelTR, @mraccess77, @patrickhlauke, @rachaelbradley)
-
SC 3.3.7 Accessible Authentication & conflict with legal and contractual obligations w3c/wcag#1430 (5 comments by @alastc, @bruce-usab, @patrickhlauke)
-
Relationship/overlap between 2.1's "Pointer Gestures" and 2.2's "Dragging" w3c/wcag#1398 (5 comments by @AndrewArch, @becka11y, @detlevhfischer, @stringyland)
-
3.2.7: Hidden Controls - what happens with optional / on-demand controls w3c/wcag#1400 (5 comments by @mraccess77, @patrickhlauke)
-
Language of Findable Help 3.2.6 is contradictory w3c/wcag#1368 (5 comments by @alastc, @guyhickling, @jake-abma, @patrickhlauke, @scottaohara)
-
3.3.7 Accessible Authentication queries on personal info w3c/wcag#1320 (4 comments by @alastc, @ghost)
-
Comment from IBM: Reword Focus Appearance (Minimum) to provide clarity w3c/wcag#1372 (4 comments by @guyhickling, @mbgower, @RavenAlly)
-
Suggest including the first note provided with SC 2.4.11 (AA) on SC 2.4.12 (AAA) as well. w3c/wcag#1405 (4 comments by @detlevhfischer, @mraccess77, @SuzanneTaylor)
-
Hidden controls SC3.2.7 - Does this cover invisible form fields? w3c/wcag#1243 (4 comments by @detlevhfischer, @guyhickling, @patrickhlauke, @StommePoes)
-
Findable Help SC3.2.6 - access to at least one option? w3c/wcag#1231 (4 comments by @alastc, @guyhickling, @littlea11ywidget)
-
Findable Help SC3.2.6 - available or provided? w3c/wcag#1232 (4 comments by @alastc, @guyhickling, @scha14)
-
Web-based course - exempted from 1.4.10 Reflow? w3c/wcag#1465 (3 comments by @alastc, @JAWS-test, @patrickhlauke)
-
Expand 1.4.10 to apply 'down to' instead of 'at' w3c/wcag#698 (3 comments by @alastc, @patrickhlauke)
-
Moving phone camera over QR code a case for 2.5.4 Motion Actuation? w3c/wcag#1120 (2 comments by @mrazzari, @patrickhlauke)
-
Findable Help: Some suggested editorial changes for clarity w3c/wcag#1462 (2 comments by @maryjom, @mraccess77)
-
SC 2.5.8 Pointer Target Spacing - Suggested reformulation of pointer clearance calculation w3c/wcag#1444 (2 comments by @alastc, @detlevhfischer)
-
SC 2.5.8 Pointer Target Spacing - Minimum pointer clearance needs better empirical backing w3c/wcag#1445 (2 comments by @detlevhfischer, @patrickhlauke)
-
What types of electronic publications are intended to be covered by 2.4.13 Fixed Reference Points? w3c/wcag#1422 (2 comments by @alastc, @AndrewArch)
-
2.4.11 Focus Appearance (Minimum) - adjacent contrast and unobscured clauses w3c/wcag#1399 (2 comments by @mraccess77, @RavenAlly)
-
Accessible Authentication (3.3.7) far too fundamentally restrictive for a Level A w3c/wcag#1364 (2 comments by @AidanA11y, @alastc)
-
Accessible Authentication (3.3.7) confusing example (properly marked up email and password) w3c/wcag#1363 (2 comments by @alastc)
-
Accessible Authentication (3.3.7): Include each step in an authentication process w3c/wcag#1358 (2 comments by @AidanA11y, @alastc)
-
2.4.11/2.4.12 Focus Appearance: consider distance between component and indicator w3c/wcag#1382 (2 comments by @detlevhfischer, @JAWS-test)
-
2.4.7/2.4.11/2.4.12 Must a focus indicator always be displayed? w3c/wcag#1387 (2 comments by @awkawk, @detlevhfischer)
-
Status of aria-hidden on Unicode characters technique from wiki w3c/wcag#1386 (2 comments by @alastc, @awkawk)
-
3.2.6 Findable Help, confusing use of "page" and "web page" w3c/wcag#1347 (2 comments by @alastc, @jake-abma)
-
2.5.8 Pointer Target Spacing could include link to the definition of mechanism w3c/wcag#1321 (2 comments by @alastc)
-
2.5.4 understanding - suggestion to remove the "user gestures towards device" angle w3c/wcag#1464 (1 comment by @patrickhlauke)
-
[WCAG 2.2 Draft Feedback] Success Criterion 2.4.13 Fixed Reference Points w3c/wcag#1449 (1 comment by @dshoukry)
-
SC 2.5.8 Pointer Target Spacing - How do input labels impact spacing requirements? w3c/wcag#1432 (1 comment by @detlevhfischer)
-
Add space between figure number and figure caption on Text Spacing and other SCs w3c/wcag#1458 (1 comment by @patrickhlauke)
-
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)
-
SC 2.5.8 Pointer Target Spacing - Clarification: Overlapping Spacing w3c/wcag#1312 (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 @AidanA11y)
-
2.4.11 Focus Appearance (minimum) - possible scenario where visible indicator is caught by wording w3c/wcag#1390 (1 comment by @mg-winter)
-
'Understanding Findable Help 3.2.6' implicitly recommends unhelpful page formats/headings w3c/wcag#1380 (1 comment by @patrickhlauke)
-
-
17 pull requests opened.
-
fix link typo in 1.4.4 understanding doc w3c/wcag#1466, by @scottaohara.
-
Add space after autogenerated figure number w3c/wcag#1459, by @patrickhlauke.
-
Text spacing understanding reword w3c/wcag#1457, by @mbgower.
-
Explain Pointer Gesture vs. dragging movement w3c/wcag#1423, by @detlevhfischer.
-
Adding copy-paste references w3c/wcag#1419, by @alastc.
-
Adding to 1st example bullet. w3c/wcag#1415, by @alastc.
-
Update to SC text about steps w3c/wcag#1414, by @alastc.
-
Tweak to intent section. w3c/wcag#1412, by @alastc.
-
Moving note into the definition w3c/wcag#1411, by @alastc.
-
"Must" to "is" w3c/wcag#1408, by @alastc.
-
Replacing the image-recognition example w3c/wcag#1407, by @alastc.
-
Update focus-appearance-minimum.html w3c/wcag#1403, by @mbgower.
-
Typo from issue 1391 w3c/wcag#1392, by @alastc.
-
Update focus-appearance-minimum.html w3c/wcag#1388, by @mbgower.
-
Update pointer-target-spacing.html w3c/wcag#1379, by @detlevhfischer.
-
Issue 1229 Clarity on self-help option w3c/wcag#1376, by @scha14.
-
Issue 1229 clarity on self help draft w3c/wcag#1375, by @scha14.
-
-
11 pull requests merged.
-
Update to SC text about steps w3c/wcag#1414.
-
Adding to 1st example bullet. w3c/wcag#1415.
-
Tweak to intent section. w3c/wcag#1412.
-
Moving note into the definition w3c/wcag#1411.
-
"Must" to "is" w3c/wcag#1408.
-
Add space after autogenerated figure number w3c/wcag#1459.
-
Typo from issue 1391 w3c/wcag#1392.
-
Update pointer-target-spacing.html w3c/wcag#1379.
-
Issue 1303 Clarification on responsible for content w3c/wcag#1366.
-
Issue 1321 add definition of mechanism w3c/wcag#1338.
-
Change "criteria" to "criterion" w3c/wcag#1371.
-
-
1 pull request closed.
-
Issue 1314 1228 Update findable-help.html (Editorial) w3c/wcag#1357.
-
-
7 pull requests received 17 new comments.
w3c/wcag-act
-
8 issues opened.
-
New rule: autocomplete attribute has valid value w3c/wcag-act#489, by @ajanec01.
-
[Broken link] ACT Rules Format 1.0 has a broken link to the rules review process w3c/wcag-act#488, by @maryjom.
-
Updated rule: "role attribute has valid value" w3c/wcag-act#487, by @Jym77.
-
Resolve "Text has minimum contrast" feedback w3c/wcag-act#485, by @maryjom.
-
New rule: Scrollable element is keyboard accessible w3c/wcag-act#484, by @WilcoFiers.
-
New rule: Visible label is part of accessible name w3c/wcag-act#482, by @WilcoFiers.
-
Updated rule: Image filename is accessible name for image w3c/wcag-act#480, by @Jym77.
-
-
4 issues closed.
-
Resolve " Role attribute has valid value" feedback w3c/wcag-act#467.
-
Resolve "aria-* attribute is defined in WAI-ARIA" feedback w3c/wcag-act#452.
-
New rule: Object element has non-empty accessible name w3c/wcag-act#470.
-
-
15 issues received 18 new comments.
-
Resolve " Role attribute has valid value" feedback w3c/wcag-act#467 (3 comments by @jeeyyy, @Jym77, @WilcoFiers)
-
Resolve "id attribute value is unique" feedback w3c/wcag-act#464 (2 comments by @maryjom, @WilcoFiers)
-
Resolving "`audio` or `video` has no audio that plays automatically" feedback w3c/wcag-act#456 (1 comment by @Jym77)
-
Resolve "Orientation of the page is not restricted using CSS transform property" feedback w3c/wcag-act#445 (1 comment by @WilcoFiers)
-
Resolve "Object element rendering non-text content has non-empty accessible name" feedback w3c/wcag-act#479 (1 comment by @carlosapaduarte)
-
-
2 pull requests opened.
-
Update wcag-ruleset-review-process.md w3c/wcag-act#486, by @WilcoFiers.
-
Add issue template w3c/wcag-act#483, by @WilcoFiers.
-
-
1 pull request merged.
-
Add issue template w3c/wcag-act#483.
-
w3c/wcag3
-
2 issues opened.
-
3.3.8 Accessible Authentication is Worrisome w3c/wcag3#177, by @SuzanneTaylor.
-
3 issues received 26 new comments.
-
Contrast Ratio Math and Related Visual Issues w3c/wcag3#192 (20 comments by @alastc, @bruce-usab, @jrus, @Myndex, @NickColley, @StommePoes, @tkeenoy)
-
3.3.8 Accessible Authentication is Worrisome w3c/wcag3#177 (5 comments by @alastc, @bruce-usab, @patrickhlauke, @SuzanneTaylor)
-
WCAG 2.2 Accessible Authentication and CAPTCHAs - why not a AAA SC just for CAPTCHAs? w3c/wcag3#176 (1 comment by @alastc)
-
w3c/coga
-
20 issues opened.
-
Comments from EO w3c/coga#199, by @lseeman.
-
comments from PhD student Emma Dixon and Amanda Lazar w3c/coga#198, by @lseeman.
-
Suggestions for streamlining the table of contents w3c/coga#193, by @julierawe.
-
4.5.3.2 How it Helps (confusing sentence) w3c/coga#192, by @martynka.
-
Consistency: "short-term memory" and "short term memory" w3c/coga#191, by @martynka.
-
4.7.3.3 How it Helps (typo/unclear) w3c/coga#190, by @martynka.
-
4.4.5.3 How it Helps (ADD) w3c/coga#188, by @martynka.
-
4.3.3.3 How it Helps (repeated text and unnecessary text) w3c/coga#185, by @martynka.
-
4.2.2.4 More Details - typo w3c/coga#184, by @martynka.
-
Repeated words (text typos) w3c/coga#183, by @martynka.
-
Plain language - Passive sentences w3c/coga#182, by @martynka.
-
[minor] match outline numbering with Objective numbering w3c/coga#181, by @shawna-slh.
-
Suggestions re icons and other aspects of the summary w3c/coga#180, by @julierawe.
-
Suggested changes to Jonathan (dyscalculia) persona and scenarios w3c/coga#179, by @julierawe.
-
Suggested changes to the Carolyn (ADHD) persona and scenarios w3c/coga#178, by @julierawe.
-
-
2 issues closed.
-
Delete content-usable/table.html w3c/coga#125.
-
Clean up branches w3c/coga#126.
-
-
27 issues received 39 new comments.
-
Suggested changes for Pattern 4.2.5 Clearly Identify Controls and Their Use w3c/coga#167 (9 comments by @julierawe, @lseeman, @SteveALee)
-
4.4.9.3 How it Helps (don't understand sentence, may need punctuation) w3c/coga#189 (2 comments by @martynka, @rachaelbradley)
-
Editorial suggestions in Introduction from Wordsmithing Meeting w3c/coga#122 (2 comments by @lseeman, @rachaelbradley)
-
Write in plain English, Use Plain Language Guideline (positive sentences) w3c/coga#186 (1 comment by @rachaelbradley)
-
4.3.3.3 How it Helps (repeated text and unnecessary text) w3c/coga#185 (1 comment by @rachaelbradley)
-
Write in plain English, Use Plain Language Guideline (Omit superfluous words)) w3c/coga#187 (1 comment by @rachaelbradley)
-
-
2 pull requests opened.
-
Use expected format for w3c.json contacts w3c/coga#196, by @dontcallmedom.
-
-
1 pull request closed.
-
2 pull requests received 4 new comments.
-
Updated coga/content-usable/design.html and coga/content-usable/index.html w3c/coga#194 (3 comments by @lseeman, @nitish-awasthi)
-
Low Vision Accessibility Task Force
Participants
-
1 participant left the Low Vision Accessibility Task Force.
-
Wayne Dick left.
-
Mobile Accessibility Task Force
Participants
-
1 participant left the Mobile Accessibility Task Force.
-
Chris McMeeking left.
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
20 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Comments from EO w3c/coga#199, by @lseeman.
-
comments from PhD student Emma Dixon and Amanda Lazar w3c/coga#198, by @lseeman.
-
Suggestions for streamlining the table of contents w3c/coga#193, by @julierawe.
-
4.5.3.2 How it Helps (confusing sentence) w3c/coga#192, by @martynka.
-
Consistency: "short-term memory" and "short term memory" w3c/coga#191, by @martynka.
-
4.7.3.3 How it Helps (typo/unclear) w3c/coga#190, by @martynka.
-
4.4.5.3 How it Helps (ADD) w3c/coga#188, by @martynka.
-
4.3.3.3 How it Helps (repeated text and unnecessary text) w3c/coga#185, by @martynka.
-
4.2.2.4 More Details - typo w3c/coga#184, by @martynka.
-
Repeated words (text typos) w3c/coga#183, by @martynka.
-
Plain language - Passive sentences w3c/coga#182, by @martynka.
-
[minor] match outline numbering with Objective numbering w3c/coga#181, by @shawna-slh.
-
Suggestions re icons and other aspects of the summary w3c/coga#180, by @julierawe.
-
Suggested changes to Jonathan (dyscalculia) persona and scenarios w3c/coga#179, by @julierawe.
-
Suggested changes to the Carolyn (ADHD) persona and scenarios w3c/coga#178, by @julierawe.
-
-
2 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Delete content-usable/table.html w3c/coga#125.
-
Clean up branches w3c/coga#126.
-
-
27 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 39 new comments.
-
Suggested changes for Pattern 4.2.5 Clearly Identify Controls and Their Use w3c/coga#167 (9 comments by @julierawe, @lseeman, @SteveALee)
-
4.4.9.3 How it Helps (don't understand sentence, may need punctuation) w3c/coga#189 (2 comments by @martynka, @rachaelbradley)
-
Editorial suggestions in Introduction from Wordsmithing Meeting w3c/coga#122 (2 comments by @lseeman, @rachaelbradley)
-
Write in plain English, Use Plain Language Guideline (positive sentences) w3c/coga#186 (1 comment by @rachaelbradley)
-
4.3.3.3 How it Helps (repeated text and unnecessary text) w3c/coga#185 (1 comment by @rachaelbradley)
-
Write in plain English, Use Plain Language Guideline (Omit superfluous words)) w3c/coga#187 (1 comment by @rachaelbradley)
-
-
2 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Use expected format for w3c.json contacts w3c/coga#196, by @dontcallmedom.
-
-
1 pull request closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
2 pull requests in the Cognitive and Learning Disabilities Accessibility Task Force received 4 new comments.
-
Updated coga/content-usable/design.html and coga/content-usable/index.html w3c/coga#194 (3 comments by @lseeman, @nitish-awasthi)
-
TR publications
-
1 document published.
-
Web Content Accessibility Guidelines (WCAG) 2.2 published as a Working Draft. History of Web Content Accessibility Guidelines (WCAG) 2.2
-
Participants
-
5 participants joined.
-
Mahita Tovinkere (Intel Corporation) joined.
-
Grady Thompson (Intel Corporation) joined.
-
Levon Spradlin (Pearson plc) joined.
-
Karen Myers (W3C) joined.
-
Sarah Horton (W3C Invited Experts) joined.
-
-
2 participants left.
-
Thomas Hoffmann (Educational Testing Service) left.
-
Sarah Horton (W3C Invited Experts) left.
-
-
1 organization joined.
-
Accessibility Shield joined.
-
GitHub
w3c/wcag
-
103 issues opened.
-
IBM Comment: Make small editorial change to Minimum Area in 2.4.11 w3c/wcag#1374, by @mbgower.
-
Comment from IBM: Make border a defined term in 2.4.11 w3c/wcag#1373, by @mbgower.
-
Comment from IBM: Reword Focus Appearance (Minimum) to provide clarity w3c/wcag#1372, by @mbgower.
-
Understanding Use of Colour and Non Text Contrast w3c/wcag#1370, by @ghost.
-
Dotted outline focus indicators in SC2.4.11 - Minimum area bullet w3c/wcag#1369, by @guyhickling.
-
Language of Findable Help 3.2.6 is contradictory w3c/wcag#1368, by @guyhickling.
-
What is meant by "a set of web pages"? w3c/wcag#1367, by @guyhickling.
-
small text correction 2.5.8: Pointer Target Spacing w3c/wcag#1355, by @jake-abma.
-
Non-modal dialogues and Unobscured 2.4.11: Focus Appearance w3c/wcag#1352, by @jake-abma.
-
Textual size fix needed 2.4.11: Focus Appearance (Minimum) w3c/wcag#1351, by @jake-abma.
-
H71 - incomplete sentence w3c/wcag#1350, by @KerstinProbiesch.
-
I18N Self-Review w3c/wcag#1349, by @michael-n-cooper.
-
2.4.11 Focus Appearance requires contrast for aliased pixels w3c/wcag#1348, by @WilcoFiers.
-
3.2.6 Findable Help, confusing use of "page" and "web page" w3c/wcag#1347, by @WilcoFiers.
-
SC 3.3.8 Re-entering usually isn't essential w3c/wcag#1346, by @WilcoFiers.
-
SC 3.3.8 Redundant entry, term "step" is ambiguous w3c/wcag#1345, by @WilcoFiers.
-
Cognitive function test exception is arbitrary w3c/wcag#1344, by @WilcoFiers.
-
Cognitive function test definition relies on informative note w3c/wcag#1343, by @WilcoFiers.
-
WCAG 2.1 Rec, 5.3.1 left-over note? w3c/wcag#1340, by @detlevhfischer.
-
2.4.11 Focus Appearance (Minimum) (AA) - clarification needed w3c/wcag#1341, by @MichellanneLi.
-
2.5.7: Dragging - essential example w3c/wcag#1336, by @ghost.
-
3.3.8: Redundant entry - session term w3c/wcag#1335, by @ghost.
-
F105: Failure of Success Criterion 2.5.1 Pointer Gestures w3c/wcag#1333, by @lgnacio.
-
3.3.7 Accessible Authentication queries on personal info w3c/wcag#1320, by @alastc.
-
Translations URLs pointing to folders rather than documents w3c/wcag#1319, by @plannero.
-
SC 3.3.7 Accessible Authentication w3c/wcag#1318, by @ysmartin.
-
confusing wording in dfn-pagebreak-locator w3c/wcag#1317, by @carmacleod.
-
Active Participants w3c/wcag#1315, by @charleshalldesign.
-
SC 3.2.6 Finding Help SC text w3c/wcag#1314, by @littlea11ywidget.
-
Understanding Accessible Authentication 3.3.7 w3c/wcag#1313, by @littlea11ywidget.
-
SC 2.5.8 Pointer Target Spacing - Clarification: Overlapping Spacing w3c/wcag#1312, by @bruskowski.
-
SC 2.5.8 Pointer Target Spacing - target size w3c/wcag#1311, by @EmanuelaGorla.
-
3.3.7: Clarify exceptions in definition w3c/wcag#1310, by @alastc.
-
ARIA11: Add clause about form role needing an accessible label w3c/wcag#1308, by @carmacleod.
-
Dragging on mobile apps w3c/wcag#1307, by @lgnacio.
-
C41 does not fulfil SC 2.4.12 w3c/wcag#1306, by @JAWS-test.
-
Example 2 for G195 is too inaccurate w3c/wcag#1305, by @JAWS-test.
-
2.4.12 Focus Appearance (Enhanced): Unobscured w3c/wcag#1304, by @JAWS-test.
-
SC 3.2.6 Being responsible for content w3c/wcag#1303, by @jbuller.
-
SC 2.4.13: Fixed Reference Points "on the same page" w3c/wcag#1302, by @jbuller.
-
Clarification on the definition of electronic publication w3c/wcag#1299, by @fstrr.
-
Is an opt-in option for flashing content sufficient to meet SC 2.3.1? w3c/wcag#1298, by @mraccess77.
-
SC 3.3.8: Redundant entry - Typo on Understanding page w3c/wcag#1294, by @NoahGresser.
-
Accessible Authentication: Does copy-paste or autofills pass? w3c/wcag#1292, by @ghost.
-
SC 2.4.11/2.4.12 Clarify third bullet point w3c/wcag#1291, by @yatil.
-
SC 2.4.11 Unclear use of thickness, other questions w3c/wcag#1290, by @yatil.
-
SC 2.4.12 - want to confirm the requirement for a 'solid' border w3c/wcag#1289, by @camusamta.
-
broken link(s) in Technique w3c/wcag#1286, by @shawna-slh.
-
Does Accessible Authentication apply to CAPTCHA? w3c/wcag#1285, by @ghost.
-
"user interface component" lowercase fixes w3c/wcag#1284, by @shawna-slh.
-
broken links in Understanding w3c/wcag#1283, by @shawna-slh.
-
Future simplification="important" technique w3c/wcag#1282, by @yatil.
-
SC 3.3.7: replace "must" by "is" w3c/wcag#1280, by @cstrobbe.
-
Add example of 8px side border w3c/wcag#1279, by @alastc.
-
Does a change of background pass Focus Appearance (Minimum) w3c/wcag#1278, by @lchandelier.
-
SC 3.3.8 Redundant Entry is missing the orange "Status" warning w3c/wcag#1277, by @StommePoes.
-
SC 3.3.8 Redundant Entry - mobility use case w3c/wcag#1276, by @StommePoes.
-
Is a date input mask required by 3.3.2 Labels or Instructions? w3c/wcag#1273, by @ghost.
-
Discrepancy between F73 and G183 w3c/wcag#1272, by @WilcoFiers.
-
Add H97 to related techniques for H69 w3c/wcag#1270, by @carmacleod.
-
Technique documents don't show the technique number w3c/wcag#1268, by @guyhickling.
-
minor issues for wide review draft w3c/wcag#1267, by @shawna-slh.
-
+ w3c/wcag#1266, by @shawna-slh.
-
Does failure of 3.1.1 imply failure of 3.1.2? w3c/wcag#1264, by @stevefaulkner.
-
Understanding 1.4.3 and 1.4.6 should refer to 1.4.11 w3c/wcag#1261, by @JAWS-test.
-
G84 indicates it's sufficient to meet ARIA19 w3c/wcag#1259, by @mraccess77.
-
SCR18 is listed as both sufficient and advisory for SC 3.3.3 w3c/wcag#1258, by @mraccess77.
-
SCR39 is missing from the How to Meet document for SC 1.4.13 w3c/wcag#1250, by @mraccess77.
-
Cleanup of the non-linked techniques. w3c/wcag#1245, by @alastc.
-
-
32 issues closed.
-
Textual size fix needed 2.4.11: Focus Appearance (Minimum) w3c/wcag#1351.
-
2.4.12 Focus Appearance (Enhanced): Unobscured w3c/wcag#1304.
-
Add example of 8px side border w3c/wcag#1279.
-
SC 2.4.11/2.4.12 Clarify third bullet point w3c/wcag#1291.
-
SC 3.3.8 Redundant Entry - mobility use case w3c/wcag#1276.
-
SC 3.3.8: Redundant entry - Typo on Understanding page w3c/wcag#1294.
-
Does Accessible Authentication apply to CAPTCHA? w3c/wcag#1285.
-
Grammar and clarity of SC2.4.11 Focus Visible (Enhanced) w3c/wcag#1055.
-
minor issues for wide review draft w3c/wcag#1267.
-
+ w3c/wcag#1266.
-
SCR39 is missing from the How to Meet document for SC 1.4.13 w3c/wcag#1250.
-
Meet 1.3.5 via name attributes mapping to schema.org? w3c/wcag#935.
-
It is time to remove the Flash techniques w3c/wcag#1140.
-
exception for logos (1.4.3, 1.4.11) w3c/wcag#902.
-
Intermediate points in definition of dragging (for SC2.5.7) w3c/wcag#1195.
-
WCAG 2.2 focus visible enhanced contrast seems to leave gap? w3c/wcag#1038.
-
90 issues received 321 new comments.
-
Focus Appearance (Minimum) SC2.4.11 - the Obscured bullet allows components to be completely obscured! w3c/wcag#1271 (22 comments by @alastc, @guyhickling, @JAWS-test, @StommePoes, @yatil)
-
SC 2.5.8 Pointer Target Spacing - Clarification: Overlapping Spacing w3c/wcag#1312 (17 comments by @aardrian, @ajanec01, @alastc, @bruskowski, @detlevhfischer, @mraccess77, @scha14)
-
WCAG 2.2 Accessible Authentication: clarification on whether this includes CAPTCHAs w3c/wcag#1256 (17 comments by @alastc, @fstrr, @ghost, @JaninaSajka, @JohnRochfordUMMS, @patrickhlauke)
-
2.4.11 Focus Appearance (Minimum) (AA) - clarification needed w3c/wcag#1341 (15 comments by @alastc, @awkawk, @jared-w-smith, @mbgower, @mraccess77, @patrickhlauke)
-
Accessible Authentication (3.3.7): clarify whether copy/paste is a cognitive function test w3c/wcag#1359 (12 comments by @alastc, @jake-abma, @patrickhlauke, @SteveALee)
-
Cross behavior between focus and hover (1.4.13) w3c/wcag#1196 (11 comments by @alastc, @idoros, @mraccess77, @scha14)
-
Understanding Use of Colour and Non Text Contrast w3c/wcag#1370 (9 comments by @ghost, @patrickhlauke)
-
2.4.11 Unusual scenario: two 'visible indicators' within the same hit area w3c/wcag#1337 (9 comments by @alastc, @awkawk, @detlevhfischer, @mraccess77, @patrickhlauke)
-
Findable Help SC3.2.6 - all changes together w3c/wcag#1242 (8 comments by @alastc, @guyhickling, @scha14, @SteveALee)
-
SC 2.4.11 Unclear use of thickness, other questions w3c/wcag#1290 (8 comments by @alastc, @carrythebanner, @juleskuehn, @mraccess77, @yatil)
-
SC 2.4.11/2.4.12 Clarify third bullet point w3c/wcag#1291 (8 comments by @alastc, @juleskuehn, @yatil)
-
Does a change of background pass Focus Appearance (Minimum) w3c/wcag#1278 (7 comments by @alastc, @JAWS-test, @lchandelier)
-
Loophole / Escape for (almost) all HTML / CSS based apps? 2.5.8 Pointer Target Spacing w3c/wcag#1354 (7 comments by @jake-abma, @patrickhlauke)
-
2.4.11 Unusual scenario: Very short links with a thick underline focus state w3c/wcag#1329 (7 comments by @36degrees, @alastc, @detlevhfischer, @mraccess77)
-
Hidden controls SC3.2.7 - Does this cover invisible form fields? w3c/wcag#1243 (7 comments by @alastc, @guyhickling, @mraccess77, @patrickhlauke, @StommePoes)
-
Grammar and clarity of SC2.4.11 Focus Visible (Enhanced) w3c/wcag#1055 (7 comments by @alastc, @guyhickling, @scha14)
-
Textual size fix needed 2.4.11: Focus Appearance (Minimum) w3c/wcag#1351 (6 comments by @alastc, @jake-abma, @patrickhlauke)
-
Does failure of 3.1.1 imply failure of 3.1.2? w3c/wcag#1264 (6 comments by @alastc, @frex65, @JAWS-test, @patrickhlauke, @stevefaulkner)
-
Graphic buttons whose name is different from the label in the legend - violation of 2.5.3? w3c/wcag#1260 (5 comments by @alastc, @guyhickling, @JAWS-test, @patrickhlauke)
-
Could autocomplete be used to meet the proposed redundant entry SC auto-populate clause? w3c/wcag#1194 (4 comments by @alastc, @jake-abma)
-
Non-modal dialogues and Unobscured 2.4.11: Focus Appearance w3c/wcag#1352 (4 comments by @alastc, @jake-abma)
-
2.4.11 Focus Visible (Enhanced) - what counts as "bounding rectangle"/"bounding box" w3c/wcag#1075 (4 comments by @36degrees, @alastc, @scha14)
-
SC 2.4.12 - want to confirm the requirement for a 'solid' border w3c/wcag#1289 (4 comments by @alastc, @camusamta, @juleskuehn)
-
ARIA11 should reference role="region", and not role="application" w3c/wcag#291 (4 comments by @alastc, @carmacleod)
-
2.5.8 Pointer Target Spacing could include link to the definition of mechanism w3c/wcag#1321 (3 comments by @ajanec01, @scha14)
-
How should 2.4.11 / 2.4.12 be applied to inline elements that wrap over multiple lines? w3c/wcag#1328 (3 comments by @36degrees, @alastc)
-
Is a date input mask required by 3.3.2 Labels or Instructions? w3c/wcag#1273 (3 comments by @ghost, @JAWS-test, @StommePoes)
-
Meet 1.3.5 via name attributes mapping to schema.org? w3c/wcag#935 (3 comments by @alastc, @patrickhlauke)
-
Comment from IBM: Reword Focus Appearance (Minimum) to provide clarity w3c/wcag#1372 (2 comments by @awkawk, @mbgower)
-
Findable Help SC3.2.6 - access to at least one option? w3c/wcag#1231 (2 comments by @guyhickling, @scha14)
-
Accessible Authentication (3.3.7) far too fundamentally restrictive for a Level A w3c/wcag#1364 (2 comments by @patrickhlauke)
-
SC3.3.8: Redundant entry - When information previously entered has been saved w3c/wcag#1239 (2 comments by @alastc, @guyhickling)
-
SC3.3.8: Redundant entry - are redundant resumes/curriculum vitae in online job applications a failure? w3c/wcag#1293 (2 comments by @alastc, @ghost)
-
3.3.7 Accessible Authentication queries on personal info w3c/wcag#1320 (2 comments by @alastc, @ghost)
-
F105: Failure of Success Criterion 2.5.1 Pointer Gestures w3c/wcag#1333 (2 comments by @alastc, @patrickhlauke)
-
SC 3.3.8: Redundant entry - Typo on Understanding page w3c/wcag#1294 (2 comments by @NoahGresser, @scha14)
-
Dotted outline focus indicators in SC2.4.11 - Minimum area bullet w3c/wcag#1369 (1 comment by @guyhickling)
-
Pointer Target Spacing (2.5.8) understanding note gives the wrong rationale? w3c/wcag#1362 (1 comment by @detlevhfischer)
-
Hidden Controls (3.2.7): clarify definition of process and controls needed to progress or complete a process w3c/wcag#1360 (1 comment by @RobGallo)
-
Cognitive function test definition relies on informative note w3c/wcag#1343 (1 comment by @gradualclearing)
-
Non-visual status message has wrong language - FAIL in 4.1.3, or elsewhere? w3c/wcag#1342 (1 comment by @awkawk)
-
Cross-reference 2.5.7 Dragging and 2.5.1 Pointer Gestures in Understanding docs w3c/wcag#1316 (1 comment by @detlevhfischer)
-
Clarifying 1.4.11 Understanding: border contrast when labels within input fields w3c/wcag#1091 (1 comment by @detlevhfischer)
-
1.4.1: Use of Color - understanding document needs to be clear if it's about "visual" or more w3c/wcag#1076 (1 comment by @ghost)
-
Is an opt-in option for flashing content sufficient to meet SC 2.3.1? w3c/wcag#1298 (1 comment by @JAWS-test)
-
SC 2.4.11: Focus Appearance (Minimum) - Possible grammatical error on Understanding page w3c/wcag#1296 (1 comment by @patrickhlauke)
-
SC 3.8.8 - duplicating emails in a signup flow: also a 'security verification', or not? w3c/wcag#1288 (1 comment by @ghost)
-
H53 Using the body of the object element is not practically supported w3c/wcag#1138 (1 comment by @WilcoFiers)
-
How to meet document indicates H4 is sufficient for 2.4.3 but h4 says not linked to any understanding documents w3c/wcag#1253 (1 comment by @alastc)
-
F104 is missing as a mapping for SC 1.4.12 in the How to Meet document. w3c/wcag#1251 (1 comment by @alastc)
-
How to Meet WCAG documents lacks mappings to g217 and F99 for SC 2.1.4 w3c/wcag#1249 (1 comment by @alastc)
-
G18 and G45 are listed as sufficient for SC 1.4.11 in the How to Meet document w3c/wcag#1248 (1 comment by @alastc)
-
G199 indicates ARIA22 is sufficient for it - it seems like a confusing statement w3c/wcag#1255 (1 comment by @guyhickling)
-
SC 1.3.5 fields with correct autocomplete inside form with autocomplete="off" w3c/wcag#1197 (1 comment by @alastc)
-
-
24 pull requests opened.
-
Change "criteria" to "criterion" w3c/wcag#1371, by @patrickhlauke.
-
Issue 1303 Clarification on responsible for content w3c/wcag#1366, by @scha14.
-
Removed "note" class w3c/wcag#1365, by @gradualclearing.
-
Issue 1314 1228 Update findable-help.html (Editorial) w3c/wcag#1357, by @scha14.
-
Issue 1314 1228 Update findable-help.html (Editorial) w3c/wcag#1356, by @scha14.
-
Fix for #1350 w3c/wcag#1353, by @awkawk.
-
Issue 1321 add definition of mechanism w3c/wcag#1338, by @scha14.
-
Adding an example of wrapping link w3c/wcag#1332, by @alastc.
-
Updating user-interface-component def w3c/wcag#1331, by @alastc.
-
Adding an 8px thick indicator example w3c/wcag#1330, by @alastc.
-
Updated understanding doc - redundant entry w3c/wcag#1327, by @alastc.
-
Updating understanding doc - redundant entry w3c/wcag#1326, by @alastc.
-
Updating the understanding - redundant entry w3c/wcag#1325, by @alastc.
-
Adding a line to the understanding for redundant entry w3c/wcag#1323, by @alastc.
-
Not fully obscured w3c/wcag#1322, by @alastc.
-
Correct typo in G219 w3c/wcag#1301, by @juleskuehn.
-
Fix outdated reference to focus-visible (enhanced) w3c/wcag#1300, by @juleskuehn.
-
Update pagebreak-locators.html w3c/wcag#1297, by @fstrr.
-
Issue 1294 typo w3c/wcag#1295, by @scha14.
-
Updates from issue 291 w3c/wcag#1269, by @alastc.
-
capitalization fix w3c/wcag#1265, by @shawna-slh.
-
Understanding 1.4.11 - clarify what does _not_ need such contrast w3c/wcag#1252, by @fstrr.
-
point out that boundaries do not need to contrast w3c/wcag#1246, by @gundulaniemann.
-
-
13 pull requests merged.
-
Updating user-interface-component def w3c/wcag#1331.
-
Adding an example of wrapping link w3c/wcag#1332.
-
Adding an 8px thick indicator example w3c/wcag#1330.
-
Not fully obscured w3c/wcag#1322.
-
Updating understanding doc - redundant entry w3c/wcag#1326.
-
Updated understanding doc - redundant entry w3c/wcag#1327.
-
Adding a line to the understanding for redundant entry w3c/wcag#1323.
-
Removing Flash Techniques w3c/wcag#1142.
-
WCAG22 - Focus Visible enh updates w3c/wcag#1121.
-
Changes to examples in Understanding 1.4.11 w3c/wcag#1065.
-
Removing application as a landmark from ARIA11 w3c/wcag#780.
-
-
2 pull requests closed.
-
Reword piano example w3c/wcag#787.
-
Draft of Error correction (Processes) w3c/wcag#1157.
-
-
18 pull requests received 36 new comments.
-
Understanding 1.4.11 - clarify what does _not_ need such contrast w3c/wcag#1252 (5 comments by @fstrr, @gundulaniemann, @patrickhlauke)
-
Dragging movement glossary definition: Deleting reference to intermediate point w3c/wcag#1214 (3 comments by @alastc, @guyhickling)
-
2.5.7 Dragging: adding reference to 2.5.1 Pointer Gestures and v.v. w3c/wcag#1334 (2 comments by @alastc, @michael-n-cooper)
-
w3c/coga
-
40 issues opened.
-
Suggested changes to the Anna (dyslexia) persona and scenarios w3c/coga#177, by @julierawe.
-
Suggested corrections and edits for Summary section w3c/coga#176, by @KimPatch.
-
Comment re 3.8.1 User Story: Adapt w3c/coga#169, by @julierawe.
-
Suggested addition to 3.7.5 User Story: Task Management w3c/coga#168, by @julierawe.
-
Typo - "nine personas" should be "ten personas" w3c/coga#166, by @dtidmarsh.
-
Suggested edits for 3.6.3 User Story: Voice Menus w3c/coga#165, by @julierawe.
-
Suggest adding more examples to 3.5.1 User Story: Distractions w3c/coga#164, by @julierawe.
-
Having names of users from various cultural backgrounds w3c/coga#161, by @fsasaki.
-
Provide guidance for working with local language experts w3c/coga#159, by @fsasaki.
-
Suggested edits to 3.4.1 User Story: Assistance and support w3c/coga#158, by @julierawe.
-
Suggested additions to 3.3.2 User Story: Visual Presentation w3c/coga#157, by @julierawe.
-
Minor updates to Design Guide introduction w3c/coga#155, by @SteveALee.
-
Editorial Pass on the Design Guide w3c/coga#154, by @SteveALee.
-
More Pattern examples w3c/coga#153, by @SteveALee.
-
Add patterns section to link to useful resources w3c/coga#152, by @SteveALee.
-
"More Details" may not be necessary w3c/coga#151, by @SteveALee.
-
Rename "Description" section in Patterns w3c/coga#150, by @SteveALee.
-
Objective content is inconsistent w3c/coga#149, by @SteveALee.
-
Typo w3c/coga#147, by @StommePoes.
-
Easy to read definition w3c/coga#144, by @plenainclusion.
-
Appreciation w3c/coga#142, by @JamieKnightBBC.
-
Math Abbreviation w3c/coga#141, by @JamieKnightBBC.
-
Review use of judgemental terms w3c/coga#140, by @JamieKnightBBC.
-
Use of Person First Language for Autism. w3c/coga#139, by @JamieKnightBBC.
-
Suggested updates to the Summary w3c/coga#138, by @SteveALee.
-
Review visual processing for inclusion in Content Usable w3c/coga#137, by @rachaelbradley.
-
Better incorporate the use of spatial representations w3c/coga#136, by @rachaelbradley.
-
-
2 issues closed.
-
Review Cognitive landing page on the WAI website w3c/coga#134.
-
Minor updates to Design Guide introduction w3c/coga#155.
-
-
12 issues received 42 new comments.
-
Review Cognitive landing page on the WAI website w3c/coga#134 (5 comments by @lseeman, @shawna-slh, @SteveALee)
-
Having names of users from various cultural backgrounds w3c/coga#161 (2 comments by @fsasaki, @SteveALee)
-
Suggested changes for Pattern 4.2.5 Clearly Identify Controls and Their Use w3c/coga#167 (1 comment by @julierawe)
-
2 pull requests opened.
-
typo: then -> than w3c/coga#148, by @nschonni.
-
"not" repeated twice. w3c/coga#146, by @daniel-montalvo.
-
-
1 pull request reopened.
-
"not" repeated twice. w3c/coga#146, by @SteveALee.
-
-
1 pull request received 1 new comment.
w3c/wcag-act
-
6 issues opened.
-
Unusual accessibility requirements mappings w3c/wcag-act#478, by @WilcoFiers.
-
Using draft specs in ACT rules w3c/wcag-act#477, by @WilcoFiers.
-
Resolve "All table header cells have assigned data cells" feedback w3c/wcag-act#476, by @daniel-montalvo.
-
New rule: Text has minimum contrast w3c/wcag-act#475, by @WilcoFiers.
-
Can we streamline the rule update process? w3c/wcag-act#474, by @WilcoFiers.
-
6 issues closed.
-
Resolve "Form control has accessible name" feedback w3c/wcag-act#432.
-
New rule: All table header cells have assigned data cells w3c/wcag-act#469.
-
New Rule: `audio` or `video` avoids automatically playing audio w3c/wcag-act#454.
-
Resolve "Button has an accessible name" feedback w3c/wcag-act#451.
-
New rule: meta viewport does not prevent zoom w3c/wcag-act#455.
-
Resolve "Link has non-empty accessible name" feedback w3c/wcag-act#439.
-
-
16 issues received 22 new comments.
-
New rule: All table header cells have assigned data cells w3c/wcag-act#469 (2 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)
-
Resolve "Orientation of the page is not restricted using CSS transform property" feedback w3c/wcag-act#445 (1 comment by @maryjom)
-
New Rule: `audio` or `video` avoids automatically playing audio w3c/wcag-act#454 (1 comment by @WilcoFiers)
-
1 pull request merged.
-
Add implementation requirements to process w3c/wcag-act#472.
-
w3c/wcag3
-
2 issues opened.
-
Proposed addition to Success Criterion 1.4.8 Visual Presentation w3c/wcag3#178, by @emanser869.
-
Guideline for Irlen Syndrome w3c/wcag3#179, by @alastc.
-
-
2 issues received 10 new comments.
-
Public Comment on 2.3.3 Animation from Interactions and prefers-reduced-motion w3c/wcag3#183 (7 comments by @alastc, @CharlesBelov, @mraccess77, @patrickhlauke)
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
40 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Suggested changes to the Anna (dyslexia) persona and scenarios w3c/coga#177, by @julierawe.
-
Suggested corrections and edits for Summary section w3c/coga#176, by @KimPatch.
-
Comment re 3.8.1 User Story: Adapt w3c/coga#169, by @julierawe.
-
Suggested addition to 3.7.5 User Story: Task Management w3c/coga#168, by @julierawe.
-
Typo - "nine personas" should be "ten personas" w3c/coga#166, by @dtidmarsh.
-
Suggested edits for 3.6.3 User Story: Voice Menus w3c/coga#165, by @julierawe.
-
Suggest adding more examples to 3.5.1 User Story: Distractions w3c/coga#164, by @julierawe.
-
Having names of users from various cultural backgrounds w3c/coga#161, by @fsasaki.
-
Provide guidance for working with local language experts w3c/coga#159, by @fsasaki.
-
Suggested edits to 3.4.1 User Story: Assistance and support w3c/coga#158, by @julierawe.
-
Suggested additions to 3.3.2 User Story: Visual Presentation w3c/coga#157, by @julierawe.
-
Minor updates to Design Guide introduction w3c/coga#155, by @SteveALee.
-
Editorial Pass on the Design Guide w3c/coga#154, by @SteveALee.
-
More Pattern examples w3c/coga#153, by @SteveALee.
-
Add patterns section to link to useful resources w3c/coga#152, by @SteveALee.
-
"More Details" may not be necessary w3c/coga#151, by @SteveALee.
-
Rename "Description" section in Patterns w3c/coga#150, by @SteveALee.
-
Objective content is inconsistent w3c/coga#149, by @SteveALee.
-
Typo w3c/coga#147, by @StommePoes.
-
Easy to read definition w3c/coga#144, by @plenainclusion.
-
Appreciation w3c/coga#142, by @JamieKnightBBC.
-
Math Abbreviation w3c/coga#141, by @JamieKnightBBC.
-
Review use of judgemental terms w3c/coga#140, by @JamieKnightBBC.
-
Use of Person First Language for Autism. w3c/coga#139, by @JamieKnightBBC.
-
Suggested updates to the Summary w3c/coga#138, by @SteveALee.
-
Review visual processing for inclusion in Content Usable w3c/coga#137, by @rachaelbradley.
-
Better incorporate the use of spatial representations w3c/coga#136, by @rachaelbradley.
-
-
2 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Review Cognitive landing page on the WAI website w3c/coga#134.
-
Minor updates to Design Guide introduction w3c/coga#155.
-
-
12 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 42 new comments.
-
Review Cognitive landing page on the WAI website w3c/coga#134 (5 comments by @lseeman, @shawna-slh, @SteveALee)
-
Having names of users from various cultural backgrounds w3c/coga#161 (2 comments by @fsasaki, @SteveALee)
-
Suggested changes for Pattern 4.2.5 Clearly Identify Controls and Their Use w3c/coga#167 (1 comment by @julierawe)
-
2 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
typo: then -> than w3c/coga#148, by @nschonni.
-
"not" repeated twice. w3c/coga#146, by @daniel-montalvo.
-
-
1 pull request reopened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
"not" repeated twice. w3c/coga#146, by @SteveALee.
-
-
1 pull request in the Cognitive and Learning Disabilities Accessibility Task Force received 1 new comment.
Accessibility Conformance Testing (ACT) Task Force
Participants
-
1 participant joined the Accessibility Conformance Testing (ACT) Task Force.
-
Levon Spradlin joined.
-
TR publications
-
1 document published.
Participants
-
3 participants joined.
-
Melina Moehnle (IRT Institut fuer Rundfunktechnik) joined.
-
Tomas Sefcovic (Fiserv) joined.
-
Julia Chen (Google LLC) joined.
-
-
1 participant left.
-
Jeffrey Johnson (SAP SE) left.
-
-
2 organizations joined.
-
IRT Institut fuer Rundfunktechnik joined.
-
Fiserv joined.
-
GitHub
w3c/wcag
-
42 issues opened.
-
Include mobile apps in SC3.2.6 Findable Help w3c/wcag#1244, by @guyhickling.
-
Hidden controls SC3.2.7 - Does this cover invisible form fields? w3c/wcag#1243, by @guyhickling.
-
Findable Help SC3.2.6 - all changes together w3c/wcag#1242, by @guyhickling.
-
Does the help have to be accessible? w3c/wcag#1237, by @JAWS-test.
-
Findable Help SC3.2.6 - is one option enough? w3c/wcag#1235, by @JAWS-test.
-
Retire technique H59 w3c/wcag#1234, by @patrickhlauke.
-
How can long list entries within selects fulfill SC 1.4.10? w3c/wcag#1233, by @JAWS-test.
-
Findable Help SC3.2.6 - available or provided? w3c/wcag#1232, by @guyhickling.
-
Findable Help SC3.2.6 - access to at least one option? w3c/wcag#1231, by @guyhickling.
-
Findable Help SC3.2.6 - same relative order w3c/wcag#1230, by @guyhickling.
-
Findable Help SC3.2.6 - what is self-help? w3c/wcag#1229, by @guyhickling.
-
Findable Help SC3.2.6 hard to understand w3c/wcag#1228, by @guyhickling.
-
SC2.4.13 Fixed Reference Points - a point for the Understanding doc w3c/wcag#1227, by @guyhickling.
-
SC2.4.13 Fixed Reference Points needs another technique w3c/wcag#1226, by @guyhickling.
-
WCAG 2.2 2.5.7 Dragging and its reference to single pointer w3c/wcag#1225, by @guyhickling.
-
Avoid confusion about WCAG versions in the header w3c/wcag#1224, by @Veyfeyken.
-
Challenges: Guideline 1.4.4 and Adaptive Design w3c/wcag#1222, by @fredesch.
-
Challenges: Multi-language support w3c/wcag#1221, by @fredesch.
-
Understanding SC 1.4.11: "that indicator it must meet" (editorial) w3c/wcag#1219, by @cstrobbe.
-
Adding references to 2.2 SCs w3c/wcag#1218, by @alastc.
-
Create new technique for new contrast formula (threshold value) w3c/wcag#1213, by @alastc.
-
Focus appearance rewording of bullet 2 for Focus Visible (Enhanced) w3c/wcag#1212, by @mbgower.
-
A user comment w3c/wcag#1210, by @guyhickling.
-
Challenges: CSS with media features can have huge number of combinations w3c/wcag#1209, by @dd8.
-
2.1 and 2.2 version documents mixed up w3c/wcag#1207, by @guyhickling.
-
Abort of the Up-Event not possible - Violation of SC 2.5.2 w3c/wcag#1203, by @JAWS-test.
-
Links ambiguous to AT users only can pass 2.4.4 and 2.4.9 w3c/wcag#1202, by @dd8.
-
Fail pages for including read-aloud functions? w3c/wcag#1199, by @detlevhfischer.
-
Cross behavior between focus and hover (1.4.13) w3c/wcag#1196, by @idoros.
-
Intermediate points in definition of dragging (for SC2.5.7) w3c/wcag#1195, by @guyhickling.
-
Understanding 1.4.11 - clarify what does _not_ need such contrast w3c/wcag#1187, by @shawna-slh.
-
-
17 issues closed.
-
Include mobile apps in SC3.2.6 Findable Help w3c/wcag#1244.
-
Change 1.4.10 Reflow to level A w3c/wcag#1050.
-
1.4.10 Reflow and having more nuance for tables w3c/wcag#1129.
-
2.4.11 Focus Visible (Enhanced) Remove F78 and F55 w3c/wcag#1067.
-
Feedback on Focus Visible (Enhanced): Too Much Math w3c/wcag#1053.
-
1.4.11 hover state clarification w3c/wcag#849.
-
2.1 and 2.2 version documents mixed up w3c/wcag#1207.
-
Focus visible using fixed size indicators w3c/wcag#1003.
-
Broken link on C39 w3c/wcag#1101.
-
Wunder w3c/wcag#1190.
-
Web w3c/wcag#1189.
-
Blank w3c/wcag#1191.
-
-
58 issues received 297 new comments.
-
Conflict between glossary definition of label and H65 sufficient technique for 3.3.2 w3c/wcag#101 (32 comments by @alastc, @awkawk, @goetsu, @innoticFR, @mraccess77, @patrickhlauke)
-
Abort of the Up-Event not possible - Violation of SC 2.5.2 w3c/wcag#1203 (25 comments by @alastc, @jake-abma, @JAWS-test, @mraccess77, @patrickhlauke)
-
Challenges: CSS with media features can have huge number of combinations w3c/wcag#1209 (22 comments by @alastc, @dd8, @jake-abma, @patrickhlauke, @sajkaj)
-
Fail pages for including read-aloud functions? w3c/wcag#1199 (18 comments by @alastc, @bruce-usab, @detlevhfischer, @jake-abma, @mraccess77, @patrickhlauke)
-
Understanding 1.4.10 Reflow - additional clarifications esp. what is a fail and what is not w3c/wcag#1188 (16 comments by @detlevhfischer, @mraccess77, @patrickhlauke, @StommePoes, @yatil)
-
SC 1.3.5 fields with correct autocomplete inside form with autocomplete="off" w3c/wcag#1197 (12 comments by @alastc, @awkawk, @detlevhfischer, @goetsu, @jake-abma, @kantoche, @mraccess77, @patrickhlauke)
-
Focus appearance rewording of bullet 2 for Focus Visible (Enhanced) w3c/wcag#1212 (9 comments by @ajanec01, @alastc)
-
WCAG 2.2 2.5.7 Dragging and its reference to single pointer w3c/wcag#1225 (9 comments by @guyhickling, @patrickhlauke)
-
Cross behavior between focus and hover (1.4.13) w3c/wcag#1196 (9 comments by @alastc, @detlevhfischer, @idoros, @JAWS-test, @mraccess77)
-
Links ambiguous to AT users only can pass 2.4.4 and 2.4.9 w3c/wcag#1202 (7 comments by @dd8, @JAWS-test, @mraccess77)
-
Intermediate points in definition of dragging (for SC2.5.7) w3c/wcag#1195 (7 comments by @detlevhfischer, @guyhickling)
-
SC 1.3.5 Technique "Use type attribute on fields in simple login forms"? w3c/wcag#504 (6 comments by @alastc, @detlevhfischer, @mraccess77, @patrickhlauke)
-
Findable Help SC3.2.6 - access to at least one option? w3c/wcag#1231 (6 comments by @guyhickling, @JAWS-test)
-
Grammar and clarity of SC2.4.11 Focus Visible (Enhanced) w3c/wcag#1055 (6 comments by @alastc, @guyhickling, @scha14)
-
Create new technique for new contrast formula (threshold value) w3c/wcag#1213 (6 comments by @alastc, @bruce-usab)
-
Understanding 1.4.11 - clarify what does _not_ need such contrast w3c/wcag#1187 (6 comments by @fstrr, @patrickhlauke, @pauljadam, @StommePoes)
-
2.1 and 2.2 version documents mixed up w3c/wcag#1207 (6 comments by @alastc, @guyhickling, @patrickhlauke, @yatil)
-
Could autocomplete be used to meet the proposed redundant entry SC auto-populate clause? w3c/wcag#1194 (6 comments by @alastc, @guyhickling, @Helixopp, @johnfoliot, @patrickhlauke)
-
Tooltip does not close when exiting the triggering item - violation of 1.4.13? w3c/wcag#1193 (6 comments by @detlevhfischer, @guyhickling, @jake-abma, @JAWS-test, @mraccess77)
-
Hidden controls SC3.2.7 - Does this cover invisible form fields? w3c/wcag#1243 (5 comments by @awkawk, @guyhickling, @JAWS-test, @mraccess77)
-
Feedback on Focus Visible (Enhanced): Too Much Math w3c/wcag#1053 (5 comments by @detlevhfischer, @scha14, @scsporie)
-
Understanding WCAG 2.1 docs still incorrectly say WCAG 2.0 w3c/wcag#1068 (5 comments by @guyhickling, @patrickhlauke, @yatil)
-
Bad/incomplete example for Understanding 3.3.2 w3c/wcag#755 (5 comments by @alastc, @innoticFR, @patrickhlauke)
-
Use entity "ratio" for contrast ratio "3:1" statements w3c/wcag#1117 (4 comments by @detlevhfischer, @patrickhlauke)
-
Potential failure techniques (or at least checks) for Text Spacing? w3c/wcag#683 (4 comments by @mbgower, @mraccess77, @nitedog)
-
Does the help have to be accessible? w3c/wcag#1237 (3 comments by @alastc, @guyhickling, @JAWS-test)
-
Language of 1.4.10/Reflow exception seems broader than intended w3c/wcag#1049 (3 comments by @alastc, @mbgower, @smhigley)
-
Understanding doc contradicts SC2.4.5 Multiple ways w3c/wcag#1077 (3 comments by @mraccess77, @patrickhlauke)
-
2.4.7 Focus Visible: WCAG 2.1 Understanding has wrong level (A instead of AA) w3c/wcag#1178 (3 comments by @alastc, @guyhickling, @yatil)
-
the Log example reads entire conversation from the top every time a line is added w3c/wcag#1186 (3 comments by @DavidMacDonald, @JAWS-test)
-
Include mobile apps in SC3.2.6 Findable Help w3c/wcag#1244 (2 comments by @guyhickling, @patrickhlauke)
-
Loophole in SC2.4.11 allows almost invisible focus indicators w3c/wcag#1156 (2 comments by @alastc, @scha14)
-
Challenges: Guideline 1.4.4 and Adaptive Design w3c/wcag#1222 (2 comments by @guyhickling, @patrickhlauke)
-
Technique H64 interpreted as 4.1.2 requiring descriptive accessible name? w3c/wcag#929 (2 comments by @awkawk, @mraccess77)
-
Inconsistent SCs that use "media alternative" in Guideline 1.2 w3c/wcag#796 (2 comments by @bruce-usab, @mbgower)
-
labelled navigation landmarks should be added to sufficient techniques for 2.4.4 w3c/wcag#619 (1 comment by @alastc)
-
Flash1: Graphic showing how to create accessible name in Flash has no accessible name w3c/wcag#1139 (1 comment by @dd8)
-
Understanding SC 1.4.11: "that indicator it must meet" (editorial) w3c/wcag#1219 (1 comment by @scha14)
-
2.4.11 Focus Visible (Enhanced) - what counts as "bounding rectangle"/"bounding box" w3c/wcag#1075 (1 comment by @scha14)
-
Should techniques for minimum contrast recommend alternate versions? w3c/wcag#1176 (1 comment by @gundulaniemann)
-
1.4.13 Content on Hover or Focus - dismissable and persistent clarification w3c/wcag#914 (1 comment by @idoros)
-
-
16 pull requests opened.
-
Versioning w3c/wcag#1240, by @michael-n-cooper.
-
Adding sentence to reflow note. #1049 w3c/wcag#1238, by @alastc.
-
Duplicate of G18.html using correct maths w3c/wcag#1223, by @bruce-usab.
-
Issue 1219 non-text-contrast.html typo fix w3c/wcag#1220, by @scha14.
-
1.3.4 - added exception for two-value fields w3c/wcag#1217, by @detlevhfischer.
-
1.3.4-exception for two value fields w3c/wcag#1216, by @detlevhfischer.
-
Reflow for table cells - Addressing 1129 w3c/wcag#1215, by @alastc.
-
Clarify title of Failure F108 w3c/wcag#1211, by @detlevhfischer.
-
Issue #101 on 3.3.2 labels w3c/wcag#1205, by @alastc.
-
Adding fstorr's updates - border note in focus-vis w3c/wcag#1204, by @alastc.
-
changes to Reflow note and Understanding w3c/wcag#1201, by @mbgower.
-
fstorr focus visible enhanced border note w3c/wcag#1200, by @fstrr.
-
Wcag22 focus visible enh updates 1067 w3c/wcag#1198, by @alastc.
-
Fix link to `prefers-reduced-motion` working example w3c/wcag#1192, by @patrickhlauke.
-
-
11 pull requests merged.
-
Reflow for table cells - Addressing 1129 w3c/wcag#1215.
-
Adding sentence to reflow note. #1049 w3c/wcag#1238.
-
Adding fstorr's updates - border note in focus-vis w3c/wcag#1204.
-
1.3.4 - added exception for two-value fields w3c/wcag#1217.
-
WCAG 2.2 Pointer Target Spacing w3c/wcag#1179.
-
WCAG 2.2 Redundant entry w3c/wcag#1046.
-
WCAG 2.2 - Fixed reference points draft w3c/wcag#1161.
-
WCAG 2.2 Hidden Controls w3c/wcag#1127.
-
Findable Help w3c/wcag#1158.
-
1.3.4-exception for two value fields w3c/wcag#1216.
-
Fix link to `prefers-reduced-motion` working example w3c/wcag#1192.
-
-
1 pull request closed.
-
fstorr focus visible enhanced border note w3c/wcag#1200.
-
-
10 pull requests received 26 new comments.
-
WCAG 2.2 Pointer Target Spacing w3c/wcag#1179 (12 comments by @alastc, @detlevhfischer, @patrickhlauke)
-
w3c/wcag-act
-
10 issues opened.
-
Resolve "iframe element has accessible name" feedback w3c/wcag-act#473, by @maryjom.
-
New rule: Object element has non-empty accessible name w3c/wcag-act#470, by @carlosapaduarte.
-
New rule: All table header cells have assigned data cells w3c/wcag-act#469, by @carlosapaduarte.
-
New rule: ARIA required owned elements w3c/wcag-act#468, by @ajanec01.
-
Resolve " Role attribute has valid value" feedback w3c/wcag-act#467, by @cpandhi.
-
Faster turnover in rule feedback w3c/wcag-act#466, by @WilcoFiers.
-
Resolve "Image has non-empty accessible name" feedback w3c/wcag-act#465, by @WilcoFiers.
-
Resolve "id attribute value is unique" feedback w3c/wcag-act#464, by @WilcoFiers.
-
Resolve "HTML page has title" feedback w3c/wcag-act#463, by @WilcoFiers.
-
Resolve "ARIA state or property is permitted" feedback w3c/wcag-act#462, by @kengdoj.
-
-
2 issues closed.
-
Resolve "Image has accessible name" feedback w3c/wcag-act#430.
-
Reviewing and publishing atomic rules used in composites w3c/wcag-act#459.
-
-
18 issues received 22 new comments.
-
Resolve "Link has non-empty accessible name" feedback w3c/wcag-act#439 (3 comments by @carlosapaduarte, @maryjom, @WilcoFiers)
-
Resolve "Button has an accessible name" feedback w3c/wcag-act#451 (2 comments by @maryjom, @WilcoFiers)
-
Resolve "Form control has accessible name" feedback w3c/wcag-act#432 (2 comments by @maryjom, @WilcoFiers)
-
New Rule: `audio` or `video` avoids automatically playing audio w3c/wcag-act#454 (1 comment by @maryjom)
-
Resolve "Orientation of the page is not restricted using CSS transform property" feedback w3c/wcag-act#445 (1 comment by @maryjom)
-
Resolve "Element with lang attribute has valid language" feedback w3c/wcag-act#431 (1 comment by @jeeyyy)
-
Reviewing and publishing atomic rules used in composites w3c/wcag-act#459 (1 comment by @WilcoFiers)
-
-
2 pull requests opened.
-
Add implementation requirements to process w3c/wcag-act#472, by @WilcoFiers.
-
Improve throughput / transparency on rule design process w3c/wcag-act#471, by @WilcoFiers.
-
-
1 pull request received 6 new comments.
-
Improve throughput / transparency on rule design process w3c/wcag-act#471 (6 comments by @kengdoj, @maryjom)
-
w3c/coga
-
7 issues opened.
-
Persona names w3c/coga#135, by @shawna-slh.
-
Review Cognitive landing page on the WAI website w3c/coga#134, by @SteveALee.
-
Update WAI Cognitive page to link to Content Usable w3c/coga#133, by @SteveALee.
-
Persona diversity w3c/coga#131, by @eschafer.
-
Glossary w3c/coga#130, by @rachaelbradley.
-
Venn Diagram Interpretation w3c/coga#129, by @charleshalldesign.
-
-
8 issues closed.
-
Update WAI Cognitive page to link to Content Usable w3c/coga#133.
-
Broken link w3c/coga#58.
-
coga-gap-analysis: keygen has been removed w3c/coga#67.
-
Duplicate bullet point w3c/coga#96.
-
Design Guide terminology w3c/coga#98.
-
Persona/index contains broken links w3c/coga#95.
-
Broken link in content usable doc w3c/coga#107.
-
-
9 issues received 12 new comments.
-
Update WAI Cognitive page to link to Content Usable w3c/coga#133 (4 comments by @lseeman, @SteveALee)
-
-
2 pull requests opened.
-
MC code fixes w3c/coga#128, by @michael-n-cooper.
-
Adds an empty Glossary document structure in W3C format into master w3c/coga#127, by @ruoxiran.
-
-
2 pull requests merged.
-
MC code fixes w3c/coga#128.
-
-
3 pull requests received 3 new comments.
-
Adds an empty Glossary document structure in W3C format into master w3c/coga#127 (1 comment by @SteveALee)
w3c/wcag3
-
2 issues received 3 new comments.
-
Future Success Criteria: Require disabled icon for disabled UI interface elements w3c/wcag3#197 (2 comments by @alastc, @patrickhlauke)
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
7 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Persona names w3c/coga#135, by @shawna-slh.
-
Review Cognitive landing page on the WAI website w3c/coga#134, by @SteveALee.
-
Update WAI Cognitive page to link to Content Usable w3c/coga#133, by @SteveALee.
-
Persona diversity w3c/coga#131, by @eschafer.
-
Glossary w3c/coga#130, by @rachaelbradley.
-
Venn Diagram Interpretation w3c/coga#129, by @charleshalldesign.
-
-
8 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Update WAI Cognitive page to link to Content Usable w3c/coga#133.
-
Broken link w3c/coga#58.
-
coga-gap-analysis: keygen has been removed w3c/coga#67.
-
Duplicate bullet point w3c/coga#96.
-
Design Guide terminology w3c/coga#98.
-
Persona/index contains broken links w3c/coga#95.
-
Broken link in content usable doc w3c/coga#107.
-
-
9 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 12 new comments.
-
Update WAI Cognitive page to link to Content Usable w3c/coga#133 (4 comments by @lseeman, @SteveALee)
-
-
2 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
MC code fixes w3c/coga#128, by @michael-n-cooper.
-
Adds an empty Glossary document structure in W3C format into master w3c/coga#127, by @ruoxiran.
-
-
2 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
MC code fixes w3c/coga#128.
-
-
3 pull requests in the Cognitive and Learning Disabilities Accessibility Task Force received 3 new comments.
-
Adds an empty Glossary document structure in W3C format into master w3c/coga#127 (1 comment by @SteveALee)
Low Vision Accessibility Task Force
Participants
-
1 chair stepped down in the Low Vision Accessibility Task Force.
-
Andrew Kirkpatrick stepped down as a chair.
-
TR publications
-
2 documents published.
Participants
-
4 participants joined.
-
Patrick Lauke (TetraLogical Services Ltd) joined.
-
Sukriti Chadha (W3C Invited Experts) joined.
-
Betsy Furler (W3C Invited Experts) joined.
-
Francesco Mariani (IBM Corporation) joined.
-
-
3 participants left.
-
Patrick Lauke (TetraLogical Services Ltd) left.
-
Keyonda Smith (W3C Invited Experts) left.
-
Andy Heath (W3C Invited Experts) left.
-
-
1 organization joined.
-
Verizon joined.
-
GitHub
w3c/wcag
-
32 issues opened.
-
ARIA24 technique does not necessarily solve the issue. w3c/wcag#1185, by @JayJune.
-
Is F4 still a failure? w3c/wcag#1184, by @dd8.
-
Should F61 also trigger 2.2.1, 2.2.4 as well as 3.2.5 ? w3c/wcag#1183, by @dd8.
-
Challenges: Test Early & Often w3c/wcag#1182, by @mgifford.
-
Does SC 1.4.3 apply to bullet points of a list? w3c/wcag#1181, by @subraumpixel.
-
I AM FIX w3c/wcag#1180, by @emmanueloe.
-
2.4.7 Focus Visible: WCAG 2.1 Understanding has unmarked WCAG 2.2 sentence w3c/wcag#1177, by @yatil.
-
Should techniques for minimum contrast recommend alternate versions? w3c/wcag#1176, by @alastc.
-
Reconsider criteria grouping for WCAG 3.0 w3c/wcag#1175, by @Dan503.
-
Challenges: Triaging Issues w3c/wcag#1172, by @mgifford.
-
Challenges: Moving Beyond the Page w3c/wcag#1171, by @mgifford.
-
Challenges: We Aren't Striking at the Root w3c/wcag#1170, by @mgifford.
-
WCAG 2.1 Understanding has WCAG 2.2 language w3c/wcag#1162, by @yatil.
-
"(Sufficient as a way to meet an unwritten technique)" is not clear w3c/wcag#1160, by @shawna-slh.
-
Loophole in SC2.4.11 allows almost invisible focus indicators w3c/wcag#1156, by @guyhickling.
-
New resources URLs on WCAG 2.1 target-size Understanding document w3c/wcag#1153, by @dotjay.
-
The working example for ARIA9 - Example 3 has problems w3c/wcag#1148, by @dd8.
-
Understanding for 2.4.3 Focus Order has contradiction w3c/wcag#1147, by @bruce-usab.
-
Plug-ins available for Technique H69 under 2.4.1 Bypass Blocks w3c/wcag#1146, by @raebened.
-
Add Obscure to 2.4.11 Focus Visible (Enhanced) w3c/wcag#1145, by @mbgower.
-
Incorrect navigation links in Understanding document w3c/wcag#1144, by @awkawk.
-
WCAG 2.1 Understanding Conformance page fails 1.3.1, 2.4.4 and 4.1.1 w3c/wcag#1141, by @dd8.
-
It is time to remove the Flash techniques w3c/wcag#1140, by @awkawk.
-
-
18 issues closed.
-
"Focus indication area" for apparent movement w3c/wcag#1059.
-
The new text for SC2.4.11: Focus Visible (Enhanced) w3c/wcag#1115.
-
Add Obscure to 2.4.11 Focus Visible (Enhanced) w3c/wcag#1145.
-
I AM FIX w3c/wcag#1180.
-
H1 at the level of an H2 in WCAG 2.2 w3c/wcag#1114.
-
Incorrect navigation links in Understanding document w3c/wcag#1144.
-
WCAG 2.1 Understanding has WCAG 2.2 language w3c/wcag#1162.
-
Reconsider criteria grouping for WCAG 3.0 w3c/wcag#1175.
-
The working example for ARIA9 - Example 3 has problems w3c/wcag#1148.
-
Changing the level of SC 2.4.7 in WCAG 2.2 w3c/wcag#1041.
-
Sticky headers/footers violation of SC 2.4.7? w3c/wcag#952.
-
42 issues received 224 new comments.
-
Add Obscure to 2.4.11 Focus Visible (Enhanced) w3c/wcag#1145 (37 comments by @alastc, @awkawk, @detlevhfischer, @JAWS-test, @mbgower, @mraccess77)
-
3.1.2 Language of parts - can single words without lang mark-up be considered a PASS? w3c/wcag#1174 (33 comments by @awkawk, @JAWS-test, @KerstinProbiesch, @MakotoUeki, @mraccess77, @patrickhlauke, @yatil)
-
Loophole in SC2.4.11 allows almost invisible focus indicators w3c/wcag#1156 (23 comments by @alastc, @guyhickling, @mbgower, @mraccess77, @patrickhlauke)
-
Failure technique F94 (1.4.4 resize text): remove "1280 pixels wide" step in test procedure w3c/wcag#704 (16 comments by @alastc, @goodwitch, @JAWS-test, @mraccess77, @patrickhlauke)
-
Link purpose (2.4.4 and 2.4.9) "ambiguous to users in general" is self-defeating w3c/wcag#1149 (15 comments by @alastc, @bruce-usab, @detlevhfischer, @Jookia, @mraccess77, @patrickhlauke)
-
Informative Techniques pages are loaded with normative RFC-2119 terms like MUST w3c/wcag#1150 (15 comments by @alastc, @awkawk, @bruce-usab, @goodwitch, @hidde, @mraccess77, @patrickhlauke)
-
WCAG 2.1 Understanding has WCAG 2.2 language w3c/wcag#1162 (12 comments by @alastc, @bruce-usab, @michael-n-cooper, @patrickhlauke, @yatil)
-
Challenges: We Aren't Striking at the Root w3c/wcag#1170 (6 comments by @JaninaSajka, @mgifford, @patrickhlauke, @WayneEDick)
-
Changing the level of SC 2.4.7 in WCAG 2.2 w3c/wcag#1041 (5 comments by @alastc, @awkawk, @bruce-usab, @guyhickling)
-
2.4.7 as it applies to static content and programmatic focus w3c/wcag#1001 (5 comments by @jrpool, @patrickhlauke)
-
Does SC 1.4.3 apply to bullet points of a list? w3c/wcag#1181 (3 comments by @JAWS-test, @subraumpixel)
-
1.4.11 Understanding: Additional focus indication of text inputs (default caret visible) w3c/wcag#1014 (3 comments by @mbgower, @mraccess77, @patrickhlauke)
-
The working example for ARIA9 - Example 3 has problems w3c/wcag#1148 (3 comments by @dd8, @detlevhfischer, @patrickhlauke)
-
Plug-ins available for Technique H69 under 2.4.1 Bypass Blocks w3c/wcag#1146 (3 comments by @alastc, @JAWS-test, @scottaohara)
-
ARIA24 technique does not necessarily solve the issue. w3c/wcag#1185 (2 comments by @JAWS-test, @mraccess77)
-
Should F61 also trigger 2.2.1, 2.2.4 as well as 3.2.5 ? w3c/wcag#1183 (2 comments by @JAWS-test, @patrickhlauke)
-
Should techniques for minimum contrast recommend alternate versions? w3c/wcag#1176 (2 comments by @detlevhfischer, @patrickhlauke)
-
Does SC 3.2.3 Consistent Navigation allow for links to be moved from one navigation group to another? w3c/wcag#1169 (2 comments by @alastc, @mraccess77)
-
WCAG 2.1 Understanding Conformance has WCAG 2.0 language, Content boxes missing(?) w3c/wcag#1168 (2 comments by @alastc, @yatil)
-
Flash1: Graphic showing how to create accessible name in Flash has no accessible name w3c/wcag#1139 (2 comments by @alastc, @dd8)
-
2.4.7 Focus Visible - explanation/understanding addition about "mode of operation"? w3c/wcag#301 (2 comments by @alastc)
-
2.4.11 checkered or dashed backgrounds can pass without being discernible w3c/wcag#1061 (1 comment by @alastc)
-
Challenges: The approach of teaching web development is not accessibility centered. w3c/wcag#1173 (1 comment by @mgifford)
-
"(Sufficient as a way to meet an unwritten technique)" is not clear w3c/wcag#1160 (1 comment by @alastc)
-
Clarify whether SC 1.3.1 requires grouped links to be in a list structure w3c/wcag#1159 (1 comment by @patrickhlauke)
-
WCAG 2.2 Focus more visible - can a visible change only in size be a failure? w3c/wcag#812 (1 comment by @alastc)
-
H53 Using the body of the object element is not practically supported w3c/wcag#1138 (1 comment by @alastc)
-
Update needed for Technique ARIA22 example "Using role=status to Provide Status Message on Shopping Cart"? w3c/wcag#1137 (1 comment by @alastc)
-
F63 shouldn't indicate use of preceding heading to meet 2.4.4 w3c/wcag#819 (1 comment by @patrickhlauke)
-
-
13 pull requests opened.
-
WCAG 2.2 Pointer Target Spacing w3c/wcag#1179, by @alastc.
-
Finding help: Changes from the CFC thread w3c/wcag#1167, by @alastc.
-
2.4.9 Understanding: Qualify Sufficient Techniques w3c/wcag#1166, by @detlevhfischer.
-
Changed pretty to straight quotes w3c/wcag#1165, by @detlevhfischer.
-
WCAG 2.2 - Fixed reference points draft w3c/wcag#1161, by @alastc.
-
Findable Help w3c/wcag#1158, by @rachaelbradley.
-
Draft of Error correction (Processes) w3c/wcag#1157, by @alastc.
-
Update target size/target size enhanced understanding resources w3c/wcag#1155, by @patrickhlauke.
-
Proposed definition for "inactive" w3c/wcag#1154, by @awkawk.
-
Updated chairs w3c/wcag#1152, by @koalie.
-
Removed "proposed" from charter w3c/wcag#1151, by @koalie.
-
Removing Flash Techniques w3c/wcag#1142, by @awkawk.
-
-
4 pull requests merged.
-
Finding help: Changes from the CFC thread w3c/wcag#1167.
-
Changed pretty to straight quotes w3c/wcag#1165.
-
Updated chairs w3c/wcag#1152.
-
-
1 pull request closed.
-
13 pull requests received 68 new comments.
-
Errata/clarification of 2.2.1 Timing Adjustable extension w3c/wcag#1040 (26 comments by @alastc, @awkawk, @bruce-usab, @mraccess77, @patrickhlauke)
-
WCAG 2.2 Pointer Target Spacing w3c/wcag#1179 (16 comments by @alastc, @detlevhfischer, @JAWS-test, @patrickhlauke, @WilcoFiers)
-
Proposed definition for "inactive" w3c/wcag#1154 (8 comments by @awkawk, @bruce-usab, @cwadamsoforacle, @patrickhlauke)
-
Update Link Purpose (in Context) understanding benefits to focus on AT w3c/wcag#1164 (2 comments by @patrickhlauke)
-
Update target size/target size enhanced understanding resources w3c/wcag#1155 (1 comment by @alastc)
-
Add clarification of "inactive" to user interface component glossary definition w3c/wcag#638 (1 comment by @patrickhlauke)
-
w3c/wcag-act
-
5 issues opened.
-
New rule: role attribute has valid value w3c/wcag-act#461, by @Jym77.
-
[reposted] How strict should our test cases be? w3c/wcag-act#460, by @WilcoFiers.
-
Reviewing and publishing atomic rules used in composites w3c/wcag-act#459, by @WilcoFiers.
-
Implementations with mostly "cantTell" results w3c/wcag-act#458, by @WilcoFiers.
-
Odd applicability because of "objective" requirement w3c/wcag-act#457, by @WilcoFiers.
-
-
6 issues closed.
-
Resolve "HTML page language is valid" feedback w3c/wcag-act#429.
-
Under Acknowledgements mention "Community Group for incubation"? w3c/wcag-act#340.
-
"accessibility requirements" does not allow for best practices w3c/wcag-act#424.
-
New rule: ARIA state or property is permitted w3c/wcag-act#453.
-
Resolve "lang and xml:lang match" feedback w3c/wcag-act#417.
-
Resolve "Image filename is accessible name for image" feedback w3c/wcag-act#447.
-
-
14 issues received 23 new comments.
-
Consistency with notes for out of scope content w3c/wcag-act#449 (6 comments by @maryjom, @tbostic32, @WilcoFiers)
-
Resolve "Link has non-empty accessible name" feedback w3c/wcag-act#439 (2 comments by @carlosapaduarte)
-
Under Acknowledgements mention "Community Group for incubation"? w3c/wcag-act#340 (1 comment by @WilcoFiers)
-
Resolve "Orientation of the page is not restricted using CSS transform property" feedback w3c/wcag-act#445 (1 comment by @kasperisager)
-
Resolving "`audio` or `video` has no audio that plays automatically" feedback w3c/wcag-act#456 (1 comment by @daniel-montalvo)
-
-
1 pull request merged.
-
editorial: fix inconsistency in accessibility requirement w3c/wcag-act#450.
-
w3c/coga
-
7 issues opened.
-
Clean up branches w3c/coga#126, by @SteveALee.
-
Delete content-usable/table.html w3c/coga#125, by @SteveALee.
-
Continue Discussion of Framing Language w3c/coga#123, by @rachaelbradley.
-
Consider dropping Appendix C and others w3c/coga#121, by @SteveALee.
-
minor copy edit suggestion w3c/coga#120, by @shawna-slh.
-
-
3 issues received 4 new comments.
-
Ensure all information from the Abstract is included in the document w3c/coga#119 (1 comment by @SteveALee)
-
1 pull request opened.
-
Edits from Wordsmithing Mega Meeting w3c/coga#124, by @rachaelbradley.
-
-
2 pull requests merged.
-
Changes from ag meeting may 2020 w3c/coga#115.
-
Edits from Wordsmithing Mega Meeting w3c/coga#124.
-
-
2 pull requests closed.
-
I made some tweaks to the Summary w3c/coga#112.
-
Responces to cfc april 2020 w3c/coga#114.
-
-
1 pull request received 2 new comments.
w3c/wcag3
-
1 issue opened.
-
We need a "Touch alternative" WCAG criteria w3c/wcag3#180, by @Dan503.
-
-
2 issues received 2 new comments.
Mobile Accessibility Task Force
Participants
-
1 participant joined the Mobile Accessibility Task Force.
-
Sukriti Chadha joined.
-
-
1 participant left the Mobile Accessibility Task Force.
-
Patrick Lauke left.
-
Accessibility Conformance Testing (ACT) Task Force
Participants
-
1 participant left the Accessibility Conformance Testing (ACT) Task Force.
-
Patrick Lauke left.
-
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 participant joined the Cognitive and Learning Disabilities Accessibility Task Force.
-
Betsy Furler joined.
-
-
1 participant left the Cognitive and Learning Disabilities Accessibility Task Force.
-
Andy Heath left.
-
GitHub
w3c/coga
-
7 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Clean up branches w3c/coga#126, by @SteveALee.
-
Delete content-usable/table.html w3c/coga#125, by @SteveALee.
-
Continue Discussion of Framing Language w3c/coga#123, by @rachaelbradley.
-
Consider dropping Appendix C and others w3c/coga#121, by @SteveALee.
-
minor copy edit suggestion w3c/coga#120, by @shawna-slh.
-
-
3 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 4 new comments.
-
Ensure all information from the Abstract is included in the document w3c/coga#119 (1 comment by @SteveALee)
-
1 pull request opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Edits from Wordsmithing Mega Meeting w3c/coga#124, by @rachaelbradley.
-
-
2 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Changes from ag meeting may 2020 w3c/coga#115.
-
Edits from Wordsmithing Mega Meeting w3c/coga#124.
-
-
2 pull requests closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
I made some tweaks to the Summary w3c/coga#112.
-
Responces to cfc april 2020 w3c/coga#114.
-
-
1 pull request in the Cognitive and Learning Disabilities Accessibility Task Force received 2 new comments.
TR publications
-
1 document published.
Participants
-
1 organization joined.
-
The Washington Post joined.
-
GitHub
w3c/wcag
-
18 issues opened.
-
H53 Using the body of the object element is not practically supported w3c/wcag#1138, by @mraccess77.
-
Should the conformance model challenges mention mitigations? w3c/wcag#1135, by @alastc.
-
css line-clamp not compliant with SC reflow, text-spacing ? w3c/wcag#1134, by @goetsu.
-
2.3.2 Three Flashes (in the wild!) - or not w3c/wcag#1132, by @detlevhfischer.
-
0.5.2 Typo error w3c/wcag#1131, by @rob212.
-
Font size used in Understanding/How to Meet links is 7.5pt w3c/wcag#1130, by @dd8.
-
1.4.10 Reflow and having more nuance for tables w3c/wcag#1129, by @patrickhlauke.
-
Question: 2.4.1 Bypass Blocks Sufficient Techniques w3c/wcag#1128, by @LaurenceRLewis.
-
Issue w3c/wcag#1126, by @Deedorsey.
-
Links in WCAG21 Techniques changelog lead to error 404 not found w3c/wcag#1125, by @detlevhfischer.
-
Visual Indicators (Affordances) w3c/wcag#1124, by @rachaelbradley.
-
unemployment w3c/wcag#1122, by @ghost.
-
No actual implementations of 2.4.9 "Link Purpose (Link Only)"? w3c/wcag#1119, by @Jookia.
-
Delete Technique G183 (hover) w3c/wcag#1118, by @guyhickling.
-
-
7 issues closed.
-
Question: 2.4.1 Bypass Blocks Sufficient Techniques w3c/wcag#1128.
-
0.5.2 Typo error w3c/wcag#1131.
-
Issue w3c/wcag#1126.
-
Focus visible not required whilst element focused w3c/wcag#1064.
-
Visual Indicators (Affordances) w3c/wcag#1124.
-
unemployment w3c/wcag#1122.
-
Focus visible for small elements with large click areas w3c/wcag#1004.
-
-
33 issues received 126 new comments.
-
Delete Technique G183 (hover) w3c/wcag#1118 (18 comments by @bruce-usab, @detlevhfischer, @guyhickling, @JAWS-test, @johnfoliot, @mraccess77, @patrickhlauke, @yatil)
-
No actual implementations of 2.4.9 "Link Purpose (Link Only)"? w3c/wcag#1119 (11 comments by @ArnaudDelafosse, @awkawk, @JAWS-test, @Jookia, @patrickhlauke)
-
1.4.10 Reflow and having more nuance for tables w3c/wcag#1129 (10 comments by @JAWS-test, @mraccess77, @patrickhlauke, @WayneEDick, @yatil)
-
2.3.2 Three Flashes (in the wild!) - or not w3c/wcag#1132 (9 comments by @detlevhfischer, @mraccess77, @patrickhlauke)
-
Sticky headers/footers violation of SC 2.4.7? w3c/wcag#952 (9 comments by @alastc, @DavidMacDonald, @JAWS-test, @mraccess77)
-
Moving phone camera over QR code a case for 2.5.4 Motion Actuation? w3c/wcag#1120 (9 comments by @detlevhfischer, @mraccess77, @patrickhlauke)
-
Why is using the title attribute a Sufficient Technique for 2.4.4 Link Purpose? w3c/wcag#1063 (6 comments by @JAWS-test, @LaurenceRLewis, @mbgower, @mraccess77)
-
css line-clamp not compliant with SC reflow, text-spacing ? w3c/wcag#1134 (5 comments by @alastc, @goetsu, @mraccess77, @patrickhlauke)
-
Focus visible not required whilst element focused w3c/wcag#1064 (5 comments by @alastc, @patrickhlauke)
-
Fail 2.5.3 Label in Name when visible label, but no accName of field is present? w3c/wcag#1133 (4 comments by @alastc, @patrickhlauke)
-
2.4.7 Focus Visible - explanation/understanding addition about "mode of operation"? w3c/wcag#301 (4 comments by @alastc, @mbgower, @patrickhlauke)
-
Text in Understanding 3.3.2 allows something functionally identical to HTML placeholder w3c/wcag#1136 (3 comments by @dd8, @patrickhlauke)
-
Feedback on Focus Visible (Enhanced): Too Much Math w3c/wcag#1053 (3 comments by @alastc, @detlevhfischer, @jake-abma)
-
Question: 2.4.1 Bypass Blocks Sufficient Techniques w3c/wcag#1128 (2 comments by @alastc, @JAWS-test)
-
Focus visible for small elements with large click areas w3c/wcag#1004 (2 comments by @alastc, @jake-abma)
-
Non-sRGB color spaces, outdated sRGB threshold, and other issues in the "relative luminance" definition w3c/wcag#360 (1 comment by @rolandog)
-
Update needed for Technique ARIA22 example "Using role=status to Provide Status Message on Shopping Cart"? w3c/wcag#1137 (1 comment by @JAWS-test)
-
Unavailable external resources in Understanding WCAG 2.0/2.1 w3c/wcag#628 (1 comment by @patrickhlauke)
-
2.4.11 checkered or dashed backgrounds can pass without being discernible w3c/wcag#1061 (1 comment by @alastc)
-
WCAG 2.1 F63 and WCAG 2.0 F63 have different test procedures w3c/wcag#1047 (1 comment by @goodwitch)
-
What does nested according to the specification mean in SC 4.1.1 w3c/wcag#978 (1 comment by @detlevhfischer)
-
1.4.13 Content on Hover or Focus - dismissable and persistent clarification w3c/wcag#914 (1 comment by @joe-watkins)
-
2.4.11 Focus Visible (Enhanced) - what counts as "bounding rectangle"/"bounding box" w3c/wcag#1075 (1 comment by @alastc)
-
2.5.2: Pointer Cancellation mentions failure for 2.5.3, editorial issue w3c/wcag#707 (1 comment by @ronsman)
-
-
2 pull requests opened.
-
WCAG 2.2 Hidden Controls w3c/wcag#1127, by @alastc.
-
WCAG22 - Focus Visible enh updates w3c/wcag#1121, by @alastc.
-
-
1 pull request merged.
-
WCAG 2.2 - Dragging SC w3c/wcag#1113.
-
-
5 pull requests received 10 new comments.
w3c/wcag-act
-
4 issues opened.
-
New rule: meta viewport does not prevent zoom w3c/wcag-act#455, by @carlosapaduarte.
-
New Rule: `audio` or `video` avoids automatically playing audio w3c/wcag-act#454, by @daniel-montalvo.
-
New rule: ARIA state or property is permitted w3c/wcag-act#453, by @Jym77.
-
3 issues closed.
-
New rule: aria-* attribute is defined in WAI-ARIA w3c/wcag-act#442.
-
New rule: id attribute value is unique w3c/wcag-act#426.
-
New rule: svg element with explicit role has accessible name w3c/wcag-act#440.
-
-
11 issues received 15 new comments.
-
Resolve "Image filename is accessible name for image" feedback w3c/wcag-act#447 (2 comments by @Jym77, @WilcoFiers)
-
Resolve "iFrame element has accessible name" feedback w3c/wcag-act#435 (2 comments by @jeeyyy, @WilcoFiers)
-
Add working example of each test case in Rules w3c/wcag-act#448 (2 comments by @kengdoj, @WilcoFiers)
-
w3c/coga
-
3 issues opened.
-
Summary headings and content w3c/coga#118, by @rachaelbradley.
-
Editorial suggestions w3c/coga#117, by @rachaelbradley.
-
Change examples to active tense w3c/coga#116, by @rachaelbradley.
-
-
2 issues received 2 new comments.
-
5 pull requests opened.
-
Changes from ag meeting may 2020 w3c/coga#115, by @rachaelbradley.
-
Responces to cfc april 2020 w3c/coga#114, by @rachaelbradley.
-
Responces to cfc april 2020 w3c/coga#113, by @rachaelbradley.
-
I made some tweaks to the Summary w3c/coga#112, by @SteveALee.
-
Suggested changes to abstract w3c/coga#111, by @SteveALee.
-
-
2 pull requests closed.
-
Responces to cfc april 2020 w3c/coga#113.
-
Suggested changes to abstract w3c/coga#111.
-
-
1 pull request reopened.
-
Suggested changes to abstract w3c/coga#111, by @SteveALee.
-
-
3 pull requests received 3 new comments.
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
3 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Summary headings and content w3c/coga#118, by @rachaelbradley.
-
Editorial suggestions w3c/coga#117, by @rachaelbradley.
-
Change examples to active tense w3c/coga#116, by @rachaelbradley.
-
-
2 issues in the Cognitive and Learning Disabilities Accessibility Task Force received 2 new comments.
-
5 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Changes from ag meeting may 2020 w3c/coga#115, by @rachaelbradley.
-
Responces to cfc april 2020 w3c/coga#114, by @rachaelbradley.
-
Responces to cfc april 2020 w3c/coga#113, by @rachaelbradley.
-
I made some tweaks to the Summary w3c/coga#112, by @SteveALee.
-
Suggested changes to abstract w3c/coga#111, by @SteveALee.
-
-
2 pull requests closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Responces to cfc april 2020 w3c/coga#113.
-
Suggested changes to abstract w3c/coga#111.
-
-
1 pull request reopened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Suggested changes to abstract w3c/coga#111, by @SteveALee.
-
-
3 pull requests in the Cognitive and Learning Disabilities Accessibility Task Force received 3 new comments.
Participants
-
3 participants joined.
-
Juan LI (Huawei) joined.
-
Omar Bonilla (ServiceNow) joined.
-
Lori Lane (University of Illinois) joined.
-
-
1 organization joined.
-
Huawei joined.
-
GitHub
w3c/wcag
-
19 issues opened.
-
Use entity "ratio" for contrast ratio "3:1" statements w3c/wcag#1117, by @alastc.
-
The new text for SC2.4.11: Focus Visible (Enhanced) w3c/wcag#1115, by @guyhickling.
-
H1 at the level of an H2 in WCAG 2.2 w3c/wcag#1114, by @Grunet.
-
Challenges: proposed clarification statement w3c/wcag#1111, by @avneeshsingh.
-
W3c w3c/wcag#1110, by @Alfian878787.
-
Not all SC have comments in Appendix A - is this deliberate? w3c/wcag#1107, by @awkawk.
-
Challenges with conformance won't really be a specification w3c/wcag#1103, by @maryjom.
-
Broken link on C39 w3c/wcag#1101, by @lauracarlson.
-
4. Robust: Duplicated "by" in sentence w3c/wcag#1098, by @anevins12.
-
2.4.4 and preceding headings as context w3c/wcag#1097, by @patrickhlauke.
-
Addition to paragraph under 3.1 w3c/wcag#1094, by @lauracarlson.
-
Conformance Challenges Goals Edit w3c/wcag#1093, by @lauracarlson.
-
-
14 issues closed.
-
Challenges: proposed clarification statement w3c/wcag#1111.
-
In WCAG Editors Draft 2.2, Change WCAG 2.0 to WCAG 2.1 w3c/wcag#1010.
-
Not all SC have comments in Appendix A - is this deliberate? w3c/wcag#1107.
-
W3c w3c/wcag#1110.
-
Challenges with conformance won't really be a specification w3c/wcag#1103.
-
Using color ALONE as focus indicator w3c/wcag#757.
-
Draft of new 2.2 SC "Dragging" w3c/wcag#835.
-
4. Robust: Duplicated "by" in sentence w3c/wcag#1098.
-
Addition to paragraph under 3.1 w3c/wcag#1094.
-
Conformance Challenges Goals Edit w3c/wcag#1093.
-
Challenges Note Challenge 4 last paragraph suggestion w3c/wcag#1092.
-
Consider Sampling Strategies as in WCAG-EM w3c/wcag#937.
-
-
26 issues received 69 new comments.
-
2.5.2 Pointer Cancellation - undo, but when (non-destructive) action happens on down event? w3c/wcag#1099 (15 comments by @alastc, @detlevhfischer, @mraccess77, @patrickhlauke)
-
Conformance Challenges Goals Edit w3c/wcag#1093 (5 comments by @guyhickling, @lauracarlson, @peterkorn, @sajkaj)
-
Formal definition of "descriptive identification" missing (SC 1.1.1) w3c/wcag#1084 (5 comments by @bruce-usab, @guyhickling, @medeaoblongata)
-
Not all SC have comments in Appendix A - is this deliberate? w3c/wcag#1107 (3 comments by @awkawk, @JaninaSajka, @peterkorn)
-
Changing the level of SC 2.4.7 in WCAG 2.2 w3c/wcag#1041 (3 comments by @alastc, @awkawk, @guyhickling)
-
Challenges Note Challenge 4 last paragraph suggestion w3c/wcag#1092 (3 comments by @peterkorn, @sajkaj)
-
Challenges with conformance won't really be a specification w3c/wcag#1103 (2 comments by @awkawk, @JaninaSajka)
-
WCAG 2.2 Focus more visible - can a visible change only in size be a failure? w3c/wcag#812 (1 comment by @alastc)
-
Modify test procedure in F91 as scope attribute on a <td> element is obsolete in HTML5 w3c/wcag#1095 (1 comment by @bruce-usab)
-
[editorial] The (WCAG 2.1) Understanding 2.4.7 doc is mentioning SC 2.4.11 of WCAG 2.2 w3c/wcag#1085 (1 comment by @guyhickling)
-
-
4 pull requests opened.
-
WCAG 2.2 - Dragging SC w3c/wcag#1113, by @alastc.
-
Updated Conformance Challenges Draft for 13 April w3c/wcag#1109, by @sajkaj.
-
Adding 'to trigger a function' to target definition w3c/wcag#1100, by @alastc.
-
Updated Conformance Challenges Draft for 3 April w3c/wcag#1096, by @sajkaj.
-
-
2 pull requests merged.
-
Updated Conformance Challenges Draft for 13 April w3c/wcag#1109.
-
Updated Conformance Challenges Draft for 3 April w3c/wcag#1096.
-
-
2 pull requests received 5 new comments.
w3c/wcag-act
-
7 issues opened.
-
Resolve "aria-* attribute is defined in WAI-ARIA" feedback w3c/wcag-act#452, by @WilcoFiers.
-
Resolve "Button has an accessible name" feedback w3c/wcag-act#451, by @maryjom.
-
Consistency with notes for out of scope content w3c/wcag-act#449, by @WilcoFiers.
-
Add working example of each test case in Rules w3c/wcag-act#448, by @kengdoj.
-
Resolve "Image filename is accessible name for image" feedback w3c/wcag-act#447, by @tbostic32.
-
Integrating ACT Rules into WCAG Supporting Documents w3c/wcag-act#446, by @nitedog.
-
-
9 issues closed.
-
New rule: Image filename is accessible name for image w3c/wcag-act#441.
-
Resolve "HTML has lang attribute" feedback w3c/wcag-act#436.
-
Look at using RDF for the ACT Rules Format w3c/wcag-act#324.
-
Add Mary Jo and Shadi as editors to WG Note w3c/wcag-act#411.
-
Discuss rule maintenance w3c/wcag-act#412.
-
Resolve "iFrame Element has Accessible Name" feedback w3c/wcag-act#428.
-
new rule: Link has accessible name w3c/wcag-act#433.
-
"acknowledgement" must be "acknowledgment" in ACT RF w3c/wcag-act#437.
-
-
16 issues received 23 new comments.
-
Resolve "iFrame element has accessible name" feedback w3c/wcag-act#435 (6 comments by @jeeyyy, @WilcoFiers)
-
Resolve "Image filename is accessible name for image" feedback w3c/wcag-act#447 (2 comments by @Jym77, @tbostic32)
-
New rule: svg element with explicit role has accessible name w3c/wcag-act#440 (1 comment by @WilcoFiers)
-
Under Acknowledgements mention "Community Group for incubation"? w3c/wcag-act#340 (1 comment by @WilcoFiers)
-
New rule: Orientation of the page is not restricted using CSS transform property w3c/wcag-act#438 (1 comment by @WilcoFiers)
-
-
1 pull request opened.
-
editorial: fix inconsistency in accessibility requirement w3c/wcag-act#450, by @WilcoFiers.
-
-
1 pull request merged.
-
Acknowledgements -> Acknowledgments w3c/wcag-act#443.
-
w3c/coga
-
3 pull requests opened.
-
Steve reordering w3c/coga#110, by @SteveALee.
-
add Rachael and lisa's changes into new branch w3c/coga#109, by @ruoxiran.
-
Structure Update w3c/coga#108, by @rachaelbradley.
-
-
2 pull requests merged.
-
add Rachael and lisa's changes into new branch w3c/coga#109.
-
Steve reordering w3c/coga#110.
-
-
1 pull request closed.
-
Structure Update w3c/coga#108.
-
-
2 pull requests received 6 new comments.
w3c/wcag3
-
1 issue opened.
-
4 issues received 17 new comments.
-
Dark mode - prefers-color-scheme w3c/wcag3#182 (7 comments by @JAWS-test, @mgifford, @patrickhlauke)
-
Contrast Ratio Math and Related Visual Issues w3c/wcag3#192 (6 comments by @alastc, @bruskowski, @jrus, @Myndex, @NateBaldwinDesign, @svgeesus)
-
Why is length of audio (1.4.2) and auto updating content (2.2.2) different? w3c/wcag3#181 (3 comments by @alastc, @bruce-usab, @Wildebrew)
-
Public Comment on 2.3.3 Animation from Interactions and prefers-reduced-motion w3c/wcag3#183 (1 comment by @guyhickling)
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
3 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Steve reordering w3c/coga#110, by @SteveALee.
-
add Rachael and lisa's changes into new branch w3c/coga#109, by @ruoxiran.
-
Structure Update w3c/coga#108, by @rachaelbradley.
-
-
2 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
add Rachael and lisa's changes into new branch w3c/coga#109.
-
Steve reordering w3c/coga#110.
-
-
1 pull request closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Structure Update w3c/coga#108.
-
-
2 pull requests in the Cognitive and Learning Disabilities Accessibility Task Force received 6 new comments.
TR publications
-
1 document published.
Participants
-
4 participants joined.
-
Daniel Montalvo (W3C) joined.
-
Isabel Holdsworth (TPGi) joined.
-
Chris Loiselle (Oracle Corporation) joined.
-
Francis Storr (Intel Corporation) joined.
-
-
2 participants left.
-
Eric Eggert (W3C) left.
-
Chris Loiselle (Oracle Corporation) left.
-
-
1 organization joined.
-
Intel Corporation joined.
-
GitHub
w3c/wcag
-
25 issues opened.
-
Challenges Note Challenge 4 last paragraph suggestion w3c/wcag#1092, by @DavidMacDonald.
-
PDF techniques page not accessible w3c/wcag#1090, by @koalie.
-
Update date is not shown w3c/wcag#1088, by @julezrulez.
-
Exception needed for 1.3.5 Identify Input Purpose w3c/wcag#1081, by @guyhickling.
-
Excepting ids and passwords from the Redundant Entry SC w3c/wcag#1080, by @guyhickling.
-
Understanding doc contradicts SC2.4.5 Multiple ways w3c/wcag#1077, by @guyhickling.
-
Public Comment on 1.3.1/1.3.3 and strikethrough w3c/wcag#1073, by @CharlesBelov.
-
Understanding WCAG 2.1 docs still incorrectly say WCAG 2.0 w3c/wcag#1068, by @patrickhlauke.
-
2.4.11 Focus Visible (Enhanced) Remove F78 and F55 w3c/wcag#1067, by @ShadowBB.
-
2.2.2 Is Play/Pause button mandatory for Carousels? w3c/wcag#1066, by @mkkwon.
-
Focus visible not required whilst element focused w3c/wcag#1064, by @alastc.
-
"Focus indication area" for apparent movement w3c/wcag#1059, by @JasonAment.
-
-
11 issues closed.
-
Possible 1.4.1 failure in WCAG 2.1 normative document w3c/wcag#1048.
-
Excepting ids and passwords from the Redundant Entry SC w3c/wcag#1080.
-
Participant list needs to be updated w3c/wcag#955.
-
Public Comment on 1.3.1/1.3.3 and strikethrough w3c/wcag#1073.
-
2.4.11 Focus Visible (Enhanced) Add user agent exception w3c/wcag#1057.
-
2.2.2 Is Play/Pause button mandatory for Carousels? w3c/wcag#1066.
-
-
38 issues received 220 new comments.
-
Change 1.4.10 Reflow to level A w3c/wcag#1050 (37 comments by @alastc, @guyhickling, @JAWS-test, @mraccess77, @smhigley, @WayneEDick)
-
Cases where more than one "Meaningful Sequence" is required for total meaning w3c/wcag#1062 (14 comments by @aarongustafson, @bruce-usab, @JAWS-test, @medeaoblongata, @mraccess77, @patrickhlauke)
-
1.4.1: Use of Color - understanding document needs to be clear if it's about "visual" or more w3c/wcag#1076 (12 comments by @JAWS-test, @mraccess77, @patrickhlauke)
-
Focus visible not required whilst element focused w3c/wcag#1064 (11 comments by @alastc, @awkawk, @cstrobbe, @JAWS-test, @patrickhlauke)
-
1.4.11 Understanding: Additional focus indication of text inputs (default caret visible) w3c/wcag#1014 (10 comments by @alastc, @detlevhfischer, @mraccess77, @patrickhlauke)
-
Feedback on Focus Visible (Enhanced): Too Much Math w3c/wcag#1053 (8 comments by @alastc, @guyhickling)
-
2.4.11 Focus Visible (Enhanced) Remove F78 and F55 w3c/wcag#1067 (8 comments by @alastc, @awkawk, @guyhickling, @mraccess77, @patrickhlauke)
-
Why is using the title attribute a Sufficient Technique for 2.4.4 Link Purpose? w3c/wcag#1063 (8 comments by @JAWS-test, @LaurenceRLewis, @mraccess77)
-
2.4.11 Focus Visible (Enhanced) - what counts as "bounding rectangle"/"bounding box" w3c/wcag#1075 (7 comments by @alastc, @detlevhfischer, @patrickhlauke)
-
Excepting ids and passwords from the Redundant Entry SC w3c/wcag#1080 (6 comments by @alastc, @guyhickling, @patrickhlauke)
-
Grammar and clarity of SC2.4.11 Focus Visible (Enhanced) w3c/wcag#1055 (6 comments by @alastc, @guyhickling, @KerstinProbiesch)
-
Public Comment on 1.3.1/1.3.3 and strikethrough w3c/wcag#1073 (6 comments by @CharlesBelov, @guyhickling, @JAWS-test, @mraccess77)
-
Expand 1.4.10 to apply 'down to' instead of 'at' w3c/wcag#698 (5 comments by @alastc, @guyhickling, @WayneEDick)
-
Intent vs. Benefits and conformance (with SC 1.2.3 and SC 1.2.5) w3c/wcag#1042 (5 comments by @alastc, @medeaoblongata)
-
4.1.1 Parsing - Exception for custom attributes other than data-*? w3c/wcag#1078 (5 comments by @alastc, @patrickhlauke, @stevefaulkner)
-
2.4.11 Focus Visible (Enhanced) Add user agent exception w3c/wcag#1057 (5 comments by @alastc, @guyhickling, @robfentress)
-
Applicability of 2.5.3 Label in Name when no label is present (or just placeholder) w3c/wcag#855 (4 comments by @JAWS-test, @kantoche, @patrickhlauke)
-
Exception needed for 1.3.5 Identify Input Purpose w3c/wcag#1081 (4 comments by @alastc, @patrickhlauke)
-
2.4.11 Focus Visible (Enhanced) Outline Offset Success Criterion w3c/wcag#1056 (4 comments by @alastc, @dbseagull, @ghost)
-
2.4.11 checkered or dashed backgrounds can pass without being discernible w3c/wcag#1061 (4 comments by @alastc, @JasonAment, @JAWS-test)
-
Possible 1.4.1 failure in WCAG 2.1 normative document w3c/wcag#1048 (2 comments by @alastc, @michael-n-cooper)
-
Understanding doc contradicts SC2.4.5 Multiple ways w3c/wcag#1077 (2 comments by @detlevhfischer, @patrickhlauke)
-
`<blockquote ... data-include="...">` not processed in Understanding 2.1 conformance w3c/wcag#1069 (2 comments by @alastc, @patrickhlauke)
-
2.4.11 Focus Visible (enhanced) is included in the 2.1 Understanding Documentation w3c/wcag#1054 (2 comments by @alastc, @patrickhlauke)
-
Non-sRGB color spaces, outdated sRGB threshold, and other issues in the "relative luminance" definition w3c/wcag#360 (1 comment by @svgeesus)
-
Potential failure techniques (or at least checks) for Text Spacing? w3c/wcag#683 (1 comment by @nitedog)
-
Formal definition of "descriptive identification" missing (SC 1.1.1) w3c/wcag#1084 (1 comment by @bruce-usab)
-
WCAG 2.2: "Focus visible (enhance)" link should be "Focus visible (enhanced)" w3c/wcag#1060 (1 comment by @alastc)
-
-
7 pull requests opened.
-
Updated Conformance Challenges Draft for 31 March w3c/wcag#1089, by @sajkaj.
-
Mc challenges tone w3c/wcag#1086, by @michael-n-cooper.
-
Mc challenges tone w3c/wcag#1083, by @michael-n-cooper.
-
Updated Conformance Challenges Draft for 17 March w3c/wcag#1082, by @sajkaj.
-
Updated Draft of Conformance challenges for FPWD re-review w3c/wcag#1079, by @sajkaj.
-
Status message added to 2.4.11 w3c/wcag#1071, by @alastc.
-
Changes to examples in Understanding 1.4.11 w3c/wcag#1065, by @patrickhlauke.
-
-
6 pull requests merged.
-
WCAG 2.2 SC - Accessible Authentication w3c/wcag#1037.
-
Updated Conformance Challenges Draft for 31 March w3c/wcag#1089.
-
Underline links in the head of the spec. w3c/wcag#1052.
-
Updated Conformance Challenges Draft for 17 March w3c/wcag#1082.
-
Updated Draft of Conformance challenges for FPWD re-review w3c/wcag#1079.
-
Status message added to 2.4.11 w3c/wcag#1071.
-
-
2 pull requests closed.
-
Mc challenges tone w3c/wcag#1086.
-
Mc challenges tone w3c/wcag#1083.
-
-
7 pull requests received 32 new comments.
-
WCAG 2.2 SC - Accessible Authentication w3c/wcag#1037 (10 comments by @alastc, @cookiecrook, @patrickhlauke)
-
Underline links in the head of the spec. w3c/wcag#1052 (4 comments by @alastc, @awkawk, @michael-n-cooper)
-
Add clarification of "inactive" to user interface component glossary definition w3c/wcag#638 (2 comments by @MelSumner, @mraccess77)
-
Remove misleading/incorrect statement from 1.4.11 understanding w3c/wcag#1058 (2 comments by @bruce-usab, @patrickhlauke)
-
w3c/wcag-act
-
7 issues opened.
-
New Rule: `audio` or `video` has no audio that plays automatically w3c/wcag-act#444, by @daniel-montalvo.
-
New rule: aria-* attribute is defined in WAI-ARIA w3c/wcag-act#442, by @jeeyyy.
-
New rule: Image filename is accessible name for image w3c/wcag-act#441, by @carlosapaduarte.
-
New rule: svg element with explicit role has accessible name w3c/wcag-act#440, by @Jym77.
-
Resolve "Link has non-empty accessible name" feedback w3c/wcag-act#439, by @kasperisager.
-
"acknowledgement" must be "acknowledgment" in ACT RF w3c/wcag-act#437, by @WilcoFiers.
-
-
4 issues closed.
-
Resolve "Button has accessible name" feedback w3c/wcag-act#427.
-
New Rule: `audio` or `video` has no audio that plays automatically w3c/wcag-act#444.
-
Resolve "HTML has lang attribute" feedback w3c/wcag-act#419.
-
Question: Duplicate link text in the title attribute w3c/wcag-act#434.
-
-
1 issue received 1 new comment.
-
Question: Duplicate link text in the title attribute w3c/wcag-act#434 (1 comment by @LaurenceRLewis)
-
-
1 pull request opened.
-
Acknowledgements -> Acknowledgments w3c/wcag-act#443, by @nitedog.
-
w3c/coga
-
1 issue opened.
-
Broken link in content usable doc w3c/coga#107, by @ruoxiran.
-
-
2 pull requests opened.
-
Pre csun 2020 ready for release w3c/coga#106, by @SteveALee.
-
Steve misc updates w3c/coga#105, by @SteveALee.
-
-
3 pull requests merged.
-
Pre csun 2020 ready for release w3c/coga#106.
-
Steve misc updates w3c/coga#105.
-
Add user stories w3c/coga#104.
-
-
3 pull requests received 11 new comments.
w3c/wcag3
-
2 issues opened.
-
Dark mode - prefers-color-scheme w3c/wcag3#182, by @mgifford.
-
-
4 issues received 21 new comments.
-
Public Comment on 2.3.3 Animation from Interactions and prefers-reduced-motion w3c/wcag3#183 (14 comments by @alastc, @CharlesBelov, @guyhickling, @mgifford, @MikeElledge, @mraccess77, @patrickhlauke)
-
Contrast Ratio Math and Related Visual Issues w3c/wcag3#192 (5 comments by @bruskowski, @mrlebay, @Myndex)
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
1 issue opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Broken link in content usable doc w3c/coga#107, by @ruoxiran.
-
-
2 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Pre csun 2020 ready for release w3c/coga#106, by @SteveALee.
-
Steve misc updates w3c/coga#105, by @SteveALee.
-
-
3 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Pre csun 2020 ready for release w3c/coga#106.
-
Steve misc updates w3c/coga#105.
-
Add user stories w3c/coga#104.
-
-
3 pull requests in the Cognitive and Learning Disabilities Accessibility Task Force received 11 new comments.
TR publications
-
1 document published.
-
Web Content Accessibility Guidelines (WCAG) 2.2 published as a First Public Working Draft. History of Web Content Accessibility Guidelines (WCAG) 2.2
-
Participants
-
9 participants joined.
-
Angel Li (Alibaba Group) joined.
-
Kepeng Li (Alibaba Group) joined.
-
Angel Li (Alibaba Group) joined.
-
Pascal Wentz (SAP SE) joined.
-
Jan Williams (TPGi) joined.
-
James Craig (Apple Inc.) joined.
-
Muhammad Saleem (Green Technology Co) joined.
-
John Kirkwood (W3C Invited Experts) joined.
-
Judy Brewer (W3C) joined.
-
-
16 participants left.
-
Angel Li (Alibaba Group) left.
-
Kepeng Li (Alibaba Group) left.
-
Azad Abbasi-Ruby (Duck Duck Go, Inc.) left.
-
Muhammad Saleem (Green Technology Co) left.
-
Jesse Hausler (Salesforce) left.
-
JoAnne Juett (Salesforce) left.
-
[DUPLICATE] Mark Sadecki (Cyxtera Technologies, Inc.) left.
-
David Ashleydale (Wells Fargo Bank N.A.) left.
-
Tiphanie Walters (Wells Fargo Bank N.A.) left.
-
Mari Carmen Suarez-Figueroa (Universidad Politécnica de Madrid) left.
-
Alistair Duggin (HM Government) left.
-
Mengni Zhang (Zhejiang University) left.
-
Liangcheng Li (Zhejiang University) left.
-
WEI WANG (Zhejiang University) left.
-
Can Wang (Zhejiang University) left.
-
Judy Brewer (W3C) left.
-
-
5 organizations joined.
-
Apple Inc. joined.
-
Green Technology Co joined.
-
Oracle Corporation joined.
-
Association BrailleNet joined.
-
Dyno Mapper joined.
-
GitHub
w3c/wcag
-
20 issues opened.
-
2.4.11 Focus Visible (Enhanced) Add user agent exception w3c/wcag#1057, by @robfentress.
-
2.4.11 Focus Visible (Enhanced) Outline Offset Success Criterion w3c/wcag#1056, by @ghost.
-
Grammar and clarity of SC2.4.11 Focus Visible (Enhanced) w3c/wcag#1055, by @guyhickling.
-
Feedback on Focus Visible (Enhanced): Too Much Math w3c/wcag#1053, by @scsporie.
-
Change 1.4.10 Reflow to level A w3c/wcag#1050, by @alastc.
-
Language of 1.4.10/Reflow exception seems broader than intended w3c/wcag#1049, by @smhigley.
-
Possible 1.4.1 failure in WCAG 2.1 normative document w3c/wcag#1048, by @WilcoFiers.
-
WCAG 2.1 F63 and WCAG 2.0 F63 have different test procedures w3c/wcag#1047, by @dd8.
-
Wrong examples in F69 - Failure of Success Criterion 1.4.4? w3c/wcag#1044, by @mucsi96.
-
Left navigation SC links for 2.4.7 through 2.4.10 are incorrect w3c/wcag#1043, by @lamador.
-
Intent vs. Benefits and conformance (with SC 1.2.3 and SC 1.2.5) w3c/wcag#1042, by @medeaoblongata.
-
Changing the level of SC 2.4.7 in WCAG 2.2 w3c/wcag#1041, by @WilcoFiers.
-
Invalid language code used in G101 example 7 w3c/wcag#1039, by @dd8.
-
WCAG 2.2 focus visible enhanced contrast seems to leave gap? w3c/wcag#1038, by @patrickhlauke.
-
Retiring technique H59 Using the link element and navigation tools w3c/wcag#1036, by @patrickhlauke.
-
Note and benefits contradict each other in 1.4.1 (Use of color) w3c/wcag#1032, by @JAWS-test.
-
Spatial Navigation to Bypass Blocks w3c/wcag#1030, by @Malvoz.
-
[Editorial] "Text Alternatives" reference w3c/wcag#1029, by @Malvoz.
-
-
15 issues closed.
-
UAAG requirements relevant for WCAG 2.2? w3c/wcag#1013.
-
Link in 2.1 failing F73 w3c/wcag#562.
-
Testing of events with JS w3c/wcag#995.
-
Who should handle text spacing? w3c/wcag#946.
-
SC 1.3.5 isn't a challenge for non-web technologies w3c/wcag#954.
-
Users Don't See Partially Constructed Web Content w3c/wcag#941.
-
Add WCAG-EM / ATAG reference w3c/wcag#1000.
-
Is this a testability or conformance challenge? w3c/wcag#940.
-
Wrong examples in F69 - Failure of Success Criterion 1.4.4? w3c/wcag#1044.
-
Invalid language code used in G101 example 7 w3c/wcag#1039.
-
40 issues received 148 new comments.
-
Change 1.4.10 Reflow to level A w3c/wcag#1050 (22 comments by @alastc, @bruce-usab, @guyhickling, @JAWS-test, @mraccess77, @patrickhlauke, @smhigley, @WilcoFiers)
-
Changing the level of SC 2.4.7 in WCAG 2.2 w3c/wcag#1041 (22 comments by @alastc, @bruce-usab, @gilluminate, @guyhickling, @jake-abma, @jared-w-smith, @JAWS-test, @johnfoliot, @mraccess77, @patrickhlauke, @WilcoFiers)
-
WCAG 2.2 focus visible enhanced contrast seems to leave gap? w3c/wcag#1038 (19 comments by @alastc, @AutoSponge, @jake-abma, @JAWS-test, @patrickhlauke)
-
WCAG 2.1 F63 and WCAG 2.0 F63 have different test procedures w3c/wcag#1047 (13 comments by @alastc, @awkawk, @dd8, @JAWS-test, @mraccess77)
-
1.4.13 Content on Hover or Focus - dismissable and persistent clarification w3c/wcag#914 (10 comments by @alastc, @RobGallo, @smhigley)
-
Left navigation SC links for 2.4.7 through 2.4.10 are incorrect w3c/wcag#1043 (7 comments by @alastc, @JAWS-test, @michael-n-cooper, @patrickhlauke)
-
Language of 1.4.10/Reflow exception seems broader than intended w3c/wcag#1049 (4 comments by @alastc, @patrickhlauke, @smhigley)
-
Possible 1.4.1 failure in WCAG 2.1 normative document w3c/wcag#1048 (3 comments by @alastc, @awkawk)
-
Intent vs. Benefits and conformance (with SC 1.2.3 and SC 1.2.5) w3c/wcag#1042 (3 comments by @alastc, @medeaoblongata, @patrickhlauke)
-
Does SC 1.4.11 require comparing focused and non-focused states w3c/wcag#541 (2 comments by @mraccess77, @patrickhlauke)
-
Feedback on Focus Visible (Enhanced): Too Much Math w3c/wcag#1053 (2 comments by @guyhickling, @JAWS-test)
-
Understanding Success Criterion 1.2.2: Captions (Prerecorded) (e.g., for images) w3c/wcag#1051 (2 comments by @JAWS-test, @LaurenceRLewis)
-
2.4.11 Focus Visible (Enhanced) Outline Offset Success Criterion w3c/wcag#1056 (1 comment by @JAWS-test)
-
2.4.11 Focus Visible (enhanced) is included in the 2.1 Understanding Documentation w3c/wcag#1054 (1 comment by @patrickhlauke)
-
Language for 1.13 Reflow challenges (SC 1.4.10) needs more description. w3c/wcag#960 (1 comment by @sajkaj)
-
Automatic testing makes less sense than expected (using SC 1.4.3 as an example) w3c/wcag#998 (1 comment by @sajkaj)
-
Bookmarklet for testing character key shortcuts (SC 2.1.4) w3c/wcag#833 (1 comment by @patrickhlauke)
-
Retiring technique H59 Using the link element and navigation tools w3c/wcag#1036 (1 comment by @alanfluff)
-
Note and benefits contradict each other in 1.4.1 (Use of color) w3c/wcag#1032 (1 comment by @patrickhlauke)
-
-
10 pull requests opened.
-
Remove misleading/incorrect statement from 1.4.11 understanding w3c/wcag#1058, by @patrickhlauke.
-
Underline links in the head of the spec. w3c/wcag#1052, by @alastc.
-
WCAG 2.2 Redundant entry w3c/wcag#1046, by @alastc.
-
Updated Draft of Conformance challenges for FPWD re-review w3c/wcag#1045, by @sajkaj.
-
Errata/clarification of 2.2.1 Timing Adjustable extension w3c/wcag#1040, by @patrickhlauke.
-
WCAG 2.2 SC - Accessible Authentication w3c/wcag#1037, by @alastc.
-
Update F3 w3c/wcag#1035, by @JAWS-test.
-
Update F87 w3c/wcag#1034, by @JAWS-test.
-
Update F81 w3c/wcag#1033, by @JAWS-test2.
-
Update link in definition of text alternatives w3c/wcag#1031, by @JAWS-test2.
-
-
2 pull requests merged.
-
Updated Draft of Conformance challenges for FPWD re-review w3c/wcag#1045.
-
Some wcag 2 / 2.2 term tweaks in intro w3c/wcag#1027.
-
-
8 pull requests received 51 new comments.
-
Errata/clarification of 2.2.1 Timing Adjustable extension w3c/wcag#1040 (32 comments by @bruce-usab, @DavidMacDonald, @jake-abma, @JAWS-test, @JAWS-test2, @patrickhlauke, @yatil)
-
WCAG 2.2 SC - Accessible Authentication w3c/wcag#1037 (10 comments by @alastc, @lauracarlson, @patrickhlauke)
-
Remove misleading/incorrect statement from 1.4.11 understanding w3c/wcag#1058 (1 comment by @patrickhlauke)
-
w3c/coga
-
4 pull requests opened.
-
Add user stories w3c/coga#104, by @SteveALee.
-
Edits to patterns jan 2020 w3c/coga#103, by @rachaelbradley.
-
Restructrue w3c/coga#102, by @ruoxiran.
-
Persona edits w3c/coga#101, by @SteveALee.
-
-
3 pull requests merged.
-
Edits to patterns jan 2020 w3c/coga#103.
-
Restructrue w3c/coga#102.
-
Persona edits w3c/coga#101.
-
w3c/wcag-act
-
8 issues opened.
-
Resolve "HTML has lang attribute" feedback w3c/wcag-act#436, by @maryjom.
-
Resolve "iFrame element has accessible name" feedback w3c/wcag-act#435, by @maryjom.
-
Question: Duplicate link text in the title attribute w3c/wcag-act#434, by @LaurenceRLewis.
-
new rule: Link has accessible name w3c/wcag-act#433, by @WilcoFiers.
-
Resolve "Form control has accessible name" feedback w3c/wcag-act#432, by @maryjom.
-
Resolve "Element with lang attribute has valid language" feedback w3c/wcag-act#431, by @kengdoj.
-
Resolve "Image has accessible name" feedback w3c/wcag-act#430, by @WilcoFiers.
-
Resolve "HTML page language is valid" feedback w3c/wcag-act#429, by @kengdoj.
-
-
6 issues received 12 new comments.
-
Resolve "lang and xml:lang match" feedback w3c/wcag-act#417 (3 comments by @jeeyyy, @Jym77, @kasperisager)
-
1 pull request merged.
-
Add the "liaison" role to review process w3c/wcag-act#425.
-
w3c/wcag3
-
2 issues received 15 new comments.
-
Contrast Ratio Math and Related Visual Issues w3c/wcag3#192 (10 comments by @bruce-usab, @jrus, @Myndex)
-
New SC for keyboard operation? w3c/wcag3#188 (5 comments by @JAWS-test, @mraccess77, @patrickhlauke)
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
4 pull requests opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Add user stories w3c/coga#104, by @SteveALee.
-
Edits to patterns jan 2020 w3c/coga#103, by @rachaelbradley.
-
Restructrue w3c/coga#102, by @ruoxiran.
-
Persona edits w3c/coga#101, by @SteveALee.
-
-
3 pull requests merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Edits to patterns jan 2020 w3c/coga#103.
-
Restructrue w3c/coga#102.
-
Persona edits w3c/coga#101.
-
Participants
-
5 participants joined.
-
Alexandra Grossi (IBM Corporation) joined.
-
Monica Wegner (Thomson Reuters Corp.) joined.
-
Gregorio Pellegrino (Fondazione LIA) joined.
-
Cristina Mussinelli (Fondazione LIA) joined.
-
Charles Hall (W3C Invited Experts) joined.
-
-
1 participant left.
-
John Kirkwood (W3C Invited Experts) left.
-
-
23 organizations joined.
-
Microsoft Corporation joined.
-
SAP SE joined.
-
Google LLC joined.
-
Macmillan Learning joined.
-
University of Illinois joined.
-
IBM Corporation joined.
-
Amazon joined.
-
NIC.br - Brazilian Network Information Center joined.
-
BarrierBreak Solutions Private Limited joined.
-
MITRE Corporation joined.
-
Fondazione LIA joined.
-
Royal National Institute of Blind People (RNIB) joined.
-
AbleDocs joined.
-
Pearson plc joined.
-
University of Southampton joined.
-
Siteimprove joined.
-
eyeo GmbH joined.
-
TPGi joined.
-
Alibaba Group joined.
-
Search Engine Optimization Inc joined.
-
Mada Center, Qatar joined.
-
AccessibilityOz joined.
-
Thomson Reuters Corp. joined.
-
GitHub
w3c/wcag
-
12 issues opened.
-
UAAG requirements relevant for WCAG 2.2? w3c/wcag#1013, by @JAWS-test.
-
Minor grammar typo in 1.3.4 Orientation - Understanding w3c/wcag#1011, by @mitchellevan.
-
In WCAG Editors Draft 2.2, Change WCAG 2.0 to WCAG 2.1 w3c/wcag#1010, by @jake-abma.
-
What does "accessibility-supported" mean? w3c/wcag#1009, by @JAWS-test.
-
Concern about SC 2.1.4 in WCAG 2.1 w3c/wcag#1008, by @spanchang.
-
F87 and custom-styled form controls w3c/wcag#1007, by @JamesCatt.
-
H44: Radio button label positioning w3c/wcag#1005, by @standardspace.
-
Focus visible for small elements with large click areas w3c/wcag#1004, by @alastc.
-
Focus visible using fixed size indicators w3c/wcag#1003, by @alastc.
-
8 issues closed.
-
Minor grammar typo in 1.3.4 Orientation - Understanding w3c/wcag#1011.
-
Confirming 3rd bullet of Character Key Shortcuts w3c/wcag#844.
-
1.4.11: please list color values with examples w3c/wcag#917.
-
-
20 issues received 98 new comments.
-
2.4.7 as it applies to static content and programmatic focus w3c/wcag#1001 (27 comments by @alastc, @awkawk, @JAWS-test, @mfairchild365, @mraccess77, @patrickhlauke)
-
F87 and custom-styled form controls w3c/wcag#1007 (15 comments by @alastc, @awkawk, @JamesCatt, @JAWS-test, @patrickhlauke)
-
H44: Radio button label positioning w3c/wcag#1005 (11 comments by @alastc, @awkawk, @JAWS-test, @standardspace)
-
Focus visible using fixed size indicators w3c/wcag#1003 (10 comments by @alastc, @jake-abma, @JAWS-test)
-
What does "accessibility-supported" mean? w3c/wcag#1009 (10 comments by @alastc, @jake-abma, @JAWS-test, @patrickhlauke, @peterkorn, @WilcoFiers)
-
Focus visible for small elements with large click areas w3c/wcag#1004 (6 comments by @alastc, @detlevhfischer, @jake-abma, @mraccess77)
-
WCAG Technique H58 wording is not consistent with BCP 47 which does not talk about "primary code" w3c/wcag#1028 (3 comments by @awkawk, @WilcoFiers)
-
Can browser dev tools > device toggle be used to test SC 1.4.10 Reflow w3c/wcag#520 (3 comments by @alastc, @JAWS-test2)
-
Automatic testing makes less sense than expected (using SC 1.4.3 as an example) w3c/wcag#998 (2 comments by @alastc, @rg-viza)
-
Wanted to confirm my understanding as SC 1.4.11 applies to hover w3c/wcag#896 (1 comment by @alastc)
-
Structure of 1.4.11 Non-Text-Contrast Understanding inconsistent with existing formatting w3c/wcag#903 (1 comment by @alastc)
-
-
14 pull requests opened.
-
Some wcag 2 / 2.2 term tweaks in intro w3c/wcag#1027, by @alastc.
-
Update definition "changes of context" w3c/wcag#1026, by @JAWS-test2.
-
Update reference link in Understanding of SC 2.4.2 (Page Titled) w3c/wcag#1025, by @JAWS-test2.
-
Update G206 to explicitly reference 1.4.8 / 1.4.10 w3c/wcag#1024, by @JAWS-test2.
-
Update ARIA11 w3c/wcag#1023, by @JAWS-test2.
-
Update Understanding "focus visible" (SC 2.4.7) w3c/wcag#1022, by @JAWS-test2.
-
Update F103 to remove progressbar as it's not an implicit live region w3c/wcag#1021, by @JAWS-test2.
-
Understanding Use of Color (SC 1.4.1) w3c/wcag#1020, by @JAWS-test2.
-
Outdated link in ARIA19 w3c/wcag#1019, by @JAWS-test2.
-
Update term "contrast ratio" for SC 1.4.11 w3c/wcag#1018, by @JAWS-test2.
-
Update Understanding On Input (SC 3.2.2) w3c/wcag#1017, by @JAWS-test2.
-
Update Working Example ARIA24 w3c/wcag#1016, by @JAWS-test2.
-
Update Working Example ARIA24 w3c/wcag#1015, by @JAWS-test.
-
Add research to acceptance criteria w3c/wcag#1006, by @michael-n-cooper.
-
-
3 pull requests merged.
-
Add research to acceptance criteria w3c/wcag#1006.
-
WCAG22 - focus visible enhanced w3c/wcag#936.
-
Non text contrast updates w3c/wcag#931.
-
-
2 pull requests closed.
-
Update Working Example ARIA24 w3c/wcag#1015.
-
*minor* fix and suggestion w3c/wcag#859.
-
-
3 pull requests received 5 new comments.
w3c/wcag-act
-
3 issues opened.
-
Resolve "iFrame Element has Accessible Name" feedback w3c/wcag-act#428, by @maryjom.
-
Resolve "Button has accessible name" feedback w3c/wcag-act#427, by @kasperisager.
-
New rule: id attribute value is unique w3c/wcag-act#426, by @WilcoFiers.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Add the "liaison" role to review process w3c/wcag-act#425, by @WilcoFiers.
-
-
2 pull requests merged.
-
Create w3c-ruleset-review-process.md w3c/wcag-act#414.
-
Update wcag-ruleset-review-process.md w3c/wcag-act#418.
-
w3c/coga
-
1 pull request opened.
-
Edits to patterns jan 2020 w3c/coga#100, by @lseeman.
-
-
1 pull request merged.
-
Edits to patterns jan 2020 w3c/coga#100.
-
w3c/wcag3
-
1 issue received 3 new comments.
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
1 pull request opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Edits to patterns jan 2020 w3c/coga#100, by @lseeman.
-
-
1 pull request merged in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Edits to patterns jan 2020 w3c/coga#100.
-