Accessibility Guidelines Working Group - Activity in 2026
No matches.
Past meetings
Participants
-
5 participants joined.
-
Scott Hollier (Centre For Accessibility Australia) joined.
-
Joshua Boele (Accessibility Foundation) joined.
-
Geraint White (W3C Invited Experts) joined.
-
Mitchell Evan (W3C Invited Experts) joined.
-
Jane Berliss-Vincent (W3C Invited Experts) joined.
-
-
8 participants left.
-
Samantha McDaniel (Microsoft Corporation) left.
-
Michael Fairchild (Microsoft Corporation) left.
-
Rachael Yomtoob (W3C Invited Experts) left.
-
Martijn Houtepen (Accessibility Foundation) left.
-
Ryan Romaine (Google LLC) left.
-
Bryan Trogdon (Google LLC) left.
-
Jeffrey Yasskin (Google LLC) left.
-
Elizabeth Patrick (Wix.com Ltd.) left.
-
-
1 organization joined.
-
Centre For Accessibility Australia joined.
-
GitHub
w3c/wcag3
-
42 issues opened.
-
COGA support for copying supported w3c/wcag3#937, by @lseeman.
-
COGA support for no artificial time limits w3c/wcag3#936, by @lseeman.
-
COGA support for "Single flash" w3c/wcag3#935, by @julierawe.
-
COGA support for "Non-verbal cues identified in transcripts" w3c/wcag3#934, by @julierawe.
-
COGA support for interactive elements distinguishable w3c/wcag3#933, by @lseeman.
-
COGA support for "Figure captions persistent" w3c/wcag3#932, by @julierawe.
-
COGA support for interactive element importance indicated w3c/wcag3#931, by @lseeman.
-
COGA support for "Captions consistent" w3c/wcag3#930, by @julierawe.
-
COGA support for numerical alternatives available w3c/wcag3#929, by @lseeman.
-
COGA support for non-verbal cues identified in captions w3c/wcag3#928, by @lseeman.
-
COGA support for "Non-verbal cues identified in audio descriptions" w3c/wcag3#927, by @julierawe.
-
"Media alternatives controllable" is redundant w3c/wcag3#925, by @mitchellevan.
-
“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.
-
1 issue reopened.
-
Use headings instead of definition list to structure the glossary w3c/wcag3#870, by @iadawn.
-
-
27 issues received 51 new comments.
-
Definition of decorative images update w3c/wcag3#878 (17 comments by @alastc, @charleshalldesign, @lauracarlson, @LJWatson, @MakotoUeki, @mraccess77, @patrickhlauke, @yatil)
-
Too much contrast: halation, overstimulation, and the APCA w3c/wcag3#221 (3 comments by @charleshalldesign, @mraccess77, @sbustelo)
-
Change all occurrences of "focus" to "keyboard focus" w3c/wcag3#908 (3 comments by @hidde, @mraccess77, @TanyaVanWorkum)
-
Inconsistent reading order of headings and permalinks in guidelines doc w3c/wcag3#868 (1 comment by @philorien)
-
Consider adding blurred content to Guideline 2.6.1 Avoid physical harm w3c/wcag3#543 (1 comment by @mraccess77)
-
Use headings instead of definition list to structure the glossary w3c/wcag3#870 (1 comment by @iadawn)
-
“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)
-
-
15 pull requests opened.
-
Update reporting tier definitions and structure w3c/wcag3#939, by @alastc.
-
Place permalinks after headings (fixes #868) w3c/wcag3#938, by @philorien.
-
Update biometrics provisions w3c/wcag3#926, by @fstrr.
-
Refactors glossary to use headings instead of definition list w3c/wcag3#923, by @adampage.
-
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.
-
8 pull requests received 23 new comments.
-
Update conformance section in Explainer w3c/wcag3#864 (7 comments by @alastc, @iadawn, @tamsinewing555)
-
Move accessibility supported to a new testing section and recast it as user agent supported w3c/wcag3#902 (3 comments by @alastc, @kfranqueiro, @mcking65)
-
Revise glossary reference in relationships-detectable to use the term "programmatically detectable" w3c/wcag3#891 (2 comments by @HaTheo, @mcking65)
-
Refactors glossary to use headings instead of definition list w3c/wcag3#923 (1 comment by @mcking65)
-
w3c/wcag
-
19 issues opened.
-
Update the stylesheet used for relative-luminance.html w3c/wcag#5424, by @remibetin.
-
WCAG 2.2 JSON Duplicate Technique G101 in JSON w3c/wcag#5420, by @airbr.
-
Homegrown partial conformance w3c/wcag#5415, by @kreukelzone.
-
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.
-
-
20 issues closed.
-
Homegrown partial conformance w3c/wcag#5415.
-
[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.
-
21 issues received 65 new comments.
-
Conforming Alternate Version (CAV) and the mechanism to reach/achieve it w3c/wcag#5373 (20 comments by @alastc, @bbarlach-sys, @detlevhfischer, @goetsu, @GreggVan, @innoticFR, @mraccess77, @patrickhlauke, @yatil)
-
In Understanding, replace heading “Key Terms” with “Relevant Glossary Entries” or similar w3c/wcag#5409 (10 comments by @GreggVan, @hidde, @iadawn, @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)
-
"Are programming languages human languages?" and repercussions for text contrast requirements w3c/wcag#5369 (3 comments by @AutoSponge, @innoticFR, @wittjeff)
-
Section 5.4 Third Party Content is missnamed w3c/wcag#5263 (2 comments by @bbarlach-sys, @patrickhlauke)
-
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)
-
Is iOS's three finger zoom defined as "assistive technology" on native mobile apps? w3c/wcag#4717 (1 comment by @patrickhlauke)
-
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)
-
-
15 pull requests opened.
-
Fix i18n issues in relative-luminance.html w3c/wcag#5426, by @remibetin.
-
Update the base stylesheet used in relative-luminance.html w3c/wcag#5425, by @remibetin.
-
Update use-of-color.html w3c/wcag#5422, by @vladyslav20082008-bot.
-
Add styles to open details/summary disclosures when printing w3c/wcag#5414, by @patrickhlauke.
-
Add intro paragraph for understanding key terms section w3c/wcag#5413, by @patrickhlauke.
-
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.
-
-
3 pull requests merged.
-
Clarifications to labels or instructions SC w3c/wcag#4995.
-
Rework 2.1.4 Character Key Shortcut understanding w3c/wcag#5336.
-
-
6 pull requests closed.
-
Add styles to open details/summary disclosures when printing w3c/wcag#5414.
-
Update use-of-color.html w3c/wcag#5422.
-
Update Statement of Partial Conformance w3c/wcag#5287.
-
Update ARIA18.html w3c/wcag#5377.
-
Implemented the F13 as a 1.1.1 and 1.3.3 failure w3c/wcag#5102.
-
-
25 pull requests received 146 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)
-
Add intro paragraph for understanding key terms section w3c/wcag#5413 (14 comments by @bruce-usab, @iadawn, @kfranqueiro, @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)
-
add clarification on button indication, fix typo w3c/wcag#5411 (6 comments by @baldino-m, @patrickhlauke)
-
Update labels-or-instructions.html - adding the reqirement that the label should be permanently available w3c/wcag#2532 (5 comments by @baldino-m, @bruce-usab, @kfranqueiro)
-
Add styles to open details/summary disclosures when printing w3c/wcag#5414 (5 comments by @adampage, @patrickhlauke)
-
Add G227: Using the Map Equivalent Purpose Framework for digital geographic maps w3c/wcag#5305 (5 comments by @frastlin, @JonathanPKatz, @patrickhlauke, @SUGambler)
-
Tweak two of the examples in 3.3.2 Labels or Instructions w3c/wcag#5408 (5 comments by @adampage, @baldino-m, @patrickhlauke)
-
Update Statement of Partial Conformance w3c/wcag#5287 (4 comments by @bbarlach-sys, @mraccess77, @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)
-
Tweak 1.4.1 Use of Color understanding note wording regarding contrast w3c/wcag#5421 (1 comment by @kfranqueiro)
-
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)
-
w3c/matf
-
6 issues received 13 new comments.
-
Success Criterion 2.4.1 - Bypass Blocks - Level A w3c/matf#8 (4 comments by @geraintwhite, @pauljadam, @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.
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 participant left the Cognitive and Learning Disabilities Accessibility Task Force.
-
Samantha McDaniel left.
-
WCAG 2.x Backlog Task Force
Past meetings
-
4 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
-
6 participants joined the WCAG 3 Assertions Task Force.
-
Scott Hollier joined.
-
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
-
5 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Mobile Accessibility Task Force
Past meetings
-
2 meetings of the Mobile Accessibility Task Force.
Participants
-
1 participant joined the Mobile Accessibility Task Force.
-
Geraint White joined.
-
-
1 participant left the Mobile Accessibility Task Force.
-
Rachael Yomtoob left.
-
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.
-
-
7 participants left.
-
Michael Gilbert (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.
-
TR publications
-
1 document published.
Past meetings
Participants
-
3 participants joined.
-
Bernardo Barlach (Google LLC) joined.
-
Zamir Shaikh (BarrierBreak Solutions Private Limited) joined.
-
Lia Carrari Rodrigues Lopes (Google LLC) joined.
-
-
7 participants left.
-
Jackie Fei (Taiwan Digital Publishing Forum) left.
-
Trevor Bostic (MITRE Corporation) left.
-
Tayef Farrar (CVS Pharmacy, Inc.) left.
-
Megan Pletzer (Deque Systems, Inc.) left.
-
Rachael Yomtoob (Deque Systems, Inc.) left.
-
Sailesh Panchang (Deque Systems, Inc.) left.
-
Priti Rohra (BarrierBreak Solutions Private Limited) left.
-
-
3 organizations left.
-
Taiwan Digital Publishing Forum left.
-
MITRE Corporation left.
-
Discover Financial Services LLC left.
-
GitHub
w3c/wcag
-
20 issues opened.
-
[spam] w3c/wcag#5231, by @g6513492gmai.
-
[spam] w3c/wcag#5226, by @kyledalton16-hub.
-
[spam] w3c/wcag#5224, by @wsx999outlook.
-
[spam] w3c/wcag#5223, by @wsx999outlook.
-
[spam] w3c/wcag#5222, by @gyi45636-hub.
-
[spam] w3c/wcag#5221, by @gyi45636-hub.
-
[spam] w3c/wcag#5220, by @gyi45636-hub.
-
[spam] w3c/wcag#5218, by @usamafulani31-wq.
-
[spam] w3c/wcag#5214, by @ivancmarius014-design.
-
[spam] w3c/wcag#5205, by @dahw67700-hue.
-
[spam] w3c/wcag#5204, by @dahw67700-hue.
-
[spam] w3c/wcag#5203, by @dahw67700-hue.
-
[spam] w3c/wcag#5202, by @chaiphet6669-afk.
-
[spam] w3c/wcag#5201, by @jillschard57-alt.
-
[spam] w3c/wcag#5198, by @arounagengane-sys.
-
[spam] w3c/wcag#5197, by @arounagengane-sys.
-
-
30 issues closed.
-
Change technique G183 from sufficient to advisory? w3c/wcag#2310.
-
Understanding Conformance 2.1 only talks about 2.0 w3c/wcag#967.
-
[spam] w3c/wcag#5231.
-
[spam] w3c/wcag#5226.
-
errata for 2.1 change log w3c/wcag#4915.
-
[spam] w3c/wcag#5223.
-
[spam] w3c/wcag#5224.
-
[spam] w3c/wcag#5222.
-
[spam] w3c/wcag#5221.
-
[spam] w3c/wcag#5220.
-
[spam] w3c/wcag#5218.
-
4.1.2 Name, role, value: Update example section? w3c/wcag#4997.
-
WCAG Wiki Scrolling w3c/wcag#4736.
-
[spam] w3c/wcag#5214.
-
[spam] w3c/wcag#5198.
-
[spam] w3c/wcag#5201.
-
[spam] w3c/wcag#5204.
-
[spam] w3c/wcag#5205.
-
[spam] w3c/wcag#5203.
-
[spam] w3c/wcag#5202.
-
[spam] w3c/wcag#5197.
-
-
13 issues received 44 new comments.
-
G143: Conflation of non-text alternative text and form control instructions w3c/wcag#5227 (9 comments by @bruce-usab, @detlevhfischer, @innoticFR)
-
SC 2.5.8 Target Size implications for ToC w3c/wcag#4540 (8 comments by @bruce-usab, @detlevhfischer, @gundulaniemann, @patrickhlauke)
-
The meta refresh element and HTTP Refresh header with zero timeout can trigger 2.3.1/2.3.2 w3c/wcag#1012 (3 comments by @cstrobbe, @patrickhlauke)
-
2.5.8 Larger target sizes could conflict with people needing page zoom w3c/wcag#1381 (1 comment by @kyledalton16-hub)
-
Working example #2 of the ARIA21 Technique does not work as described w3c/wcag#4779 (1 comment by @patrickhlauke)
-
Autocomplete for passwords is discouraged for security concerns (WCAG 2.1 Success Criterion 1.3.5) w3c/wcag#2110 (1 comment by @patrickhlauke)
-
1.3.5 Identify Input Purpose - What to Do When the Browser Is Too Helpful w3c/wcag#5195 (1 comment by @patrickhlauke)
-
SCR28 ("Using an expandable and collapsible menu to bypass block of content") is showing its age w3c/wcag#3654 (1 comment by @detlevhfischer)
-
-
17 pull requests opened.
-
Build: Upgrade dependencies found in npm audit w3c/wcag#5242, by @kfranqueiro.
-
Fix various grammatical errors w3c/wcag#5241, by @kfranqueiro.
-
Fix typos in requirements notes and conformance challenges w3c/wcag#5239, by @Gabriel-Dalton.
-
Fix repeated word, run-together sentences and punctuation slips w3c/wcag#5238, by @Gabriel-Dalton.
-
Chore: run all `.png` images through `pngcrush` w3c/wcag#5229, by @patrickhlauke.
-
Fix grammar and punctuation issues across documentation w3c/wcag#5219, by @Gabriel-Dalton.
-
Build: Store cheerio results that are repeatedly referenced w3c/wcag#5216, by @kfranqueiro.
-
Build: Upgrade slugify and specify transliterate: false to save 2s w3c/wcag#5215, by @kfranqueiro.
-
Update understanding conformance to explain why it talks about 2.0 w3c/wcag#5209, by @patrickhlauke.
-
Update F74.html w3c/wcag#5192, by @detlevhfischer.
-
Add Adam Page to informative docs footer w3c/wcag#5190, by @kfranqueiro.
-
Restore token configuration for deploy workflow w3c/wcag#5188, by @kfranqueiro.
-
-
17 pull requests merged.
-
Chore: run all `.png` images through `pngcrush` w3c/wcag#5229.
-
Rework G183 to be purely about contrast ratio w3c/wcag#5186.
-
Build: Store cheerio results that are repeatedly referenced w3c/wcag#5216.
-
Avoid focus outline "hugging" container w3c/wcag#5184.
-
Change the example for 4.1.2 Name, Role, Value understanding w3c/wcag#5045.
-
Add Adam Page to informative docs footer w3c/wcag#5190.
-
Restore token configuration for deploy workflow w3c/wcag#5188.
-
Define explicit permissions for publish workflow w3c/wcag#5173.
-
-
3 pull requests closed.
-
Fix grammar and punctuation issues across documentation w3c/wcag#5219.
-
20 pull requests received 79 new comments.
-
Rework G183 to be purely about contrast ratio w3c/wcag#5186 (18 comments by @andrewhick, @bruce-usab, @detlevhfischer, @giacomo-petri, @mraccess77, @patrickhlauke)
-
Rename Focus Not Obscured SCs to Focused Component Not Obscured w3c/wcag#5183 (8 comments by @bruce-usab, @fstrr, @ljkoakley, @patrickhlauke, @yatil)
-
Update understanding conformance to explain why it talks about 2.0 w3c/wcag#5209 (8 comments by @detlevhfischer, @patrickhlauke)
-
Fix grammar and punctuation issues across documentation w3c/wcag#5219 (4 comments by @kfranqueiro, @patrickhlauke, @w3cbot)
-
Avoid focus outline "hugging" container w3c/wcag#5184 (4 comments by @adampage, @bruce-usab, @giacomo-petri)
-
Reinstate G200 only as advisory for 3.2.5 Change on Request, strip "secure session" inaccuracy w3c/wcag#5187 (4 comments by @baldino-m, @detlevhfischer, @patrickhlauke)
-
3.2.4 understanding: Reword examples w3c/wcag#5022 (3 comments by @bruce-usab, @kfranqueiro, @patrickhlauke)
-
Clarify 1.4.13 Content on Hover or Focus understanding explanation for "Dismissible" w3c/wcag#5175 (3 comments by @fstrr, @patrickhlauke)
-
Change mention of "numbered item" to just "item" / "numbered technique" to just "technique" w3c/wcag#5235 (2 comments by @bruce-usab)
-
Add extra (non-normative) note to the definition of "conforming alternate version" w3c/wcag#5236 (2 comments by @bruce-usab)
-
Add new examples and resource link to Understanding Three Flashes or Below Threshold w3c/wcag#5228 (2 comments by @detlevhfischer, @thealexmosk)
-
Understanding techniques: change "Numbered list" to just "List" and simplify w3c/wcag#5200 (2 comments by @baldino-m, @patrickhlauke)
-
Fix repeated word, run-together sentences and punctuation slips w3c/wcag#5238 (1 comment by @kfranqueiro)
-
w3c/wcag3
-
9 issues opened.
-
Approach to ACT tests and accessibilty supported w3c/wcag3#771, by @alastc.
-
[spam] w3c/wcag3#758, by @anassandoval65-sketch.
-
[spam] w3c/wcag3#749, by @lb1644861-spec.
-
"Speakers identified" should apply beyond video content w3c/wcag3#748, by @ashleemboyer.
-
"Transcripts available" does not account for signed content w3c/wcag3#747, by @ashleemboyer.
-
Update the definition of text w3c/wcag3#744, by @alastc.
-
6 issues closed.
-
Recommend removing “Keyboard navigable if responsive” w3c/wcag3#599.
-
[spam] w3c/wcag3#758.
-
[spam] w3c/wcag3#749.
-
[Transcripts Available] background video unclear w3c/wcag3#519.
-
Requirements: Keyboard only w3c/wcag3#267.
-
10 issues received 40 new comments.
-
Ambiguity of the term "character" and its impact on internationalization and testability w3c/wcag3#546 (12 comments by @alastc, @asmusf, @mraccess77, @murata2makoto)
-
Update the definition of text w3c/wcag3#744 (8 comments by @alastc, @charleshalldesign, @hidde, @murata2makoto)
-
Can flashing requirements account for zoom? w3c/wcag3#631 (5 comments by @GreggVan, @gundulaniemann, @WilcoFiers)
-
[Transcripts Available] background video unclear w3c/wcag3#519 (5 comments by @camusamta, @lauracarlson, @MakotoUeki)
-
"Sentences do not include unnecessary words" is not internationally testable w3c/wcag3#742 (4 comments by @alastc, @mraccess77, @murata2makoto, @patrickhlauke)
-
Pseudo-motion: Expand to include examples, and consider making this its own provision. w3c/wcag3#739 (2 comments by @mraccess77, @rachaelbradley)
-
Keyboard navigable if responsive. - breakpoints are problematic. w3c/wcag3#608 (1 comment by @iadawn)
-
Should Text and Wording add Japanese as a guardrail language? w3c/wcag3#553 (1 comment by @murata2makoto)
-
-
30 pull requests opened.
-
Move Applies when back to in-order; collapse single bullet to inline w3c/wcag3#781, by @kfranqueiro.
-
Build: Upgrade dependencies found in npm audit w3c/wcag3#780, by @kfranqueiro.
-
Dev: Fix link to dev page for renaming provisions w3c/wcag3#779, by @kfranqueiro.
-
Reflect WCAG_PUBLISH behavior in informative provision lists w3c/wcag3#777, by @kfranqueiro.
-
Move Tests to informative (and remove :::tests directive) w3c/wcag3#776, by @kfranqueiro.
-
Add build system for ACT working examples w3c/wcag3#774, by @adampage.
-
Motion updates survey 2 w3c/wcag3#773, by @alastc.
-
frontload what we are giving examples of, merge last two w3c/wcag3#772, by @hidde.
-
Sign language batch 2 w3c/wcag3#770, by @iadawn.
-
Removed guardrail languages + other changes to blocks-of-text-a… w3c/wcag3#768, by @julierawe.
-
Removed guardrail languages + other changes to text-style-readable-en… w3c/wcag3#767, by @julierawe.
-
Removed guardrail languages + other changes to text-style-readable-mi… w3c/wcag3#766, by @julierawe.
-
Removed guardrail languages from blocks-of-text-readable-enhanced.md w3c/wcag3#765, by @julierawe.
-
Removed table and other changes to blocks-of-text-readable-minimum.md w3c/wcag3#764, by @julierawe.
-
Build: Move "Applies when" to top; enforce containing a list w3c/wcag3#763, by @kfranqueiro.
-
Added two paragraphs to ed note in text-appearance.md w3c/wcag3#762, by @julierawe.
-
Add publishing system for ACT working examples w3c/wcag3#760, by @adampage.
-
Informative docs: Don't list or render pages for empty entries w3c/wcag3#759, by @kfranqueiro.
-
Shorten 3rd ed note in clear-language.md w3c/wcag3#757, by @julierawe.
-
update state definition w3c/wcag3#756, by @fstrr.
-
Add content from WCAG 2.2 Understanding w3c/wcag3#755, by @tamsinewing555.
-
Develop informative materials for 2.8.1 Consistency w3c/wcag3#753, by @iadawn.
-
Add informative materials for 2.8.1 Consistency w3c/wcag3#752, by @iadawn.
-
Update pointer pressure not relied upon w3c/wcag3#751, by @fstrr.
-
update to needs more research w3c/wcag3#750, by @rachaelbradley.
-
Removing the programmatically determinable part of "text" w3c/wcag3#746, by @alastc.
-
Add informative site footer with last modified date and history URL w3c/wcag3#745, by @kfranqueiro.
-
Add sign language equivalent requirement w3c/wcag3#743, by @iadawn.
-
-
26 pull requests merged.
-
Move Tests to informative (and remove :::tests directive) w3c/wcag3#776.
-
Dev: Fix link to dev page for renaming provisions w3c/wcag3#779.
-
update to needs more research w3c/wcag3#750.
-
Remove “Keyboard navigable if responsive” provision w3c/wcag3#666.
-
Move informative links to headings; float issues links w3c/wcag3#731.
-
Simplify simple-pointer-input-available.md w3c/wcag3#652.
-
clarify view definition based on feedback in WCAG-EM w3c/wcag3#630.
-
Shorten 3rd ed note in clear-language.md w3c/wcag3#757.
-
frontload what we are giving examples of, merge last two w3c/wcag3#772.
-
Added two paragraphs to ed note in text-appearance.md w3c/wcag3#762.
-
Edit Graphical Object Contrast Sufficient typo w3c/wcag3#681.
-
Explainer editorial suggestions 2.2 Out of Scope w3c/wcag3#594.
-
Page/view title available - Updates after survey w3c/wcag3#696.
-
Build: Move "Applies when" to top; enforce containing a list w3c/wcag3#763.
-
Fix typecheck errors (mostly affecting dev pages) w3c/wcag3#730.
-
-
5 pull requests closed.
-
Add publishing system for ACT working examples w3c/wcag3#760.
-
Exploring presentation of links to informative materials w3c/wcag3#685.
-
Add content from WCAG 2.2 Understanding w3c/wcag3#755.
-
Add informative materials for 2.8.1 Consistency w3c/wcag3#752.
-
30 pull requests received 125 new comments.
-
Page/view title available - Updates after survey w3c/wcag3#696 (15 comments by @alastc, @fstrr, @giacomo-petri)
-
Update pointer pressure not relied upon w3c/wcag3#751 (11 comments by @fstrr, @iadawn, @patrickhlauke)
-
Add build system for ACT working examples w3c/wcag3#774 (5 comments by @adampage, @kfranqueiro, @WilcoFiers)
-
Add informative site footer with last modified date and history URL w3c/wcag3#745 (3 comments by @iadawn, @shawna-slh)
-
Rework “No repetitive links” as “No adjacent interactive elements” w3c/wcag3#602 (2 comments by @adampage)
-
Removed guardrail languages + other changes to text-style-adjustable.md w3c/wcag3#769 (2 comments by @iadawn, @rachaelbradley)
-
Removed guardrail languages + other changes to text-style-readable-en… w3c/wcag3#767 (2 comments by @iadawn, @rachaelbradley)
-
Removed guardrail languages + other changes to text-style-readable-mi… w3c/wcag3#766 (2 comments by @iadawn, @rachaelbradley)
-
Removed table and other changes to blocks-of-text-readable-minimum.md w3c/wcag3#764 (2 comments by @iadawn, @rachaelbradley)
-
Informative docs: Don't list or render pages for empty entries w3c/wcag3#759 (1 comment by @kfranqueiro)
-
Removed guardrail languages + other changes to blocks-of-text-a… w3c/wcag3#768 (1 comment by @rachaelbradley)
-
Removed guardrail languages from blocks-of-text-readable-enhanced.md w3c/wcag3#765 (1 comment by @rachaelbradley)
-
[Errors indicated] Make it more clear this is about textual indication w3c/wcag3#571 (1 comment by @hidde)
w3c/matf
-
6 issues received 15 new comments.
-
Define 'mobile operating systems' in scope w3c/matf#102 (4 comments by @detlevhfischer, @JJdeGroot, @shoobe01)
-
Definition of "user agent" in mobile application context w3c/matf#63 (3 comments by @jha11y, @TanyaVanWorkum)
-
SUB - Accessibility interface - Figure out where the accessibility interface definition should be used w3c/matf#247 (2 comments by @jwlilly, @TanyaVanWorkum)
-
Success Criterion 2.5.8 - Target Size (Minimum) - Level AA w3c/matf#10 (2 comments by @detlevhfischer, @TanyaVanWorkum)
-
-
4 pull requests opened.
-
2.5.7 update content w3c/matf#295, by @JJdeGroot.
-
Add draft for 3.2.2 w3c/matf#294, by @jha11y.
-
Add new definitions w3c/matf#293, by @JJdeGroot.
-
Add new contributors w3c/matf#292, by @JJdeGroot.
-
-
1 pull request merged.
-
Add new contributors w3c/matf#292.
-
-
4 pull requests received 8 new comments.
w3c/wai-wcag-em
-
7 issues opened.
-
A few minor typos w3c/wai-wcag-em#222, by @KateZhaoTR.
-
Section 3 cross-reference numbering typo w3c/wai-wcag-em#220, by @KateZhaoTR.
-
Random sample set w3c/wai-wcag-em#219, by @detlevhfischer.
-
Sampling vs. all views w3c/wai-wcag-em#218, by @detlevhfischer.
-
regular expressions w3c/wai-wcag-em#217, by @detlevhfischer.
-
sample vs sample set w3c/wai-wcag-em#216, by @detlevhfischer.
-
2 issues closed.
-
A few minor typos w3c/wai-wcag-em#222.
-
Section 3 cross-reference numbering typo w3c/wai-wcag-em#220.
-
-
5 issues received 6 new comments.
-
5 pull requests opened.
-
Update README.md w3c/wai-wcag-em#226, by @hidde.
-
update acks w3c/wai-wcag-em#225, by @hidde.
-
Pre publication minor fixes w3c/wai-wcag-em#223, by @iadawn.
-
Fix typo in reference w3c/wai-wcag-em#221, by @hidde.
-
link to specific w3 version w3c/wai-wcag-em#215, by @hidde.
-
-
4 pull requests merged.
-
update acks w3c/wai-wcag-em#225.
-
Pre publication minor fixes w3c/wai-wcag-em#223.
-
Fix typo in reference w3c/wai-wcag-em#221.
-
link to specific w3 version w3c/wai-wcag-em#215.
-
w3c/coga
-
1 issue opened.
-
Trabajo w3c/coga#387, by @kvincoreas-cmd.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
SECURITY.mdCreate SECURITY.md w3c/coga#388, by @kvincoreas-cmd.
-
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
-
6 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Mobile Accessibility Task Force
Past meetings
-
3 meetings of the Mobile Accessibility Task Force.
Participants
-
2 participants left the Mobile Accessibility Task Force.
-
Megan Pletzer left.
-
Rachael Yomtoob left.
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
1 issue opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Trabajo w3c/coga#387, by @kvincoreas-cmd.
-
-
1 issue in the Cognitive and Learning Disabilities Accessibility Task Force received 1 new comment.
-
1 pull request opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
SECURITY.mdCreate SECURITY.md w3c/coga#388, by @kvincoreas-cmd.
-
Past meetings
Participants
-
4 participants joined.
-
Martijn Houtepen (Accessibility Foundation) joined.
-
John Lilly (TPGi) joined.
-
Matthew King (W3C Invited Experts) joined.
-
Nikolay Yordanov (SAP SE) joined.
-
-
3 participants left.
-
Shelby Mitchell (Discover Financial Services LLC) left.
-
Mitchell Evan (W3C Invited Experts) left.
-
Charu Pandhi (TPGi) left.
-
-
1 organization joined.
-
Accessibility Foundation joined.
-
GitHub
w3c/matf
-
1 issue opened.
-
14 issues closed.
-
Success Criterion 3.1.1 - Language of Page - Level A w3c/matf#14.
-
Success Criterion 2.4.2 - Page Titled - Level A w3c/matf#9.
-
1 issue reopened.
-
26 issues received 95 new comments.
-
Success Criterion 2.5.8 - Target Size (Minimum) - Level AA w3c/matf#10 (16 comments by @JJdeGroot, @jwlilly, @shoobe01, @TanyaVanWorkum)
-
Definition of the (underlaying) layer is in a mobile application / mobile platform w3c/matf#270 (14 comments by @JJdeGroot, @rwapp, @shoobe01, @TanyaVanWorkum)
-
Definition of "user agent" in mobile application context w3c/matf#63 (13 comments by @jha11y, @JJdeGroot, @shoobe01, @TanyaVanWorkum)
-
Definition of "set of Web pages / set of software programs" in mobile application context w3c/matf#11 (11 comments by @JJdeGroot, @shoobe01, @TanyaVanWorkum)
-
Success Criterion 2.5.3 - Label in Name - Level A w3c/matf#39 (10 comments by @detlevhfischer, @JJdeGroot, @jwlilly, @pauljadam, @TanyaVanWorkum)
-
Define 'mobile operating systems' in scope w3c/matf#102 (6 comments by @JJdeGroot, @shoobe01, @TanyaVanWorkum)
-
SUB - Accessibility interface - Figure out where the accessibility interface definition should be used w3c/matf#247 (2 comments by @shoobe01, @TanyaVanWorkum)
-
SUB - 2.5.7 - Dragging Movements - Clarify what the layer is in a mobile application / mobile platform w3c/matf#212 (1 comment by @JJdeGroot)
-
SUB - SC 2.5.7: Dragging Movements (Level AA) does not have a scroll bar example w3c/matf#111 (1 comment by @JJdeGroot)
-
SUB - 3.1.1 - Language of Page - Add Note with exception for Android, and indicating how to meet it on iOS w3c/matf#165 (1 comment by @JJdeGroot)
-
SUB - 2.4.2 - Page Titled - Think about semantic requirements for identifying titles? w3c/matf#153 (1 comment by @JJdeGroot)
-
-
2 pull requests opened.
-
Add draft for 2.5.8 w3c/matf#291, by @JJdeGroot.
-
Use local HTML instead of hosted to bypass Cloudflare checks w3c/matf#290, by @JJdeGroot.
-
-
4 pull requests merged.
-
Add draft for 2.5.7 w3c/matf#286.
-
Add draft for 3.1.1 w3c/matf#287.
-
Add draft for 2.4.2 w3c/matf#288.
w3c/wcag3
-
10 issues opened.
-
Need to change the name for “Trigger warning available” w3c/wcag3#736, by @julierawe.
-
[spam] w3c/wcag3#716, by @keshineroyusuf1.
-
[spam] w3c/wcag3#714, by @schnurjennifer1-hue.
-
Page/view title - Ambiguity when applied to non-HTML documents w3c/wcag3#694, by @giacomo-petri.
-
4 issues closed.
-
[spam] w3c/wcag3#716.
-
[spam] w3c/wcag3#714.
-
Proposal for a WCAG Content API w3c/wcag3#84.
-
1 issue reopened.
-
[spam] w3c/wcag3#704, by @patrickhlauke.
-
-
14 issues received 48 new comments.
-
WCAG 3.0 Working Draft — Comment on Autonomous Agents as Primary and Proxy Users w3c/wcag3#636 (24 comments by @alastc, @GreggVan, @hidde, @iadawn, @patrickhlauke, @theaeaton24, @yatil)
-
Page/view title - Ambiguity when applied to non-HTML documents w3c/wcag3#694 (5 comments by @alastc, @giacomo-petri, @GreggVan, @maryjom)
-
Supplemental rather than assertion? - Sign language live (Assertion) w3c/wcag3#471 (3 comments by @iadawn, @md84419)
-
If such a guideline doesn't exist yet, some form of guideline around heartbeat audio? w3c/wcag3#683 (3 comments by @fstrr, @glkdrlgkrlzflnjkgh)
-
A single volume control on a player? - Audio description volume (Supplemental) w3c/wcag3#456 (2 comments by @GreggVan, @maryjom)
-
The definition of "minimum bounding box" does not allow vertical writing w3c/wcag3#672 (2 comments by @alastc, @murata2makoto)
-
Ambiguity of the term "character" and its impact on internationalization and testability w3c/wcag3#546 (1 comment by @alastc)
-
Please adjust 3.1.1 - the definitions of core and supplemental, so WCAG 3 is more equitable. w3c/wcag3#653 (1 comment by @alastc)
-
-
26 pull requests opened.
-
User control user needs statements review w3c/wcag3#741, by @tamsinewing555.
-
Text and wording user needs statements review w3c/wcag3#740, by @tamsinewing555.
-
Process and task completion user needs statements review w3c/wcag3#732, by @tamsinewing555.
-
Move informative links to headings; float issues links w3c/wcag3#731, by @kfranqueiro.
-
Fix typecheck errors (mostly affecting dev pages) w3c/wcag3#730, by @kfranqueiro.
-
Add workflow that runs both typechecks and build; update .nvmrc w3c/wcag3#729, by @kfranqueiro.
-
Layout user needs statements review w3c/wcag3#727, by @tamsinewing555.
-
Input/operation user needs statements review w3c/wcag3#726, by @tamsinewing555.
-
Interactive components user needs statements review w3c/wcag3#725, by @tamsinewing555.
-
Error handling user needs statements review w3c/wcag3#721, by @tamsinewing555.
-
Help and feedback user needs statements review w3c/wcag3#720, by @tamsinewing555.
-
Policy and protection user needs statements review w3c/wcag3#719, by @tamsinewing555.
-
Consistency across views user needs statements review w3c/wcag3#718, by @tamsinewing555.
-
Animation and movement user needs statements review w3c/wcag3#717, by @tamsinewing555.
-
Configure Shiki theme for code snippets w3c/wcag3#715, by @kfranqueiro.
-
Images and media user needs statements review w3c/wcag3#713, by @tamsinewing555.
-
Guideline 2.1.1 Image alternatives: Review user needs statements w3c/wcag3#712, by @tamsinewing555.
-
Perform minor/patch dependency updates related to npm audit w3c/wcag3#711, by @kfranqueiro.
-
Upgrade actions to recent versions relying on Node v24 w3c/wcag3#710, by @kfranqueiro.
-
update definition of Interactive Element w3c/wcag3#702, by @fstrr.
-
Multi-step process provisions w3c/wcag3#701, by @giacomo-petri.
-
Page/view title available - Updates after survey w3c/wcag3#696, by @giacomo-petri.
-
Clean up defunct properties in respecConfigs, and add class="remove" w3c/wcag3#686, by @kfranqueiro.
-
Exploring presentation of links to informative materials w3c/wcag3#685, by @iadawn.
-
Remove tabindex added to syntax-highlighted pre elements by Shiki w3c/wcag3#684, by @kfranqueiro.
-
-
8 pull requests merged.
-
Configure Shiki theme for code snippets w3c/wcag3#715.
-
Perform minor/patch dependency updates related to npm audit w3c/wcag3#711.
-
Upgrade actions to recent versions relying on Node v24 w3c/wcag3#710.
-
Refine “Custom keys documented” provision w3c/wcag3#665.
-
-
1 pull request closed.
-
20 pull requests received 111 new comments.
-
Interactive components user needs statements review w3c/wcag3#725 (31 comments by @iadawn, @tamsinewing555)
-
Images and media user needs statements review w3c/wcag3#713 (21 comments by @iadawn, @tamsinewing555)
-
update definition of Interactive Element w3c/wcag3#702 (12 comments by @adampage, @fstrr, @giacomo-petri, @hidde, @iadawn)
-
Exploring presentation of links to informative materials w3c/wcag3#685 (7 comments by @fstrr, @hidde, @iadawn, @kfranqueiro)
-
Rework “No repetitive links” as “No adjacent interactive elements” w3c/wcag3#602 (7 comments by @fstrr, @iadawn)
-
Exploring presentation of links to informative materials, toggletip edition w3c/wcag3#709 (5 comments by @hidde, @iadawn, @kfranqueiro)
-
Text and wording user needs statements review w3c/wcag3#740 (4 comments by @julierawe, @tamsinewing555)
-
Remove tabindex added to syntax-highlighted pre elements by Shiki w3c/wcag3#684 (2 comments by @hidde, @kfranqueiro)
-
[Errors indicated] Make it more clear this is about textual indication w3c/wcag3#571 (1 comment by @iadawn)
-
w3c/wcag
-
18 issues opened.
-
[spam] w3c/wcag#5182, by @maxicosportsport-stack.
-
[SPAM] w3c/wcag#5180, by @maxicosportsport-stack.
-
[spam] w3c/wcag#5179, by @maxicosportsport-stack.
-
[spam] w3c/wcag#5177, by @xitlaliguadaluperodriguezcamo-ctrl.
-
[spam] w3c/wcag#5174, by @colemanlarry016-alt.
-
2.5.3 Label in name, F96 example for logos w3c/wcag#5171, by @detlevhfischer.
-
[SPAM] w3c/wcag#5164, by @financialgrant.
-
Updates to G183 now no longer need underline on focus (or anytime!) w3c/wcag#5162, by @mbgower.
-
[spam] w3c/wcag#5161, by @ahyf113113-bot.
-
[spam] w3c/wcag#5160, by @n5f92h948r-jpg.
-
Language in benefit is unclear w3c/wcag#5157, by @iadawn.
-
What to do text of 1.2.3 understanding document w3c/wcag#5156, by @goetsu.
-
1.1.1/1.2: Does "time-based media" include short animations? w3c/wcag#5155, by @dbjorge.
-
[spam] w3c/wcag#5152, by @financialgrant.
-
[spam] w3c/wcag#5150, by @creatorf16.
-
[spam] w3c/wcag#5148, by @eishyaripriya-commits.
-
40 issues closed.
-
1.4.5 Benefits section lists beneficiaries w3c/wcag#4334.
-
Language in benefit is unclear w3c/wcag#5157.
-
Should C40 be also sufficient for 1.4.11 Non-Text Contrast? w3c/wcag#2575.
-
3.1.2 Lang of Parts exceptions need to be Key Terms w3c/wcag#4094.
-
add definition for “path-based gesture” for 2.2 w3c/wcag#758.
-
[spam] w3c/wcag#5182.
-
Text Spacing and Resize Text used in combination? w3c/wcag#4877.
-
[spam] w3c/wcag#5174.
-
[SPAM] w3c/wcag#5180.
-
[spam] w3c/wcag#5179.
-
[spam] w3c/wcag#5177.
-
WCAG 2.0 errata missing from WCAG 2.0 w3c/wcag#920.
-
F34 references a removed future technique w3c/wcag#5126.
-
[SPAM] w3c/wcag#5164.
-
[spam] w3c/wcag#5161.
-
[spam] w3c/wcag#5160.
-
improve About pages w3c/wcag#2880.
-
[spam] w3c/wcag#5152.
-
Improving links from WCAG TR definitions to Understanding w3c/wcag#4066.
-
[spam] w3c/wcag#5150.
-
[spam] w3c/wcag#5148.
-
1.4.4 and 1.4.10 – Refresh or not? w3c/wcag#4884.
-
3.1.2 Language of Parts clarification w3c/wcag#4113.
-
On Input understanding doc makes broad strokes about buttons w3c/wcag#5059.
-
25 issues received 69 new comments.
-
Does SC 1.2.1 require the alternative for time-based media for video-only to be visible? w3c/wcag#3642 (24 comments by @alastc, @awkawk, @bruce-usab, @dbjorge, @GreggVan, @innoticFR, @lauracarlson, @MakotoUeki, @mraccess77)
-
3.3.8/3.3.9: How is "authentication process" defined? w3c/wcag#3264 (5 comments by @patrickhlauke, @sander-nl, @TestPartners)
-
Clarify whether SC 1.3.1 requires grouped links to be in a list structure w3c/wcag#1159 (3 comments by @bruce-usab, @goetsu, @patrickhlauke)
-
Updates to G183 now no longer need underline on focus (or anytime!) w3c/wcag#5162 (3 comments by @mraccess77, @patrickhlauke)
-
H53 Using the body of the object element is not practically supported w3c/wcag#1138 (3 comments by @innoticFR, @patrickhlauke)
-
1.1.1/1.2: Does "time-based media" include short animations? w3c/wcag#5155 (3 comments by @detlevhfischer, @innoticFR, @patrickhlauke)
-
Paragraph symbol used for self-link in spec has insufficient contrast, looks awkward with the underline w3c/wcag#5185 (1 comment by @patrickhlauke)
-
Unclear if focus indicator counts when determining if the focus is obscured w3c/wcag#3950 (1 comment by @patrickhlauke)
-
Add HTML examples to WCAG 2.5.3 label-in-name.html#examples w3c/wcag#4994 (1 comment by @detlevhfischer)
-
-
17 pull requests opened.
-
Rework G183 to be purely about contrast ratio w3c/wcag#5186, by @patrickhlauke.
-
Avoid focus outline "hugging" container w3c/wcag#5184, by @patrickhlauke.
-
Rename Focus Not Obscured SCs to Focused Component Not Obscured w3c/wcag#5183, by @patrickhlauke.
-
Summer 2026 errata for WCAG 2.1 / 2.2 w3c/wcag#5176, by @patrickhlauke.
-
Define explicit permissions for publish workflow w3c/wcag#5173, by @kfranqueiro.
-
Update github actions and .nvmrc to rely on Node 24 w3c/wcag#5167, by @kfranqueiro.
-
Commit updates to techniques change log w3c/wcag#5166, by @kfranqueiro.
-
Fix About Techniques link added in #5002 w3c/wcag#5159, by @kfranqueiro.
-
Tweak On Input understanding benefits w3c/wcag#5158, by @patrickhlauke.
-
Replace explicit TR/WCAG2X references with relative link or variable w3c/wcag#5151, by @kfranqueiro.
-
Clean up respecConfigs w3c/wcag#5147, by @kfranqueiro.
-
CI: Stop building requirements doc in publish workflow w3c/wcag#5146, by @kfranqueiro.
-
28 pull requests merged.
-
Expand 1.4.5 Images of Text benefits w3c/wcag#5065.
-
Tweak On Input understanding benefits w3c/wcag#5158.
-
Expand consistent navigation understanding intent w3c/wcag#4833.
-
Update github actions and .nvmrc to rely on Node 24 w3c/wcag#5167.
-
Commit updates to techniques change log w3c/wcag#5166.
-
Add two in-page links to Understanding Non-Text Contrast w3c/wcag#5128.
-
Tweak PDF2 intent w3c/wcag#5069.
-
Remove left-over mention of non-existent technique in F34 w3c/wcag#5132.
-
Reformat tables out of Understanding 1.4.11 w3c/wcag#4960.
-
Fix About Techniques link added in #5002 w3c/wcag#5159.
-
Update branch from main w3c/wcag#5118.
-
Clean up respecConfigs w3c/wcag#5147.
-
CI: Stop building requirements doc in publish workflow w3c/wcag#5146.
-
Update On Input to address different button types w3c/wcag#5107.
-
-
6 pull requests closed.
-
Tweaks to G183 w3c/wcag#2508.
-
Initial draft for Spring 2026 Errata w3c/wcag#5033.
-
Clarify SC 3.3.2 phone number example wording w3c/wcag#5025.
-
Clarify Dismissible paragraph in Understanding SC 1.4.13 w3c/wcag#5030.
-
Update Understanding "focus visible" (SC 2.4.7) w3c/wcag#1022.
-
Add "also" to Note 1 for 2.2.2 Pause, Stop, Hide w3c/wcag#5130.
-
-
28 pull requests received 78 new comments.
-
Add note to 1.4.4 Resize Text to explicitly mention that UA-controlled text is not covered w3c/wcag#5181 (7 comments by @bruce-usab, @patrickhlauke)
-
Focus obscured and semi-transparent/blurred overlays - reword, and DO make it fail at AAA w3c/wcag#4824 (5 comments by @awkawk, @gundulaniemann, @hidde, @patrickhlauke)
-
Reformat tables out of Understanding 1.4.11 w3c/wcag#4960 (5 comments by @adampage, @gundulaniemann, @hidde, @patrickhlauke)
-
Update G206 to explicitly reference 1.4.8 / 1.4.10 w3c/wcag#1024 (5 comments by @gundulaniemann, @patrickhlauke, @scottaohara)
-
Change 'serialize' to 'linearize' in Note 2 of Consistent Help w3c/wcag#5119 (4 comments by @awkawk, @bruce-usab, @GreggVan, @patrickhlauke)
-
Expand 1.4.5 Images of Text benefits w3c/wcag#5065 (4 comments by @adampage, @awkawk, @bruce-usab, @patrickhlauke)
-
Add two in-page links to Understanding Non-Text Contrast w3c/wcag#5128 (3 comments by @bruce-usab, @patrickhlauke)
-
Add a cross-reference from 2.4.7 focus visible understanding to 1.4.11 non-text contrast w3c/wcag#5067 (2 comments by @patrickhlauke)
-
Add note to 3.1.2 Language of Parts to clarify single words can be phrases/passages w3c/wcag#5178 (1 comment by @bruce-usab)
-
Clarify 1.4.13 Content on Hover or Focus understanding explanation for "Dismissible" w3c/wcag#5175 (1 comment by @bruce-usab)
-
Rework note and example in definition of "image of text" w3c/wcag#5013 (1 comment by @patrickhlauke)
-
Clarify Dismissible paragraph in Understanding SC 1.4.13 w3c/wcag#5030 (1 comment by @patrickhlauke)
-
Remove G200, tweak G201 to apply to links and buttons, fix association of the technique with appropriate SCs w3c/wcag#4955 (1 comment by @bruce-usab)
-
Amend "contrast ratio" term - move out non-term notes to understanding docs w3c/wcag#4400 (1 comment by @patrickhlauke)
-
Add a non-normative explanation of "proper name" to 3.1.2 Language of Parts understanding w3c/wcag#5135 (1 comment by @patrickhlauke)
w3c/wai-wcag-em
-
4 issues received 8 new comments.
-
Problematic definition of view w3c/wai-wcag-em#182 (4 comments by @JeroenHulscher, @stevefaulkner, @WilcoFiers)
-
"Accessibility Supported" and Accessibility APIs... w3c/wai-wcag-em#150 (2 comments by @A11yTea, @JeroenHulscher)
-
Comments on "4.3.2 Step 3.2: Include a randomly selected sample set" w3c/wai-wcag-em#171 (1 comment by @hidde)
-
-
9 pull requests opened.
-
trailing dot. w3c/wai-wcag-em#214, by @JeroenHulscher.
-
Use updated view def w3c/wai-wcag-em#213, by @hidde.
-
Correct reference w3c/wai-wcag-em#212, by @tamsinewing555.
-
update README with latest changes w3c/wai-wcag-em#211, by @hidde.
-
update view to merely refer to other standards w3c/wai-wcag-em#210, by @hidde.
-
set up with note status w3c/wai-wcag-em#209, by @hidde.
-
remove draft review questions w3c/wai-wcag-em#208, by @hidde.
-
Suggested edits w3c/wai-wcag-em#207, by @tamsinewing555.
-
make more explicit that samples are added on top w3c/wai-wcag-em#206, by @hidde.
-
-
10 pull requests merged.
-
trailing dot. w3c/wai-wcag-em#214.
-
Use updated view def w3c/wai-wcag-em#213.
-
Correct reference w3c/wai-wcag-em#212.
-
update README with latest changes w3c/wai-wcag-em#211.
-
update view to merely refer to other standards w3c/wai-wcag-em#210.
-
remove draft review questions w3c/wai-wcag-em#208.
-
set up with note status w3c/wai-wcag-em#209.
-
Suggested edits w3c/wai-wcag-em#207.
-
make more explicit that samples are added on top w3c/wai-wcag-em#206.
-
Update README.md w3c/wai-wcag-em#205.
-
-
1 pull request received 2 new comments.
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
-
5 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Mobile Accessibility Task Force
Past meetings
-
4 meetings of the Mobile Accessibility Task Force.
Participants
-
1 participant joined the Mobile Accessibility Task Force.
-
John Lilly joined.
-
WCAG2ICT Task Force
Participants
-
1 participant left the WCAG2ICT Task Force.
-
Mitchell Evan left.
-
Past meetings
Participants
-
11 participants joined.
-
takumi hiramatsu (Cybozu) joined.
-
Rachael Yomtoob (W3C Invited Experts) joined.
-
Grace Snow (TetraLogical Services Ltd) joined.
-
Nicki Berry (HM Government) joined.
-
Katherine Lees (W3C Invited Experts) joined.
-
Stephanie-Lee Steer (W3C Invited Experts) joined.
-
Theo Hale (W3C Invited Experts) joined.
-
Marat Faizov (HM Government) joined.
-
Andrew Hick (HM Government) joined.
-
Emanuel Silva (HM Government) joined.
-
Mansi Anand (Level Access) joined.
-
-
2 participants left.
-
Demelza Feltham (TetraLogical Services Ltd) left.
-
Akash Shukla (TPGi) left.
-
GitHub
w3c/wcag
-
21 issues opened.
-
[spam] w3c/wcag#5144, by @very16098-dev.
-
[spam] w3c/wcag#5143, by @calcaok9-glitch.
-
[spam] w3c/wcag#5129, by @Guillermes2908.
-
F34 references a removed future technique w3c/wcag#5126, by @HadleyLuker.
-
[spam] w3c/wcag#5125, by @madeehadar864-cloud.
-
[spam] w3c/wcag#5112, by @govardhan2000reddy-wq.
-
[spam] w3c/wcag#5108, by @mujangukixu-devi.
-
What is a "presentation"? 1.4.10 Reflow w3c/wcag#5106, by @A11yTea.
-
[spam] w3c/wcag#5105, by @sajiaghias21-collab.
-
Failure examples not explicitly labled as failures w3c/wcag#5103, by @bruce-usab.
-
[spam] w3c/wcag#5101, by @arularulrock690-boop.
-
[spam] w3c/wcag#5099, by @ayedalkhshan3-cell.
-
-
27 issues closed.
-
[spam] w3c/wcag#5144.
-
[spam] w3c/wcag#5143.
-
[spam] w3c/wcag#5139.
-
Request for <link rel="canonical"> on Understanding docs w3c/wcag#5086.
-
[spam] w3c/wcag#5129.
-
[spam] w3c/wcag#5127.
-
[spam] w3c/wcag#5125.
-
Failure examples not explicitly labled as failures w3c/wcag#5103.
-
[spam] w3c/wcag#5117.
-
What is a "presentation"? 1.4.10 Reflow w3c/wcag#5106.
-
[spam] w3c/wcag#5112.
-
Focus Order - Example aren't the only ways to pass or fail w3c/wcag#3469.
-
Adding disclaimer at the top of techniques? w3c/wcag#1567.
-
Consider rewording technical information in F3 w3c/wcag#4660.
-
G186, but many, many videos w3c/wcag#4444.
-
[spam] w3c/wcag#5109.
-
[spam] w3c/wcag#5108.
-
[spam] w3c/wcag#5105.
-
[spam] w3c/wcag#5101.
-
[spam] w3c/wcag#5099.
-
-
1 issue reopened.
-
43 issues received 88 new comments.
-
Representative color sampling for WCAG contrast: center pixel or area average w3c/wcag#5110 (10 comments by @JAWS-test, @nakano0949-web, @patrickhlauke, @TestPartners)
-
3.1.2 Language of Parts clarification w3c/wcag#4113 (8 comments by @awkawk, @chaals, @patrickhlauke)
-
Failure F46 for markup in layout tables doesn't taken into account role presentation or none w3c/wcag#3565 (6 comments by @bruce-usab, @patrickhlauke)
-
What is an "input field"? (1.3.5 Identify Input Purpose) w3c/wcag#1652 (3 comments by @mraccess77, @patrickhlauke)
-
Clarify whether SC 1.3.1 requires grouped links to be in a list structure w3c/wcag#1159 (3 comments by @goetsu, @patrickhlauke)
-
SC 2.2.2: Pause, Stop, Hide: is a scrollable viewport a sufficient “mechanism” to “hide” moving content? w3c/wcag#5029 (3 comments by @A11yTea, @patrickhlauke)
-
Does SC 1.2.1 require the alternative for time-based media for video-only to be visible? w3c/wcag#3642 (2 comments by @awkawk, @lauracarlson)
-
Contrast understanding docs (1.4.3, 1.4.6, 1.4.11) need guidance on when to use pixel-picking w3c/wcag#3761 (2 comments by @dbjorge, @patrickhlauke)
-
Failure examples not explicitly labled as failures w3c/wcag#5103 (2 comments by @bruce-usab, @iadawn)
-
Supplement suggestion to use MathML with new "intent" attribute w3c/wcag#5093 (1 comment by @patrickhlauke)
-
Can we consider a technique to meet Focus appearance that exposes tooltips? w3c/wcag#2139 (1 comment by @grace-snow)
-
Incomprehensible paragraph in chapter "Dismissable" (Understanding SC 1.4.13) w3c/wcag#1409 (1 comment by @venkatvemuri28)
-
Seeking confirmation that 2.4.6 applies also to headings & labels that are not visible w3c/wcag#2134 (1 comment by @A11yTea)
-
respec-generated glossary links different from xslt-generated glossary links w3c/wcag#594 (1 comment by @kfranqueiro)
-
Out of date, with typo, Requirements For WCAG 2.1 GitHub pages page w3c/wcag#4653 (1 comment by @kfranqueiro)
-
SC 2.4.11 | Add Escape key as a passing technique for auto-appearing overlays such as cookie banners w3c/wcag#5054 (1 comment by @martinbethann)
-
Mechanism provided by the platform AND stopping 1.4.2: Audio Control w3c/wcag#1533 (1 comment by @A11yTea)
-
SC 3.3.8 Accessible Authentication: Phone numbers are not personal, permanent, or universal w3c/wcag#5087 (1 comment by @patrickhlauke)
-
Can large headings be exempt from Success Criterion 1.4.4 Resize text? w3c/wcag#1671 (1 comment by @adampage)
-
-
18 pull requests opened.
-
[spam] w3c/wcag#5142, by @aaiyaiy369-boop.
-
Update dependencies flagged by npm audit w3c/wcag#5137, by @kfranqueiro.
-
Remove left-over mention of non-existent technique in F34 w3c/wcag#5132, by @patrickhlauke.
-
Add "also" to Note 1 for 2.2.2 Pause, Stop, Hide w3c/wcag#5130, by @patrickhlauke.
-
Add two in-page links to Understanding Non-Text Contrast w3c/wcag#5128, by @bruce-usab.
-
Fix 20 broken external links in WCAG 2.2 documentation (#4964) w3c/wcag#5123, by @mikeyil.
-
Convert `<text>` to `<path>` in Understanding 1.4.11 example SVGs w3c/wcag#5122, by @adampage.
-
Remove doubled words from informative docs w3c/wcag#5121, by @kfranqueiro.
-
Change 'serialize' to 'linearize' in Note 2 of Consistent Help w3c/wcag#5119, by @bruce-usab.
-
Update branch from main w3c/wcag#5118, by @bruce-usab.
-
Update On Input to address different button types w3c/wcag#5107, by @fstrr.
-
Implemented the F13 as a 1.1.1 and 1.3.3 failure w3c/wcag#5102, by @baldino-m.
-
Add missing definition for "proper name" w3c/wcag#5098, by @patrickhlauke.
-
Update Bypass Blocks to match other SC w3c/wcag#5097, by @bruce-usab.
-
-
13 pull requests merged.
-
Update dependencies flagged by npm audit w3c/wcag#5137.
-
Remove doubled words from informative docs w3c/wcag#5121.
-
Clarification on example and simplification of tests for H39 w3c/wcag#3613.
-
C41: fix change of contrast ratio in Procedure w3c/wcag#4422.
-
G183: Expand rationale to not just be about low vision users w3c/wcag#4887.
-
Add figure caption numbering to techniques w3c/wcag#5062.
-
Remove note in F24 about css background images w3c/wcag#4823.
-
-
2 pull requests closed.
-
[spam] w3c/wcag#5142.
-
Add missing definition for "proper name" w3c/wcag#5098.
-
-
1 pull request reopened.
-
Fix 20 broken external links in WCAG 2.2 documentation (#4964) w3c/wcag#5123, by @mikeyil.
-
-
27 pull requests received 160 new comments.
-
Update F46 to cover tables with structural elements that are marked presentational w3c/wcag#3566 (36 comments by @awkawk, @bruce-usab, @mraccess77, @patrickhlauke, @pkra, @stevefaulkner, @yatil)
-
Add missing definition for "proper name" w3c/wcag#5098 (19 comments by @adampage, @bruce-usab, @chaals, @detlevhfischer, @gundulaniemann, @iadawn, @patrickhlauke, @WilcoFiers)
-
Update On Input to address different button types w3c/wcag#5107 (12 comments by @awkawk, @fstrr, @patrickhlauke, @scottaohara)
-
Add a non-normative explanation of "proper name" to 3.1.2 Language of Parts understanding w3c/wcag#5135 (11 comments by @adampage, @chaals, @giacomo-petri, @patrickhlauke)
-
Reformat tables out of Understanding 1.4.11 w3c/wcag#4960 (9 comments by @adampage, @fstrr, @kfranqueiro, @patrickhlauke)
-
Update 1.4.11 Non-text Contrast to address concerns about visual boundaries w3c/wcag#5064 (8 comments by @adampage, @bruce-usab, @detlevhfischer, @fstrr, @patrickhlauke)
-
Add note about logo/logotypes contrast to 1.4.3, 1.4.6, and 1.4.11 understanding w3c/wcag#4402 (7 comments by @adampage, @detlevhfischer, @patrickhlauke)
-
Fix typos and clarify “starts automatically” in 2.2.2 Pause, Stop, Hide Understanding w3c/wcag#4822 (4 comments by @bruce-usab, @giacomo-petri, @patrickhlauke)
-
Focus obscured and semi-transparent/blurred overlays - reword, and DO make it fail at AAA w3c/wcag#4824 (3 comments by @adampage, @giacomo-petri)
-
Add two in-page links to Understanding Non-Text Contrast w3c/wcag#5128 (2 comments by @patrickhlauke)
-
Change 'serialize' to 'linearize' in Note 2 of Consistent Help w3c/wcag#5119 (2 comments by @bruce-usab, @patrickhlauke)
-
Convert `<text>` to `<path>` in Understanding 1.4.11 example SVGs w3c/wcag#5122 (1 comment by @adampage)
-
Add new Technique: Guarding keyboard event handlers against IME composition w3c/wcag#5081 (1 comment by @mehm8128)
-
Update normative wording of 4.1.3 and definition of "status message" w3c/wcag#4952 (1 comment by @WilcoFiers)
-
Update ARIA23 and server log working example to remove `aria-relevant` w3c/wcag#5077 (1 comment by @patrickhlauke)
-
w3c/wcag3
-
6 issues opened.
-
We need a Page Variations conformance requirement w3c/wcag3#682, by @fstrr.
-
Drop “privacy” and/or “security” as categories for consequences w3c/wcag3#677, by @hidde.
-
4 issues closed.
-
New SC for keyboard operation? w3c/wcag3#188.
-
How-Tos should be an Overview w3c/wcag3#405.
-
-
21 issues received 51 new comments.
-
Replace absolute units (px) with relative units (rem) as the baseline for font-size in WCAG 3.0 Outcomes. w3c/wcag3#642 (14 comments by @alastc, @chaals, @graphic-designer)
-
Proposal: Evolution of Conformance Testing for Modern CSS Interoperability w3c/wcag3#649 (6 comments by @graphic-designer, @hidde, @iadawn, @JAWS-test)
-
If such a guideline doesn't exist yet, some form of guideline around heartbeat audio? w3c/wcag3#683 (3 comments by @fstrr, @glkdrlgkrlzflnjkgh)
-
The definition of "minimum bounding box" does not allow vertical writing w3c/wcag3#672 (3 comments by @alastc, @hidde, @murata2makoto)
-
Please adjust 3.1.1 - the definitions of core and supplemental, so WCAG 3 is more equitable. w3c/wcag3#653 (3 comments by @GreggVan, @lseeman)
-
Pseudo-Elements Override Users' Accessibility and Safety Css w3c/wcag3#40 (2 comments by @alastc, @MarjaE2)
-
"View" definition should handle time-based and disappearing content w3c/wcag3#635 (1 comment by @alastc)
-
Future Success Criteria: Require disabled icon for disabled UI interface elements w3c/wcag3#197 (1 comment by @adampage)
-
Change of User Need Definition - should also apply to the physical world and human interaction w3c/wcag3#406 (1 comment by @adampage)
-
1.2.5: ADD a Guideline to Require Audio Description for Live Content w3c/wcag3#168 (1 comment by @adampage)
-
-
12 pull requests opened.
-
Edit Graphical Object Contrast Sufficient typo w3c/wcag3#681, by @fstrr.
-
Update dependencies flagged by npm audit w3c/wcag3#680, by @kfranqueiro.
-
Fix typos in glossary and preselections-visible documentation w3c/wcag3#679, by @Gabriel-Dalton.
-
Build: Rename requirement to provision across codebase w3c/wcag3#676, by @kfranqueiro.
-
Change all instances of z.object to z.strictObject for validation w3c/wcag3#675, by @kfranqueiro.
-
Fix remark plugin logic to work on Windows w3c/wcag3#674, by @kfranqueiro.
-
Sign language updates w3c/wcag3#673, by @iadawn.
-
Remove cspell ignorePaths that no longer exist w3c/wcag3#671, by @kfranqueiro.
-
Add local-only dev (or editor) tools for renaming entries w3c/wcag3#670, by @kfranqueiro.
-
Remove stray `howto` from “Keyboard focus appearance” guideline w3c/wcag3#667, by @adampage.
-
Remove “Keyboard navigable if responsive” provision w3c/wcag3#666, by @adampage.
-
Refine “Custom keys documented” provision w3c/wcag3#665, by @adampage.
-
-
9 pull requests merged.
-
Build: Rename requirement to provision across codebase w3c/wcag3#676.
-
Update dependencies flagged by npm audit w3c/wcag3#680.
-
Add local-only dev (or editor) tools for renaming entries w3c/wcag3#670.
-
Requirements: Re-add previous editors to formerEditors w3c/wcag3#662.
-
Remove cspell ignorePaths that no longer exist w3c/wcag3#671.
-
Fix remark plugin logic to work on Windows w3c/wcag3#674.
-
Move informative guideline/provision files to a subdirectory w3c/wcag3#663.
-
-
5 pull requests received 15 new comments.
-
Requirements: Re-add previous editors to formerEditors w3c/wcag3#662 (4 comments by @iadawn, @kfranqueiro)
w3c/matf
-
3 issues closed.
-
13 issues received 43 new comments.
-
Success Criterion 2.5.3 - Label in Name - Level A w3c/matf#39 (8 comments by @detlevhfischer, @jha11y, @JJdeGroot, @pauljadam, @shoobe01)
-
Definition of the (underlaying) layer is in a mobile application / mobile platform w3c/matf#270 (5 comments by @JJdeGroot, @shoobe01)
-
Success Criterion 3.1.1 - Language of Page - Level A w3c/matf#14 (5 comments by @JJdeGroot, @TanyaVanWorkum)
-
Success Criterion 2.4.2 - Page Titled - Level A w3c/matf#9 (5 comments by @JJdeGroot, @TanyaVanWorkum)
-
Success Criterion 2.4.11 - Focus Not Obscured (Minimum) - Level AA w3c/matf#52 (3 comments by @JJdeGroot)
-
Provide examples of "not modified by the author" and "provided by the user agent or platform software" w3c/matf#80 (3 comments by @JJdeGroot)
-
SUB - make a draft of the definition of "user interface component" in mobile application context w3c/matf#227 (1 comment by @JJdeGroot)
-
-
3 pull requests opened.
-
Add draft for 2.4.2 w3c/matf#288, by @JJdeGroot.
-
Add draft for 3.1.1 w3c/matf#287, by @JJdeGroot.
-
Add draft for 2.5.7 w3c/matf#286, by @JJdeGroot.
-
-
1 pull request merged.
-
Draft text for definition: user interface component. w3c/matf#280.
-
w3c/wai-wcag-em
-
20 issues closed.
-
Problematic definition of view w3c/wai-wcag-em#182.
-
If this is known to the evaluator? w3c/wai-wcag-em#128.
-
Documenting outcomes - include severity and user impact w3c/wai-wcag-em#179.
-
"Comprehensively evaluate" misleading w3c/wai-wcag-em#184.
-
Two suggested additional bullet points for the Define The Scope section w3c/wai-wcag-em#170.
-
Reference Accessibility Maturity Model in the abstract for context w3c/wai-wcag-em#177.
-
Documenting test process as a step w3c/wai-wcag-em#174.
-
Make it clearer that looking at all pages instead of sample is also good practice w3c/wai-wcag-em#175.
-
"Accessibility Supported" and Accessibility APIs... w3c/wai-wcag-em#150.
-
2.3 Involving Users (Optional) w3c/wai-wcag-em#143.
-
Contact information for the evaluator w3c/wai-wcag-em#130.
-
Policy context for use w3c/wai-wcag-em#124.
-
User Journeys and Top Tasks w3c/wai-wcag-em#123.
-
More on automated tools and approaches w3c/wai-wcag-em#116.
-
Statement of Partial Conformance w3c/wai-wcag-em#122.
-
Avoid repetition w3c/wai-wcag-em#152.
-
Digital product conformance? w3c/wai-wcag-em#183.
-
Rework Step 1.3 support baseline? w3c/wai-wcag-em#185.
-
-
1 issue reopened.
-
Rework Step 1.3 support baseline? w3c/wai-wcag-em#185, by @JeroenHulscher.
-
-
15 issues received 19 new comments.
-
"Accessibility Supported" and Accessibility APIs... w3c/wai-wcag-em#150 (4 comments by @A11yTea, @hidde, @JeroenHulscher)
-
Looking for feedback (and possible home): Well-Known URI for Accessibility Issue Reporting w3c/wai-wcag-em#188 (1 comment by @JeroenHulscher)
-
Two suggested additional bullet points for the Define The Scope section w3c/wai-wcag-em#170 (1 comment by @JeroenHulscher)
-
Make it clearer that looking at all pages instead of sample is also good practice w3c/wai-wcag-em#175 (1 comment by @hidde)
-
Documenting outcomes - include severity and user impact w3c/wai-wcag-em#179 (1 comment by @JeroenHulscher)
-
-
10 pull requests opened.
-
Update README.md w3c/wai-wcag-em#205, by @hidde.
-
add note on asking around w3c/wai-wcag-em#204, by @hidde.
-
address most concerns with the view definition raised in #182 w3c/wai-wcag-em#203, by @hidde.
-
Fixes #179 by adding it to a note w3c/wai-wcag-em#202, by @JeroenHulscher.
-
Fixes #176 w3c/wai-wcag-em#201, by @JeroenHulscher.
-
Update procedure.md w3c/wai-wcag-em#200, by @JeroenHulscher.
-
FIxes #143 w3c/wai-wcag-em#199, by @JeroenHulscher.
-
Fixed #152 w3c/wai-wcag-em#198, by @JeroenHulscher.
-
Fixes #183 w3c/wai-wcag-em#197, by @JeroenHulscher.
-
fixes #185 w3c/wai-wcag-em#196, by @JeroenHulscher.
-
-
11 pull requests merged.
-
add note on asking around w3c/wai-wcag-em#204.
-
address most concerns with the view definition raised in #182 w3c/wai-wcag-em#203.
-
Fixes #179 by adding it to a note w3c/wai-wcag-em#202.
-
Fixes #176 w3c/wai-wcag-em#201.
-
Update procedure.md w3c/wai-wcag-em#200.
-
FIxes #143 w3c/wai-wcag-em#199.
-
Fixed #152 w3c/wai-wcag-em#198.
-
Fixes #183 w3c/wai-wcag-em#197.
-
fixes #185 w3c/wai-wcag-em#196.
-
Add EPUB in references w3c/wai-wcag-em#195.
-
Improve grammar w3c/wai-wcag-em#194.
-
-
1 pull request received 1 new comment.
WCAG 2.x Backlog Task Force
Past meetings
-
5 meetings of the WCAG 2.x Backlog Task Force.
Participants
-
1 participant joined the WCAG 2.x Backlog Task Force.
-
Lori Oakley joined.
-
-
1 participant left the WCAG 2.x Backlog Task Force.
-
Akash Shukla 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
-
2 meetings of the Mobile Accessibility Task Force.
Participants
-
1 participant joined the Mobile Accessibility Task Force.
-
Rachael Yomtoob joined.
-
WCAG2ICT Task Force
Participants
-
1 participant joined the WCAG2ICT Task Force.
-
James Harrington joined.
-
Lifecycle
-
1 charter extension.
-
Charter extended until 28 August 2026.
-
Past meetings
Participants
-
6 participants joined.
-
Jeffrey Yasskin (Google LLC) joined.
-
Lori Oakley (W3C Invited Experts) joined.
-
Heather Bellis (W3C Invited Experts) joined.
-
Samantha Estoesta (Level Access) joined.
-
Erin Evans (Oracle Corporation) joined.
-
Monica Gaines (Oracle Corporation) joined.
-
-
6 participants left.
-
Theo Hale (W3C Invited Experts) left.
-
David Middleton (Level Access) left.
-
Chris Wilson (Google LLC) left.
-
Nora GOUGANE (CANTON CONSULTING) left.
-
Heather Bellis (W3C Invited Experts) left.
-
Lori Oakley (W3C Invited Experts) left.
-
-
2 organizations left.
-
CANTON CONSULTING left.
-
Fabasoft left.
-
GitHub
w3c/wcag
-
23 issues opened.
-
site-oriented SC use inconsistent phrasing w3c/wcag#5096, by @bruce-usab.
-
Supplement suggestion to use MathML with new "intent" attribute w3c/wcag#5093, by @NSoiffer.
-
Request for <link rel="canonical"> on Understanding docs w3c/wcag#5086, by @HadleyLuker.
-
[spam] w3c/wcag#5076, by @Foxrid5988.
-
F69 is an insufficient Failure technique for Resize Text w3c/wcag#5071, by @mbgower.
-
[spam] w3c/wcag#5070, by @nathaliesoucy689-code.
-
On Input understanding doc makes broad strokes about buttons w3c/wcag#5059, by @scottaohara.
-
[spam] w3c/wcag#5058, by @icpsergioydulce-cloud.
-
[spam] w3c/wcag#5055, by @tarsemhundal036-crypto.
-
WCAG22 class for span needs a refresh w3c/wcag#5041, by @bruce-usab.
-
[spam] w3c/wcag#5040, by @oe99901-ship-it.
-
[spam] w3c/wcag#5039, by @oe99901-ship-it.
-
2.4.13 Focus Appearance - Figure 1 image appears to be incorrect w3c/wcag#5034, by @abbott567.
-
-
59 issues closed.
-
Remove jQuery from working examples w3c/wcag#4979.
-
Need more understanding on SCs 2.5.5 and 2.5.8 Target sizes w3c/wcag#3551.
-
A mobile text size setting affects only some text w3c/wcag#2884.
-
[spam] w3c/wcag#5076.
-
Understanding Focus Visible vs Not Obscured w3c/wcag#3504.
-
[spam] w3c/wcag#5070.
-
Machine readable principle hierarchy and technical language? w3c/wcag#3081.
-
Clarification on password re-entry in 3.3.7 Redundant Entry w3c/wcag#4210.
-
UX issue around persistent tooltips w3c/wcag#1727.
-
3.1.3 Unusual Words and neologisms/slang/made-up words w3c/wcag#3591.
-
SC 1.3.1: Responsive stacked table w3c/wcag#4137.
-
fix Notes and Examples visual weight and visual flow w3c/wcag#2873.
-
fix 'Help Improve this page' box w3c/wcag#2877.
-
[spam] w3c/wcag#5058.
-
[spam] w3c/wcag#5055.
-
Understanding Conformance refresh w3c/wcag#5003.
-
Add banner to old WCAG 2.0 informative documents w3c/wcag#3815.
-
No WCAG success criteria for users with Speech impairments w3c/wcag#4062.
-
Review Reflow In Brief material w3c/wcag#4283.
-
Target Size Minimum - Example 2 w3c/wcag#3369.
-
Deprecated criterion 4.1.1 Parsing w3c/wcag#3641.
-
Commonly used image buttons FAIL 1.4.5: Images of Text? w3c/wcag#1748.
-
Images of text when text is on page w3c/wcag#1647.
-
F105: Failure of Success Criterion 2.5.1 Pointer Gestures w3c/wcag#1333.
-
Guideline Proposal / New Success Criterion proposal w3c/wcag#4788.
-
Explanation for Benefit nr.3 SC 3.2.5: Change on Request w3c/wcag#740.
-
New placement of Understanding link w3c/wcag#742.
-
2.5.3 Label in Name - case insensitve? w3c/wcag#3812.
-
2.5.7 Dragging Movements - Carousels - Overflowed Containers w3c/wcag#2684.
-
Target Size Minimum, user agent control, and scrolling areas w3c/wcag#3485.
-
Errata for 2.5.5 Target Size (Enhanced) to align with 2.5.8 w3c/wcag#2857.
-
[spam] w3c/wcag#5040.
-
[spam] w3c/wcag#5039.
-
1 issue reopened.
-
Editorial issues in "assistive technology" definition w3c/wcag#3269, by @patrickhlauke.
-
-
70 issues received 106 new comments.
-
Review WCAG2Mobile to see which web-specific parts can be merged into WCAG itself w3c/wcag#5091 (8 comments by @detlevhfischer, @JJdeGroot, @mraccess77, @patrickhlauke)
-
Clarify use of "tag" in PDF14 w3c/wcag#3197 (6 comments by @CharlesBelov, @DuffJohnson, @mraccess77)
-
WCAG22 class for span needs a refresh w3c/wcag#5041 (4 comments by @bruce-usab, @kfranqueiro, @patrickhlauke)
-
Links ambiguous to AT users only can pass 2.4.4 and 2.4.9 w3c/wcag#1202 (3 comments by @bruce-usab, @m13v, @patrickhlauke)
-
SC 3.3.8 Accessible Authentication: Phone numbers are not personal, permanent, or universal w3c/wcag#5087 (3 comments by @markjharvey, @patrickhlauke)
-
F69 is an insufficient Failure technique for Resize Text w3c/wcag#5071 (3 comments by @bruce-usab, @mraccess77)
-
Aligning SC 1.2.5 (pre-rec Audio Description) and SC 1.2.2 (pre-rec Captions) to a DOM declared language rule w3c/wcag#4940 (2 comments by @alastc, @wrxpirate)
-
Moving phone camera over QR code a case for 2.5.4 Motion Actuation? w3c/wcag#1120 (2 comments by @detlevhfischer, @patrickhlauke)
-
Clarification needed for contrast requirements for focusable _disabled_ controls w3c/wcag#5053 (2 comments by @bruce-usab, @patrickhlauke)
-
Clarify CAPTCHA content scope, within 'accessible authentication (minimum)' understanding doc w3c/wcag#3320 (2 comments by @mraccess77, @patrickhlauke)
-
Target Size Minimum, user agent control, and scrolling areas w3c/wcag#3485 (2 comments by @fstrr, @patrickhlauke)
-
Need more understanding on SCs 2.5.5 and 2.5.8 Target sizes w3c/wcag#3551 (1 comment by @patrickhlauke)
-
G176 "Keeping the flashing area small enough" needs updating w3c/wcag#4358 (1 comment by @patrickhlauke)
-
Informative Techniques pages are loaded with normative RFC-2119 terms like MUST w3c/wcag#1150 (1 comment by @patrickhlauke)
-
2.5.4 understanding - suggestion to remove the "user gestures towards device" angle w3c/wcag#1464 (1 comment by @patrickhlauke)
-
respec-generated glossary links different from xslt-generated glossary links w3c/wcag#594 (1 comment by @kfranqueiro)
-
2.5.8 Target Size (Minimum): equivalent, inline, and essential exceptions w3c/wcag#3253 (1 comment by @patrickhlauke)
-
Improving links from WCAG TR definitions to Understanding w3c/wcag#4066 (1 comment by @patrickhlauke)
-
Machine readable principle hierarchy and technical language? w3c/wcag#3081 (1 comment by @patrickhlauke)
-
Clarify that separators, resize handlers, scrollbars are also covered in 2.5.8 target size w3c/wcag#3629 (1 comment by @patrickhlauke)
-
1.4.12: Text Spacing: Languages and Scripts Results/Exceptions and Content Edit w3c/wcag#1786 (1 comment by @patrickhlauke)
-
Understanding SC 3.2.2: On Input (Level A) definition of New Window glossary term w3c/wcag#3125 (1 comment by @patrickhlauke)
-
Can large headings be exempt from Success Criterion 1.4.4 Resize text? w3c/wcag#1671 (1 comment by @patrickhlauke)
-
Change 1.4.9: Images of Text (No Exception) to 1.4.9: Images of Text (50% Exception) w3c/wcag#1749 (1 comment by @patrickhlauke)
-
SC 2.4.11 | Add Escape key as a passing technique for auto-appearing overlays such as cookie banners w3c/wcag#5054 (1 comment by @patrickhlauke)
-
Should scroll gradient fail Contrast (Minimum), and are there more desirable patterns? w3c/wcag#4622 (1 comment by @Myndex)
-
Update PDF17 to be in sync with Adobe Acrobat Pro 2023 menus w3c/wcag#3196 (1 comment by @DuffJohnson)
-
No WCAG success criteria for users with Speech impairments w3c/wcag#4062 (1 comment by @patrickhlauke)
-
Addition about heading hierarchy / nesting in Understanding SC 4.1.1 w3c/wcag#2776 (1 comment by @patrickhlauke)
-
Add the use of aria-current as a sufficient technique for Info And Relationships? w3c/wcag#1681 (1 comment by @patrickhlauke)
-
Would "descriptive transcript" pass "alternative for time-based media"? w3c/wcag#4958 (1 comment by @patrickhlauke)
-
Further expand the explanation for exemptions to 3.1.4 Abbreviations w3c/wcag#5044 (1 comment by @patrickhlauke)
-
3.3.1 Error identification - does the default browser error validation count as PASS? w3c/wcag#961 (1 comment by @patrickhlauke)
-
Errata for 2.5.5 Target Size (Enhanced) to align with 2.5.8 w3c/wcag#2857 (1 comment by @patrickhlauke)
-
The checks in Failure technique F85 for Focus Order need to be tweaked w3c/wcag#3223 (1 comment by @patrickhlauke)
-
-
24 pull requests opened.
-
Reference term errata based on explicit dfn id, not generated one w3c/wcag#5084, by @kfranqueiro.
-
Remove unused include (flagged by Adam Page) w3c/wcag#5083, by @kfranqueiro.
-
Add index page for working-examples in dev and PR previews w3c/wcag#5082, by @kfranqueiro.
-
Update 4.1.3 Status Messages interpretation to cover `ariaNotify` w3c/wcag#5079, by @patrickhlauke.
-
Add example section for visual markup explanation to G96 w3c/wcag#5073, by @CharlesBelov.
-
Clarify conditions for resize failure in F69 w3c/wcag#5072, by @mbgower.
-
Tweak PDF2 intent w3c/wcag#5069, by @patrickhlauke.
-
Expand 1.4.5 Images of Text benefits w3c/wcag#5065, by @patrickhlauke.
-
Add figure caption numbering to techniques w3c/wcag#5062, by @patrickhlauke.
-
Update liquid and lodash as per npm audit w3c/wcag#5057, by @kfranqueiro.
-
Update info-and-relationships.html w3c/wcag#5050, by @mhdipozn-cmd.
-
Add "Help improve this page" box to About pages w3c/wcag#5049, by @kfranqueiro.
-
Change the example for 4.1.2 Name, Role, Value understanding w3c/wcag#5045, by @patrickhlauke.
-
Turn pass/fail text in svg to outlines/paths w3c/wcag#5043, by @patrickhlauke.
-
17 pull requests merged.
-
Remove unused include (flagged by Adam Page) w3c/wcag#5083.
-
Add index page for working-examples in dev and PR previews w3c/wcag#5082.
-
Update 1.3.6 advisory technique bullet w3c/wcag#4663.
-
Remove jQuery from Techniques / Working Examples w3c/wcag#4981.
-
Remove obsolete wcag21/requirements page w3c/wcag#4656.
-
Update liquid and lodash as per npm audit w3c/wcag#5057.
-
Add "Help improve this page" box to About pages w3c/wcag#5049.
-
Adding H99 to multiple ways w3c/wcag#2549.
-
Add note to abbreviations understanding about exemptions w3c/wcag#4815.
-
Changes to 3.1.3 Unusual Words understanding w3c/wcag#4841.
-
Turn pass/fail text in svg to outlines/paths w3c/wcag#5043.
-
Add pointerevents alias to biblio.ts w3c/wcag#5020.
-
4 pull requests closed.
-
Enable to remove old logs on serverlog.html working-example w3c/wcag#4996.
-
Move link to Understanding to its own DD w3c/wcag#5005.
-
Update info-and-relationships.html w3c/wcag#5050.
-
35 pull requests received 201 new comments.
-
Update normative wording of 4.1.3 and definition of "status message" w3c/wcag#4952 (25 comments by @awkawk, @baldino-m, @bruce-usab, @joelamyman, @patrickhlauke, @WilcoFiers)
-
Disambiguation of path-based gesture versus dragging movement w3c/wcag#4843 (25 comments by @bruce-usab, @detlevhfischer, @patrickhlauke)
-
Add banner to top of techniques pages, tweak boxout content about techniques w3c/wcag#5002 (21 comments by @fstrr, @iadawn, @patrickhlauke, @tamsinewing555)
-
Update 4.1.3 Status Messages interpretation to cover `ariaNotify` w3c/wcag#5079 (18 comments by @adampage, @baldino-m, @bruce-usab, @detlevhfischer, @fstrr, @kfranqueiro, @patrickhlauke)
-
Update F3 "using CSS to include images that convey [...] information" w3c/wcag#4814 (14 comments by @baldino-m, @bruce-usab, @patrickhlauke)
-
Clarification on example and simplification of tests for H39 w3c/wcag#3613 (11 comments by @awkawk, @bruce-usab, @detlevhfischer, @mgifford, @patrickhlauke)
-
Add note to abbreviations understanding about exemptions w3c/wcag#4815 (10 comments by @chaals, @kfranqueiro, @patrickhlauke)
-
Add note about logo/logotypes contrast to 1.4.3, 1.4.6, and 1.4.11 understanding w3c/wcag#4402 (6 comments by @fstrr, @patrickhlauke)
-
Update ARIA23 and server log working example to remove `aria-relevant` w3c/wcag#5077 (5 comments by @adampage, @JAWS-test, @patrickhlauke)
-
Remove jQuery from Techniques / Working Examples w3c/wcag#4981 (5 comments by @fstrr, @patrickhlauke)
-
Add clarification that moving phone/tablet camera for QR/bar code is not a motion actuation concern w3c/wcag#5089 (5 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 (5 comments by @patrickhlauke)
-
Update 1.4.11 Non-text Contrast to address concerns about visual boundaries w3c/wcag#5064 (5 comments by @adampage, @patrickhlauke)
-
Consistency: use "touchscreen" rather than "touch screen" (normative) w3c/wcag#5038 (4 comments by @awkawk, @hidde, @patrickhlauke)
-
Add new failure technique for non-semantic ruby annotation w3c/wcag#4829 (3 comments by @patrickhlauke, @xfq)
-
Expand 2.1.2 understanding to make it more ... understandable w3c/wcag#4726 (3 comments by @detlevhfischer, @patrickhlauke)
-
Add example section for visual markup explanation to G96 w3c/wcag#5073 (2 comments by @patrickhlauke, @w3cbot)
-
C41: fix change of contrast ratio in Procedure w3c/wcag#4422 (2 comments by @adampage, @patrickhlauke)
-
Enable to remove old logs on serverlog.html working-example w3c/wcag#4996 (2 comments by @patrickhlauke)
-
Remove note in F24 about css background images w3c/wcag#4823 (2 comments by @adampage, @patrickhlauke)
-
Add clarification that moving phone/tablet camera for QR/bar code is not a motion actuation concern w3c/wcag#5088 (1 comment by @patrickhlauke)
-
Add index page for working-examples in dev and PR previews w3c/wcag#5082 (1 comment by @patrickhlauke)
-
Update Link Purpose (in Context) understanding benefits to focus on AT w3c/wcag#1164 (1 comment by @patrickhlauke)
-
w3c/wcag#5035 (1 comment by @kfranqueiro)
-
w3c/wcag#5052 (1 comment by @kfranqueiro)
-
Amend "contrast ratio" term - move out non-term notes to understanding docs w3c/wcag#4400 (1 comment by @patrickhlauke)
-
w3c/wcag3
-
21 issues opened.
-
Request for desktop mode w3c/wcag3#664, by @alastc.
-
Note in Guideline 2.2.3 Clear language w3c/wcag3#659, by @xfq.
-
Reference to ISO 639 w3c/wcag3#658, by @xfq.
-
Unify the two definitions of "assertion" w3c/wcag3#657, by @jyasskin.
-
Assertions should be core or supplemental w3c/wcag3#654, by @lseeman.
-
Errors co-located: use “submission status” instead? w3c/wcag3#646, by @hidde.
-
single pointer and simple pointer are too confusable w3c/wcag3#643, by @bruce-usab.
-
Text style readable: underlining of text w3c/wcag3#641, by @Finnberrys.
-
Image types identified w3c/wcag3#640, by @Finnberrys.
-
"View" definition should handle time-based and disappearing content w3c/wcag3#635, by @WilcoFiers.
-
Assertions Feedback and Follow up Q's w3c/wcag3#634, by @sydneycolemanfromgoogle.
-
-
2 issues closed.
-
Detectable Image and CSS background images w3c/wcag3#357.
-
Image role overlap with Detectable image w3c/wcag3#358.
-
-
27 issues received 104 new comments.
-
Proposal: Evolution of Conformance Testing for Modern CSS Interoperability w3c/wcag3#649 (27 comments by @alastc, @graphic-designer, @hidde, @hollsk, @TestPartners)
-
single pointer and simple pointer are too confusable w3c/wcag3#643 (7 comments by @bruce-usab, @GreggVan, @patrickhlauke)
-
Rendering‑aware contrast model proposal for WCAG 3 w3c/wcag3#590 (3 comments by @Myndex, @nakano0949-web)
-
Please adjust 3.1.1 - the definitions of core and supplemental, so WCAG 3 is more equitable. w3c/wcag3#653 (2 comments by @GreggVan, @jmcsorle)
-
Include draft list of outcomes in WCAG 3 "dashboard" page w3c/wcag3#56 (2 comments by @adampage, @detlevhfischer)
-
WCAG 3.0 Working Draft — Comment on Autonomous Agents as Primary and Proxy Users w3c/wcag3#636 (2 comments by @hidde, @patrickhlauke)
-
Contrast Research: APCA Peer Reviews + Defining a Visual Contrast Guideline w3c/wcag3#29 (1 comment by @milessea)
-
How does the guideline ensure text is sufficiently readable for people with CVD (colourblindness) w3c/wcag3#403 (1 comment by @Myndex)
-
"purely decorative" vs "decorative" - Decorative images (Foundational) w3c/wcag3#466 (1 comment by @Finnberrys)
-
Relation from Flashing/motion requriements to the warning requirement w3c/wcag3#632 (1 comment by @nattarnoff)
-
About definition in Glossary: Process in Explainer for WCAG 3.0 w3c/wcag3#315 (1 comment by @adampage)
-
What about language of the page and language of parts (in Human Language requirement)? w3c/wcag3#486 (1 comment by @MaxAccess)
-
9 pull requests opened.
-
Move informative guideline/provision files to a subdirectory w3c/wcag3#663, by @kfranqueiro.
-
Requirements: Re-add previous editors to formerEditors w3c/wcag3#662, by @kfranqueiro.
-
Refine simple pointer input definition w3c/wcag3#661, by @adampage.
-
Fix `single pointer` → `simple pointer` typo in glossary w3c/wcag3#660, by @adampage.
-
Simplify simple-pointer-input-available.md w3c/wcag3#652, by @bruce-usab.
-
Fix TS warnings and make config stricter to surface them as errors w3c/wcag3#651, by @kfranqueiro.
-
Upgrade Astro-related dependencies and force-upgrade yaml w3c/wcag3#650, by @kfranqueiro.
-
Add user needs into informative section w3c/wcag3#648, by @iadawn.
-
Move groups/index.json to groups.json and remove patch-package w3c/wcag3#633, by @kfranqueiro.
-
-
6 pull requests merged.
-
Refine simple pointer input definition w3c/wcag3#661.
-
Fix `single pointer` → `simple pointer` typo in glossary w3c/wcag3#660.
-
Upgrade Astro-related dependencies and force-upgrade yaml w3c/wcag3#650.
-
-
2 pull requests closed.
-
Update pointer-activation-controllable.md w3c/wcag3#588.
-
Exploring presentation for informative documentation w3c/wcag3#625.
-
-
2 pull requests received 5 new comments.
-
clarify view definition based on feedback in WCAG-EM w3c/wcag3#630 (4 comments by @hidde, @WilcoFiers)
-
Rework “No repetitive links” as “No adjacent interactive elements” w3c/wcag3#602 (1 comment by @bruce-usab)
-
w3c/coga
-
1 issue received 1 new comment.
w3c/matf
-
9 issues closed.
-
Add a draft for 3.1.2 w3c/matf#277.
-
12 issues received 34 new comments.
-
Success Criterion 2.4.2 - Page Titled - Level A w3c/matf#9 (8 comments by @JJdeGroot, @mitch11-vispero, @shoobe01, @TanyaVanWorkum)
-
Success Criterion 2.4.11 - Focus Not Obscured (Minimum) - Level AA w3c/matf#52 (6 comments by @detlevhfischer, @jha11y, @shoobe01)
-
Success Criterion 3.1.1 - Language of Page - Level A w3c/matf#14 (4 comments by @JJdeGroot, @shoobe01, @TanyaVanWorkum)
-
Success Criterion 2.5.7 - Dragging Movements - Level AA w3c/matf#53 (3 comments by @detlevhfischer, @shoobe01)
-
Definition of the (underlaying) layer is in a mobile application / mobile platform w3c/matf#270 (3 comments by @rwapp, @shoobe01)
-
Definition of "dragging movements" in mobile application context w3c/matf#65 (3 comments by @detlevhfischer, @shoobe01)
-
Success Criterion 1.3.3 - Sensory Characteristics - Level A w3c/matf#24 (1 comment by @patrickhlauke)
-
SUB -2.4.11 - Focus Not Obscured (Minimum) - Clarify "author-created" definition w3c/matf#209 (1 comment by @jha11y)
-
-
1 pull request merged.
-
3.1.2-draft w3c/matf#278.
-
-
1 pull request received 1 new comment.
w3c/wai-wcag-em
-
1 issue opened.
-
[minor] random sample cannot be replicated; is not crucial w3c/wai-wcag-em#192, by @shawna-slh.
-
-
15 issues closed.
-
Include epub in introduction (factors) and sample types w3c/wai-wcag-em#112.
-
[minor] random sample cannot be replicated; is not crucial w3c/wai-wcag-em#192.
-
Remove procedure section numbers? w3c/wai-wcag-em#186.
-
Age of the site and the number of pages w3c/wai-wcag-em#125.
-
Structured Sample Set = List of URLs? w3c/wai-wcag-em#129.
-
Reporting formatting w3c/wai-wcag-em#117.
-
Check our content with WCAG 3 style guide w3c/wai-wcag-em#107.
-
Randomly selected samples w3c/wai-wcag-em#121.
-
update step 1a “Define the Scope of the Product ” w3c/wai-wcag-em#81.
-
Documents are often underrepresented in sample, but overrepresented in variety w3c/wai-wcag-em#25.
-
Accessibility Statements w3c/wai-wcag-em#120.
-
update types of website w3c/wai-wcag-em#16.
-
Suggested sample types: component, document, screen name, state w3c/wai-wcag-em#78.
-
Include identification of assistive devices to be used in the evaluation w3c/wai-wcag-em#178.
-
-
1 issue reopened.
-
Clarity needed on components and sampling w3c/wai-wcag-em#172, by @hidde.
-
-
23 issues received 54 new comments.
-
Usefulness and value of random sample is questionable w3c/wai-wcag-em#173 (17 comments by @hidde, @karlgroves, @shawna-slh, @stevefaulkner)
-
Clarity needed on components and sampling w3c/wai-wcag-em#172 (7 comments by @hidde, @JeroenHulscher, @karlgroves)
-
Documenting test process as a step w3c/wai-wcag-em#174 (4 comments by @hidde, @karlgroves, @stevefaulkner)
-
[minor] random sample cannot be replicated; is not crucial w3c/wai-wcag-em#192 (3 comments by @hidde, @shawna-slh)
-
Reference Accessibility Maturity Model in the abstract for context w3c/wai-wcag-em#177 (2 comments by @hidde, @stevefaulkner)
-
Two suggested additional bullet points for the Define The Scope section w3c/wai-wcag-em#170 (1 comment by @hidde)
-
Include epub in introduction (factors) and sample types w3c/wai-wcag-em#112 (1 comment by @JeroenHulscher)
-
Documents are often underrepresented in sample, but overrepresented in variety w3c/wai-wcag-em#25 (1 comment by @JeroenHulscher)
-
Create overview of different types of websites (/software/documents) that WCAG could apply to w3c/wai-wcag-em#26 (1 comment by @JeroenHulscher)
-
Suggested sample types: component, document, screen name, state w3c/wai-wcag-em#78 (1 comment by @JeroenHulscher)
-
Include identification of assistive devices to be used in the evaluation w3c/wai-wcag-em#178 (1 comment by @lsr-explore)
-
-
3 pull requests opened.
-
Add EPUB in references w3c/wai-wcag-em#195, by @JeroenHulscher.
-
Improve grammar w3c/wai-wcag-em#194, by @tamsinewing555.
-
reduce importance of recording method of random sample selection w3c/wai-wcag-em#193, by @hidde.
-
-
3 pull requests merged.
-
reduce importance of recording method of random sample selection w3c/wai-wcag-em#193.
-
Editorial suggestions w3c/wai-wcag-em#191.
-
remove respec numbering to avoid redundant numbering w3c/wai-wcag-em#190.
-
-
2 pull requests received 10 new comments.
-
reduce importance of recording method of random sample selection w3c/wai-wcag-em#193 (1 comment by @shawna-slh)
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
7 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
1 issue in the Cognitive and Learning Disabilities Accessibility Task Force received 1 new comment.
Mobile Accessibility Task Force
Past meetings
-
4 meetings of the Mobile Accessibility Task Force.
Participants
-
1 participant joined the Mobile Accessibility Task Force.
-
Samantha Estoesta joined.
-
WCAG 2.x Backlog Task Force
Past meetings
-
4 meetings of the WCAG 2.x Backlog Task Force.
Participants
-
1 participant joined the WCAG 2.x Backlog Task Force.
-
Venkata Vemuri joined.
-
-
1 participant left the WCAG 2.x Backlog Task Force.
-
Lori Oakley left.
-
TR publications
-
3 documents published.
-
W3C Accessibility Guidelines (WCAG) 3.0 published as a Working Draft. History of W3C Accessibility Guidelines (WCAG) 3.0
-
Requirements for WCAG 3.0 published as a Draft Note. History of Requirements for WCAG 3.0
-
Past meetings
Participants
-
1 chair appointed.
-
Adam Page became a chair.
-
-
11 participants joined.
-
Christopher Land (Oracle Corporation) joined.
-
Jonny James (TPGi) joined.
-
James Harrington (CVS Pharmacy, Inc.) joined.
-
Ashlee Fisher (W3C Invited Experts) joined.
-
Diego Della Rossa (UsableNet) joined.
-
Jaunita Flessas (W3C Invited Experts) joined.
-
Michael (preferred name is Godwin) Godwin (W3C Invited Experts) joined.
-
Anton Steckert (SAP SE) joined.
-
Christina Adams (Siteimprove) joined.
-
Jean-Yves Moyen (Siteimprove) joined.
-
Aleksandra Nichols (Deque Systems, Inc.) joined.
-
-
4 participants left.
-
Paul Adam (CVS Pharmacy, Inc.) left.
-
Kiara Stewart (Shopify) left.
-
Kazuhiro Tobita (Cybozu) left.
-
Christina Adams (Siteimprove) left.
-
GitHub
w3c/wcag3
-
17 issues opened.
-
Relation from Flashing/motion requriements to the warning requirement w3c/wcag3#632, by @alastc.
-
Can flashing requirements account for zoom? w3c/wcag3#631, by @alastc.
-
Can user-preferences be relied on for "No flashing"? w3c/wcag3#629, by @alastc.
-
README link to process presentation is not publicly accessible w3c/wcag3#626, by @Gabriel-Dalton.
-
2.1.1 Image Alternatives - Assertion Recommendation w3c/wcag3#619, by @utkudyn-a11y.
-
2.1.4 Captions - Core Requirement Suggestion w3c/wcag3#618, by @utkudyn-a11y.
-
Focus placed should be a core requirement w3c/wcag3#616, by @ajsaucier.
-
2.1.2 Media Alternatives - Test case (and definitions) w3c/wcag3#611, by @JasonAment.
-
Keyboard navigable if responsive. - breakpoints are problematic. w3c/wcag3#608, by @JasonAment.
-
2.1.1 - Decorative images hidden - Test procedure update. w3c/wcag3#607, by @JasonAment.
-
2.1.1 - Core requirement: Images detectable - Test needs update w3c/wcag3#606, by @JasonAment.
-
Equivalent for 2.1.4 Character Key Shortcuts? w3c/wcag3#603, by @adampage.
-
Reorganization of WCAG 3: Core + Satellites w3c/wcag3#600, by @murata2makoto.
-
-
14 issues received 31 new comments.
-
Keyboard navigable if responsive. - breakpoints are problematic. w3c/wcag3#608 (5 comments by @adampage, @JasonAment, @mraccess77)
-
Can flashing requirements account for zoom? w3c/wcag3#631 (4 comments by @alastc, @detlevhfischer, @GreggVan, @WilcoFiers)
-
Relation from Flashing/motion requriements to the warning requirement w3c/wcag3#632 (3 comments by @GreggVan, @patrickhlauke)
-
What about language of the page and language of parts (in Human Language requirement)? w3c/wcag3#486 (3 comments by @julierawe, @MaxAccess)
-
Can user-preferences be relied on for "No flashing"? w3c/wcag3#629 (2 comments by @alastc, @patrickhlauke)
-
Gap in WCAG: Toast Notifications That Dismiss on Scroll or Focus Change w3c/wcag3#430 (2 comments by @adampage, @jducrot)
-
[Image alternatives] “decorative“ and “purely decorative” distinction not useful w3c/wcag3#518 (1 comment by @adampage)
-
Add explicit requirement for Scrollable regions to be included in keyboard tab order w3c/wcag3#622 (1 comment by @mraccess77)
-
2.1.1 - Core requirement: Images detectable - Test needs update w3c/wcag3#606 (1 comment by @mraccess77)
-
-
12 pull requests opened.
-
clarify view definition based on feedback in WCAG-EM w3c/wcag3#630, by @hidde.
-
Updates to flashing w3c/wcag3#628, by @alastc.
-
Exploring presentation for informative documentation w3c/wcag3#625, by @iadawn.
-
Removing the old essential exception, not referenced anymore. w3c/wcag3#620, by @alastc.
-
Add initial informative architecture w3c/wcag3#615, by @kfranqueiro.
-
Exploring use of registry to support more text scripts w3c/wcag3#613, by @iadawn.
-
Enforce applies-when appearing before except-when (not after) w3c/wcag3#612, by @kfranqueiro.
-
Change back to Editors Draft w3c/wcag3#609, by @iadawn.
-
Make order of applies when / except when consistent w3c/wcag3#604, by @hidde.
-
Rework “No repetitive links” as “No adjacent interactive elements” w3c/wcag3#602, by @fstrr.
-
Publication preparation fixes w3c/wcag3#601, by @iadawn.
-
-
6 pull requests merged.
-
Make order of applies when / except when consistent w3c/wcag3#604.
-
Add initial informative architecture w3c/wcag3#615.
-
Change back to Editors Draft w3c/wcag3#609.
-
Add links to other docs w3c/wcag3#595.
-
Revise Custom Keys Documented w3c/wcag3#598.
-
1 pull request closed.
-
Publication preparation fixes w3c/wcag3#601.
-
-
2 pull requests received 6 new comments.
w3c/wai-wcag-em
-
17 issues opened.
-
Looking for feedback (and possible home): Well-Known URI for Accessibility Issue Reporting w3c/wai-wcag-em#188, by @AutoSponge.
-
Remove procedure section numbers? w3c/wai-wcag-em#186, by @iadawn.
-
Rework Step 1.3 support baseline? w3c/wai-wcag-em#185, by @iadawn.
-
"Comprehensively evaluate" misleading w3c/wai-wcag-em#184, by @iadawn.
-
Digital product conformance? w3c/wai-wcag-em#183, by @iadawn.
-
Problematic definition of view w3c/wai-wcag-em#182, by @WilcoFiers.
-
Documenting outcomes - include severity and user impact w3c/wai-wcag-em#179, by @lsr-explore.
-
Include identification of assistive devices to be used in the evaluation w3c/wai-wcag-em#178, by @lsr-explore.
-
Reference Accessibility Maturity Model in the abstract for context w3c/wai-wcag-em#177, by @lsr-explore.
-
Make it clearer that looking at all pages instead of sample is also good practice w3c/wai-wcag-em#175, by @hidde.
-
Documenting test process as a step w3c/wai-wcag-em#174, by @karlgroves.
-
Usefulness and value of random sample is questionable w3c/wai-wcag-em#173, by @karlgroves.
-
Clarity needed on components and sampling w3c/wai-wcag-em#172, by @karlgroves.
-
Comments on "4.3.2 Step 3.2: Include a randomly selected sample set" w3c/wai-wcag-em#171, by @graemecoleman.
-
Two suggested additional bullet points for the Define The Scope section w3c/wai-wcag-em#170, by @graemecoleman.
-
4.1.2 - Move supplementary example to non-normative note w3c/wai-wcag-em#168, by @JasonAment.
-
-
3 issues closed.
-
4.1.2 - Move supplementary example to non-normative note w3c/wai-wcag-em#168.
-
Recommend pre-filling of realistic data, not just creating new accounts w3c/wai-wcag-em#158.
-
Recommend storing videos as well as screenshots w3c/wai-wcag-em#159.
-
-
11 issues received 22 new comments.
-
Remove procedure section numbers? w3c/wai-wcag-em#186 (10 comments by @hidde, @iadawn, @kfranqueiro)
-
Include identification of assistive devices to be used in the evaluation w3c/wai-wcag-em#178 (1 comment by @hidde)
-
Make it clearer that looking at all pages instead of sample is also good practice w3c/wai-wcag-em#175 (1 comment by @hidde)
-
Recommend pre-filling of realistic data, not just creating new accounts w3c/wai-wcag-em#158 (1 comment by @hidde)
-
-
8 pull requests opened.
-
Editorial suggestions w3c/wai-wcag-em#191, by @tamsinewing555.
-
remove respec numbering to avoid redundant numbering w3c/wai-wcag-em#190, by @hidde.
-
re-add 'view' to avoid linking to working draft developing definition w3c/wai-wcag-em#189, by @hidde.
-
Suggestions from review of draft w3c/wai-wcag-em#187, by @iadawn.
-
Mention videos as part of issue description w3c/wai-wcag-em#181, by @hidde.
-
Mention test accounts and prefill data w3c/wai-wcag-em#180, by @hidde.
-
Move target to note w3c/wai-wcag-em#169, by @hidde.
-
minor changelog name tweak suggestion w3c/wai-wcag-em#167, by @shawna-slh.
-
-
6 pull requests merged.
-
re-add 'view' to avoid linking to working draft developing definition w3c/wai-wcag-em#189.
-
Suggestions from review of draft w3c/wai-wcag-em#187.
-
Move target to note w3c/wai-wcag-em#169.
-
Mention test accounts and prefill data w3c/wai-wcag-em#180.
-
Mention videos as part of issue description w3c/wai-wcag-em#181.
-
minor changelog name tweak suggestion w3c/wai-wcag-em#167.
-
-
4 pull requests received 29 new comments.
-
re-add 'view' to avoid linking to working draft developing definition w3c/wai-wcag-em#189 (1 comment by @iadawn)
w3c/wcag
-
30 issues opened.
-
[spam] w3c/wcag#5028, by @jelliebaehez.
-
[spam] w3c/wcag#5027, by @jelliebaehez.
-
definition of perimeter / "shared pixels" w3c/wcag#5023, by @innoticFR.
-
[spam] w3c/wcag#5016, by @florezrolando1020-lgtm.
-
[spam] w3c/wcag#5015, by @florezrolando1020-lgtm.
-
[spam] w3c/wcag#5014, by @florezrolando1020-lgtm.
-
[spam] w3c/wcag#5011, by @muhrendy848-boop.
-
[spam] w3c/wcag#5008, by @hienrikshiz20132-jpg.
-
[spam] w3c/wcag#5006, by @renehernandez8406-droid.
-
Understanding Conformance refresh w3c/wcag#5003, by @bruce-usab.
-
Typo Suggestion for Technique: G194 w3c/wcag#4998, by @mattyzenny.
-
4.1.2 Name, role, value: Update example section? w3c/wcag#4997, by @detlevhfischer.
-
Add HTML examples to WCAG 2.5.3 label-in-name.html#examples w3c/wcag#4994, by @ljoakley.
-
Links distinguished by color on their own line w3c/wcag#4986, by @cizquierdof.
-
Repeated word in Pause, Stop, Hide understanding page. w3c/wcag#4983, by @EmptyEnd6893.
-
Remove jQuery from working examples w3c/wcag#4979, by @fstrr.
-
Update working examples w3c/wcag#4978, by @fstrr.
-
Broken link on https://www.w3.org/WAI/WCAG21/Techniques/css/C43 w3c/wcag#4976, by @bikerben33.
-
[spam] w3c/wcag#4971, by @felixvc2103-gif.
-
29 issues closed.
-
[spam] w3c/wcag#5027.
-
[spam] w3c/wcag#5028.
-
WCAG 2 Backlog TF review of Label in Name Algorithm w3c/wcag#4312.
-
[spam] w3c/wcag#5014.
-
[spam] w3c/wcag#5015.
-
[spam] w3c/wcag#5016.
-
Update working examples w3c/wcag#4978.
-
Repeated word in Pause, Stop, Hide understanding page. w3c/wcag#4983.
-
Typo Suggestion for Technique: G194 w3c/wcag#4998.
-
Technique F95: Realated technique SCR39 missing w3c/wcag#3789.
-
G54/G160: unclear "advisory techniques" w3c/wcag#4552.
-
G200: why is 3.2.1 On Focus referenced? w3c/wcag#4043.
-
[spam] w3c/wcag#5011.
-
[spam] w3c/wcag#5008.
-
[spam] w3c/wcag#5006.
-
Links distinguished by color on their own line w3c/wcag#4986.
-
[spam] w3c/wcag#4971.
-
-
26 issues received 65 new comments.
-
Greyed out submit buttons (conditional upon successful form completion) w3c/wcag#922 (7 comments by @bruce-usab, @gerardkcohen, @hidde, @innoticFR, @patrickhlauke)
-
Broken link on https://www.w3.org/WAI/WCAG21/Techniques/css/C43 w3c/wcag#4976 (6 comments by @bikerben33, @kfranqueiro, @patrickhlauke)
-
Consider providing examples of when controls _don't_ need labels - 3.3.2 labels or instructions w3c/wcag#4977 (6 comments by @alastc, @brooksienoodlesoup, @patrickhlauke, @xi)
-
WCAG 2 Backlog TF review of Label in Name Algorithm w3c/wcag#4312 (4 comments by @patrickhlauke, @WilcoFiers)
-
What is the WCAG definition of "component"? w3c/wcag#4252 (3 comments by @innoticFR, @patrickhlauke)
-
SC 2.4.4: Use of Title and ARIA Techniques for Supplementing Link Text w3c/wcag#4780 (3 comments by @goetsu, @patrickhlauke)
-
Biblio reference to `[[pointervents]]` in understanding target size (minimum) and (enhanced) w3c/wcag#5004 (2 comments by @patrickhlauke, @plehegar)
-
Input Purposes for User Interface Components is an appendix, so should be marked as non-normative w3c/wcag#3777 (2 comments by @patrickhlauke)
-
Proposed 2.4.6 Guidelines: Risk of Subjective Editorial Judgment and Potential Impacts on Creative Content w3c/wcag#5007 (1 comment by @fstrr)
-
Add HTML examples to WCAG 2.5.3 label-in-name.html#examples w3c/wcag#4994 (1 comment by @patrickhlauke)
-
There is no function to remove server logs on aria-role-log/serverlog.html working-example w3c/wcag#4993 (1 comment by @patrickhlauke)
-
-
19 pull requests opened.
-
Initial draft for Spring 2026 Errata w3c/wcag#5033, by @patrickhlauke.
-
Clarify Dismissible paragraph in Understanding SC 1.4.13 w3c/wcag#5030, by @venkatvemuri28.
-
Upgrade eleventy, glob, and transitive dependencies; remove nunjucks w3c/wcag#5026, by @kfranqueiro.
-
Clarify SC 3.3.2 phone number example wording w3c/wcag#5025, by @venkatvemuri28.
-
3.2.4 understanding: Reword examples w3c/wcag#5022, by @patrickhlauke.
-
Add pointerevents alias to biblio.ts w3c/wcag#5020, by @kfranqueiro.
-
Rework note and example in definition of "image of text" w3c/wcag#5013, by @patrickhlauke.
-
Replace "Single-A" and "Double-A" with "Level A" and "Level AA" w3c/wcag#5009, by @patrickhlauke.
-
Move link to Understanding to its own DD w3c/wcag#5005, by @bruce-usab.
-
G194: typo "a on" → "an" w3c/wcag#4999, by @fstrr.
-
Enable to remove old logs on serverlog.html working-example w3c/wcag#4996, by @mehm8128.
-
Clarifications to labels or instructions SC w3c/wcag#4995, by @scottaohara.
-
Understanding 2.2.2: remove extra "provide" w3c/wcag#4984, by @fstrr.
-
Rename techniques/general/G148.html to G148.html w3c/wcag#4982, by @Erims-Svcbtc.
-
Remove jQuery from Techniques / Working Examples w3c/wcag#4981, by @fstrr.
-
Standardize working examples w3c/wcag#4980, by @fstrr.
-
Update H91.html w3c/wcag#4975, by @goetsu.
-
[spam] w3c/wcag#4974, by @sovereignaquafoundation-max.
-
-
17 pull requests merged.
-
Standardize working examples w3c/wcag#4980.
-
Understanding 2.2.2: remove extra "provide" w3c/wcag#4984.
-
G194: typo "a on" → "an" w3c/wcag#4999.
-
Add missing related technique SCR39 to F95 (and vice-versa) w3c/wcag#4883.
-
Update F85: the trigger control itself is removed w3c/wcag#4769.
-
Remove "advisory techniques" mention from G54 / G160 w3c/wcag#4580.
-
Remove all remaining unused XML/XSLT w3c/wcag#4885.
-
New ARIA technique for the aria-current attribute w3c/wcag#1707.
-
Add note about `transaction-amount` to 1.3.5 understanding w3c/wcag#4362.
-
Don't just refer to SCs by their number, don't use colon w3c/wcag#4939.
-
5 pull requests closed.
-
Rename techniques/general/G148.html to G148.html w3c/wcag#4982.
-
Adds SCR39 as related technique to F95 w3c/wcag#4896.
-
[spam] w3c/wcag#4974.
-
Update non-text-contrast.html w3c/wcag#3946.
-
-
47 pull requests received 246 new comments.
-
Disambiguation of path-based gesture versus dragging movement w3c/wcag#4843 (57 comments by @adampage, @detlevhfischer, @fstrr, @giacomo-petri, @patrickhlauke, @scottaohara)
-
Clarifications to labels or instructions SC w3c/wcag#4995 (23 comments by @detlevhfischer, @scottaohara)
-
Remove note in F24 about css background images w3c/wcag#4823 (14 comments by @bruce-usab, @detlevhfischer, @mgifford, @patrickhlauke)
-
Add note about logo/logotypes contrast to 1.4.3, 1.4.6, and 1.4.11 understanding w3c/wcag#4402 (13 comments by @fstrr, @patrickhlauke)
-
Update normative wording of 4.1.3 and definition of "status message" w3c/wcag#4952 (9 comments by @adampage, @bruce-usab, @detlevhfischer, @patrickhlauke)
-
Fix grammar in Privacy and Security Considerations w3c/wcag#4776 (9 comments by @awkawk, @bruce-usab, @kfranqueiro, @ljoakley, @patrickhlauke)
-
Add note to abbreviations understanding about exemptions w3c/wcag#4815 (8 comments by @chaals, @detlevhfischer, @patrickhlauke)
-
Amend process definition to remove registration example w3c/wcag#3538 (8 comments by @awkawk, @detlevhfischer, @patrickhlauke)
-
Normative change to SC 2.2.2 - replace "information" with "content", rewrite note 3 w3c/wcag#4920 (7 comments by @awkawk, @ljoakley, @patrickhlauke)
-
Amend "contrast ratio" term - move out non-term notes to understanding docs w3c/wcag#4400 (7 comments by @awkawk, @baldino-m, @detlevhfischer, @patrickhlauke, @WilcoFiers)
-
Add extra note to pause-stop-hide understanding about multiple instances w3c/wcag#4817 (5 comments by @adampage, @detlevhfischer, @patrickhlauke)
-
Update F3 "using CSS to include images that convey [...] information" w3c/wcag#4814 (5 comments by @adampage, @patrickhlauke)
-
Proposed new Failure Technique for 1.4.13 (Content on hover or focus) w3c/wcag#4934 (5 comments by @patrickhlauke)
-
Add banner to top of techniques pages, tweak boxout content about techniques w3c/wcag#5002 (4 comments by @alastc, @patrickhlauke, @yatil)
-
Add missing related technique SCR39 to F95 (and vice-versa) w3c/wcag#4883 (4 comments by @patrickhlauke, @venkatvemuri28)
-
Update keyboard-no-exception understanding intent to cover assistive technology like switch input w3c/wcag#3669 (4 comments by @patrickhlauke)
-
WCAG2ICT recommendation: change section / region for 1.3.6 Identify Purpose (AAA) w3c/wcag#4797 (3 comments by @awkawk, @bruce-usab)
-
Update F85: the trigger control itself is removed w3c/wcag#4769 (3 comments by @ljoakley, @patrickhlauke)
-
Don't just refer to SCs by their number, don't use colon w3c/wcag#4939 (3 comments by @patrickhlauke)
-
w3c/wcag#5021 (2 comments by @kfranqueiro)
-
Add clarification in 2.4.4 and 2.4.9 understanding that link text is/includes accessible name w3c/wcag#1570 (2 comments by @patrickhlauke)
-
Update labels-or-instructions.html - adding the reqirement that the label should be permanently available w3c/wcag#2532 (2 comments by @fstrr, @patrickhlauke)
-
w3c/wcag#5031 (1 comment by @kfranqueiro)
-
Replace "Single-A" and "Double-A" with "Level A" and "Level AA" w3c/wcag#5009 (1 comment by @patrickhlauke)
-
Focus obscured and semi-transparent/blurred overlays - reword, and DO make it fail at AAA w3c/wcag#4824 (1 comment by @mgifford)
-
Update keyboard to remove normative acceptance of "completely custom … w3c/wcag#3670 (1 comment by @patrickhlauke)
-
Clarification on example and simplification of tests for H39 w3c/wcag#3613 (1 comment by @patrickhlauke)
-
w3c/matf
-
2 issues closed.
-
17 issues received 22 new comments.
-
Success Criterion 2.5.8 - Target Size (Minimum) - Level AA w3c/matf#10 (4 comments by @detlevhfischer, @JJdeGroot, @shoobe01)
-
Definition of the (underlaying) layer is in a mobile application / mobile platform w3c/matf#270 (1 comment by @JJdeGroot)
-
SUB - 3.2.2 - On Input - take a closer look at what "Changing the setting" means in 3.2.2 w3c/matf#197 (1 comment by @JJdeGroot)
-
Success Criterion 2.4.11 - Focus Not Obscured (Minimum) - Level AA w3c/matf#52 (1 comment by @JJdeGroot)
-
Definition of "set of Web pages / set of software programs" in mobile application context w3c/matf#11 (1 comment by @JJdeGroot)
-
SUB - Accessibility interface - Figure out where the accessibility interface definition should be used w3c/matf#247 (1 comment by @JJdeGroot)
-
Definition of "keyboard interface" in mobile application context w3c/matf#66 (1 comment by @JJdeGroot)
-
-
2 pull requests received 3 new comments.
w3c/coga
-
2 issues opened.
-
Intended Groups w3c/coga#385, by @charleshalldesign.
-
Definition of Module w3c/coga#384, by @charleshalldesign.
-
-
1 issue received 3 new comments.
-
1 pull request received 2 new comments.
-
Fix HTML link to google doc in symbols-non-verbal.html w3c/coga#378 (2 comments by @jesuscarrandi098-lang)
-
w3c/wcag-act
-
2 issues closed.
-
Wide Review Tracker w3c/wcag-act#566.
WCAG 2.x Backlog Task Force
Past meetings
-
4 meetings of the WCAG 2.x Backlog Task Force.
WCAG2ICT Task Force
Participants
-
1 chair appointed in the WCAG2ICT Task Force.
-
Laura Miller became a chair.
-
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
5 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Participants
-
1 participant joined the Accessibility Conformance Testing (ACT) Task Force.
-
Jean-Yves Moyen joined.
-
Mobile Accessibility Task Force
Past meetings
-
2 meetings of the Mobile Accessibility Task Force.
Participants
-
1 participant left the Mobile Accessibility Task Force.
-
Paul Adam left.
-
Cognitive and Learning Disabilities Accessibility Task Force
GitHub
w3c/coga
-
2 issues opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Intended Groups w3c/coga#385, by @charleshalldesign.
-
Definition of Module w3c/coga#384, by @charleshalldesign.
-
-
1 issue in the Cognitive and Learning Disabilities Accessibility Task Force received 3 new comments.
-
1 pull request in the Cognitive and Learning Disabilities Accessibility Task Force received 2 new comments.
-
Fix HTML link to google doc in symbols-non-verbal.html w3c/coga#378 (2 comments by @jesuscarrandi098-lang)
-
TR publications
-
2 documents published.
-
Accessibility Conformance Testing (ACT) Rules Format 1.1 published as a Recommendation. History of Accessibility Conformance Testing (ACT) Rules Format 1.1
-
Past meetings
Participants
-
5 participants joined.
-
Dirk Ginader (Google LLC) joined.
-
Charles Hall (W3C Invited Experts) joined.
-
Chris Grimley (IBM Corporation) joined.
-
Sydney Coleman (Google LLC) joined.
-
Eloisa Guerrero (W3C Invited Experts) joined.
-
-
4 participants left.
-
David Buik (University of Edinburgh) left.
-
Jaunita Flessas (W3C Invited Experts) left.
-
Rain Breaw Michaels (Google LLC) left.
-
Michael Gower (IBM Corporation) left.
-
-
1 organization left.
-
University of Edinburgh left.
-
GitHub
w3c/wcag
-
40 issues opened.
-
Understanding text in video lacks applicable examples w3c/wcag#4966, by @bruce-usab.
-
Missing related resources for sign language need replacing w3c/wcag#4961, by @patrickhlauke.
-
[spam] w3c/wcag#4959, by @wwndel1313-spec.
-
Would "descriptive transcript" pass "alternative for time-based media"? w3c/wcag#4958, by @mbgower.
-
[spam] w3c/wcag#4951, by @josegarielgomezmende678-hue.
-
[spam] w3c/wcag#4950, by @RxHealthcare71351.
-
[spam] w3c/wcag#4949, by @sunilbhaivalvi676-star.
-
[spam] w3c/wcag#4948, by @storeyjeff27-cpu.
-
[spam] w3c/wcag#4946, by @michaelcoats-dotcom.
-
Clarification request on SC 2.4.3 nested focusable example w3c/wcag#4944, by @MeenaPatel17.
-
Translate view area (steradians) into CSS pixels w3c/wcag#4943, by @patrickhlauke.
-
Technique G167 - Example 2 - usability for voice control? w3c/wcag#4942, by @rekapali.
-
[spam] w3c/wcag#4941, by @str8up2themax-dev.
-
SC 2.2.2 animation triggered by scrolling not compliant ? w3c/wcag#4937, by @goetsu.
-
Do user settings count as "information" for 3.3.6? w3c/wcag#4935, by @jkshapiro.
-
[spam] w3c/wcag#4933, by @tomritzow.
-
[spam] w3c/wcag#4932, by @tomritzow.
-
[spam] w3c/wcag#4931, by @tomritzow.
-
[spam] w3c/wcag#4930, by @julmatalikhan302-jpg.
-
[spam] w3c/wcag#4928, by @ganavadillu-max.
-
Consider adding more examples/author guidance for 1.4.11 issues w3c/wcag#4924, by @scottaohara.
-
[spam] w3c/wcag#4923, by @reychellbarrera89-eng.
-
1.3.1 placeholder alone not sufficent as accessible name? w3c/wcag#4918, by @detlevhfischer.
-
errata for 2.1 change log w3c/wcag#4915, by @bruce-usab.
-
Contemplate guidance related to text scaling (meta text-scale) w3c/wcag#4914, by @kfranqueiro.
-
SC 3.3.2 misleading example w3c/wcag#4913, by @goetsu.
-
audio and video terms in glossary need work w3c/wcag#4910, by @bruce-usab.
-
[spam] w3c/wcag#4908, by @cahyudingapo-droid.
-
[spam] w3c/wcag#4907, by @paco20201871-ui.
-
[spam] w3c/wcag#4905, by @fuentesvazquezjoseeduardo.
-
[spam] w3c/wcag#4904, by @hk0140736-ui.
-
[spam] w3c/wcag#4903, by @hk0140736-ui.
-
[spam] w3c/wcag#4902, by @hk0140736-ui.
-
[spam] w3c/wcag#4901, by @hk0140736-ui.
-
-
33 issues closed.
-
[spam] w3c/wcag#4959.
-
[spam] w3c/wcag#4951.
-
Motion actuation (2.5.4) question on exception w3c/wcag#727.
-
Applicability of map markings to SC 1.4.11 w3c/wcag#2025.
-
[spam] w3c/wcag#4950.
-
[spam] w3c/wcag#4949.
-
[spam] w3c/wcag#4948.
-
[spam] w3c/wcag#4946.
-
Clarification request on SC 2.4.3 nested focusable example w3c/wcag#4944.
-
Changelog for Understanding and Techniques pages w3c/wcag#4003.
-
[spam] w3c/wcag#4941.
-
Chore: delete stale branches w3c/wcag#3878.
-
[spam] w3c/wcag#4933.
-
[spam] w3c/wcag#4932.
-
[spam] w3c/wcag#4931.
-
[spam] w3c/wcag#4930.
-
[spam] w3c/wcag#4928.
-
[spam] w3c/wcag#4923.
-
Understanding Conformance page is pretty broken w3c/wcag#3637.
-
Browser default language for date picker with type="date" w3c/wcag#3691.
-
[spam] w3c/wcag#4908.
-
[spam] w3c/wcag#4907.
-
[spam] w3c/wcag#4905.
-
[spam] w3c/wcag#4901.
-
[spam] w3c/wcag#4902.
-
[spam] w3c/wcag#4903.
-
[spam] w3c/wcag#4904.
-
-
45 issues received 112 new comments.
-
Does the SC 1.4.3 Contrast minium exception apply to text outside a disabled control? w3c/wcag#4874 (7 comments by @aardrian, @bruce-usab, @detlevhfischer, @giacomo-petri, @gundulaniemann)
-
2.2.2 Pause, stop, hide SC text should make it clear it applies to all content w3c/wcag#3478 (7 comments by @etherplain, @patrickhlauke)
-
1.3.1 placeholder alone not sufficent as accessible name? w3c/wcag#4918 (6 comments by @detlevhfischer, @mraccess77, @patrickhlauke, @scottaohara)
-
Definition title attributes can be awkwardly clipped w3c/wcag#4899 (6 comments by @kfranqueiro, @patrickhlauke)
-
Anti-Aliasing Significantly Reduces Measured Contrast — Proposal for Rendering-Aware WCAG Guidance w3c/wcag#4954 (6 comments by @nakano0949-web, @patrickhlauke)
-
Do issues with Windows high contrast mode fall under WCAG 2.1? w3c/wcag#623 (5 comments by @detlevhfischer, @maryjom, @mraccess77, @patrickhlauke)
-
Missing related resources for sign language need replacing w3c/wcag#4961 (4 comments by @patrickhlauke, @TestPartners)
-
Technique G167 - Example 2 - usability for voice control? w3c/wcag#4942 (4 comments by @detlevhfischer, @patrickhlauke, @TestPartners)
-
Add one-time-code to list of autocomplete attributes w3c/wcag#2613 (3 comments by @fstrr, @mraccess77, @patrickhlauke)
-
Issue with point 1.4.4 - text resizing up to 200% w3c/wcag#4730 (3 comments by @alastc, @patrickhlauke)
-
Need to clean up references in techniques for use of title attribute w3c/wcag#1561 (3 comments by @bruce-usab, @spanchang, @venkatvemuri28)
-
At narrow viewports, Understanding SC 1.4.11 has undesirable horizontal scrolling overflow w3c/wcag#4641 (2 comments by @adampage, @patrickhlauke)
-
The horizontal scrolling requirement in SC 1.4.8 w3c/wcag#3345 (2 comments by @alastc, @murata2makoto)
-
Text Spacing and Resize Text used in combination? w3c/wcag#4877 (2 comments by @bruce-usab, @mbgower)
-
Clarification: Decorative autoplay background video and SC 2.2.2 vs SC 1.1.1 w3c/wcag#4921 (2 comments by @CharlesBelov, @patrickhlauke)
-
Browser default language for date picker with type="date" w3c/wcag#3691 (2 comments by @patrickhlauke, @shawnthompson)
-
Would "descriptive transcript" pass "alternative for time-based media"? w3c/wcag#4958 (1 comment by @alastc)
-
Errata for 2.5.5 Target Size (Enhanced) to align with 2.5.8 w3c/wcag#2857 (1 comment by @patrickhlauke)
-
example sentence for 3.2.5: Change on Request already covered by 3.2.2: On Input w3c/wcag#1779 (1 comment by @patrickhlauke)
-
Do icons / images without visible text fail 2.4.6 Headings and Labels, always? w3c/wcag#1695 (1 comment by @patrickhlauke)
-
What does nested according to the specification mean in SC 4.1.1 w3c/wcag#978 (1 comment by @patrickhlauke)
-
Clarify page level or viewport level for 2.2.2 Pause, stop, hide when there are many moving things on a page. w3c/wcag#4447 (1 comment by @babielmam)
-
Clarification request on SC 2.4.3 nested focusable example w3c/wcag#4944 (1 comment by @patrickhlauke)
-
SC 2.2.2 animation triggered by scrolling not compliant ? w3c/wcag#4937 (1 comment by @patrickhlauke)
-
WCAG 2 Backlog TF review of Label in Name Algorithm w3c/wcag#4312 (1 comment by @dan-tripp-siteimprove)
-
Feedback on https://deploy-preview-4055--wcag2.netlify.app/understanding/reflow w3c/wcag#4273 (1 comment by @patrickhlauke)
-
Should scroll gradient fail Contrast (Minimum), and are there more desirable patterns? w3c/wcag#4622 (1 comment by @mbgower)
-
Need help confirming proper understanding of 2.4.3 Focus Order w3c/wcag#4895 (1 comment by @A11yTea)
-
19 pull requests opened.
-
Reformat tables out of Understanding 1.4.11 w3c/wcag#4960, by @adampage.
-
Stop relying on githack URLs w3c/wcag#4956, by @kfranqueiro.
-
Don't just refer to SCs by their number alone w3c/wcag#4947, by @patrickhlauke.
-
Don't just refer to SCs by their number, don't use colon w3c/wcag#4939, by @patrickhlauke.
-
[spam] w3c/wcag#4936, by @raulin3989-boop.
-
Update 1.4.3 and 1.4.6 to include references to text in video w3c/wcag#4927, by @patrickhlauke.
-
Edit to two figure captions in Understanding Focus Appearance w3c/wcag#4925, by @bruce-usab.
-
Update PDF9.html w3c/wcag#4922, by @patrickhlauke.
-
Two typos in 2.1 Change Log w3c/wcag#4919, by @bruce-usab.
-
Remove allowCompoundWords from cspell config to catch more errors w3c/wcag#4916, by @kfranqueiro.
-
fix: typo on bypass blocks w3c/wcag#4912, by @bwu-patreon.
-
Add link to revision history in each page's footer w3c/wcag#4909, by @kfranqueiro.
-
Update affiliations w3c/wcag#4906, by @iadawn.
-
-
13 pull requests merged.
-
Stop relying on githack URLs w3c/wcag#4956.
-
Update links in Understanding SC 4.1.3 w3c/wcag#4258.
-
Add link to revision history in each page's footer w3c/wcag#4909.
-
Remove broken link from C29 w3c/wcag#3700.
-
Consistency: "user agent" rather than "user-agent" w3c/wcag#4845.
-
fix: typo on bypass blocks w3c/wcag#4912.
-
Update broken link to working link in G102 w3c/wcag#3703.
-
-
5 pull requests closed.
-
Understanding Label in Name editorial w3c/wcag#4897.
-
Update definition for "status message" w3c/wcag#4840.
-
revise understanding doc to reference web components w3c/wcag#2794.
-
[spam] w3c/wcag#4936.
-
Update PDF9.html w3c/wcag#4922.
-
-
40 pull requests received 177 new comments.
-
New ARIA technique for the aria-current attribute w3c/wcag#1707 (25 comments by @alastc, @bruce-usab, @dbjorge, @fstrr, @kfranqueiro, @patrickhlauke)
-
Add new failure technique for non-semantic ruby annotation w3c/wcag#4829 (11 comments by @adampage, @bruce-usab, @iadawn, @kfranqueiro, @murata2makoto)
-
Don't just refer to SCs by their number, don't use colon w3c/wcag#4939 (10 comments by @bruce-usab, @kfranqueiro, @maryjom, @patrickhlauke, @shawna-slh)
-
Update 1.4.3 and 1.4.6 to include references to text in video w3c/wcag#4927 (7 comments by @bruce-usab, @dbjorge, @patrickhlauke, @TestPartners)
-
Update definition for "status message" w3c/wcag#4840 (7 comments by @bruce-usab, @lilzesh, @patrickhlauke, @TestPartners)
-
2.4.9 Understanding: Qualify Sufficient Techniques w3c/wcag#1166 (7 comments by @kfranqueiro, @patrickhlauke)
-
3.1.2 Language of Parts - Computed acc name clarification + ambiguous example w3c/wcag#4423 (5 comments by @bruce-usab, @patrickhlauke)
-
Update links in Understanding SC 4.1.3 w3c/wcag#4258 (5 comments by @detlevhfischer, @jorycunningham, @patrickhlauke, @scottaohara)
-
Understanding Label in Name editorial w3c/wcag#4897 (4 comments by @bruce-usab, @patrickhlauke, @scottaohara)
-
Update normative wording of 4.1.3 and definition of "status message" w3c/wcag#4952 (4 comments by @electrickite, @fstrr, @patrickhlauke)
-
Technique using ARIA live region and a progress bar (for 4.1.3) w3c/wcag#4686 (4 comments by @patrickhlauke)
-
Better clarify the "Supported Interface" exception for motion in understanding w3c/wcag#4813 (4 comments by @alastc, @detlevhfischer, @patrickhlauke)
-
Transplant note styling from spec base.css to understanding base.css w3c/wcag#4890 (4 comments by @bruce-usab, @iadawn, @kfranqueiro, @patrickhlauke)
-
fix: use correct HTML attribute `aria-describedby`, not `aria-describedBy` w3c/wcag#4917 (4 comments by @d-koppenhagen, @patrickhlauke, @w3cbot)
-
Add missing related technique SCR39 to F95 (and vice-versa) w3c/wcag#4883 (4 comments by @patrickhlauke, @venkatvemuri28)
-
Modernize H62 to deprecate `rb` and complement new failure technique w3c/wcag#4830 (3 comments by @bruce-usab, @murata2makoto)
-
Add note about `transaction-amount` to 1.3.5 understanding w3c/wcag#4362 (3 comments by @bruce-usab, @dbjorge)
-
Reformat tables out of Understanding 1.4.11 w3c/wcag#4960 (2 comments by @bruce-usab, @patrickhlauke)
-
Amend "contrast ratio" term - move out non-term notes to understanding docs w3c/wcag#4400 (2 comments by @patrickhlauke)
-
Clarification of 2.5.3 Label in Name understanding (case insensitivity) w3c/wcag#4836 (2 comments by @bruce-usab)
-
Add clarification about intermediate steps (on the way to 200%) for resize text w3c/wcag#4839 (2 comments by @bruce-usab, @patrickhlauke)
-
Update Link Purpose (in Context) understanding benefits to focus on AT w3c/wcag#1164 (1 comment by @scottaohara)
-
Remove allowCompoundWords from cspell config to catch more errors w3c/wcag#4916 (1 comment by @bruce-usab)
-
New CSS technique: "Using CSS z-index to un-obscure focused content" w3c/wcag#3593 (1 comment by @patrickhlauke)
-
Change “Success Criterion” case from title to sentence in technique template partials w3c/wcag#4900 (1 comment by @bruce-usab)
-
WCAG2ICT recommendation: change section / region for 1.3.6 Identify Purpose (AAA) w3c/wcag#4797 (1 comment by @bruce-usab)
-
Skip "New" paragraph when scanning definitions to make link titles w3c/wcag#4857 (1 comment by @bruce-usab)
w3c/wcag3
-
17 issues opened.
-
Recommend removing “Keyboard navigable if responsive” w3c/wcag3#599, by @adampage.
-
Explainer minor editorial on 2.2 Out of scope w3c/wcag3#593, by @bruce-usab.
-
WCAG 3.0 Requirements: clarification for native mobile apps w3c/wcag3#591, by @spanchang.
-
Rendering‑aware contrast model proposal for WCAG 3 w3c/wcag3#590, by @nakano0949-web.
-
Biometrics overlap w3c/wcag3#572, by @alastc.
-
Nested clauses: impact on readability is language-dependent w3c/wcag3#569, by @murata2makoto.
-
Pointer Controllable vs Pointer Cancellation w3c/wcag3#564, by @bruce-usab.
-
Should "No nested clauses" change from supplemental to best practice? w3c/wcag3#560, by @julierawe.
-
Should Text and Wording add Japanese as a guardrail language? w3c/wcag3#553, by @julierawe.
-
Is "No nested clauses" too hard to implement? w3c/wcag3#552, by @julierawe.
-
Should "Summaries available" change from core to supplemental? w3c/wcag3#551, by @julierawe.
-
-
4 issues closed.
-
Pointer Controllable vs Pointer Cancellation w3c/wcag3#564.
-
[No nested clauses] The word "aced" w3c/wcag3#529.
-
Spell out acronyms w3c/wcag3#527.
-
28 issues received 49 new comments.
-
Ambiguity of the term "character" and its impact on internationalization and testability w3c/wcag3#546 (6 comments by @alastc, @GreggVan, @MakotoUeki, @mraccess77, @TestPartners)
-
“Progress Saved”, as currently written, could place a burden on smaller sites w3c/wcag3#427 (4 comments by @hidde, @venkatvemuri28)
-
Requirements: Text-to-speech supported w3c/wcag3#202 (3 comments by @julierawe, @mraccess77, @shawnthompson)
-
Ambiguity of the term "word" and its impact on internationalization and testability w3c/wcag3#547 (3 comments by @alastc, @murata2makoto)
-
Recommend removing “Keyboard navigable if responsive” w3c/wcag3#599 (2 comments by @hidde, @patrickhlauke)
-
Rendering‑aware contrast model proposal for WCAG 3 w3c/wcag3#590 (2 comments by @nakano0949-web, @patrickhlauke)
-
Consider adding blurred content to Guideline 2.6.1 Avoid physical harm w3c/wcag3#543 (2 comments by @DaleenRabe, @mraccess77)
-
The definition for 'figure caption' appears to make 'Figure captions persistent' impossible to apply w3c/wcag3#584 (1 comment by @patrickhlauke)
-
Controllable infinite scrolling [EXPLORATORY] - Switch off infinite scrolling w3c/wcag3#482 (1 comment by @sazzad-m)
-
Consistent navigation terminology - Simplify understanding + definition of consistent w3c/wcag3#483 (1 comment by @sazzad-m)
-
"purely decorative" vs "decorative" - Decorative images (Foundational) w3c/wcag3#466 (1 comment by @grace-snow)
-
Consider using “user agents” in definition of support instead of “browsers” w3c/wcag3#545 (1 comment by @GreggVan)
-
How does the guideline ensure text is sufficiently readable for people with CVD (colourblindness) w3c/wcag3#403 (1 comment by @sdw32)
-
Return to product starting point - Clarify platform applicability and re-evaluate the type/level w3c/wcag3#448 (1 comment by @giacomo-petri)
-
Location within product - Clarify what appropriate means w3c/wcag3#449 (1 comment by @giacomo-petri)
-
Conventional layouts - Define more clearly the applicability and reconsider which guideline it belongs to w3c/wcag3#443 (1 comment by @giacomo-petri)
-
Supplemental rather than assertion? - Sign language live (Assertion) w3c/wcag3#471 (1 comment by @md84419)
-
[Clear language] word choice, 'text content' vs 'written content' w3c/wcag3#532 (1 comment by @julierawe)
-
[Non-literal language explained] exception doesn't need to be there w3c/wcag3#531 (1 comment by @julierawe)
-
-
32 pull requests opened.
-
Revise Custom Keys Documented w3c/wcag3#598, by @adampage.
-
Fixes for issues found during publication process w3c/wcag3#597, by @iadawn.
-
Set publication dates w3c/wcag3#596, by @iadawn.
-
Add links to other docs w3c/wcag3#595, by @iadawn.
-
Explainer editorial suggestions 2.2 Out of Scope w3c/wcag3#594, by @bruce-usab.
-
Update my fork w3c/wcag3#589, by @bruce-usab.
-
Update pointer-activation-controllable.md w3c/wcag3#588, by @bruce-usab.
-
Explainer editor note w3c/wcag3#586, by @rachaelbradley.
-
Update to explainer w3c/wcag3#585, by @rachaelbradley.
-
Explainer should be draft note w3c/wcag3#583, by @iadawn.
-
fix a couple of typos w3c/wcag3#582, by @fstrr.
-
Fix remaining lodash-es import due to overlapping PRs w3c/wcag3#581, by @kfranqueiro.
-
remove “non-decorative image” and “style property” terms w3c/wcag3#580, by @hidde.
-
fix charter extended to date w3c/wcag3#579, by @shawna-slh.
-
Rename "foundational" to "core" within Explainer w3c/wcag3#578, by @kfranqueiro.
-
Add support for issueLabel field w3c/wcag3#576, by @kfranqueiro.
-
Definitions update 2026 02 w3c/wcag3#574, by @alastc.
-
[Errors indicated] Make it more clear this is about textual indication w3c/wcag3#571, by @hidde.
-
Test fixes w3c/wcag3#570, by @rachaelbradley.
-
Finish renaming pointer-controllable (was missed in children) w3c/wcag3#568, by @kfranqueiro.
-
Publication prep changes w3c/wcag3#567, by @iadawn.
-
fix to conformance section w3c/wcag3#566, by @rachaelbradley.
-
editorial wrt pointer cancellation w3c/wcag3#565, by @bruce-usab.
-
Adjustments to the "about section" for the Feb 2026 draft w3c/wcag3#563, by @alastc.
-
Add ednote to Text appearance guideline w3c/wcag3#562, by @kfranqueiro.
-
re-name expected behavior requirements w3c/wcag3#559, by @fstrr.
-
add supplemental type to focus retention w3c/wcag3#558, by @fstrr.
-
Fix definition respec issues w3c/wcag3#557, by @iadawn.
-
Update contributors w3c/wcag3#555, by @iadawn.
-
-
28 pull requests merged.
-
Fixes for issues found during publication process w3c/wcag3#597.
-
Set publication dates w3c/wcag3#596.
-
Explainer editor note w3c/wcag3#586.
-
Update to explainer w3c/wcag3#585.
-
Explainer should be draft note w3c/wcag3#583.
-
Publication prep changes w3c/wcag3#567.
-
fix a couple of typos w3c/wcag3#582.
-
Fix remaining lodash-es import due to overlapping PRs w3c/wcag3#581.
-
remove “non-decorative image” and “style property” terms w3c/wcag3#580.
-
Add support for issueLabel field w3c/wcag3#576.
-
Rename "foundational" to "core" within Explainer w3c/wcag3#578.
-
fix charter extended to date w3c/wcag3#579.
-
Definitions update 2026 02 w3c/wcag3#574.
-
Update contributors w3c/wcag3#555.
-
Test fixes w3c/wcag3#570.
-
fix to conformance section w3c/wcag3#566.
-
editorial wrt pointer cancellation w3c/wcag3#565.
-
Adjustments to the "about section" for the Feb 2026 draft w3c/wcag3#563.
-
Fix definition respec issues w3c/wcag3#557.
-
Add ednote to Text appearance guideline w3c/wcag3#562.
-
add supplemental type to focus retention w3c/wcag3#558.
-
re-name expected behavior requirements w3c/wcag3#559.
-
Updates from editorial work in October w3c/wcag3#414.
-
Requirements: Link to WCAG 2.0 requirements instead of 2.2 w3c/wcag3#549.
-
-
1 pull request closed.
-
Update my fork w3c/wcag3#589.
-
-
5 pull requests received 15 new comments.
-
[Errors indicated] Make it more clear this is about textual indication w3c/wcag3#571 (4 comments by @hidde, @iadawn)
-
Adjustments to the "about section" for the Feb 2026 draft w3c/wcag3#563 (2 comments by @iadawn, @kfranqueiro)
-
Add ReSpec post-processing check for placeholder definition references w3c/wcag3#577 (1 comment by @hidde)
w3c/matf
-
11 issues received 23 new comments.
-
Definition of the (underlaying) layer is in a mobile application / mobile platform w3c/matf#270 (5 comments by @JJdeGroot, @rwapp)
-
Success Criterion 2.4.2 - Page Titled - Level A w3c/matf#9 (4 comments by @camusamta, @jha11y, @shoobe01, @TanyaVanWorkum)
-
SUB - 2.5.7 - Dragging Movements - acceptable alternatives w3c/matf#265 (3 comments by @detlevhfischer, @JJdeGroot)
-
SUB - Accessibility interface - Figure out where the accessibility interface definition should be used w3c/matf#247 (2 comments by @shoobe01)
-
Success Criterion 2.4.11 - Focus Not Obscured (Minimum) - Level AA w3c/matf#52 (1 comment by @shoobe01)
-
Definition of "keyboard interface" in mobile application context w3c/matf#66 (1 comment by @shoobe01)
-
w3c/wai-wcag-em
-
7 issues opened.
-
illegal activities w3c/wai-wcag-em#165, by @ghost.
-
Illegal activity w3c/wai-wcag-em#162, by @ghost.
-
Change full title of WCAG-EM 2.0? w3c/wai-wcag-em#160, by @shawna-slh.
-
Recommend storing videos as well as screenshots w3c/wai-wcag-em#159, by @lloydi.
-
Recommend pre-filling of realistic data, not just creating new accounts w3c/wai-wcag-em#158, by @lloydi.
-
Some minor typos spotted while reading through w3c/wai-wcag-em#157, by @lloydi.
-
Ip pin w3c/wai-wcag-em#156, by @twilliams06170206-tech.
-
-
5 issues closed.
-
Change full title of WCAG-EM 2.0? w3c/wai-wcag-em#160.
-
Some minor typos spotted while reading through w3c/wai-wcag-em#157.
-
Illegal activity w3c/wai-wcag-em#162.
-
illegal activities w3c/wai-wcag-em#165.
-
Ip pin w3c/wai-wcag-em#156.
-
-
3 issues received 9 new comments.
-
6 pull requests opened.
-
Change document title w3c/wai-wcag-em#166, by @JeroenHulscher.
-
Update devcontainer.json with me Illegal activity w3c/wai-wcag-em#164, by @ghost.
-
illegal activity w3c/wai-wcag-em#163, by @ghost.
-
Fix typos (thanks @lloydi) w3c/wai-wcag-em#161, by @hidde.
-
use samples instead of web pages w3c/wai-wcag-em#155, by @hidde.
-
"the WCAG" -> "WCAG" w3c/wai-wcag-em#154, by @shawna-slh.
-
-
4 pull requests merged.
-
Change document title w3c/wai-wcag-em#166.
-
Fix typos (thanks @lloydi) w3c/wai-wcag-em#161.
-
use samples instead of web pages w3c/wai-wcag-em#155.
-
"the WCAG" -> "WCAG" w3c/wai-wcag-em#154.
-
-
2 pull requests closed.
-
illegal activity w3c/wai-wcag-em#163.
-
Update devcontainer.json with me Illegal activity w3c/wai-wcag-em#164.
-
-
1 pull request received 1 new comment.
w3c/wcag-act
-
3 pull requests merged.
-
untested lowercase as the other outcome types w3c/wcag-act#614.
-
Add link to bikeshed docs w3c/wcag-act#613.
-
Update reference to BBC guidance w3c/wcag-act#612.
-
WCAG 2.x Backlog Task Force
Past meetings
-
4 meetings of the WCAG 2.x Backlog Task Force.
Participants
-
1 chair stepped down in the WCAG 2.x Backlog Task Force.
-
Michael Gower stepped down as a chair.
-
-
3 participants left the WCAG 2.x Backlog Task Force.
-
Jaunita Flessas left.
-
Rain Breaw Michaels left.
-
Michael Gower left.
-
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
5 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Mobile Accessibility Task Force
Past meetings
-
3 meetings of the Mobile Accessibility Task Force.
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 participant left the Cognitive and Learning Disabilities Accessibility Task Force.
-
Rain Breaw Michaels left.
-
WCAG2ICT Task Force
Participants
-
1 chair stepped down in the WCAG2ICT Task Force.
-
Mary Jo Mueller stepped down as a chair.
-
Past meetings
Participants
-
7 participants joined.
-
Abraham Glasser (W3C Invited Experts) joined.
-
Jeniffer Deus (NIC.br - Brazilian Network Information Center) joined.
-
Janina Sajka (Level Access) joined.
-
Emilio Franceschini (Oracle Corporation) joined.
-
Ye Eun Jeon (National Information Society Agency (NIA)) joined.
-
KyoungSoon Hong (National Information Society Agency (NIA)) joined.
-
JAEIL SONG (National Information Society Agency (NIA)) joined.
-
-
8 participants left.
-
Eloisa Guerrero (W3C Invited Experts) left.
-
Emilio Franceschini (Oracle Corporation) left.
-
Janina Sajka (Level Access) left.
-
Charles Adams (Oracle Corporation) left.
-
Casey Smith (Capital One Discover Network) left.
-
Kai Recke (eyeo GmbH) left.
-
Catherine Droege (Thomson Reuters Corp.) left.
-
Alyssa Priddy (Thomson Reuters Corp.) left.
-
-
1 organization joined.
-
National Information Society Agency (NIA) joined.
-
-
1 organization left.
-
eyeo GmbH left.
-
GitHub
w3c/wcag3
-
59 issues opened.
-
[Blocks of text readable (minimum)] make text characteristics optional? w3c/wcag3#548, by @hidde.
-
Assess usage of the word “clearly” throughout the specification w3c/wcag3#544, by @hidde.
-
List common triggers w3c/wcag3#542, by @sydneycolemanfromgoogle.
-
Speech and voice input - Real-time text available w3c/wcag3#540, by @sydneycolemanfromgoogle.
-
Keyboard interface input - Bidirectional navigation w3c/wcag3#539, by @sydneycolemanfromgoogle.
-
Text-to-speech - Text detectable w3c/wcag3#537, by @sydneycolemanfromgoogle.
-
Text Appearance - Text style readable (minimum) w3c/wcag3#536, by @sydneycolemanfromgoogle.
-
Media Alternative - What is a meaningful sound? w3c/wcag3#535, by @sydneycolemanfromgoogle.
-
Issue 425: Address testability concerns in Common Words w3c/wcag3#534, by @sydneycolemanfromgoogle.
-
why say human languages? w3c/wcag3#533, by @sydneycolemanfromgoogle.
-
[No nested clauses] Clarify examples aren't exhaustive w3c/wcag3#530, by @sydneycolemanfromgoogle.
-
[No nested clauses] The word "aced" w3c/wcag3#529, by @sydneycolemanfromgoogle.
-
fail above pass w3c/wcag3#528, by @sydneycolemanfromgoogle.
-
Spell out acronyms w3c/wcag3#527, by @sydneycolemanfromgoogle.
-
[2.2.3 Clear language] Consolidate editor's notes? w3c/wcag3#526, by @sydneycolemanfromgoogle.
-
[Numerical alternatives available] scope too broad? w3c/wcag3#522, by @sydneycolemanfromgoogle.
-
[Transcripts Available] background video unclear w3c/wcag3#519, by @sydneycolemanfromgoogle.
-
Image Alternatives (Foundational Requirements) w3c/wcag3#510, by @sydneycolemanfromgoogle.
-
Add sampling methodology to WCAG? w3c/wcag3#509, by @sydneycolemanfromgoogle.
-
Testability of Clear Language requirements w3c/wcag3#507, by @sydneycolemanfromgoogle.
-
Retro-Compatibility w3c/wcag3#506, by @sydneycolemanfromgoogle.
-
Should bidirectional navigation be symmetrical? w3c/wcag3#505, by @fstrr.
-
[Error notification] Rename to “Application errors available”? w3c/wcag3#503, by @hidde.
-
What counts as "high-contrast" in Adjustable text color? w3c/wcag3#501, by @julierawe.
-
"2.1.1 Which foundational requirements apply" seems incorrect w3c/wcag3#500, by @WilcoFiers.
-
What does a text alternative need to be equivalent to? w3c/wcag3#499, by @WilcoFiers.
-
Typo in the editors note on 2. Guidelines w3c/wcag3#497, by @WilcoFiers.
-
Remove the term "outcome" from WCAG 3.0 w3c/wcag3#496, by @WilcoFiers.
-
Decorative image requirement has self-contradicting definition w3c/wcag3#495, by @WilcoFiers.
-
What does "detectable" mean in "Non-decorative images are detectable" w3c/wcag3#494, by @WilcoFiers.
-
Guidelines are not guidelines w3c/wcag3#493, by @WilcoFiers.
-
Clear language definition w3c/wcag3#492, by @julierawe.
-
Change numerical alternatives to an assertion? w3c/wcag3#491, by @julierawe.
-
Add dark mode w3c/wcag3#489, by @fstrr.
-
-
5 issues closed.
-
Issue 425: Address testability concerns in Common Words w3c/wcag3#534.
-
Define “artificial time limits” w3c/wcag3#439.
-
[spam] w3c/wcag3#488.
-
-
36 issues received 94 new comments.
-
Requirements: Text appearance w3c/wcag3#266 (12 comments by @GreggVan, @Myndex, @patrickhlauke, @sdw32, @TestPartners)
-
[Error notification] “Automatic” and “clearly” are vague, consider removing or removing w3c/wcag3#504 (12 comments by @fstrr, @GreggVan, @hidde, @mraccess77, @skerrvy, @TestPartners)
-
Should bidirectional navigation be symmetrical? w3c/wcag3#505 (11 comments by @detlevhfischer, @fstrr, @GreggVan, @patrickhlauke)
-
why say human languages? w3c/wcag3#533 (8 comments by @fstrr, @hidde, @LJWatson, @mraccess77, @patrickhlauke, @sydneycolemanfromgoogle)
-
Media Alternative - What is a meaningful sound? w3c/wcag3#535 (5 comments by @hidde, @LJWatson, @patrickhlauke)
-
[Captions available (prerecorded)] define “important sounds”? w3c/wcag3#525 (3 comments by @detlevhfischer, @hidde, @sydneycolemanfromgoogle)
-
Speech and voice input - Real-time text available w3c/wcag3#540 (3 comments by @GreggVan, @mraccess77, @sydneycolemanfromgoogle)
-
How does the guideline ensure text is sufficiently readable for people with CVD (colourblindness) w3c/wcag3#403 (2 comments by @Myndex)
-
Ambiguity of the term "character" and its impact on internationalization and testability w3c/wcag3#546 (2 comments by @murata2makoto, @xfq)
-
[Clear language] word choice, 'text content' vs 'written content' w3c/wcag3#532 (2 comments by @hidde, @sydneycolemanfromgoogle)
-
[Non-literal language explained] exception doesn't need to be there w3c/wcag3#531 (2 comments by @hidde, @sydneycolemanfromgoogle)
-
Testability of Clear Language requirements w3c/wcag3#507 (2 comments by @sydneycolemanfromgoogle, @TestPartners)
-
[Data entry validated] what about fields that depend on content of other fields? w3c/wcag3#523 (2 comments by @hidde, @sydneycolemanfromgoogle)
-
[Adjustable text size] should require all mechanisms rather than “at least one” w3c/wcag3#513 (2 comments by @mraccess77, @progers)
-
Ambiguity of the term "word" and its impact on internationalization and testability w3c/wcag3#547 (1 comment by @murata2makoto)
-
Consider using “user agents” in definition of support instead of “browsers” w3c/wcag3#545 (1 comment by @hidde)
-
“Progress Saved”, as currently written, could place a burden on smaller sites w3c/wcag3#427 (1 comment by @venkatvemuri28)
-
Explainer: 2.2 Out of Scope — explicit coverage for native mobile w3c/wcag3#517 (1 comment by @hidde)
-
Clear language - Abbreviations explained --- There's duplicate language w3c/wcag3#538 (1 comment by @julierawe)
-
Gap in WCAG: Toast Notifications That Dismiss on Scroll or Focus Change w3c/wcag3#430 (1 comment by @scurker)
-
-
2 pull requests opened.
-
Requirements: Link to WCAG 2.0 requirements instead of 2.2 w3c/wcag3#549, by @kfranqueiro.
-
-
2 pull requests merged.
-
2 pull requests received 3 new comments.
-
Update 2.4.1 “All elements keyboard actionable” to “All components keyboard operable” w3c/wcag3#511 (1 comment by @kfranqueiro)
w3c/wcag
-
28 issues opened.
-
Definition title attributes can be awkwardly clipped w3c/wcag#4899, by @robinwhittleton.
-
Need help confirming proper understanding of 2.4.3 Focus Order w3c/wcag#4895, by @A11yTea.
-
Improve/extend G215 path-based/multipoint w3c/wcag#4892, by @patrickhlauke.
-
[spam] w3c/wcag#4889, by @christopherjamesmarthinus5-max.
-
[spam] w3c/wcag#4888, by @christopherjamesmarthinus5-max.
-
Dates of recommendations unclear w3c/wcag#4886, by @julezrulez.
-
1.4.4 and 1.4.10 – Refresh or not? w3c/wcag#4884, by @JuliaTol-properaccess.
-
Definitions for live and prerecorded w3c/wcag#4882, by @bruce-usab.
-
Language of the parts for phonetic translations w3c/wcag#4879, by @alastc.
-
[spam] w3c/wcag#4878, by @jabaanartemio.
-
Text Spacing and Resize Text used in combination? w3c/wcag#4877, by @mbgower.
-
"Appropriate accessible name or description" wording is misleading w3c/wcag#4873, by @baldino-m.
-
[spam] w3c/wcag#4871, by @00000000kkkkkk.
-
[spam] w3c/wcag#4870, by @00000000kkkkkk.
-
[spam] w3c/wcag#4866, by @shepperd122-boop.
-
[spam] w3c/wcag#4864, by @tommyk1ee1988-ship-it.
-
[spam] w3c/wcag#4862, by @natefraser130-ux.
-
1.1.1 Divergent language of the image short alternative text w3c/wcag#4860, by @LaurenceZaysser.
-
1.2.5 AUDIO (and textual) description w3c/wcag#4855, by @LaurenceZaysser.
-
[spam] w3c/wcag#4854, by @jackbattop-max.
-
[spam] w3c/wcag#4851, by @ghbfddfkgdgjjyyy-ship-it.
-
[spam] w3c/wcag#4849, by @raymond669966-cmd.
-
[spam] w3c/wcag#4844, by @menamedhat131-lgtm.
-
-
34 issues closed.
-
Dates of recommendations unclear w3c/wcag#4886.
-
High-contrast button: fully accessible or just 1.4.3/1.4.11? w3c/wcag#4893.
-
Proposal to Rephrase Success Criterion 4.1.1 w3c/wcag#2525.
-
Problems with blockquotes' pseudo-element styles w3c/wcag#4134.
-
G82 Technique title (SC 1.1.1) w3c/wcag#2118.
-
Success Criterion 2.4.2 -- Disconnect in the examples w3c/wcag#3803.
-
F26 is suspicious (1.3.3 Sensory Characteristics) w3c/wcag#4115.
-
[spam] w3c/wcag#4889.
-
[spam] w3c/wcag#4888.
-
WCAG 2.1 F63 and WCAG 2.0 F63 have different test procedures w3c/wcag#1047.
-
[spam] w3c/wcag#4878.
-
[spam] w3c/wcag#4871.
-
[spam] w3c/wcag#4870.
-
[spam] w3c/wcag#4866.
-
[spam] w3c/wcag#4864.
-
Referencing latest understanding and quick ref docs w3c/wcag#834.
-
[spam] w3c/wcag#4862.
-
[spam] w3c/wcag#4854.
-
[spam] w3c/wcag#4851.
-
[spam] w3c/wcag#4849.
-
"at least" should be "at most" in WCAG 2.1 SC 1.4.12 w3c/wcag#635.
-
[spam] w3c/wcag#4844.
-
-
1 issue reopened.
-
SHould G223 point to Focus Appearance? w3c/wcag#3967, by @patrickhlauke.
-
-
46 issues received 122 new comments.
-
empty programmatic headings w3c/wcag#4655 (10 comments by @alastc, @bruce-usab, @DuffJohnson, @mraccess77, @patrickhlauke)
-
1.4.4 and 1.4.10 – Refresh or not? w3c/wcag#4884 (9 comments by @bruce-usab, @mraccess77, @TestPartners, @yatil)
-
Applicability of map markings to SC 1.4.11 w3c/wcag#2025 (6 comments by @bruce-usab, @mraccess77, @patrickhlauke, @TestPartners)
-
Definition title attributes can be awkwardly clipped w3c/wcag#4899 (5 comments by @iadawn, @patrickhlauke, @robinwhittleton)
-
Text Spacing and Resize Text used in combination? w3c/wcag#4877 (5 comments by @bruce-usab, @mraccess77, @patrickhlauke)
-
Definitions for live and prerecorded w3c/wcag#4882 (5 comments by @bruce-usab, @GreggVan, @patrickhlauke)
-
SC-1.3.1 - paragraphs not semantically coded w3c/wcag#4759 (4 comments by @bruce-usab, @mmiron-HC, @patrickhlauke, @scottaohara)
-
Language of the parts for phonetic translations w3c/wcag#4879 (4 comments by @JediLin, @patrickhlauke)
-
2.5.7 Dragging Movements - Carousels - Overflowed Containers w3c/wcag#2684 (4 comments by @patrickhlauke, @WestonThayer)
-
Definition of 'user inactivity' seems to include a Note that isn't marked up as a note w3c/wcag#4117 (3 comments by @alastc, @bruce-usab, @patrickhlauke)
-
Is a video player considered a single component for purposes of single character shortcuts SC 2.1.4? w3c/wcag#1950 (2 comments by @detlevhfischer, @patrickhlauke)
-
Need help confirming proper understanding of 2.4.3 Focus Order w3c/wcag#4895 (2 comments by @patrickhlauke, @TestPartners)
-
SC 2.4.4 Link Purpose (In Context) and multiple links with identical link text w3c/wcag#4762 (2 comments by @detlevhfischer, @patrickhlauke)
-
SHould G223 point to Focus Appearance? w3c/wcag#3967 (2 comments by @patrickhlauke, @venkatvemuri28)
-
1.1.1 Divergent language of the image short alternative text w3c/wcag#4860 (2 comments by @LaurenceZaysser, @patrickhlauke)
-
"at least" should be "at most" in WCAG 2.1 SC 1.4.12 w3c/wcag#635 (2 comments by @kfranqueiro, @patrickhlauke)
-
What does nested according to the specification mean in SC 4.1.1 w3c/wcag#978 (1 comment by @patrickhlauke)
-
"Note" CSS / top padding for Understandings not same as Main document, 0px Vs. 5px w3c/wcag#2462 (1 comment by @patrickhlauke)
-
Feedback on https://deploy-preview-4055--wcag2.netlify.app/understanding/reflow w3c/wcag#4273 (1 comment by @patrickhlauke)
-
WCAG 2.1 F63 and WCAG 2.0 F63 have different test procedures w3c/wcag#1047 (1 comment by @kfranqueiro)
-
Does the SC 1.4.3 Contrast minium exception apply to text outside a disabled control? w3c/wcag#4874 (1 comment by @bruce-usab)
-
Recommandation on equivalence/identity between TOC links and their targets (documents/headings) w3c/wcag#4875 (1 comment by @LaurenceZaysser)
-
References to New WCAG 2.2 definitions are setting "New" as title instead of the definition w3c/wcag#3511 (1 comment by @bruce-usab)
-
2.1.4: One-Character Shortcuts: Question About the Third Condition w3c/wcag#4786 (1 comment by @rahulpundir019)
-
2.5.8: Are all slider variants excluded or only sliders that look and are operated like sliders w3c/wcag#2713 (1 comment by @meladmunther)
-
22 pull requests opened.
-
Update "Fork & Edit on GitHub" links to point to precise file w3c/wcag#4898, by @kfranqueiro.
-
Understanding Label in Name editorial w3c/wcag#4897, by @bruce-usab.
-
Adds SCR39 as related technique to F95 w3c/wcag#4896, by @umut-gultekin.
-
G183: Expand rationale to not just be about low vision users w3c/wcag#4887, by @patrickhlauke.
-
Remove all remaining unused XML/XSLT w3c/wcag#4885, by @kfranqueiro.
-
Add missing related technique SCR39 to F95 (and vice-versa) w3c/wcag#4883, by @venkatvemuri28.
-
Remove Chuck from list of co-chairs in footer w3c/wcag#4880, by @kfranqueiro.
-
Tweak Understanding Headings and Labels 2.4.6 w3c/wcag#4876, by @bruce-usab.
-
Nullify WAI blockquote styles w3c/wcag#4863, by @kfranqueiro.
-
Fix example section nesting in H91 and PDF9 w3c/wcag#4859, by @kfranqueiro.
-
Clean up redundant "relates to" text and workaround w3c/wcag#4858, by @kfranqueiro.
-
Skip "New" paragraph when scanning definitions to make link titles w3c/wcag#4857, by @kfranqueiro.
-
Implement cache-busted CSS filenames w3c/wcag#4856, by @kfranqueiro.
-
Update header design w3c/wcag#4853, by @remibetin.
-
Update footer design to match the WAI website's w3c/wcag#4850, by @remibetin.
-
Tweaks to orientation understanding w3c/wcag#4848, by @patrickhlauke.
-
Chore: code cleanup w3c/wcag#4847, by @patrickhlauke.
-
Build: Support entire content of technique h1 being wrapped w3c/wcag#4846, by @kfranqueiro.
-
Consistency: "user agent" rather than "user-agent" w3c/wcag#4845, by @patrickhlauke.
-
18 pull requests merged.
-
Add github workflow to run build on PRs w3c/wcag#4739.
-
Fix ill-formed w3c.json w3c/wcag#4314.
-
Clean up redundant "relates to" text and workaround w3c/wcag#4858.
-
Nullify WAI blockquote styles w3c/wcag#4863.
-
Fix example section nesting in H91 and PDF9 w3c/wcag#4859.
-
remove reference to td elements with scope attributes w3c/wcag#4785.
-
G82: Change "the" to "interactive" in title w3c/wcag#4764.
-
Re-phrased Example 1 description for F33 technique w3c/wcag#4758.
-
Add "text" to the ARIA8 requirement description w3c/wcag#4811.
-
3.3.2 - Form control labels using non-text content w3c/wcag#4626.
-
Remove Chuck from list of co-chairs in footer w3c/wcag#4880.
-
Update header design w3c/wcag#4853.
-
Update footer design to match the WAI website's w3c/wcag#4850.
-
Chore: code cleanup w3c/wcag#4847.
-
Build: Support entire content of technique h1 being wrapped w3c/wcag#4846.
-
-
15 pull requests closed.
-
Fix links to Understanding WCAG 2.1 to 2.2 w3c/wcag#4245.
-
Remove reference to WCAG 2.0 w3c/wcag#3054.
-
Tech no reliance on path or multipoint w3c/wcag#793.
-
Rewrite h69 d macdonald w3c/wcag#1946.
-
updated resource links for H91 technique w3c/wcag#3212.
-
Remove reference to "black/white color blindness" w3c/wcag#2899.
-
Rounding update w3c/wcag#2726.
-
Add note markup to user inactivity definition w3c/wcag#4118.
-
Implement cache-busted CSS filenames w3c/wcag#4856.
-
Issue 2505: re-title H54 to use "term" instead of "word" w3c/wcag#2506.
-
Tweak definition for "human language" w3c/wcag#4787.
-
2.5.1 understanding note on sliders w3c/wcag#3148.
-
-
62 pull requests received 226 new comments.
-
3.3.2 - Form control labels using non-text content w3c/wcag#4626 (22 comments by @alastc, @detlevhfischer, @giacomo-petri, @gundulaniemann, @patrickhlauke)
-
Disambiguation of path-based gesture versus dragging movement w3c/wcag#4843 (22 comments by @detlevhfischer, @fstrr, @patrickhlauke)
-
3.1.2 Language of Parts - Computed acc name clarification + ambiguous example w3c/wcag#4423 (20 comments by @bruce-usab, @detlevhfischer, @giacomo-petri, @patrickhlauke, @WilcoFiers, @YummyBacon5)
-
Update definition for "status message" w3c/wcag#4840 (15 comments by @bruce-usab, @camusamta, @dbjorge, @electrickite, @patrickhlauke, @TestPartners, @WilcoFiers)
-
Better clarify the "Supported Interface" exception for motion in understanding w3c/wcag#4813 (10 comments by @alastc, @bruce-usab, @detlevhfischer, @patrickhlauke)
-
Add note about `transaction-amount` to 1.3.5 understanding w3c/wcag#4362 (8 comments by @patrickhlauke)
-
Update footer design to match the WAI website's w3c/wcag#4850 (7 comments by @iadawn, @kfranqueiro, @remibetin, @w3cbot)
-
Fix typos and clarify “starts automatically” in 2.2.2 Pause, Stop, Hide Understanding w3c/wcag#4822 (6 comments by @bruce-usab, @patrickhlauke)
-
Add new failure technique for non-semantic ruby annotation w3c/wcag#4829 (6 comments by @adampage, @kfranqueiro, @patrickhlauke)
-
Expand title of H54 - "defining instance of a word *or phrase*" w3c/wcag#4812 (6 comments by @bruce-usab, @fstrr, @kfranqueiro, @patrickhlauke)
-
Transplant note styling from spec base.css to understanding base.css w3c/wcag#4890 (5 comments by @iadawn, @patrickhlauke, @scottaohara)
-
Understanding Label in Name editorial w3c/wcag#4897 (4 comments by @baldino-m, @bruce-usab, @kfranqueiro)
-
Conform phrasing in exception of 1.4.13 w3c/wcag#4741 (4 comments by @dbjorge, @patrickhlauke, @WilcoFiers)
-
Update links in Understanding SC 4.1.3 w3c/wcag#4258 (3 comments by @adampage, @bruce-usab, @w3cbot)
-
Issue2525 parsing syntactical - changes to 4.1.1 normative (obsolete) and understanding w3c/wcag#2793 (3 comments by @alastc, @patrickhlauke)
-
Add extra note to pause-stop-hide understanding about multiple instances w3c/wcag#4817 (3 comments by @detlevhfischer, @patrickhlauke)
-
Understanding 1.4.11 - clarify what does _not_ need such contrast w3c/wcag#1252 (3 comments by @gundulaniemann, @patrickhlauke)
-
Update F3 "using CSS to include images that convey [...] information" w3c/wcag#4814 (3 comments by @bruce-usab, @detlevhfischer, @patrickhlauke)
-
G82: Change "the" to "interactive" in title w3c/wcag#4764 (3 comments by @bruce-usab, @detlevhfischer, @patrickhlauke)
-
Total rewrite of example for SCR27 w3c/wcag#4558 (3 comments by @joshuamaker8-create, @patrickhlauke)
-
Technique using ARIA live region and a progress bar (for 4.1.3) w3c/wcag#4686 (3 comments by @bruce-usab, @patrickhlauke)
-
Skip "New" paragraph when scanning definitions to make link titles w3c/wcag#4857 (3 comments by @bruce-usab, @patrickhlauke)
-
Configure cspell to ignore multi-line content within a containing `[lang]` element w3c/wcag#4852 (3 comments by @adampage, @kfranqueiro, @patrickhlauke)
-
Add missing related technique SCR39 to F95 (and vice-versa) w3c/wcag#4883 (2 comments by @umut-gultekin, @venkatvemuri28)
-
Update F46 to cover tables with structural elements that are marked presentational w3c/wcag#3566 (2 comments by @detlevhfischer)
-
Tweak Understanding Headings and Labels 2.4.6 w3c/wcag#4876 (2 comments by @bruce-usab, @patrickhlauke)
-
Add note about logo/logotypes contrast to 1.4.3, 1.4.6, and 1.4.11 understanding w3c/wcag#4402 (2 comments by @detlevhfischer, @patrickhlauke)
-
Normalize `h1` text to permit leading, trailing, and wrapping whitespace w3c/wcag#4831 (2 comments by @adampage, @kfranqueiro)
-
Update "Fork & Edit on GitHub" links to point to precise file w3c/wcag#4898 (1 comment by @patrickhlauke)
-
Remove unnecessary code class and pre xml:space attributes from informative docs w3c/wcag#4611 (1 comment by @patrickhlauke)
-
Update Link Purpose (in Context) understanding benefits to focus on AT w3c/wcag#1164 (1 comment by @patrickhlauke)
-
Add note on synchronized media in audio description definition w3c/wcag#4371 (1 comment by @nigelmegitt)
-
Update the term "name" - make a clearer connection between "name" and "accessible name" w3c/wcag#4633 (1 comment by @bruce-usab)
-
Update keyboard to remove normative acceptance of "completely custom … w3c/wcag#3670 (1 comment by @patrickhlauke)
-
WCAG2ICT recommendation: change section / region for 1.3.6 Identify Purpose (AAA) w3c/wcag#4797 (1 comment by @bruce-usab)
-
w3c/matf
-
2 issues opened.
-
WCAG2ICT v20251211 updates w3c/matf#285, by @JJdeGroot.
-
EN 301 549 v4.1.0 updates w3c/matf#284, by @JJdeGroot.
-
-
2 issues closed.
-
15 issues received 40 new comments.
-
Definition of "user agent" in mobile application context w3c/matf#63 (13 comments by @detlevhfischer, @JJdeGroot, @shoobe01, @TanyaVanWorkum)
-
WCAG2ICT v20251211 updates w3c/matf#285 (5 comments by @detlevhfischer, @JJdeGroot, @TanyaVanWorkum)
-
Definition of the (underlaying) layer is in a mobile application / mobile platform w3c/matf#270 (2 comments by @JJdeGroot)
-
Definition of "set of Web pages / set of software programs" in mobile application context w3c/matf#11 (2 comments by @JJdeGroot)
-
SUB - 2.4.5 - Multiple Ways - draft a note that propose acceptable ways to meet SC in mobile apps w3c/matf#163 (2 comments by @detlevhfischer, @shoobe01)
-
Proposal: Standardization of core accessibility roles and states for native mobile platforms w3c/matf#283 (2 comments by @JJdeGroot, @khsbory)
-
Clarification on the scope of "mobile" devices in WCAG2Mobile w3c/matf#281 (1 comment by @JJdeGroot)
-
-
1 pull request merged.
-
Definition of change of context w3c/matf#279.
-
-
2 pull requests received 2 new comments.
w3c/wai-wcag-em
-
3 issues opened.
-
Avoid repetition w3c/wai-wcag-em#152, by @hidde.
-
Process for comparing structured and random seems weird w3c/wai-wcag-em#151, by @hidde.
-
"Accessibility Supported" and Accessibility APIs... w3c/wai-wcag-em#150, by @A11yTea.
-
-
1 issue closed.
-
[spam] w3c/wai-wcag-em#148.
-
-
1 pull request opened.
-
update status w3c/wai-wcag-em#153, by @hidde.
-
-
1 pull request merged.
-
update status w3c/wai-wcag-em#153.
-
w3c/wcag-act
-
3 pull requests opened.
-
untested lowercase as the other outcome types w3c/wcag-act#614, by @daniel-montalvo.
-
Add link to bikeshed docs w3c/wcag-act#613, by @daniel-montalvo.
-
Update reference to BBC guidance w3c/wcag-act#612, by @chrisn.
-
w3c/coga
-
1 issue opened.
-
Provide information on the methodologies used w3c/coga#382, by @jenstrickland.
-
-
1 pull request opened.
-
Need merge for FPWD of research modules w3c/coga#381, by @ruoxiran.
-
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.
-
Charles Adams left.
-
Accessibility Conformance Testing (ACT) Task Force
Past meetings
-
4 meetings of the Accessibility Conformance Testing (ACT) Task Force.
Participants
-
1 participant left the Accessibility Conformance Testing (ACT) Task Force.
-
Charles Adams left.
-
Mobile Accessibility Task Force
Past meetings
-
3 meetings of the Mobile Accessibility Task Force.
Participants
-
2 participants left the Mobile Accessibility Task Force.
-
Charles Adams left.
-
Casey Smith left.
-
Cognitive and Learning Disabilities Accessibility Task Force
Participants
-
1 participant joined the Cognitive and Learning Disabilities Accessibility Task Force.
-
Janina Sajka joined.
-
-
2 participants left the Cognitive and Learning Disabilities Accessibility Task Force.
-
Janina Sajka left.
-
Charles Adams left.
-
GitHub
w3c/coga
-
1 issue opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Provide information on the methodologies used w3c/coga#382, by @jenstrickland.
-
-
1 pull request opened in the Cognitive and Learning Disabilities Accessibility Task Force.
-
Need merge for FPWD of research modules w3c/coga#381, by @ruoxiran.
-
WCAG2ICT Task Force
Participants
-
1 participant left the WCAG2ICT Task Force.
-
Charles Adams left.
-
Low Vision Accessibility Task Force
Participants
-
1 participant left the Low Vision Accessibility Task Force.
-
Charles Adams left.
-