Accessibility Guidelines Working Group - Activity
No matches.
Past meetings
Participants
-
3 participants joined.
-
Geraint White (W3C Invited Experts) joined.
-
Mitchell Evan (W3C Invited Experts) joined.
-
Jane Berliss-Vincent (W3C Invited Experts) joined.
-
-
4 participants left.
-
Ryan Romaine (Google LLC) left.
-
Bryan Trogdon (Google LLC) left.
-
Jeffrey Yasskin (Google LLC) left.
-
Elizabeth Patrick (Wix.com Ltd.) left.
-
GitHub
w3c/wcag
-
13 issues opened.
-
0552678618 w3c/wcag#5412, by @suuzuali022-gif.
-
[spam] w3c/wcag#5410, by @vovanhieu925-star.
-
[spam] w3c/wcag#5406, by @lardinroselia932-lab.
-
[spam] w3c/wcag#5405, by @tuhinbond9-svg.
-
[spam] w3c/wcag#5400, by @umahr086-dot.
-
[spam] w3c/wcag#5398, by @ccgxcjig-create.
-
[spam] w3c/wcag#5397, by @nutasdoo112-prog.
-
Broken links w3c/wcag#5392, by @Eric-Kadaster.
-
Pointer activation indicated (enhanced) w3c/wcag#5389, by @fstrr.
-
Pointer activation indicated (minimum) w3c/wcag#5388, by @fstrr.
-
Focus indicator style guide w3c/wcag#5387, by @fstrr.
-
-
16 issues closed.
-
[spam] w3c/wcag#5412.
-
[spam] w3c/wcag#5410.
-
[spam] w3c/wcag#5406.
-
[spam] w3c/wcag#5405.
-
[spam] w3c/wcag#5400.
-
[spam] w3c/wcag#5398.
-
[spam] w3c/wcag#5397.
-
What is considered 'functionality' in 1.4.10 Reflow w3c/wcag#5320.
-
Broken links w3c/wcag#5392.
-
Must focusable elements have a role? w3c/wcag#3029.
-
Examples for SC 2.1.4 too faint - difficult to discern w3c/wcag#953.
-
Focus indicator style guide w3c/wcag#5387.
-
Pointer activation indicated (minimum) w3c/wcag#5388.
-
Pointer activation indicated (enhanced) w3c/wcag#5389.
-
-
18 issues received 55 new comments.
-
Conforming Alternate Version (CAV) and the mechanism to reach/achieve it w3c/wcag#5373 (19 comments by @alastc, @bbarlach-sys, @detlevhfischer, @goetsu, @GreggVan, @innoticFR, @mraccess77, @patrickhlauke, @yatil)
-
Reiterate that 4.1.2 is scoped to states/properties *that can be set by the user* w3c/wcag#5395 (8 comments by @fstrr, @innoticFR, @patrickhlauke, @scottaohara)
-
In Understanding, replace heading “Key Terms” with “Relevant Glossary Entries” or similar w3c/wcag#5409 (6 comments by @GreggVan, @hidde, @patrickhlauke, @yatil)
-
"Are programming languages human languages?" and repercussions for text contrast requirements w3c/wcag#5369 (3 comments by @AutoSponge, @innoticFR, @wittjeff)
-
Understanding 2.5.3 - actually rendered examples but no markup examples? w3c/wcag#882 (2 comments by @fstrr, @patrickhlauke)
-
2.5.8 Understanding origin of minimum "24" w3c/wcag#4178 (2 comments by @patrickhlauke, @TanyaVanWorkum)
-
What is considered 'functionality' in 1.4.10 Reflow w3c/wcag#5320 (2 comments by @patrickhlauke, @scottaohara)
-
Consider providing examples of when controls _don't_ need labels - 3.3.2 labels or instructions w3c/wcag#4977 (2 comments by @mitchellevan)
-
1.4.5 Move the note embedded in a paragraph to the standard styling w3c/wcag#5318 (1 comment by @patrickhlauke)
-
How to determine the difference in volume for an audio file (SC 1.4.7)? w3c/wcag#1516 (1 comment by @oo-pibe)
-
-
9 pull requests opened.
-
add clarification on button indication, fix typo w3c/wcag#5411, by @fstrr.
-
Tweak two of the examples in 3.3.2 Labels or Instructions w3c/wcag#5408, by @patrickhlauke.
-
Change "correct" to "appropriate" in 4.1.2 "in brief" w3c/wcag#5407, by @patrickhlauke.
-
Tweak "programmatically determined" definition example w3c/wcag#5403, by @patrickhlauke.
-
Note for 2.5.8 Target Size (Minimum) and how 24x24 was chosen w3c/wcag#5402, by @patrickhlauke.
-
Add map and third party guidance to Understanding 1.4.11 w3c/wcag#5396, by @jsabutis.
-
-
2 pull requests merged.
-
Rework 2.1.4 Character Key Shortcut understanding w3c/wcag#5336.
-
3 pull requests closed.
-
Update ARIA18.html w3c/wcag#5377.
-
Implemented the F13 as a 1.1.1 and 1.3.3 failure w3c/wcag#5102.
-
-
18 pull requests received 110 new comments.
-
Proposed new Failure Technique for 1.4.13 (Content on hover or focus) w3c/wcag#4934 (31 comments by @baldino-m, @giacomo-petri, @kfranqueiro, @mitchellevan, @patrickhlauke)
-
Clarifications to labels or instructions SC w3c/wcag#4995 (18 comments by @mitchellevan, @patrickhlauke, @scottaohara)
-
Expand F13: add example image, expand the explanation and test procedure, make it a 1.3.3 failure as well w3c/wcag#5386 (16 comments by @baldino-m, @giacomo-petri, @patrickhlauke)
-
Reiterate that 4.1.2 is scoped to states/properties *that can be set by the user* w3c/wcag#5399 (9 comments by @bruce-usab, @patrickhlauke, @scottaohara)
-
Implemented the F13 as a 1.1.1 and 1.3.3 failure w3c/wcag#5102 (8 comments by @mitchellevan, @patrickhlauke)
-
Tweak two of the examples in 3.3.2 Labels or Instructions w3c/wcag#5408 (5 comments by @adampage, @baldino-m, @patrickhlauke)
-
Change "correct" to "appropriate" in 4.1.2 "in brief" w3c/wcag#5407 (3 comments by @patrickhlauke, @yatil)
-
Update Intent of Accessible Authentication (Enhanced) w3c/wcag#5374 (2 comments by @bruce-usab, @patrickhlauke)
-
Update error identification to add reference to 1.3.1 and remove some links to ARIA techniques w3c/wcag#5375 (2 comments by @patrickhlauke)
-
Change 'serialize' to 'linearize' in Note 2 of Consistent Help w3c/wcag#5119 (1 comment by @swissashoxi-anks)
-
Note for 2.5.8 Target Size (Minimum) and how 24x24 was chosen w3c/wcag#5402 (1 comment by @baldino-m)
-
New Failure Technique for 1.4.13 Content on hover or focus when popup content cannot be dismissed w3c/wcag#4770 (1 comment by @patrickhlauke)
-
Add G227: Using the Map Equivalent Purpose Framework for digital geographic maps w3c/wcag#5305 (1 comment by @JonathanPKatz)
-
w3c/wcag3
-
29 issues opened.
-
“Feedback mechanism available” needs to be expanded w3c/wcag3#922, by @lbeaze.
-
“Contextual help available” needs to factor in close proximity w3c/wcag3#919, by @lbeaze.
-
Three concerns about “Consistent control location” w3c/wcag3#918, by @lbeaze.
-
Concerns about the exceptions in “Pointer focus indicated” w3c/wcag3#917, by @lbeaze.
-
Why aren’t there any core requirements in “Expected Behavior”? w3c/wcag3#916, by @lbeaze.
-
“Focus retained” needs to cover more than just keyboard tabbing w3c/wcag3#915, by @lbeaze.
-
WCAG 3: Functional Performance Statements w3c/wcag3#914, by @maryjom.
-
There should be no exception on Flashing w3c/wcag3#913, by @GreggVan.
-
Auto updating text is not mentioned in WCAG 3 w3c/wcag3#912, by @GreggVan.
-
2.4.1 Keyboard -- Keyboard Operable - is missing key parts w3c/wcag3#910, by @GreggVan.
-
Move 2.3.3 Navigating content down to the Keyboard Section of Inputs w3c/wcag3#909, by @GreggVan.
-
Change all occurrences of "focus" to "keyboard focus" w3c/wcag3#908, by @GreggVan.
-
[spam] w3c/wcag3#905, by @krystalw262-dot.
-
Should "language adjustable" provisions use "applies when" format? w3c/wcag3#900, by @ashleemboyer.
-
Definition of "programmatically determinable" is not fit for purpose w3c/wcag3#885, by @mcking65.
-
Decorative images should NOT be "programmatically hidden" w3c/wcag3#884, by @mcking65.
-
[spam] w3c/wcag3#881, by @gergelyvera.
-
-
7 issues closed.
-
Media Alternative - What is a meaningful sound? w3c/wcag3#535.
-
2.1.2 Media Alternatives - Test case (and definitions) w3c/wcag3#611.
-
[spam] w3c/wcag3#905.
-
single pointer and simple pointer are too confusable w3c/wcag3#643.
-
[spam] w3c/wcag3#881.
-
18 issues received 36 new comments.
-
Definition of decorative images update w3c/wcag3#878 (17 comments by @alastc, @charleshalldesign, @lauracarlson, @LJWatson, @MakotoUeki, @mraccess77, @patrickhlauke, @yatil)
-
Change all occurrences of "focus" to "keyboard focus" w3c/wcag3#908 (3 comments by @hidde, @mraccess77, @TanyaVanWorkum)
-
“Focus retained” needs to cover more than just keyboard tabbing w3c/wcag3#915 (1 comment by @GreggVan)
-
Clarify if the diacritics requirement only applies to Hebrew and Arabic w3c/wcag3#490 (1 comment by @lbeaze)
-
[Sounds Identified]: contradicts “transcripts available”? w3c/wcag3#520 (1 comment by @mylonelycomputer)
-
Clarifying and Enhancing Requirements for Sign Language and Subtitles in WCAG 3.0 w3c/wcag3#325 (1 comment by @iadawn)
-
Sign language: make it count in tiers and usable by policy tags w3c/wcag3#876 (1 comment by @md84419)
-
Pseudo-motion: Expand to include examples, and consider making this its own provision. w3c/wcag3#739 (1 comment by @charleshalldesign)
-
Provision "All steps listed" should not include redundant programmatic availability requirements w3c/wcag3#892 (1 comment by @GreggVan)
-
Definition of "programmatically determinable" is not fit for purpose w3c/wcag3#885 (1 comment by @GreggVan)
-
Separate visual label and programmatic name requirements for interactive elements w3c/wcag3#890 (1 comment by @GreggVan)
-
-
11 pull requests opened.
-
Add three exploratory sign language provisions w3c/wcag3#907, by @iadawn.
-
Add sign language for major choices w3c/wcag3#904, by @iadawn.
-
-
2 pull requests merged.
-
Tidy up explainer definitions w3c/wcag3#872.
-
5 pull requests received 18 new comments.
-
Revise glossary reference in relationships-detectable to use the term "programmatically detectable" w3c/wcag3#891 (2 comments by @HaTheo, @mcking65)
-
Move accessibility supported to a new testing section and recast it as user agent supported w3c/wcag3#902 (2 comments by @alastc, @mcking65)
w3c/matf
-
6 issues received 12 new comments.
-
Success Criterion 2.4.1 - Bypass Blocks - Level A w3c/matf#8 (3 comments by @geraintwhite, @TanyaVanWorkum)
-
Success Criterion 3.2.4 - Consistent Identification - Level AA w3c/matf#55 (3 comments by @pauljadam, @TanyaVanWorkum)
-
Success Criterion 3.2.3 - Consistent Navigation - Level AA w3c/matf#54 (2 comments by @TanyaVanWorkum)
-
-
1 pull request merged.
-
Scope refinement w3c/matf#300.
-
-
1 pull request received 1 new comment.
WCAG 2.x Backlog Task Force
Past meetings
-
3 meetings of the WCAG 2.x Backlog Task Force.
Participants
-
1 participant joined the WCAG 2.x Backlog Task Force.
-
Mitchell Evan joined.
-
WCAG 3 Assertions Task Force
Participants
-
5 participants joined the WCAG 3 Assertions Task Force.
-
Kevin White joined.
-
Adam Page joined.
-
Glenda Sims joined.
-
Stu Shearing joined.
-
Amanda Mace joined.
-
-
2 participants left the WCAG 3 Assertions Task Force.
-
Kevin White left.
-
Adam Page left.
-
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
4 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Mobile Accessibility Task Force
Past meetings
-
1 meeting of the Mobile Accessibility Task Force.
Participants
-
1 participant joined the Mobile Accessibility Task Force.
-
Geraint White joined.
-
WCAG 3 Guidance Documents Task Force
Participants
-
6 participants joined the WCAG 3 Guidance Documents Task Force.
-
Andrew Kirkpatrick joined.
-
Matthew King joined.
-
Wendy Reid joined.
-
Giacomo Petri joined.
-
John Kirkwood joined.
-
Wilco Fiers joined.
-
WCAG2ICT Task Force
Participants
-
1 participant joined the WCAG2ICT Task Force.
-
Mitchell Evan joined.
-
-
1 participant left the WCAG2ICT Task Force.
-
Bryan Trogdon left.
-
Lifecycle
-
1 charter extension.
-
Charter extended until 28 October 2026.
-
TR publications
-
2 documents published.
-
W3C Accessibility Guidelines (WCAG) 3.0 published as a Working Draft. History of W3C Accessibility Guidelines (WCAG) 3.0
-
Past meetings
-
5 meetings.
Participants
-
2 participants joined.
-
Matthew Luken (Deque Systems, Inc.) joined.
-
Sam Waller (W3C Invited Experts) joined.
-
-
4 participants left.
-
Michael Keane (UnitedHealth Group) left.
-
Janina Sajka (Level Access) left.
-
Christopher Land (Oracle Corporation) left.
-
Angela Young (Navy Federal Credit Union) left.
-
-
2 organizations left.
-
UnitedHealth Group left.
-
Green Technology Co left.
-
GitHub
w3c/wcag3
-
14 issues opened.
-
Definition of decorative images update w3c/wcag3#878, by @alastc.
-
And/or in “Error messages collocated” is confusing w3c/wcag3#877, by @hidde.
-
Sign language: make it count in tiers and usable by policy tags w3c/wcag3#876, by @alastc.
-
AFixt Comments on WCAG 3 draft as of 10 September 2026 w3c/wcag3#874, by @karlgroves.
-
Ambiguity of uppercase vs lowercase usage of RFC 2119 key words w3c/wcag3#873, by @bruce-usab.
-
Use headings instead of definition list to structure the glossary w3c/wcag3#870, by @mcking65.
-
Inconsistent reading order of headings and permalinks in guidelines doc w3c/wcag3#868, by @mcking65.
-
'No time limits' should be assertion instead of requirement w3c/wcag3#865, by @mhtpnacc.
-
Feedback for the Introduction plain language disclosure w3c/wcag3#863, by @ericwbailey.
-
[spam] w3c/wcag3#854, by @wsnchristopher.
-
21 issues closed.
-
Improving equity between different disabilities w3c/wcag3#230.
-
Trusted Tester sampling guidance w3c/wcag3#255.
-
UsableNet Feedback/Input on Representative Sample w3c/wcag3#252.
-
Email: Intopia Feedback - WCAG 3.0 FPWD (5 - Processes) w3c/wcag3#280.
-
Email: Intopia Feedback - WCAG 3.0 FPWD (4 - Testing) w3c/wcag3#281.
-
Trusted Tester comment on WCAG3 draft: Conformance Levels w3c/wcag3#254.
-
Consider Adding New Requirements to Reporting w3c/wcag3#244.
-
Feedback on conformance w3c/wcag3#102.
-
Composition of Functional needs w3c/wcag3#416.
-
Retro-Compatibility w3c/wcag3#506.
-
Image Alternatives (Foundational Requirements) w3c/wcag3#510.
-
About Bronze - Silver - Gold and scope of views etc. w3c/wcag3#304.
-
[spam] w3c/wcag3#857.
-
[spam] w3c/wcag3#854.
-
-
1 issue reopened.
-
Assertions Feedback and Follow up Q's w3c/wcag3#634, by @alastc.
-
-
41 issues received 64 new comments.
-
Definition of decorative images update w3c/wcag3#878 (17 comments by @alastc, @charleshalldesign, @lauracarlson, @mraccess77, @patrickhlauke, @pkra, @vavroom, @yatil)
-
Ambiguity of uppercase vs lowercase usage of RFC 2119 key words w3c/wcag3#873 (2 comments by @patrickhlauke)
-
Keyboard operation with assistive technology: 2.1.1 or 4.1.2? w3c/wcag3#186 (2 comments by @adampage, @patrickhlauke)
-
What if it was 10 years ago? - Testing with users (Assertion) w3c/wcag3#473 (2 comments by @airbr, @kfranqueiro)
-
It is unclear why Hover content persistent has been broken into a separate requirement w3c/wcag3#879 (1 comment by @GreggVan)
-
Need clear intention of mentioning web content publisher's responsibility for user generated contents w3c/wcag3#246 (1 comment by @hidde)
-
UsableNet - WCAG Team comment - Consider the legal and practical importance of conformance. w3c/wcag3#258 (1 comment by @hidde)
-
Email: Siteimprove Comments on WCAG 3.0 Draft (2 - Testing is difficult to carry out efficiently) w3c/wcag3#260 (1 comment by @hidde)
-
Starting point position - Clarify the differences between good practice and best practice w3c/wcag3#450 (1 comment by @hidde)
-
Assertions are too long and hard to follow. Please replace the text of how to write an assertion, with a link. w3c/wcag3#655 (1 comment by @hidde)
-
Mapping to WCAG2 (via email: ITI Comments on First Public Working Draft) w3c/wcag3#284 (1 comment by @alastc)
-
Separate this into two? - Meaningful visual information (Foundational) w3c/wcag3#470 (1 comment by @kfranqueiro)
-
-
27 pull requests opened.
-
Scoping statement update w3c/wcag3#880, by @alastc.
-
include variations w3c/wcag3#875, by @hidde.
-
Tidy up explainer definitions w3c/wcag3#872, by @iadawn.
-
Reset ED status w3c/wcag3#871, by @iadawn.
-
Update pointer-speed-not-relied-on.md w3c/wcag3#866, by @bruce-usab.
-
Update conformance section in Explainer w3c/wcag3#864, by @tamsinewing555.
-
Add link to published version from unpublished draft banner w3c/wcag3#860, by @kfranqueiro.
-
Add additional sign language provisions w3c/wcag3#859, by @kfranqueiro.
-
Add sign language equivalent requirement w3c/wcag3#858, by @kfranqueiro.
-
Shorten issue labels that would end up over 50-char limit by default w3c/wcag3#856, by @kfranqueiro.
-
remove capitalization from path based gesture term w3c/wcag3#855, by @fstrr.
-
fix to contributors w3c/wcag3#853, by @rachaelbradley.
-
Adjusting editors note to point to intro for questions w3c/wcag3#852, by @rachaelbradley.
-
Removed nested CSS w3c/wcag3#850, by @iadawn.
-
spelling fixes and changes so all instances of tiers align w3c/wcag3#849, by @rachaelbradley.
-
Fix typos/inconsistencies added in #846 w3c/wcag3#848, by @kfranqueiro.
-
Change affiliation w3c/wcag3#847, by @iadawn.
-
Editorial changes from 842 and 843 w3c/wcag3#846, by @rachaelbradley.
-
Editorial review of conformance sections w3c/wcag3#844, by @tamsinewing555.
-
2026 sep publication prep w3c/wcag3#843, by @iadawn.
-
Editorial review of Explainer w3c/wcag3#842, by @tamsinewing555.
-
Matt's suggestions for clarifying conformance requirements w3c/wcag3#841, by @mcking65.
-
Display status marker on informative provision page w3c/wcag3#840, by @kfranqueiro.
-
Rename best practice to recommended practice everywhere w3c/wcag3#839, by @kfranqueiro.
-
Add "this summary is non-normative" to plain-language summaries w3c/wcag3#838, by @kfranqueiro.
-
-
17 pull requests merged.
-
Reset ED status w3c/wcag3#871.
-
Add link to published version from unpublished draft banner w3c/wcag3#860.
-
fix to contributors w3c/wcag3#853.
-
Removed nested CSS w3c/wcag3#850.
-
Adjusting editors note to point to intro for questions w3c/wcag3#852.
-
Fix typos/inconsistencies added in #846 w3c/wcag3#848.
-
spelling fixes and changes so all instances of tiers align w3c/wcag3#849.
-
Change affiliation w3c/wcag3#847.
-
Editorial changes from 842 and 843 w3c/wcag3#846.
-
2026 sep publication prep w3c/wcag3#843.
-
Rename best practice to recommended practice everywhere w3c/wcag3#839.
-
Display status marker on informative provision page w3c/wcag3#840.
-
Show draft badge/box using WAI styles w3c/wcag3#831.
-
Incorporate pre-CFC conformance section feedback w3c/wcag3#834.
-
-
3 pull requests closed.
-
Sign language batch 2 w3c/wcag3#770.
-
Add sign language equivalent requirement w3c/wcag3#743.
-
-
16 pull requests received 148 new comments.
-
update definition of Interactive Element w3c/wcag3#702 (27 comments by @adampage, @fstrr, @hidde, @iadawn, @mcking65, @reidmore-online)
-
Editorial review of conformance sections w3c/wcag3#844 (21 comments by @kfranqueiro, @tamsinewing555)
-
Update conformance section in Explainer w3c/wcag3#864 (14 comments by @adampage, @iadawn, @tamsinewing555)
-
Incorporate pre-CFC conformance section feedback w3c/wcag3#834 (5 comments by @alastc, @kfranqueiro, @rachaelbradley)
-
Proposal to address Matt's feedback from review of pre-CFC Section 3 Conformance w3c/wcag3#836 (3 comments by @alastc, @kfranqueiro, @mcking65)
w3c/matf
-
1 issue opened.
-
Comments regarding new MATF group note w3c/matf#299, by @detlevhfischer.
-
-
28 issues closed.
-
Guidance: Grouping elements w3c/matf#20.
-
Collect limitations of operating systems / frameworks w3c/matf#268.
-
WCAG2ICT term to modify: "Closed Functionality" w3c/matf#89.
-
WCAG2ICT Key term to modify: "menu-driven interface" w3c/matf#90.
-
-
39 issues received 43 new comments.
-
Success Criterion 2.4.5 - Multiple Ways - Level AA w3c/matf#13 (4 comments by @detlevhfischer, @frecann, @JJdeGroot)
-
Success Criterion 2.4.1 - Bypass Blocks - Level A w3c/matf#8 (2 comments by @detlevhfischer, @JJdeGroot)
-
Success Criterion 3.2.4 - Consistent Identification - Level AA w3c/matf#55 (1 comment by @JJdeGroot)
-
Where should custom actions be assessed in our guidance (or under WCAG?) w3c/matf#101 (1 comment by @JJdeGroot)
-
SUB - make a draft of WCAG2ICT term to modify: "Content (on and off the Web)" w3c/matf#234 (1 comment by @JJdeGroot)
-
Create a list of known Android/iOS components that fail contrast requirements w3c/matf#259 (1 comment by @JJdeGroot)
-
Clarification on the scope of "mobile" devices in WCAG2Mobile w3c/matf#281 (1 comment by @JJdeGroot)
-
Proposal: Standardization of core accessibility roles and states for native mobile platforms w3c/matf#283 (1 comment by @JJdeGroot)
-
SUB - 4.1.2 - Name, Role, Value - Decide on "standard user interface" w3c/matf#202 (1 comment by @JJdeGroot)
-
SUB - 1.4.4 - Resize Text - Define "loss of content or functionality" w3c/matf#137 (1 comment by @JJdeGroot)
-
SUB - 3.2.3 - Consistent Navigation - Define "navigational mechanisms" w3c/matf#214 (1 comment by @JJdeGroot)
-
SUB - 2.1.2 - No Keyboard Trap - Group agrees that existing actions capture what's needed to draft 2.1.2 w3c/matf#186 (1 comment by @JJdeGroot)
-
Definition of "navigational mechanisms" in mobile application context w3c/matf#71 (1 comment by @JJdeGroot)
-
Definitions for consistently referring to UI patterns used in mobile application context w3c/matf#85 (1 comment by @JJdeGroot)
-
SUB - make a draft of WCAG2ICT term to modify: "Closed Functionality" w3c/matf#235 (1 comment by @JJdeGroot)
-
SUB - make adraft of WCAG2ICT Key term to modify: "menu-driven interface" w3c/matf#236 (1 comment by @JJdeGroot)
-
-
2 pull requests opened.
-
Scope refinement w3c/matf#300, by @alastc.
-
Editorial comments tanya w3c/matf#298, by @TanyaVanWorkum.
-
-
1 pull request merged.
-
Editorial comments tanya w3c/matf#298.
-
-
1 pull request received 27 new comments.
w3c/wcag
-
28 issues opened.
-
[spam] w3c/wcag#5385, by @colinandres885-boop.
-
Target Size: Inline link adjacent to control w3c/wcag#5384, by @aardrian.
-
[spam] w3c/wcag#5382, by @basakbitu115-design.
-
[spam] w3c/wcag#5381, by @basakbitu115-design.
-
[spam] w3c/wcag#5380, by @g2240992-bot.
-
[spam] w3c/wcag#5379, by @g2240992-bot.
-
[spam] w3c/wcag#5378, by @allkasirkazemsaadi-beep.
-
[spam] w3c/wcag#5372, by @amonmono68-oss.
-
[spam] w3c/wcag#5371, by @krishnakumargondmbc-cell.
-
[spam] w3c/wcag#5370, by @krishnakumargondmbc-cell.
-
[spam] w3c/wcag#5367, by @angelreyesr992-cmyk.
-
[spam] w3c/wcag#5366, by @valeriekilgore1971-eng.
-
[spam] w3c/wcag#5364, by @adamumahammed56-eng.
-
[spam] w3c/wcag#5361, by @hoseinhaftekhanehgi7-netizen.
-
[spam] w3c/wcag#5360, by @rydell803-svg.
-
[spam] w3c/wcag#5356, by @benjaminandrew386-boop.
-
[spam] w3c/wcag#5355, by @hamza05524319-maker.
-
[spam] w3c/wcag#5353, by @Sesanamoo.
-
[spam] w3c/wcag#5352, by @mynajmin7-ui.
-
[spam] w3c/wcag#5351, by @mynajmin7-ui.
-
[spam] w3c/wcag#5350, by @mynajmin7-ui.
-
[spam] w3c/wcag#5347, by @ShadyLady4911.
-
[spam] w3c/wcag#5346, by @kol123858-ui.
-
Question regarding WCAG 1.4.10 and e-mail(clients) w3c/wcag#5342, by @joshuaboele.
-
-
38 issues closed.
-
[spam] w3c/wcag#5385.
-
[spam] w3c/wcag#5382.
-
[spam] w3c/wcag#5381.
-
[spam] w3c/wcag#5380.
-
[spam] w3c/wcag#5379.
-
[spam] w3c/wcag#5378.
-
[spam] w3c/wcag#5372.
-
[spam] w3c/wcag#5370.
-
[spam] w3c/wcag#5371.
-
Technique F86: Add related technique ARIA14 w3c/wcag#3791.
-
Technique G73, Example 3 (SC 1.1.1) w3c/wcag#2128.
-
[spam] w3c/wcag#5367.
-
[spam] w3c/wcag#5366.
-
[spam] w3c/wcag#5364.
-
site-oriented SC use inconsistent phrasing w3c/wcag#5096.
-
[spam] w3c/wcag#5361.
-
[spam] w3c/wcag#5360.
-
[spam] w3c/wcag#5359.
-
Missing related resources for sign language need replacing w3c/wcag#4961.
-
Exception needed for 1.3.5 Identify Input Purpose w3c/wcag#1081.
-
SC 1.4.11 - Solid colour logo as link w3c/wcag#4376.
-
[spam] w3c/wcag#5356.
-
[spam] w3c/wcag#5355.
-
[spam] w3c/wcag#5353.
-
[spam] w3c/wcag#5350.
-
[spam] w3c/wcag#5351.
-
[spam] w3c/wcag#5352.
-
[spam] w3c/wcag#5347.
-
[spam] w3c/wcag#5346.
-
Question regarding WCAG 1.4.10 and e-mail(clients) w3c/wcag#5342.
-
-
3 issues reopened.
-
[spam] w3c/wcag#5380, by @g2240992-bot.
-
[spam] w3c/wcag#5380, by @g2240992-bot.
-
[spam] w3c/wcag#5380, by @g2240992-bot.
-
-
20 issues received 80 new comments.
-
Must focusable elements have a role? w3c/wcag#3029 (28 comments by @aardrian, @bruce-usab, @grace-snow, @mraccess77, @patrickhlauke, @stes-acc, @tombrunet)
-
Does the use of `Summary` and `Details` for an accordion pass 1.3.1? w3c/wcag#5321 (6 comments by @mbgower, @pkra)
-
Target Size: Inline link adjacent to control w3c/wcag#5384 (4 comments by @aardrian, @detlevhfischer, @patrickhlauke)
-
Distinguish theoretical backward compatibility from practical backward compatibility w3c/wcag#5344 (4 comments by @alastc, @bruce-usab, @murata2makoto)
-
3.3.8/3.3.9: How is "authentication process" defined? w3c/wcag#3264 (2 comments by @bruce-usab, @patrickhlauke)
-
Conforming Alternate Version (CAV) and the mechanism to reach/achieve it w3c/wcag#5373 (1 comment by @patrickhlauke)
-
Clarification for 3.3.7 Redundant Entry and going "Back" in a multi-step form w3c/wcag#4481 (1 comment by @Marat-Faizov)
-
"Are programming languages human languages?" and repercussions for text contrast requirements w3c/wcag#5369 (1 comment by @patrickhlauke)
-
Does the SC 1.4.3 Contrast minium exception apply to text outside a disabled control? w3c/wcag#4874 (1 comment by @patrickhlauke)
-
No definition of what constitutes an A, AA, or AAA conformance Level w3c/wcag#3889 (1 comment by @patrickhlauke)
-
-
9 pull requests opened.
-
Update ARIA18.html w3c/wcag#5377, by @acyngel.
-
Create SECURITY.md w3c/wcag#5376, by @octocatsback.
-
Update Intent of Accessible Authentication (Enhanced) w3c/wcag#5374, by @bruce-usab.
-
Clarify scope of 11ty build system w3c/wcag#5358, by @kfranqueiro.
-
Tweak 1.3.5 identify input purpose understanding w3c/wcag#5357, by @patrickhlauke.
-
Replace "best practice" with alternative wordings (informative) w3c/wcag#5345, by @patrickhlauke.
-
-
11 pull requests merged.
-
Add ARIA14 reference to F86 w3c/wcag#5331.
-
Expand "Understanding Levels of Conformance" w3c/wcag#5303.
-
Clarify scope of 11ty build system w3c/wcag#5358.
-
Tweak 1.3.5 identify input purpose understanding w3c/wcag#5357.
-
Remove or repoint some outdated or missing links w3c/wcag#5292.
-
Update focus appearance image to match the intended design w3c/wcag#5289.
-
Revise understanding for SC 3.2.4 Consistent Identification w3c/wcag#5251.
-
-
3 pull requests closed.
-
Create SECURITY.md w3c/wcag#5376.
-
Update Bypass Blocks to match other SC w3c/wcag#5097.
-
-
15 pull requests received 139 new comments.
-
Proposed new Failure Technique for 1.4.13 (Content on hover or focus) w3c/wcag#4934 (32 comments by @baldino-m, @giacomo-petri, @patrickhlauke, @stes-acc)
-
Replace "best practice" with alternative wordings (informative) w3c/wcag#5345 (30 comments by @alastc, @bruce-usab, @mraccess77, @patrickhlauke)
-
Rework 2.1.4 Character Key Shortcut understanding w3c/wcag#5336 (25 comments by @alastc, @baldino-m, @bruce-usab, @detlevhfischer, @kfranqueiro, @patrickhlauke)
-
Add G227: Using the Map Equivalent Purpose Framework for digital geographic maps w3c/wcag#5305 (12 comments by @bruce-usab, @frastlin, @nickgiudice, @patrickhlauke, @stevo399)
-
Reword "best practice" in Label in Name note and guidelines introduction text (normative) w3c/wcag#5348 (11 comments by @alastc, @grace-snow, @mraccess77, @patrickhlauke, @WilcoFiers)
-
Clarifications to labels or instructions SC w3c/wcag#4995 (7 comments by @detlevhfischer, @patrickhlauke)
-
New Failure Technique for 1.4.13 Content on hover or focus when popup content cannot be dismissed w3c/wcag#4770 (6 comments by @fstrr)
-
Add new Technique: Guarding keyboard event handlers against IME composition w3c/wcag#5081 (3 comments by @mehm8128, @patrickhlauke)
-
Mark up quoted note as actual note in 1.4.5 Images of Text understanding w3c/wcag#5337 (3 comments by @baldino-m, @patrickhlauke)
-
Update 1.4.11 Non-text Contrast with additional boundary examples w3c/wcag#5362 (2 comments by @Blackbaud-MattGregg, @detlevhfischer)
-
WCAG 3 Guidance Documents Task Force
Participants
-
9 participants joined the WCAG 3 Guidance Documents Task Force.
-
Ashlee Fisher joined.
-
Shadi Abou-Zahra joined.
-
Gregg Vanderheiden joined.
-
Jeroen Hulscher joined.
-
Charles Hall joined.
-
Hidde de Vries joined.
-
Jennifer Delisi joined.
-
Alastair Campbell joined.
-
Rachael Bradley Montgomery joined.
-
Mobile Accessibility Task Force
Past meetings
-
4 meetings of the Mobile Accessibility Task Force.
Participants
-
1 participant joined the Mobile Accessibility Task Force.
-
James Harrington joined.
-
-
1 participant left the Mobile Accessibility Task Force.
-
Michael Keane left.
-
WCAG 2.x Backlog Task Force
Past meetings
-
4 meetings of the WCAG 2.x Backlog Task Force.
Participants
-
1 participant left the WCAG 2.x Backlog Task Force.
-
Michael Keane left.
-
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 participant left the Cognitive and Learning Disabilities Accessibility Task Force.
-
Janina Sajka left.
-
WCAG 3 Assertions Task Force
Participants
-
2 participants joined the WCAG 3 Assertions Task Force.
-
Rachael Bradley Montgomery joined.
-
Adam Page joined.
-
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
5 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Past meetings
Participants
-
7 participants joined.
-
Michael Gilbert (Google LLC) joined.
-
Jeffrey Yasskin (Google LLC) joined.
-
Lia Carrari Rodrigues Lopes (Google LLC) joined.
-
Dirk Ginader (Google LLC) joined.
-
Michael Gilbert (Google LLC) joined.
-
Stephan Morris (See Me Please) joined.
-
Daniel Leighton (See Me Please) joined.
-
-
9 participants left.
-
Michael Gilbert (Google LLC) left.
-
Lia Carrari Rodrigues Lopes (Google LLC) left.
-
Lia Carrari Rodrigues Lopes (Google LLC) left.
-
Lia Carrari Rodrigues Lopes (Google LLC) left.
-
Jeffrey Yasskin (Google LLC) left.
-
Jeffrey Yasskin (Google LLC) left.
-
Dirk Ginader (Google LLC) left.
-
Sydney Coleman (Google LLC) left.
-
Stephan Morris (See Me Please) left.
-
-
1 organization joined.
-
See Me Please joined.
-
GitHub
w3c/wcag3
-
23 issues opened.
-
Submission status notified - programmatic as well w3c/wcag3#830, by @alastc.
-
Refine "Data entry validated" text w3c/wcag3#822, by @HaTheo.
-
Input method versus input modality w3c/wcag3#820, by @adampage.
-
AFixt Comments on the WCAG 3 Conformance Model w3c/wcag3#816, by @karlgroves.
-
Refine "Submission status notified" Rule Text w3c/wcag3#814, by @HaTheo.
-
Recommended addition to “Focus indicator style guide” w3c/wcag3#810, by @julierawe.
-
Three concerns about “Focus indicator size sufficient” w3c/wcag3#809, by @julierawe.
-
Target size and target spacing not mentioned in WCAG 3 w3c/wcag3#808, by @julierawe.
-
Accessibility controls: browser vs content author w3c/wcag3#805, by @mm2t.
-
Dynamically displayed contents w3c/wcag3#804, by @mm2t.
-
[Captions available (pre-recorded)] Recordings of meetings w3c/wcag3#802, by @Finnberry.
-
Concerns about the exception in “Errors Preventable” w3c/wcag3#791, by @julierawe.
-
Two big concerns about “Error messages collocated” w3c/wcag3#790, by @julierawe.
-
The “New interfaces” provision is critical and supported by COGA w3c/wcag3#784, by @julierawe.
-
“Disabled controls explained” leaves out timing-related considerations w3c/wcag3#783, by @julierawe.
-
“Sensory characteristics not relied on” leaves out haptics/touch w3c/wcag3#782, by @julierawe.
-
-
10 issues received 16 new comments.
-
[Captions available (pre-recorded)] Recordings of meetings w3c/wcag3#802 (5 comments by @chaals, @Finnberrys, @GreggVan)
-
Pseudo-motion: Expand to include examples, and consider making this its own provision. w3c/wcag3#739 (1 comment by @julierawe)
-
-
32 pull requests opened.
-
Fail on common directive mistakes not caught by remark-directive w3c/wcag3#837, by @kfranqueiro.
-
Some contributor fixes w3c/wcag3#835, by @iadawn.
-
Incorporate pre-CFC conformance section feedback w3c/wcag3#834, by @adampage.
-
Explainer - conformance w3c/wcag3#833, by @alastc.
-
More general on how materials could support policy makers w3c/wcag3#832, by @iadawn.
-
Show draft badge/box using WAI styles w3c/wcag3#831, by @kfranqueiro.
-
Make hardcoded color values resilient to dark mode w3c/wcag3#829, by @adampage.
-
Fix mispositioned status markers at the guideline level w3c/wcag3#828, by @adampage.
-
Add “Progress towards and beyond conformance” section w3c/wcag3#827, by @adampage.
-
Update conformance section w3c/wcag3#826, by @adampage.
-
Add explicit darkmode support to account for ReSpec 37.3.3+ w3c/wcag3#825, by @kfranqueiro.
-
Experiment with universal approach to text presentation provisions w3c/wcag3#824, by @iadawn.
-
Fix issues with last-minute images and media changes w3c/wcag3#821, by @kfranqueiro.
-
overridePermalinkLabels: Skip self-links that aren't in a section w3c/wcag3#819, by @kfranqueiro.
-
Improve aria-labels for permalinks w3c/wcag3#818, by @kfranqueiro.
-
Reuse ProvisionsList in "Provisions under this guideline" w3c/wcag3#817, by @kfranqueiro.
-
Reorganize images and media section w3c/wcag3#815, by @kfranqueiro.
-
Reorganization of media section w3c/wcag3#813, by @rachaelbradley.
-
Preparation for Aug 2026 publication w3c/wcag3#812, by @iadawn.
-
Add Adam Page as editor w3c/wcag3#806, by @iadawn.
-
Add dev page to audit missing/extraneous issue labels w3c/wcag3#803, by @kfranqueiro.
-
Provision restyle experiment: Separate informative link w3c/wcag3#801, by @adampage.
-
Provision restyle experiment: Linked headings w3c/wcag3#800, by @adampage.
-
chore: use built-in cSpell HTML regex w3c/wcag3#799, by @nschonni.
-
Consistently sort ACT Rules / Best Practices / Methods lists w3c/wcag3#798, by @kfranqueiro.
-
Incorporate pre/code styles from w3c/wcag#4683 w3c/wcag3#797, by @kfranqueiro.
-
Grammar pass on applies/except when w3c/wcag3#796, by @kfranqueiro.
-
Migrate Methods to informative docs w3c/wcag3#795, by @kfranqueiro.
-
Informative docs: Move In brief section before normative content w3c/wcag3#794, by @kfranqueiro.
-
remove "AI of all sorts" w3c/wcag3#793, by @fstrr.
-
Add README for informative files; remove unused user-needs directive w3c/wcag3#792, by @kfranqueiro.
-
-
31 pull requests merged.
-
Some contributor fixes w3c/wcag3#835.
-
Preparation for Aug 2026 publication w3c/wcag3#812.
-
More general on how materials could support policy makers w3c/wcag3#832.
-
Explainer - conformance w3c/wcag3#833.
-
Add “Progress towards and beyond conformance” section w3c/wcag3#827.
-
Update conformance section w3c/wcag3#826.
-
Add explicit darkmode support to account for ReSpec 37.3.3+ w3c/wcag3#825.
-
Fix mispositioned status markers at the guideline level w3c/wcag3#828.
-
Updates to flashing w3c/wcag3#628.
-
Fix issues with last-minute images and media changes w3c/wcag3#821.
-
Reorganize images and media section w3c/wcag3#815.
-
Develop informative materials for 2.8.1 Consistency w3c/wcag3#753.
-
Improve aria-labels for permalinks w3c/wcag3#818.
-
Reuse ProvisionsList in "Provisions under this guideline" w3c/wcag3#817.
-
Provision restyle experiment: Linked headings w3c/wcag3#800.
-
Add Adam Page as editor w3c/wcag3#806.
-
Add dev page to audit missing/extraneous issue labels w3c/wcag3#803.
-
Add build system for ACT working examples w3c/wcag3#774.
-
Consistently sort ACT Rules / Best Practices / Methods lists w3c/wcag3#798.
-
Grammar pass on applies/except when w3c/wcag3#796.
-
Migrate Methods to informative docs w3c/wcag3#795.
-
Sign language updates w3c/wcag3#673.
-
Incorporate pre/code styles from w3c/wcag#4683 w3c/wcag3#797.
-
remove "AI of all sorts" w3c/wcag3#793.
-
Build: Upgrade dependencies found in npm audit w3c/wcag3#780.
-
Reflect WCAG_PUBLISH behavior in informative provision lists w3c/wcag3#777.
-
-
3 pull requests closed.
-
Make hardcoded color values resilient to dark mode w3c/wcag3#829.
-
Reorganization of media section w3c/wcag3#813.
-
Exploring use of registry to support more text scripts w3c/wcag3#613.
-
-
25 pull requests received 175 new comments.
-
Incorporate pre-CFC conformance section feedback w3c/wcag3#834 (17 comments by @adampage, @bruce-usab, @iadawn, @kfranqueiro)
-
Add “Progress towards and beyond conformance” section w3c/wcag3#827 (15 comments by @alastc, @iadawn, @kfranqueiro, @rachaelbradley)
-
Update pointer pressure not relied upon w3c/wcag3#751 (10 comments by @adampage, @bruce-usab, @kfranqueiro)
-
chore: use built-in cSpell HTML regex w3c/wcag3#799 (9 comments by @kfranqueiro, @nschonni, @w3cbot)
-
Add explicit darkmode support to account for ReSpec 37.3.3+ w3c/wcag3#825 (8 comments by @adampage, @kfranqueiro)
-
Provision restyle experiment: Separate informative link w3c/wcag3#801 (3 comments by @iadawn, @rachaelbradley)
-
Proposal to address Matt's feedback from review of pre-CFC Section 3 Conformance w3c/wcag3#836 (2 comments by @kfranqueiro, @mcking65)
-
Rework “No repetitive links” as “No adjacent interactive elements” w3c/wcag3#602 (2 comments by @kfranqueiro)
-
More general on how materials could support policy makers w3c/wcag3#832 (1 comment by @rachaelbradley)
w3c/wcag
-
56 issues opened.
-
[spam] w3c/wcag#5341, by @mariaraiz042-spec.
-
[spam] w3c/wcag#5340, by @proezasus-netizen.
-
[spam] w3c/wcag#5339, by @FrancesCabrini13.
-
[spam] w3c/wcag#5338, by @mhmoud12mhmoud34-dot.
-
[spam] w3c/wcag#5333, by @g4813923-a11y.
-
[spam] w3c/wcag#5330, by @notarioabraham-lab.
-
[spam] w3c/wcag#5329, by @notarioabraham-lab.
-
[spam] w3c/wcag#5328, by @aaronperegrina18-ui.
-
[spam] w3c/wcag#5327, by @Nassey777.
-
ISO does not require abbreviation/initialism expansion w3c/wcag#5324, by @daniel-montalvo.
-
[spam] w3c/wcag#5322, by @jameschristopherfrederick18-star.
-
Does the use of `Summary` and `Details` for an accordion pass 1.3.1? w3c/wcag#5321, by @mbgower.
-
What is considered 'functionality' in 1.4.10 Reflow w3c/wcag#5320, by @jake-abma.
-
[spam] w3c/wcag#5319, by @esreada88-netizen.
-
1.4.5 Move the note embedded in a paragraph to the standard styling w3c/wcag#5318, by @ljkoakley.
-
[spam] w3c/wcag#5313, by @tomritzow.
-
[spam] w3c/wcag#5312, by @lopzaira2-cpu.
-
[spam] w3c/wcag#5311, by @myexampl35-dotcom.
-
[spam] w3c/wcag#5307, by @mrwan009988-hub.
-
[spam] w3c/wcag#5306, by @mrwan009988-hub.
-
[spam] w3c/wcag#5291, by @a30244829-maker.
-
Consider generalizing listing of autocomplete attributes for 1.3.5 w3c/wcag#5288, by @scottaohara.
-
The procedure in F19 could be made more accurate w3c/wcag#5286, by @giacomo-petri.
-
F111 could be clarified and simplified w3c/wcag#5285, by @giacomo-petri.
-
Step 2 of the procedure in F107 is ambiguous w3c/wcag#5283, by @giacomo-petri.
-
Editorial: step 3 of the procedure in F103 appears unnecessary w3c/wcag#5282, by @giacomo-petri.
-
F102 procedure should better align with the scope of 1.4.10 w3c/wcag#5281, by @giacomo-petri.
-
F99 should use "user interface component" instead of "input" w3c/wcag#5280, by @giacomo-petri.
-
The wording "programmatically linked label" in F96 is ambiguous w3c/wcag#5279, by @giacomo-petri.
-
Editorial - two typo in the procedure of F85 w3c/wcag#5275, by @giacomo-petri.
-
F75 could be simplified and clarified w3c/wcag#5274, by @giacomo-petri.
-
Editorial: the first step of the procedure in F72 could be removed w3c/wcag#5273, by @giacomo-petri.
-
The procedure in F65 is too implementation-specific w3c/wcag#5272, by @giacomo-petri.
-
The first step of the procedure in F63 is too restrictive w3c/wcag#5271, by @giacomo-petri.
-
F55 incorrectly maps to SC 2.4.7 and SC 2.4.13 w3c/wcag#5270, by @giacomo-petri.
-
F50 is more restrictive than the 2.2.2 SC w3c/wcag#5269, by @giacomo-petri.
-
F49 procedure is missing the target element w3c/wcag#5268, by @giacomo-petri.
-
F46 does not account for tables with a presentational role w3c/wcag#5267, by @giacomo-petri.
-
F42 should acknowledge intentionally duplicated links w3c/wcag#5266, by @giacomo-petri.
-
Procedure in failure techniques F38 and F39 are too strict w3c/wcag#5265, by @giacomo-petri.
-
[spam] w3c/wcag#5264, by @jameschristopherfrederick18-star.
-
Section 5.4 Third Party Content is missnamed w3c/wcag#5263, by @bruce-usab.
-
The procedure in F36 does not 100% align with SC 3.2.2 w3c/wcag#5262, by @giacomo-petri.
-
The procedure in F24 does not clearly identify the target element w3c/wcag#5261, by @giacomo-petri.
-
F9 should also map to SC 3.2.1 w3c/wcag#5260, by @giacomo-petri.
-
F20 incorrectly maps to SC 4.1.2 w3c/wcag#5259, by @giacomo-petri.
-
Procedure in failure technique F16 is too strict w3c/wcag#5258, by @giacomo-petri.
-
Tests procedures inaccuracies w3c/wcag#5248, by @giacomo-petri.
-
[spam] w3c/wcag#5246, by @kumarsanoj65641-a11y.
-
-
36 issues closed.
-
[spam] w3c/wcag#5341.
-
[spam] w3c/wcag#5340.
-
[spam] w3c/wcag#5339.
-
[spam] w3c/wcag#5338.
-
F17 removal lost important tests w3c/wcag#1492.
-
[spam] w3c/wcag#5333.
-
[spam] w3c/wcag#5330.
-
[spam] w3c/wcag#5329.
-
[spam] w3c/wcag#5328.
-
[spam] w3c/wcag#5313.
-
[spam] w3c/wcag#5322.
-
F70 goes beyond WCAG 4.1.1 w3c/wcag#2187.
-
[spam] w3c/wcag#5327.
-
Understanding WCAG 2.1 docs still incorrectly say WCAG 2.0 w3c/wcag#1068.
-
Update the definition of process w3c/wcag#1605.
-
1.3.5: Does not account for credit card number parts w3c/wcag#2754.
-
G183: 4.5:1 in headline of example 1, 5:1 in the example w3c/wcag#2897.
-
Editorial - two typo in the procedure of F85 w3c/wcag#5275.
-
[spam] w3c/wcag#5319.
-
1.3.1 placeholder alone not sufficent as accessible name? w3c/wcag#4918.
-
[spam] w3c/wcag#5312.
-
[spam] w3c/wcag#5311.
-
[spam] w3c/wcag#5307.
-
[spam] w3c/wcag#5306.
-
Not all headings are appropriately nested in (sub)sections w3c/wcag#3926.
-
SC 2.5.8 Target Size implications for ToC w3c/wcag#4540.
-
Consistent Identification examples 2 and 8 w3c/wcag#4250.
-
[spam] w3c/wcag#5291.
-
[spam] w3c/wcag#5264.
-
[spam] w3c/wcag#5246.
-
-
1 issue reopened.
-
30 issues received 94 new comments.
-
Does the use of `Summary` and `Details` for an accordion pass 1.3.1? w3c/wcag#5321 (8 comments by @mbgower, @patrickhlauke)
-
Examples for SC 2.1.4 too faint - difficult to discern w3c/wcag#953 (6 comments by @elichad, @patrickhlauke)
-
1.4.13 Content on Hover or Focus - applicable to animated flip cards w3c/wcag#4071 (6 comments by @detlevhfischer, @fstrr, @patrickhlauke)
-
Add one-time-code to list of autocomplete attributes w3c/wcag#2613 (5 comments by @patrickhlauke, @thw0rted)
-
Not all headings are appropriately nested in (sub)sections w3c/wcag#3926 (4 comments by @kfranqueiro, @patrickhlauke)
-
No definition of what constitutes an A, AA, or AAA conformance Level w3c/wcag#3889 (3 comments by @Helixopp, @patrickhlauke)
-
Withdrawn standards are listed in the References section on Understanding SC 1.4.3 and 1.4.6 w3c/wcag#4259 (2 comments by @patrickhlauke)
-
Chromium autocomplete behaviour now incompatible with Input Purpose & security w3c/wcag#2032 (2 comments by @alastc, @patrickhlauke)
-
If field asks for input about "your organization" is that covered under SC 1.3.5? w3c/wcag#642 (2 comments by @patrickhlauke)
-
Paragraph symbol used for self-link in spec has insufficient contrast, looks awkward with the underline w3c/wcag#5185 (2 comments by @patrickhlauke)
-
SC 2.5.8 Target Size implications for ToC w3c/wcag#4540 (2 comments by @bbarlach-sys, @patrickhlauke)
-
The meta refresh element and HTTP Refresh header with zero timeout can trigger 2.3.1/2.3.2 w3c/wcag#1012 (2 comments by @JediLin, @patrickhlauke)
-
Understanding WCAG 2.1 docs still incorrectly say WCAG 2.0 w3c/wcag#1068 (1 comment by @patrickhlauke)
-
G183: 4.5:1 in headline of example 1, 5:1 in the example w3c/wcag#2897 (1 comment by @patrickhlauke)
-
1.3.1 placeholder alone not sufficent as accessible name? w3c/wcag#4918 (1 comment by @patrickhlauke)
-
Consider providing examples of when controls _don't_ need labels - 3.3.2 labels or instructions w3c/wcag#4977 (1 comment by @erikgustafsson)
-
Broken internal links on the WCAG 2.2 Understanding and Techniques pages w3c/wcag#4962 (1 comment by @fstrr)
-
Tooltips (title attributes) for new WCAG 2.2 terms show "New" instead of the definition w3c/wcag#5247 (1 comment by @patrickhlauke)
-
30 pull requests opened.
-
Rework 2.1.4 Character Key Shortcut understanding w3c/wcag#5336, by @patrickhlauke.
-
Add ARIA14 reference to F86 w3c/wcag#5331, by @patrickhlauke.
-
Update color contrast references w3c/wcag#5326, by @patrickhlauke.
-
Fix ISO references w3c/wcag#5325, by @daniel-montalvo.
-
Backport summer 2026 errata to 2.1 w3c/wcag#5317, by @kfranqueiro.
-
Update spec-generator URLs for WCAG-2.1 branch w3c/wcag#5316, by @kfranqueiro.
-
Create SECURITY.md w3c/wcag#5310, by @mrwan009988-hub.
-
language tweak - limits on function / look and feel w3c/wcag#5309, by @chaals.
-
Expand "Understanding Levels of Conformance" w3c/wcag#5303, by @patrickhlauke.
-
css reflow working example: swap TBC for C33 w3c/wcag#5301, by @fstrr.
-
fix motion actuation link w3c/wcag#5300, by @fstrr.
-
Override `blockquote p:last-of-type` bottom margin w3c/wcag#5299, by @patrickhlauke.
-
UK/US spelling fix - stylised>stylized w3c/wcag#5298, by @patrickhlauke.
-
Remove or repoint some outdated or missing links w3c/wcag#5292, by @patrickhlauke.
-
P,S,H interaction → interactions w3c/wcag#5290, by @fstrr.
-
Update focus appearance image to match the intended design w3c/wcag#5289, by @fstrr.
-
Update Statement of Partial Conformance w3c/wcag#5287, by @bruce-usab.
-
Editorial - two typo in the procedure of F85 w3c/wcag#5276, by @giacomo-petri.
-
Add `one-time-code` to list of input purposes w3c/wcag#5255, by @patrickhlauke.
-
Update F68 test procedure to rely on computed accessible names w3c/wcag#5253, by @giacomo-petri.
-
Revise understanding for SC 3.2.4 Consistent Identification w3c/wcag#5251, by @giacomo-petri.
-
23 pull requests merged.
-
Summer 2026 errata for WCAG 2.1 / 2.2 w3c/wcag#5176.
-
Backport summer 2026 errata to 2.1 w3c/wcag#5317.
-
Override `blockquote p:last-of-type` bottom margin w3c/wcag#5299.
-
Editorial - two typo in the procedure of F85 w3c/wcag#5276.
-
Build: Upgrade dependencies found in npm audit w3c/wcag#5242.
-
Update spec-generator URLs for WCAG-2.1 branch w3c/wcag#5316.
-
Conform phrasing in exception of 1.4.13 w3c/wcag#4741.
-
Don't just refer to SCs by their number alone w3c/wcag#4947.
-
Amend process definition to remove registration example w3c/wcag#3538.
-
Fix grammar in Privacy and Security Considerations w3c/wcag#4776.
-
Two typos in 2.1 Change Log w3c/wcag#4919.
-
Backport editorial fixes from #3267 to 2.1 w3c/wcag#4796.
-
css reflow working example: swap TBC for C33 w3c/wcag#5301.
-
3.2.4 understanding: Reword examples w3c/wcag#5022.
-
P,S,H interaction → interactions w3c/wcag#5290.
-
fix motion actuation link w3c/wcag#5300.
-
UK/US spelling fix - stylised>stylized w3c/wcag#5298.
-
Fix various grammatical errors w3c/wcag#5241.
-
-
9 pull requests closed.
-
Update color contrast references w3c/wcag#5326.
-
Create SECURITY.md w3c/wcag#5310.
-
language tweak - limits on function / look and feel w3c/wcag#5309.
-
Fix typos in requirements notes and conformance challenges w3c/wcag#5239.
-
-
37 pull requests received 172 new comments.
-
Revise understanding for SC 3.2.4 Consistent Identification w3c/wcag#5251 (31 comments by @adampage, @baldino-m, @bruce-usab, @giacomo-petri, @patrickhlauke)
-
Expand "Understanding Levels of Conformance" w3c/wcag#5303 (30 comments by @bruce-usab, @chaals, @patrickhlauke)
-
Fix 20 broken external links in WCAG 2.2 documentation (#4964) w3c/wcag#5123 (21 comments by @patrickhlauke)
-
Remove or repoint some outdated or missing links w3c/wcag#5292 (6 comments by @alastc, @baldino-m, @bruce-usab, @patrickhlauke)
-
Update Bypass Blocks to match other SC w3c/wcag#5097 (5 comments by @alastc, @bruce-usab, @patrickhlauke)
-
Add extra (non-normative) note to the definition of "conforming alternate version" w3c/wcag#5236 (5 comments by @awkawk, @patrickhlauke)
-
1.3.5: Mention heuristics, turning off autocomplete for forms, and tweak examples w3c/wcag#5293 (5 comments by @baldino-m, @bruce-usab, @patrickhlauke)
-
Implemented the F13 as a 1.1.1 and 1.3.3 failure w3c/wcag#5102 (3 comments by @baldino-m, @kfranqueiro)
-
Override `blockquote p:last-of-type` bottom margin w3c/wcag#5299 (3 comments by @adampage, @kfranqueiro, @patrickhlauke)
-
language tweak - limits on function / look and feel w3c/wcag#5309 (2 comments by @chaals, @patrickhlauke)
-
Update F68 test procedure to rely on computed accessible names w3c/wcag#5253 (2 comments by @giacomo-petri, @patrickhlauke)
-
Tweak wording for G73: caption contains the link, the entire caption isn't a link w3c/wcag#5332 (1 comment by @kfranqueiro)
-
Update focus appearance image to match the intended design w3c/wcag#5289 (1 comment by @patrickhlauke)
-
Skip "New" paragraph when scanning definitions to make link titles w3c/wcag#4857 (1 comment by @kfranqueiro)
-
Consistency: use "touchscreen" rather than "touch screen" (normative) w3c/wcag#5038 (1 comment by @kfranqueiro)
-
w3c/matf
-
2 issues opened.
-
Provide difference overview of first draft and second draft w3c/matf#297, by @JJdeGroot.
-
"Comments on Webviews and Web Content" draft section w3c/matf#296, by @jha11y.
-
-
22 issues closed.
-
SUB - draft the definition of "cross-platform framework" w3c/matf#231.
-
Definition of "cross-platform framework" w3c/matf#84.
-
Define 'mobile operating systems' in scope w3c/matf#102.
-
Success Criterion 3.2.2 - On Input - Level A w3c/matf#42.
-
Success Criterion 2.5.3 - Label in Name - Level A w3c/matf#39.
-
2 issues received 3 new comments.
-
5 pull requests merged.
-
2.5.7 update content w3c/matf#295.
-
Add draft for 2.5.8 w3c/matf#291.
-
Add new definitions w3c/matf#293.
-
Add draft for 3.2.2 w3c/matf#294.
-
Add draft for 2.5.3 w3c/matf#223.
-
-
5 pull requests received 16 new comments.
w3c/coga
-
5 issues opened.
-
2 w3c/coga#393, by @zabiullahsadatzaher-hue.
-
zabiullah w3c/coga#392, by @zabiullahsadatzaher-hue.
-
allblackthug1 w3c/coga#391, by @allblackthug1983-coder.
-
GGRep w3c/coga#390, by @tianaid404-byte.
-
-
4 issues closed.
-
Trabajo w3c/coga#387.
-
2 w3c/coga#393.
-
GGRep w3c/coga#390.
-
allblackthug1 w3c/coga#391.
-
w3c/wai-wcag-em
-
1 issue opened.
-
Defining scope w3c/wai-wcag-em#227, by @RenateRoke.
-
WCAG 2.x Backlog Task Force
Past meetings
-
4 meetings of the WCAG 2.x Backlog Task Force.
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
3 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Participants
-
2 participants joined the Accessibility Conformance Testing (ACT) Task Force.
-
Adam Page joined.
-
Karen Herr joined.
-
Mobile Accessibility Task Force
Past meetings
-
2 meetings of the Mobile Accessibility Task Force.
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 participant joined the Cognitive and Learning Disabilities Accessibility Task Force.
-
Bernardo Barlach joined.
-
GitHub
w3c/coga
-
5 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
2 w3c/coga#393, by @zabiullahsadatzaher-hue.
-
zabiullah w3c/coga#392, by @zabiullahsadatzaher-hue.
-
allblackthug1 w3c/coga#391, by @allblackthug1983-coder.
-
GGRep w3c/coga#390, by @tianaid404-byte.
-
-
4 issues closed in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Trabajo w3c/coga#387.
-
2 w3c/coga#393.
-
GGRep w3c/coga#390.
-
allblackthug1 w3c/coga#391.
-