Minutes from AG (formerly WCAG) WG meetings
This page shows minutes of the Accessibility Guidelines Working Group. Minutes for task forces are available from their respective pages. Minutes for all groups working on WCAG 3 are available from WCAG 3 Minutes.
Minutes | Topics | Resolutions
Display information about these minutes
Showing minutes for channel(s):
2017
- 31 January: Web Content Accessibility Guidelines Working Group Teleconference
- 24 January: Web Content Accessibility Guidelines Working Group Teleconference
- 17 January: Web Content Accessibility Guidelines Working Group Teleconference
- 10 January: Web Content Accessibility Guidelines Working Group Teleconference
- 3 January: Web Content Accessibility Guidelines Working Group Teleconference
2016
- 21 December: Web Content Accessibility Guidelines Working Group Teleconference
- 20 December: Web Content Accessibility Guidelines Working Group Teleconference
- 13 December: Web Content Accessibility Guidelines Working Group Teleconference
- 6 December: Web Content Accessibility Guidelines Working Group Teleconference
- 5 December: SV_MEETING_TITLE
- 29 November: Web Content Accessibility Guidelines Working Group Teleconference
- 22 November: Web Content Accessibility Guidelines Working Group
Teleconference
- Charter status and request - Link for Advisory committee reps: https://www.w3.org/2002/09/wbs/33280/accessibility-guidelines-2016/results
- Communication follow up
- Holiday schedule
- Silver Task Force update
- Survey: https://www.w3.org/2002/09/wbs/35422/ACT_DPUB_Review_Nov_2016/results
- [DPUB] Request to consider inclusion of accessibility metadata
- [DPUB] Request to clarify relationship of guidelines to web content-based publications
- Survey: https://www.w3.org/2002/09/wbs/35422/NewSC_20161122/results
- Review ACT Framework Requirements
- 15 November: Web Content Accessibility Guidelines Working Group
Teleconference
- [Continue with items 2-4]Â https://www.w3.org/2002/09/wbs/35422/GithubIssuesNov12016/
- Moving ARIA2 technique from 3.3.3 and putting in 3.3.2; adding ARIA21 to 3.3.3 #246
- Making G53 more generic to meet 2.4.4 #242
- Include H90 as a technique for 1.3.1 Info and Relationships #240
- Working group review of ACT Framework Requirements + DPUB request https://www.w3.org/2002/09/wbs/35422/ACT_DPUB_Review_Nov_2016/
- CFCs, commenting and participation.
- Silver Stakeholder Submission form
- ACT stuff and DPUB
- 8 November: Web Content Accessibility Guidelines Working Group
Teleconference
- Charter status update
- Charter edit re: DPUB
- CFC Responses
- Survey of GitHub items for review: https://www.w3.org/2002/09/wbs/35422/Misc20161025/results (#'s 1-4)
- Consider language changes in Sufficient Techniques section of 1.3.2 SC for item 1 #243
- Moving ARIA2 technique from 3.3.3 and putting in 3.3.2; adding ARIA21 to 3.3.3
- 1 November: Web Content Accessibility Guidelines Working Group
Teleconference
- [Continue with items 4 & 5 ] Survey of GitHub items for review:Â https://www.w3.org/2002/09/wbs/35422/Misc20161025/Â
- Issue 245
- Issue 244
- https://www.w3.org/2002/09/wbs/35422/SilverTFWorkStatement/
- New Github issues -https://www.w3.org/2002/09/wbs/35422/GithubIssuesNov12016/.
- Include C29 as a technique for 1.4.3 Contrast (Minimum) and related technique for G174 #239
- 25 October: Web Content Accessibility Guidelines Working Group
Teleconference
- 11:00-11:05 - Schedule for November and December
- 11:05-11:35 - Survey of GitHub items for review: https://www.w3.org/2002/09/wbs/35422/Misc20161025/
- Issue 199
- Issue 200
- Issue 232
- 11:05-11:35 - Survey of GitHub items for review: https://www.w3.org/2002/09/wbs/35422/Misc20161025/
- 11:35-12:00 - Silver Plan Survey: https://www.w3.org/2002/09/wbs/35422/SilverProcess/
- 12:00-12:30 - DPUB joining WCAG to discuss techniques and success criteria (please review http://w3c.github.io/dpub-accessibility/)
- 18 October: Web Content Accessibility Guidelines Working Group Teleconference
- 11 October: Web Content Accessibility Guidelines Working Group Teleconference
- 4 October: Web Content Accessibility Guidelines Working Group Teleconference
- 27 September: Web Content Accessibility Guidelines Working Group Teleconference
- 21 September: AG Breakout
- 20 September: WCAG FtF
- 19 September: Web Content Accessibility Guidelines Working Group Teleconference
- 13 September: Web Content Accessibility Guidelines Working Group Teleconference
- 30 August: Web Content Accessibility Guidelines Working Group
Teleconference
- TPAC Agenda (https://www.w3.org/WAI/GL/wiki/Meetings/TPAC_2016)
- Publication of Techniques and Understanding Documents (https://www.w3.org/2002/09/wbs/35422/fall2016pubs/)
- Survey: Initial Review of Proposed SC (https://www.w3.org/2002/09/wbs/35422/NewSC_initialthoughts/)
- New SC: Provide Rapid and Direct Feedback
- 4. New SC: Touch with Assistive Technology
- 23 August: Web Content Accessibility Guidelines Working Group Teleconference
- 16 August: Web Content Accessibility Guidelines Working Group
Teleconference
- TPAC Registration closes September 2:Â https://www.w3.org/2016/09/TPAC
- Updated charter discussion (http://www.w3.org/2016/08/draft-wcag-charter – DRAFT)Â
- Survey on Public Comments: https://www.w3.org/2002/09/wbs/35422/August9Misc/
- Update to H86
- Update to H83
- Changes to PDF Technology Notes
- Remove H46
- Updated charter discussion (http://www.w3.org/2016/08/draft-wcag-charter – DRAFT)Â
- Changing the working group name
- 9 August: Web Content Accessibility Guidelines Working Group Teleconference
- 2 August: Web Content Accessibility Guidelines Working Group Teleconference
- 26 July: Web Content Accessibility Guidelines Working Group Meeting
- TPAC Registration reminder (https://www.w3.org/2016/09/TPAC/)
- Success Criteria acceptance criteria discussion (Lisa shares some example SC)
- WCAG Techniques and Understanding update - comments
- ACT Task Force Proposal presentation and discussion (11:10 – 11:30)
- Communication practices discussion (10 min)
- Success Criteria acceptance criteria discussion (Lisa shares some example SC)
- 19 July: Web Content Accessibility Guidelines Working Group Teleconference
- 12 July: Web Content Accessibility Guidelines Working Group Teleconference
- 5 July: Web Content Accessibility Guidelines Working Group Teleconference
- 28 June: Web Content Accessibility Guidelines Working Group Teleconference
- 21 June: Web Content Accessibility Guidelines Working Group
Teleconference
- TPAC Registration reminder (https://www.w3.org/2016/09/TPAC/)
- WCAG Techniques and Understanding review coming this week. Focus for the months ahead.
- Success Criteria acceptance criteria (https://www.w3.org/2002/09/wbs/35422/WCAG21Reqs/results#xq2)
- Guidance for TF’s and others submitting new SC (https://www.w3.org/2002/09/wbs/35422/WCAG21Reqs/results#xq3)
- 14 June: Web Content Accessibility Guidelines Working Group Teleconference
- 7 June: Web Content Accessibility Guidelines Working Group
Teleconference
- TPAC Registration (https://www.w3.org/2016/09/TPAC/)
- Mobile TF survey: https://www.w3.org/2002/09/wbs/66524/2016-0509/
- https://www.w3.org/2002/09/wbs/35422/20160607Misc/
- PDF Proposaal
- Adding PX comment to G18 and G145
- Remove references of 3.2.1 from f52
- Focus order with TabIndex - is it allowed? #182
- TPAC Registration (https://www.w3.org/2016/09/TPAC/)
- H91: https://lists.w3.org/Archives/Public/w3c-wai-gl/2016AprJun/0660.html
- WCAG Techniques and Understanding timeline
- COGA update (Lisa)
- WCAG Techniques and Understanding timeline
- WCAG.next timeline
- 31 May: Web Content Accessibility Guidelines Working Group Teleconference
- 24 May: Web Content Accessibility Guidelines Working Group Teleconference
- 17 May: Web Content Accessibility Guidelines Working Group
Teleconference
- new introductions
- TPAC Registration https://www.w3.org/2016/09/TPAC/
- WCAG.next
- TPAC Registration https://www.w3.org/2016/09/TPAC/
- Github issues questions (Survey) https://www.w3.org/2002/09/wbs/35422/17thMay2016/
- Proposal Should G83: "Providing text descriptions to identify required fields that were not completed" reference 3.3.2
- <Joshue108> TOPIC: F38 and 4.1.1 conflict ? #186
- "Large text" - using px rather than pt as unit #181
- Does WCAG 2.0 SC 1.3.1 mean that headings areas, footer areas are required to be identified programatically or in text
- 10 May: Web Content Accessibility Guidelines Working Group Teleconference
- 3 May: Web Content Accessibility Guidelines Working Group Teleconference
- 26 April: Web Content Accessibility Guidelines Working Group Teleconference
- 19 April: Web Content Accessibility Guidelines Working Group Teleconference
- 12 April: Web Content Accessibility Guidelines Working Group Teleconference
- 5 April: Web Content Accessibility Guidelines Working Group Teleconference
- 29 March: Web Content Accessibility Guidelines Working Group Teleconference
- 15 March: Web Content Accessibility Guidelines Working Group Teleconference
- 8 March: Web Content Accessibility Guidelines Working Group Teleconference
- 1 March: Web Content Accessibility Guidelines Working Group Teleconference
- 23 February: Web Content Accessibility Guidelines Working Group
Teleconference
- QuickRef update (Eric)
- Low Vision TF update (Jim Allan/AWK)
- WCAG2FAQ review request: https://www.w3.org/WAI/WCAG20/wcag2faq.html (volunteers needed)
- Techniques and Understanding Review: https://www.w3.org/2002/09/wbs/35422/Feb2016TandU/results, closed
- WCAG2FAQ review request: https://www.w3.org/WAI/WCAG20/wcag2faq.html (volunteers needed)
- Dpub review (http://w3c.github.io/dpub-accessibility/)
- Extension document issues (https://www.w3.org/2002/09/wbs/35422/Misc20160223/results, list discussion on 2.2)
- 16 February: Web Content Accessibility Guidelines Working Group Teleconference
- 9 February: Web Content Accessibility Guidelines Working Group Teleconference
- 26 January: Web Content Accessibility Guidelines Working Group
Teleconference
- Extension document comment survey [continued / to be short!]
- Survey for attendance: https://www.w3.org/2002/09/wbs/35422/WhenWCAG/
- • Extension document comment survey [continued / to be short!] (https://www.w3.org/2002/09/wbs/35422/Ext_req_comments/
- • UAAG/ATAG update.
- • Proposed responses to Github issues: https://www.w3.org/2002/09/wbs/35422/Jan26_2016/
- [Github ISSUE: #151] ARIA5: About jQuery code
- Github ISSUE: #150] ARIA4/5: Clarification of a user interface component
- [Github ISSUE: #148] WAI-ARIA Technology Notes: Old UA descriptions
- • Github issues walkthru. https://github.com/w3c/wcag/issues
- 19 January: Web Content Accessibility Guidelines Working Group Teleconference
- 12 January: Web Content Accessibility Guidelines Working Group Teleconference
- 5 January: Web Content Accessibility Guidelines Working Group Teleconference
2015
- 15 December: Web Content Accessibility Guidelines Working Group Teleconference
- 1 December: Web Content Accessibility Guidelines Working Group Teleconference
- 24 November: Web Content Accessibility Guidelines Working Group Teleconference
- 17 November: Web Content Accessibility Guidelines Working Group Teleconference
- 10 November: Web Content Accessibility Guidelines Working Group Teleconference
- 3 November: Web Content Accessibility Guidelines Working Group Teleconference
- 13 October: Web Content Accessibility Guidelines Working Group Teleconference
- 6 October: Web Content Accessibility Guidelines Working Group Teleconference
- 22 September: Web Content Accessibility Guidelines Working Group Teleconference
- 15 September: Web Content Accessibility Guidelines Working Group Teleconference
- 8 September: Web Content Accessibility Guidelines Working Group Teleconference
- 1 September: Web Content Accessibility Guidelines Working Group
Teleconference
- Quickref update
- Re-approval of publication (due to minor change) - survey item1 https://www.w3.org/2002/09/wbs/35422/Sept1st2015/#wbsq2
- "Future link" techniques - survey item2 https://www.w3.org/2002/09/wbs/35422/Sept1st2015/#wbsq3
- Working group Decision policy
- Github issues and work progress - survey item3,4,5,6 https://www.w3.org/2002/09/wbs/35422/Sept1st2015/
- 25 August: Web Content Accessibility Guidelines Working Group
Teleconference
- QuickRef & update
- Quick Reference
- Announcements
- Techniques and understanding update
- Proposal for Techniques
- Survey on https://www.w3.org/2002/09/wbs/35422/20150825/
- Survey Items 2,3
- Item1 (issue 113)
- 4. Issue 105: 1.2.2 and 1.2.4 Non-Vocal Music Captioning Requirements
- Issue 71: C31:Using percent for font sizes
- 11 August: Web Content Accessibility Guidelines Working Group Teleconference
- 21 July: Web Content Accessibility Guidelines Working Group Teleconference
- 7 July: Web Content Accessibility Guidelines Working Group Teleconference
- 30 June: Web Content Accessibility Guidelines Working Group
Teleconference
- Review of Editor's drafts for Techniques and Understanding documents https://www.w3.org/2002/09/wbs/35422/publication_july2015/
- QRG Updates from Eric
- Discussion of Low Vision Task Force - and review of draft task force work statement http://www.w3.org/WAI/GL/low-vision-a11y-tf/work-statement
- Discussion of breakdown of WG/TF tasks.
- 23 June: Web Content Accessibility Guidelines Working Group Teleconference
- 9 June: Web Content Accessibility Guidelines Working Group Teleconference
- 2 June: Web Content Accessibility Guidelines Working Group
Teleconference
- New /TR Style Sheet Update 2016. https://www.w3.org/2002/09/wbs/35422/TRUpdate2016/
- Continue review of Post-WCAG 2 issues - from row 13/14 https://www.w3.org/WAI/GL/wiki/Post_WCAG_2_Issues_Sorted
- Quickref update
- Discussion on Summer Schedule for working group
- Continue review of Post-WCAG 2 issues - from row 13/14 https://www.w3.org/WAI/GL/wiki/Post_WCAG_2_Issues_Sorted
- 26 May: Web Content Accessibility Guidelines Working Group Teleconference
- 19 May: Web Content Accessibility Guidelines Working Group Teleconference
- 12 May: Web Content Accessibility Guidelines Working Group Teleconference
- 5 May: Web Content Accessibility Guidelines Working Group Teleconference
- 28 April: Web Content Accessibility Guidelines Working Group Teleconference
- 21 April: Web Content Accessibility Guidelines Working Group Teleconference
- 14 April: Web Content Accessibility Guidelines Working Group Teleconference
- 7 April: Web Content Accessibility Guidelines Working Group
Teleconference
- TPAC
- TPAC final call
- Extension model discussion: Including the sub topics
- Background pointers
- What type of extensions?
- Will extensions be A, AA, AAA?
- Will extensions conform to WCAG requirements for success criteria?
- Categorisation of current open issues in the context of the extension model
- WCAG working group and public engagement/interaction
- 31 March: Web Content Accessibility Guidelines Working Group
Teleconference
- TPAC https://www.w3.org/2002/09/wbs/35422/24thMarch2015/results#x2673
- TPAC 2015
- Page structure tutorial https://www.w3.org/2002/09/wbs/35532/PageStructureTutorial1/
- New issue https://github.com/w3c/wcag/issues/86
- New Issues
- Page structure tutorial https://www.w3.org/2002/09/wbs/35532/PageStructureTutorial1/
- Page Structure Tutorial
- Charter update - https://www.w3.org/2002/09/wbs/35422/2015WCAGSurvey/
- Charter Discussion
- 24 March: Web Content Accessibility Guidelines Working Group
Teleconference
- WCAG F2F @ TPAC Sapporo, and comment responses etc New survey https://www.w3.org/2002/09/wbs/35422/24thMarch2015/
- Would you attend a WCAG Face to Face meeting at TPAC Sapporo 2015?
- [Updated Test Procedure F68] Procedure looks wrong
- [Comment Response F3] Clarify the meaning of "is also available" in step #3 of F3 test #80
- [Comment response G136] Meaning of "Alternate version" is not clear
- Returning to [Comment Response F3] Clarify the meaning of "is also available" in step #3 of F3 test #80
- Techniques work
- Charter update
- Techniques work
- 17 March: Web Content Accessibility Guidelines Working Group
Teleconference
- Review of Issues https://github.com/w3c/wcag/issues
- Monitoring of WAI-IG list
- Discussion of timeline and goals for next update of supporting documents
- Reminder about outstanding actions
- TPAC 2015. 26-30 October, 2015 in Sapporo, Japan
- TPAC
- Page Structure Tutorial: http://w3c.github.io/wai-tutorials/page-structure/
- Page Structure Tutorial
- 10 March: Web Content Accessibility Guidelines Working Group Teleconference
- 17 February: Web Content Accessibility Guidelines Working Group Teleconference
- 10 February: Web Content Accessibility Guidelines Working Group Teleconference
- 3 February: Web Content Accessibility Guidelines Working Group Teleconference
- 27 January: Web Content Accessibility Guidelines Working Group Teleconference
- 20 January: Web Content Accessibility Guidelines Working Group
Teleconference
- [Comments needing responses]: https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses
- Continue tutorials review (plus WG review of sections 6-11 of Forms Tutorial: <https://www.w3.org/2002/09/wbs/1/TutorialsForms/> )
- #6 Validating Input
- 7. User Notifications
- 8. Multi Page Forms
- 9. Custom Controls
- 11. Overall and other
- 13 January: Web Content Accessibility Guidelines Working Group Teleconference
- 6 January: Web Content Accessibility Guidelines Working Group
Teleconference
- WCAG WG review of the Cognitive A11y TF 'Cognitive Accessibility User Research' document.
- Cognitive Accessibility User Research' document
- Upcoming public review of WCAG Understanding and Techniques with How to Meet public review drafts
- working group approval for public review
- Final feedback for final tasks of Quickref refresh.
- Final Tutorials Review/Publication approval Cycle
- Discussion on working group priorities
2014
- 16 December: Web Content Accessibility Guidelines Working Group Teleconference
- 9 December: Web Content Accessibility Guidelines Working Group
Teleconference
- Open question on a comment, and a proposed response https://www.w3.org/2002/09/wbs/35422/9thDec2014/results
- LC-2950 Current uniqueness or necessity of F17 is unclear
- Question regarding LC-2951 (Remove F42)
- Please continue to feed the wiki with your comments and feedback https://www.w3.org/WAI/GL/wiki/Resource_Redesign/Quickref/Analysis
- agendum 2. "Please continue to feed the wiki with your comments and feedback
- parsing feedback from the working group survey
- agendum 3. "parsing feedback from the working group survey"
- Discuss https://www.w3.org/2006/02/lc-comments-tracker/35422/NOTE-WCAG20-TECHS-20140306/2958
- LC-2958
- discuss http://www.w3.org/2006/02/lc-comments-tracker/35422/WD-WCAG20-TECHS-20140107/2877
- LC-2877
- 2 December: Web Content Accessibility Guidelines Working Group
Teleconference
- US Section 508 Access Board
- add input on the Quickref update https://www.w3.org/WAI/GL/wiki/Resource_Redesign/Quickref/Analysis
- survey review
- 1. Please provide any comments on the visual design or informational structure that you feel particularly help or hinder use of the techniques document or of individual techniques.
- 2. Please provide any suggestions you have for changes to make the techniques document more useful or easier to use
- 3. Do you have any suggestions for improvements to the Introduction to Understanding WCAG 2.0 section?
- 4. Do you have any suggestions for improvements to the Understanding Techniques for WCAG Success Criteria section?
- 5. Please provide any comments on the visual design or informational structure that you feel particularly help or hinder use of the Understanding document.
- 6. Please provide any suggestions you have for changes to make the techniques document more useful or easier to use.
- 7. Do you have any suggestions for improvements to these sections (of How To Meet)?
- 8. When customizing the How to Meet WCAG 2.0 resource to show only a specific technology, such as CSS, general techniques are also included. Do you like this? Please provide any comments or thoughts on this behavior you would like to share.
- 10. Please provide any comments on the visual design or informational structure that you feel particularly help or hinder use of the How to Meet WCAG 2.0 resource
- 11. Please provide any suggestions you have for changes to make the How to Meet WCAG 2.0 document more useful or easier to use.
- 12. Are there any other ideas or suggestions that you have that would make implementing support for the WCAG 2.0 success criteria easier for you?
- 13. Do you feel that there is benefit in offering additional features to the documents discussed, such as tagging, commenting, or rating to help share further information on these resources? Please comment.
- 14. Please provide any comments or suggestions for improving the information and usability of the WCAG Overview
- 16. Please provide any comments or suggestions for improving the information and usability of The WCAG 2.0 Documents
- 18. Please provide any comments or suggestions for improving the information and usability of the Accessibility Principles page
- Action Items
- 25 November: Web Content Accessibility Guidelines Working Group Teleconference
- 18 November: Web Content Accessibility Guidelines Working Group Teleconference
- 4 November: Web Content Accessibility Guidelines Working Group
Teleconference
- New Survey https://www.w3.org/2002/09/wbs/35422/2ndNov2014/
- 1. Mobile TF proposed changes to G90:Providing keyboard-triggered event handlers
- 2. Mobile TF proposed changes to G162: Positioning labels to maximize predictability of relationships
- Discussion of efficiency improvements for Working Group processes
- Continue review/analysis of supporting documents survey data
- 27 October: Web Content Accessibility Guidelines Working Group
Teleconference
- Recap of Sunday meeting
- Discuss ways to increase engagement by working group members
- Long-term vision / WAI2020
- Plan for reaching out to stakeholders
- Long-term vision / WAI2020
- Plan for reaching out to stakeholders
- Review of survey data analysis with EO and WAI-DEV project
- QuickRef improvement planning work
- Discussion of Institutional Memory project
- Discussion of efficiency improvements for Working Group processes
- Review of actions and next steps
- 26 October: Web Content Accessibility Guidelines Working Group Teleconference
- 21 October: Web Content Accessibility Guidelines Working Group
Teleconference
- TPAC Plans
- TPAC
- October 14 Survey: https://www.w3.org/2002/09/wbs/35422/14thOct2014/
- LC-2961 UPDATED] Remove example 1 from ARIA7
- [LC-2954 UPDATED] Clarify F68 is applicable for controls that use visible labels
- 3. Mobile TF proposed changes to G53:Identifying the purpose of a link using link text combined with the text of the enclosing sentence
- Mobile TF proposed changes to G60:Playing a sound that turns off automatically within three seconds
- [LC-2961 UPDATED] Remove example 1 from ARIA7
- Mobile TF proposed changes to G61:Presenting repeated components in the same relative order each time they appear
- 14 October: Web Content Accessibility Guidelines Working Group
Teleconference
- Finish survey from last week
- G78
- G202
- G9
- Eric Eggert will join the call for a brief discussion on WCAG feedback on the WAI-DEV tutorials.
- Carousel interaction #163
- Finish survey from last week
- Technique needed for CSS and alt text for generated content: https://www.w3.org/WAI/PF/Group/track/issues/542
- Discuss Action 274 and Mobile TF feedback
- Follow up on Aside technique
- Action 274
- TPAC Planning: Current TPAC structure and other ideas.
- 7 October: Web Content Accessibility Guidelines Working Group
Teleconference
- Public Survey update
- TPAC reminder
- Survey for October 7, 2014 https://www.w3.org/2002/09/wbs/35422/20141007Misc/
- 2. [LC-2966] Proposal to review guidelines for language markup appropriateness
- 3. [LC-2953] F55: Remove Example 3 as it's same as Example 2
- 4. Mobile TF proposed changes to G9
- 1. [LC-2954] Clarify F68 is applicable for controls that use visible labels
- 5. Mobile TF proposed changes to G21
- 6. Mobile TF proposed changes to G78
- 30 September: Web Content Accessibility Guidelines Working Group
Teleconference
- Open actions review [start at ACTION-213]:
- Action 274
- Action 213
- Action-206
- Action-205
- Action 204
- Action-203
- Action-198
- Action-192
- Action 190
- Survey for September 30th, 2014:
- Carousel tutorial review
- [LC-2957] Remove layout table section from H39 and H73
- LC-2957
- LC-2959
- [LC-2956] Remove F48
- LC-2956
- [LC-2962] Updated response to 'Placeholder text responsibility'
- [LC-2961] Remove example 1 from ARIA7
- LC-2954
- 23 September: Web Content Accessibility Guidelines Working Group
Teleconference
- TPAC registration reminder
- TPAC registration reminder. If you have not registered, please do so asap per Michael. The plan is for 1PM Sunday meeting at Google.
- Survey for September 23, 2014 https://www.w3.org/2002/09/wbs/35422/20140923/results
- Survey for Sept 23.
- forms tutorial review.
- Follow up on Aside technique https://www.w3.org/WAI/GL/wiki/Using_the_aside_element_to_indicate_tangentially_related_content
- Mobile update to G4
- Survey for September 23, 2014 https://www.w3.org/2002/09/wbs/35422/20140923/results
- Mobile Update to G4
- Clarify the diffrence between F40 and F41
- Placeholder Accessibility
- 16 September: Web Content Accessibility Guidelines Working Group
Teleconference
- Open actions https://www.w3.org/WAI/GL/track/actions/open
- Open actions
- Comments needing responses (Please pick two each)
- Comments needing responses
- Draft of User Survey and TPAC planning for September 16th, 2014:
- TPAC Planning
- Update on HTML5/ARIA TF call schedule
- HTML5/ARIA tf meetings
- Discussion on approaches to Mobile Technique development and existing techniques
- New EOWG Forms Tutorial
- 9 September: Web Content Accessibility Guidelines Working Group
Teleconference
- Publication update
- TPAC F2F - October 25-26, 2014
- Miscellaneous Survey for September 9, 2014: https://www.w3.org/2002/09/wbs/35422/Sept9Survey2014/
- LC-2964: 1.3.2. Violation?
- Mobile: Change to Technique G4
- Open actions (https://www.w3.org/WAI/GL/track/actions/open) and issues (https://www.w3.org/WAI/GL/track/issues/open)
- Miscellaneous Survey for September 9, 2014: https://www.w3.org/2002/09/wbs/35422/Sept9Survey2014/
- Companion survey document
- 2 September: Web Content Accessibility Guidelines Working Group
Teleconference
- September 2nd Survey - https://www.w3.org/2002/09/wbs/35422/Sept2nd_2014/
- Publication of editors draft
- Final review draft of the technique
- Response to comment 2963: F89 confusing
- Update on Accessibility Support Database Update from Shadi
- Institutional Memory Collection for 26th August 2014
- Institutional Memory
- 26 August: Web Content Accessibility Guidelines Working Group
Teleconference
- August 26th Survey - https://www.w3.org/2002/09/wbs/35422/comments26Aug2014/
- August 26 Survey
- LC-2949: Not just charts and graphs
- Captions for video in foreign language
- Captions Techniques Update
- Publication review, approval, and link checking. Timeline update
- Institutional Memory Collection for 26th August 2014 - https://www.w3.org/2002/09/wbs/35422/IMCAugust2014/
- Review open issues and actions http://www.w3.org/WAI/GL/track/actions/open
- 19 August: Web Content Accessibility Guidelines Working Group
Teleconference
- Feedback on Developers' Guide to Features of Web Accessibility Evaluation Tools 29th July 2014 https://www.w3.org/2002/09/wbs/35422/29thAugust2014/results
- Survey from August 5th- https://www.w3.org/2002/09/wbs/35422/20140805/results (only #s 4 and 6).
- Questions for foreign language
- 6. Improvements to Understanding and Techniques
- 12 August: Web Content Accessibility Guidelines Working Group Teleconference
- 5 August: Web Content Accessibility Guidelines Working Group Teleconference
- 29 July: Web Content Accessibility Guidelines Working Group Teleconference
- 22 July: Web Content Accessibility Guidelines Working Group Teleconference
- 15 July: Web Content Accessibility Guidelines Working Group Teleconference
- 8 July: Web Content Accessibility Guidelines Working Group Teleconference
- Actions and Issues check-in:
- Update on Mobile A11y TF progress from Kathy
- Final pass to resolve any remaining comments on WCAG-EM pre publication.
- Continue with Success Criteria walkthrough:
- New SC Walkthrough Survey:
- Final pass to resolve any remaining comments on WCAG-EM pre publication.
- Comments needing responses https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses
- New Survey:
- 24 June: Web Content Accessibility Guidelines Working Group
Teleconference
- Reminder No call next week - July 1
- Discussion with WCAG-EM about changes and requested review (Shadi - 15 minutes)
- Updates with WCAG Evaluation Methodology
- Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/
- If ready, discussion on EO proposal for 'techniques being informative' wording
- From June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/
- Review of comments https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses
- Review of open actions and issues. http://www.w3.org/WAI/GL/track/actions/ http://www.w3.org/WAI/GL/track/issues/
- Start walking through WCAG SC for pros/cons/improvements:
- 17 June: Web Content Accessibility Guidelines Working Group
Teleconference
- Upcoming calls. No call July 1.
- Cognitive Task Force Report https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page#Reports
- June 10 Survey: https://www.w3.org/2002/09/wbs/35422/10thJune2014/
- 1. Pull request #27 Proposed edit for ACTION-1378
- 2. Pull request #28 ACTION-184 Example of validating multiple controls
- 3. New technique: Creating a conforming alternate version for web pages which are designed to be responsive / progressively enhanced
- 10 June: Web Content Accessibility Guidelines Working Group
Teleconference
- #5 left on survey https://www.w3.org/2002/09/wbs/35422/2705_2014/
- https://www.w3.org/2002/09/wbs/35422/20140520/ (#3 and #4)
- Review open action items: http://www.w3.org/WAI/GL/track/actions/
- Review open issues: http://www.w3.org/WAI/GL/track/issues/
- https://www.w3.org/WAI/GL/wiki/Post_WCAG_2
- https://www.w3.org/WAI/GL/wiki/Using_the_aside_element_to_associate_content_related_to_an_article
- 3 June: Web Content Accessibility Guidelines Working Group
Teleconference
- Updated LC-2895 Response: https://www.w3.org/2002/09/wbs/35422/EOLC2895/
- Review open action items: http://www.w3.org/WAI/GL/track/actions/
- Review open action items: http://www.w3.org/WAI/GL/track/actions/"
- Review open issues: http://www.w3.org/WAI/GL/track/issues/
- Issue 11
- ISSUE 14
- https://www.w3.org/WAI/GL/wiki/EOTutorials_review#Overview_of_Issues
- EO Tutorials Review
- https://www.w3.org/2002/09/wbs/35422/2705_2014/ (all 4 items)
- LC-2869: Table failure modification
- 27 May: Web Content Accessibility Guidelines Working Group Teleconference
- 20 May: Web Content Accessibility Guidelines Working Group Teleconference
- 13 May: Web Content Accessibility Guidelines Working Group
Teleconference
- Review of https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses (4 new)
- Update on Cognitive Accessibility Task Force from Lisa Seeman.
- Review of https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses (4 new)
- Discussion on comment processing - improving how we deal with questions to the working group, from the working group.
- Misc Survey 6th May 2014 https://www.w3.org/2002/09/wbs/35422/20140506/results (only LC-2854)
- Survey. Techniques and Institutional Memory. https://www.w3.org/2002/09/wbs/35422/13May2014/
- 6 May: Web Content Accessibility Guidelines Working Group Teleconference
- 29 April: WCAG Working Group
- 1) Complete review of technique 'Using the region role to identify a region on a page'
- Proposed comment responses:
- Comment LC-2922: Draft response "Are ARIA landmarks required?"
- 2891
- 2888
- 2885
- 2886
- Cognitive TF update: From Lisa. [Latest TF report available here https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Reports
- Update on technique assignments and progress
- Update on WCAG @ TPAC 2014 https://www.w3.org/2002/09/wbs/35422/wcagtpac14/
- 22 April: Web Content Accessibility Guidelines Working Group
Teleconference
- Publication timeline update
- WCAG @ TPAC 2014? https://www.w3.org/2002/09/wbs/35422/wcagtpac14/
- Miscellaneous responses to survey items and 1 new technique: https://www.w3.org/2002/09/wbs/35422/misc22April2014/
- LC2917
- LC2916
- LC2918
- LC2919
- New Technique: Using the region role to identify a region on a page
- 15 April: Web Content Accessibility Guidelines Working Group
Teleconference
- Publication timeline update - Techniques in by May 15!
- Survey on techniques and comments: https://www.w3.org/2002/09/wbs/35422/15thApril2014/
- move h87 to a general technique
- Comment LC-2892: Draft response
- The following is a proposed update to technique H30. The proposal is to add an example 7 to the technique: Example 7REOLUTION:
- G141 edit
- 8 April: Web Content Accessibility Guidelines Working Group
Teleconference
- republishing WCAG supporting docs
- Publication timeline update
- New survey of draft responses to comments and one new technique https://www.w3.org/2002/09/wbs/35422/08042014survey/
- Comment LC-2890: Draft response
- Comment LC-2903: Draft response
- Comment LC-2892: Draft response
- LC-2880: Draft response
- ARIA Technique: Using Aria-Invalid to Indicate An Error Field
- 1 April: Web Content Accessibility Guidelines Working Group
Teleconference
- Publications Update
- New survey of draft responses to comments https://www.w3.org/2002/09/wbs/35422/1stApril2014/
- update on https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses
- review of David MacDs http://davidmacd.com/WCAG/wcag-html5-techniques-review.html
- Update on Techniques progress https://www.w3.org/WAI/GL/wiki/Working_Group_Techniques_Development_Assignments
- 25 March: Web Content Accessibility Guidelines Working Group Teleconference
- 18 March: Web Content Accessibility Guidelines Working Group Teleconference
- Joint meeting with Eval Task Force
- Review teams: Do we recommend that website accessibility evaluations are more effective with a team of 2-3 evaluators, as opposed to 1 only?
- Techniques: Can we be more encouraging about the use of techniques (for evaluation!), yet be clear that the SCs are the checking targets?
- Support for evaluators: Throughout the work we've noted that WCAG 2 does not provide adequate support for evaluators and that we will not be able to cover these needs in WCAG-EM -- reporting back to WCAG...
- Scoring: There are many reasons for and against, and different (and strong) opinions within WCAG WG -- how should we move forward on this?
- Cognitive Task Force Report (Lisa Seeman)
- Mobile TF update
- Mobile Task Force (Kathy Wahlbin)
- Task Forces checkin - Mobile, Cognitive, Techniques
- Techniques Task Force
- Gap analysis - requirements not covered by WCAG 2.0
- Explore future guidelines work goals
- Gap analysis - requirements not covered by WCAG 2.0
- Improving public input and source format
- 11 March: Web Content Accessibility Guidelines Working Group
Teleconference
- Draft responses for March 11th, 2014
- Publication Update
- Review WCAG errata (http://www.w3.org/WAI/WCAG20/errata/)
- Review available techniques (https://www.w3.org/WAI/GL/wiki/Working_Group_Techniques_Development_Assignments)
- Call for collecting information published by others on WCAG 2.0 related to concerns or needed improvements
- Draft responses for March 11th, 2014
- LC-2882: Add a warning about the poor support for this technique h69
- Comment LC-2884: This technique should be generalized h90
- Comment LC-2877: The technique should mention input type = file
- Comment LC-2905: Techniques F17 procedure #1 and F77 both check for duplicate ID values (#15)
- 4 March: Web Content Accessibility Guidelines Working Group
Teleconference
- Updating the scribe list
- Close out final comment https://www.w3.org/2002/09/wbs/35422/aria10f65/results
- Incorrect JAWS keystroke comment https://www.w3.org/2006/02/lc-comments-tracker/35422/WD-WCAG20-TECHS-20140107/2898
- Responding to unaddressed comments
- Misc survey for February 25th, 2014 https://www.w3.org/2002/09/wbs/35422/20140225/results
- LC-2880: This technique should be a failure technique
- LC-2882: Add a warning about the poor support for this technique h69
- Git Pull request 8: Additional example for ARIA9
- LC-2895: Add "Techniques for Specific Technologies"
- CSUN - WCAG F2F Agenda http://www.w3.org/WAI/GL/2014/03/ftf-meeting
- Assigning comment responses https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses
- Publication status
- 25 February: Web Content Accessibility Guidelines Working Group
Teleconference
- Misc survey for February 25th, 2014 https://www.w3.org/2002/09/wbs/35422/20140225/
- Edits to ARIA10
- CSUN Hackathon for AT testing of ARIA
- Edits to ARIA10
- 2. Revised version of F65
- 5. Git Pull request 9: Less Latin
- 6. Git Pull request 8: Additional example for ARIA9
- 7. REDO: LC-2895: Add "Techniques for Specific Technologies"
- discuss ARIA10/F65 https://www.w3.org/2002/09/wbs/35422/imagediscussmtg/results
- CSUN
- 20 February: Web Content Accessibility Guidelines Working Group Teleconference
- 18 February: Web Content Accessibility Guidelines Working Group
Teleconference
- New Techniques: https://www.w3.org/2002/09/wbs/35422/20140211misc/
- LC-2872: GIT and official W3C docs
- LC:2874: Edits to G200
- LC-2883: HTML technique is a duplicate of H93
- LC-2893: Understanding Sucess Criterion 1.4.3
- LC2895: Add "Techniques for Specific Technologies"
- LC-2897: ARIA 10 and requiring alt attributes
- LC-2881: This technique should be advisory G183
- Volunteers needed for remaining comments
- 11 February: Web Content Accessibility Guidelines Working Group
Teleconference
- New Techniques: https://www.w3.org/2002/09/wbs/35422/20140211misc/
- New Technique: Using the track element to provide captions
- New Technique: Using the track element to provide audio descriptions
- CSUN update – meeting confirmed
- New Techniques: https://www.w3.org/2002/09/wbs/35422/20140211misc/
- 3. New Failure: Failure of SC 1.4.2
- CSUN update – meeting confirmed
- CSUN
- Techniques planning and expectations for working group members
- Techniques planning
- 4 February: Web Content Accessibility Guidelines Working Group Teleconference
- 28 January: Web Content Accessibility Guidelines Working Group
Teleconference
- Update on choosing a scribe. Updated list to be maintained. http://www.w3.org/WAI/GL/wiki/Scribe_List
- Short, easy survey: https://www.w3.org/2002/09/wbs/35422/20140128/
- Public Comment: Promote 2.4.7 from AA to A
- Post WCAG 2 wiki
- Public Comment: Promote 2.4.7 from AA to A
- CSUN F2F update
- CSUN F2F
- Techniques planning for next update
- Call for reviewers: https://dvcs.w3.org/hg/html-proposals/raw-file/default/longdesc1/longdesc.html
- Comments on the current techniques and understanding drafts
- 21 January: Web Content Accessibility Guidelines Working Group Teleconference
- 14 January: WCAG Working Group Teleconference
- Continue ARIA Techniques review - only #4 and #6 https://www.w3.org/2002/09/wbs/35422/20131126ARIA_Techniques/
- Discussion of Evaluation Methodology Note and approval for publication of working draft https://www.w3.org/2002/09/wbs/35422/20131126EM_Review/
- Approval of techniques and understanding documents for public review https://www.w3.org/2002/09/wbs/35422/techunderstandpublic/
- Discussion of Evaluation Methodology Note and approval for publication of working draft https://www.w3.org/2002/09/wbs/35422/20131126EM_Review/
- 7 January: Web Content Accessibility Guidelines Working Group Teleconference
2013
- 17 December: Web Content Accessibility Guidelines Working Group
Teleconference
- Next meeting
- Continue ARIA Techniques review - only #4 and #6 https://www.w3.org/2002/09/wbs/35422/20131126ARIA_Techniques/
- http://www.w3.org/WAI/GL/wiki/Using_aria-labelledby_to_provide_a_name_for_user_interface_controls
- http://www.w3.org/WAI/GL/wiki/Using_aria-labelledby_to_concatenate_a_label_from_several_text_nodes
- http://www.w3.org/WAI/GL/wiki/ARIA2:_Identifying_required_fields_with_the_aria-required_property
- Misc survey for December 10, 2013 https://www.w3.org/2002/09/wbs/35422/20131210/
- ARIA Technique: Using ARIA Live Regions or role=alert to Identify Errors .
- http://www.w3.org/WAI/GL/wiki/Using_ARIA_Live_Regions_or_role%3Dalert_to_Identify_Errors using grouping roles for form controls
- Comment on F16
- Table failure modification
- Misc survey for December 17, 2013 https://www.w3.org/2002/09/wbs/35422/20131217Misc/
- F89
- 4. ARIA TF: Using aria-alertdialog to Identify Errors
- 10 December: Web Content Accessibility Guidelines Working Group Teleconference
- 3 December: Web Content Accessibility Guidelines Working Group
Teleconference
- Kick-off review of Evaluation Methodology Note <https://www.w3.org/2002/09/wbs/35422/20131126EM_Review/>
- 1) Volunteers needed to run through techniques looking for any out of date items/content.
- Volunteer needed to craft a proposed response for: https://www.w3.org/2006/02/lc-comments-tracker/35422/NOTE-WCAG20-TECHS-20130905/2866
- LC-2861 is a dupe of LC-2860 - brief heads up to the group about removing
- Continue ARIA Techniques review <https://www.w3.org/2002/09/wbs/35422/20131126ARIA_Techniques/>
- 26 November: WCAG Working Group Teleconference
- Update on techniques and understanding release schedule
- Feedback on updated Techniques 5th November 2013 (#3 only) <https://www.w3.org/2002/09/wbs/35422/Nov5_2013/>
- 3. Updated technique Using the group role to identify related form controls
- 2. LC-2865: Bad link in H42
- 3. LC-2863: Edits to G73
- 4. LC-2860: Techniques should be scoped by Success criteria
- 1. LC-2864: Bad link in understanding 1.3.1
- 5. LC-2868: links with different text and 2.4.4
- 7. ARIA Technique: ARIA3: Identifying valid range information with the aria-valuemin and aria-valuemax properties
- 3. ARIA Technique: Using aria-label to provide an invisible label where a visible label cannot be used
- 1. ARIA Technique: Failure of Success Criterion 1.3.1 due to the use of role=presentation on content which conveys semantic information
- 2. ARIA Technique: Using aria-describedby to provide descriptions of objects
- 3. [Still open, discussed on 26th Nov] Updated technique Using the group role to identify related form controls
- 19 November: WCAG
- 12 November: SV_MEETING_TITLE
- Survey for 12th of November https://www.w3.org/2002/09/wbs/35422/Nov5_2013/
- Feedback on updated Techniques 5th November 2013
- 1. [Start here on 12th Nov] Updated review of F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type image
- 4. Draft response to comment LC-2863: G73 – Providing a long description in another location with a link […]
- 3. Updated technique Using the group role to identify related form controls
- 1. [Start here on 12th Nov] Updated review of F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type image
- . Updated review of F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images or applets in HTML in a way that allows assistive technology to ignore them
- 1. [Start here on 12th Nov] Updated review of F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type image
- Institutional Memory Exercise https://www.w3.org/2002/09/wbs/35422/InstM12112013/
- 5 November: WCAG
- Continue techniques review https://www.w3.org/2002/09/wbs/35422/Techsreview15thOct2013/
- 2. [Start here 5th Nov] Using the aria-describedby property to provide a descriptive label for user interface controls
- 3. Update to Identifying required fields with the aria-required property
- 5. Using the group role to identify related form controls
- 7. ARIA-edit: F68: Failure of Success Criterion 1.3.1 and 4.1.2
- Cognitive A11Y TF
- 29 October: WCAG Working Group Teleconference
- Update on Mobile TF
- October 29 survey https://www.w3.org/2002/09/wbs/35422/Oct29_2013/
- 1. Comment LC-2857: Draft response to Captions Technique
- 2. Comment LC-2858: Providing descriptive link text in spacer gif alt tag
- 3. Owners needed to complete proposed techniques
- 4. Comment LC-2861: Draft response to Techniques should be scoped by Succescriterium
- Continue techniques review https://www.w3.org/2002/09/wbs/35422/Techsreview15thOct2013/
- 1. [Start here on 22nd Oct] Update of using role=heading
- 22 October: Web Content Accessibility Guidelines Working Group
Teleconference
- ARIA Technique: Using ARIA Live Regions or role=alert to Identify Errors [Open]
- 8. HTML Technique: Using heading tags to markup row header cells that group rows [Not accepted -start from here on 15th Oct with update]
- 9. HTML and XHTML Techniques - H63: Using the scope attribute to associate header cells and data cells in data tables - re-written
- 8. HTML Technique: Using heading tags to markup row header cells that group rows [Not accepted -start from here on 15th Oct with update]
- Get the groups thoughts on improving the technique submission/commenting process
- 15 October: Web Content Accessibility Guidelines Working Group
Teleconference
- https://www.w3.org/2002/09/wbs/35422/20131008comments/
- #8 headings in tables...
- HTML and XHTML Techniques - H63: Using the scope attribute to associate header cells and data cells in data tables - re-written Please give us your feedback on the following as a potential new technique.
- https://www.w3.org/2002/09/wbs/35422/Techsreview15thOct2013/
- 8 October: Web Content Accessibility Guidelines Working Group
Teleconference
- Survey for October 8 https://www.w3.org/2002/09/wbs/35422/20131008comments/results
- 2. ARIA Technique: Using ARIA Live Regions or role=alert to Identify Errors
- 3. LC-2844: Out of date User Agent Support info
- LC-2853: H45 update for chromevox
- 6. aria-describedby comments LC-2848 and LC-2847
- 8. HTML Technique: Using heading tags to markup row header cells that group rows
- 1 October: WCAG Working Group Teleconference
- 24 September: Web Content Accessibility Guidelines Working Group Teleconference
- 17 September: Web Content Accessibility Guidelines
- 10 September: Web Content Accessibility Guidelines Working Group Teleconference
- 3 September: Web Content Accessibility Guidelines Working Group Teleconference
- 27 August: WCAG WG
- Last Public Comments https://www.w3.org/2002/09/wbs/35422/20130827LastPublicComments/?
- ULTIMATE !!! Survey from the WCAG2ICT Taskforce https://www.w3.org/2002/09/wbs/35422/UltimateWTI/?
- LC-2823 Conformance
- Last Public Comments https://www.w3.org/2002/09/wbs/35422/20130827LastPublicComments/?
- LC-2791
- https://www.w3.org/2002/09/wbs/35422/WCAG_Aug20_2013/results#x2690 'Headings using role="heading"'
- 20 August: Web Content Accessibility Guidelines Working Group
Teleconference
- Comment LC-2825: The text for the SC 3.3.2 intent is not worded right
- Comment LC-2826: H50 not helpful to anyone
- Comment LC-2810: Poor Example in SCR20
- Comment LC-2826: H50 not helpful to anyone
- Comment LC-2799: Specifying consistent page numbering for PDF documents
- Comment LC-2808: EOWG comments
- Comment LC-2796: Firefox supports zoom
- Comment LC-2800: PDF lists
- Comment LC-2790: Using aria-describedby to provide descriptions of objects
- Comment LC-2791: Techniques for WCAG 2.0 H45 longdesc: Missing on-page description example
- Comment LC-2810: Poor Example in SCR20
- Comment LC-2792: Techniques for WCAG 2.0 H45 longdesc: User agent support
- Comment LC-2798: Include G88
- Comment LC-2784: Focus Visible Understanding SC 2.4.7 Loophole
- Comment LC-2785: *Labels or Instructions*: Understanding SC 3.3.2
- Comment LC-2811: Allowing for Responsive Design methods
- Comment LC-2806:External Resources
- 13 August: Web Content Accessibility Guidelines
- 6 August: Web Content Accessibility Guidelines
- https://www.w3.org/2002/09/wbs/35422/ARIATechs_June21_2013/results#xdialog
- https://www.w3.org/2002/09/wbs/35422/ARIATechs_Aug6_2013 survey
- 2. WCAG review of ARIA-edit: F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control
- WCAG review of HTML5 spec on text alternatives
- Institutional Memory
- 30 July: Web Content Accessibility Guidelines Working Group
Teleconference
- WCAG review of 'Using aria-label for link purpose' technique https://www.w3.org/2002/09/wbs/35422/ARIATechs_June21_2013/results#xalertdia
- WCAG review of 'Using aria-labelledby to concatenate a label from several text nodes' technique https://www.w3.org/2002/09/wbs/35422/ARIATechs_June21_2013/results#xad
- Next time
- 23 July: WCAG
- 16 July: Web Content Accessibility Guidelines Working Group Teleconference
- 9 July: Web Content Accessibility Guidelines Working Group
Teleconference
- Ultimate version of WCAG 2 ICT
- Fix our Note in SC 4.1.2 to tell readers this is for "software developers" (rather than for "Web authors")
- Characterization of this document
- Acceptance of the full text of WCAG2ICT Working Group Note for publication
- Changes to Understanding, Techniques, and Quickref to clarify referencing WCAG issues
- New section in Understanding: Understanding Techniques for WCAG Success Criteria
- Rewritten Sufficient and Advisory Techniques section of Understanding intro
- Rewritten Introduction to Techniques for WCAG 2.0
- Proposed FAQ additions
- 25 June: Web Content Accessibility Guidelines Working Group Teleconference
- 18 June: Web Content Accessibility Guidelines Working Group
Teleconference
- LC-2745 : Adding an Example 4: Validating PDF
- LC-2632: SCR37: Creating Custom Dialogs in a Device Independent Way
- LC-2751: discrepancy between the normative text and the "Understanding" document for WCAG 1.4.5
- LC-2753: Caption in HTML5 table
- LC-2751: discrepancy between the normative text and the "Understanding" document for WCAG 1.4.5
- LC-2725: WCAG Compliance
- Charter and Accessibility Support Database
- 11 June: Web Content Accessibility Guidelines Working Group Teleconference
- 4 June: Web Content Accessibility Guidelines Working Group Teleconference
- 28 May: Web Content Accessibility Guidelines Working Group Teleconference
- 21 May: WCAG Working Group Meeting
- 14 May: Web Content Accessibility Guidelines Working Group
Teleconference
- Miscellaneous WCAG2ICT Issues for 14th May 2013
- Definition of STRUCTURE - (and its use in 1.3.1)
- Can we change web pages to NON-WEB DOCUMENTS OR SOFTWARE? Structure will (post errata) say: "The way the parts of a Web page are organized in relation to each other", and we want it in WCAG2ICT to be "The way the parts of a [NON-WEB DOCUMENTS OR SOFTWARE] are organizaed in relation to each other"
- Text for Principle 4: Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
- Text for Guideline 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies.
- Removing reference to (non-existent) conformance section -- and cleanup of substitution misses
- WCAG2ICT guidance for viewport definition
- Call for WG input to new WCAG Charter
- Support Web Content Accessibility Guidelines (WCAG) 2.0 Recommendation
- 7 May: Web Content Accessibility Guidelines Working Group Teleconference
- 30 April: Web Content Accessibility Guidelines Working Group
Teleconference
- Miscellaneous Issues for 30 April 2013: https://www.w3.org/2002/09/wbs/35422/20130430Misc/
- Miscellaneous WCAG2ICT Issues for 30 April 2013: https://www.w3.org/2002/09/wbs/35422/20130430WCAG2ICT/
- Comment LC-2754 for Web Content Accessibility
- Applying Command-line interfaces to WCAG
- WCAG2ICT Glossary change: AAA-only terms
- WCAG2ICT glossary change to assistive technology definition
- WCAG2ICT glossary change to same functionality
- WCAG2ICT change to introduction
- WCAG2ICT change Comments on Conformance
- 18 April: Web Content Accessibility Guidelines Working Group Teleconference
- 11 April: Web Content Accessibility Guidelines Working Group
Teleconference
- WCAG WG Meeting Time
- WCAG2ICT: Closed functionality List item 1.2.3
- WCAG2ICT: Closed functionality List items 1.2.8, 2.1.3, 3.1.6
- LC-2632: Creating Custom Dialogs
- LC-2717: Map element and bypass blocks
- LC-2718: Additions to H91
- What meets 2.4.1?
- Call for review of RDWG Research Report on Mobile Web Accessibility
- 28 March: Web Content Accessibility Guidelines Working Group
Teleconference
- LC-2726 : Weird display bug in Safari?
- LC-2747 : H69 should not be sufficient for SC 2.4.1
- LC-2748 : If "skip to main" link is not the very first link/focusable item on a page, should I call a WCAG 2.0 violation?
- LC-2749 : 2.4.1 Bypass Blocks - is it only required to meet one of the sufficient techniques?
- WCAG WG Meeting Time
- 21 March: Web Content Accessibility Guidelines Working Group Teleconference
- LC-2744 : Proposed a failure of 2.4.3 focus order when dynamically inserting content
- LC-2728 : Visual styling
- LC-2718 : H91: Using HTML form controls and links
- LC-2631 : SCR18: Providing client-side validation and alert
- WCAG2ICT harmonization with M376 - Part 1 Introduction
- Edit to WCAG2ICT language for SC 1.1.1
- Edit to WCAG2ICT language for SC 2.2.2
- Edit to WCAG2ICT language for SC 2.4.2
- Edit to WCAG2ICT language for SC 3.3.4
- 14 March: Web Content Accessibility Guidelines Working Group Teleconference
- 7 March: Web Content Accessibility Guidelines Working Group Teleconference
- 21 February: Web Content Accessibility Guidelines Working Group Teleconference
- 14 February: Web Content Accessibility Guidelines Working Group
Teleconference
- Definition of ¨Set of Software¨ https://www.w3.org/2002/09/wbs/35422/FINAL4SC/results#xSoftDef
- SC 2.4.1 - Bypass Blocks https://www.w3.org/2002/09/wbs/35422/FINAL4SC/results#x241
- SC 2.4.5 - Multiple Ways https://www.w3.org/2002/09/wbs/35422/FINAL4SC/results#x245
- SC 3.2.3 - Consistent Navigation https://www.w3.org/2002/09/wbs/35422/FINAL4SC/results#x323
- SC 3.2.4: Consistent Identification https://www.w3.org/2002/09/wbs/35422/FINAL4SC/results#x324
- SC 3.2.4: Consistent Identification https://www.w3.org/2002/09/wbs/35422/FINAL4SC/results#x324i
- Software or Programs
- Introduction https://www.w3.org/2002/09/wbs/35422/WCAGevalTaskForce/results#xq2
- Using this Methodology https://www.w3.org/2002/09/wbs/35422/WCAGevalTaskForce/results#xUsing
- Conformance Evaluation Procedure and Considerations for Particular Situations https://www.w3.org/2002/09/wbs/35422/WCAGevalTaskForce/results#xprocedur
- 7 February: Web Content Accessibility Guidelines Working Group Teleconference
- 31 January: Web Content Accessibility Guidelines Working Group Teleconference
- 17 January: Web Content Accessibility Guidelines Working Group
Teleconference
- Update of Techniques
- LC-2730 : Why is there a test for CSS?
- LC-2723 : Use of ALT=" " (containing a space) contradicts F30
- LC-2743 : "Page Titled" vs. "Page Titles"
- LC-2722, LC-2733 : How to Meet WCAG 2.0: Sufficient Techniques for 1.1.1 – Non-text Content
- Sufficient Technique for SC 1.3.1 : Using ARIA landmarks to identify regions of a page
- Sufficient Technique for SC 2.4.1 : Using ARIA landmarks to bypass blocks of content
- Sufficient Technique for SC 1.3.1 : Headings using role=heading
- Advisory Technique for SC 1.3.2 : Using aria-flowto
- 10 January: Web Content Accessibility Guidelines Working Group Teleconference
2012
- 13 December: Web Content Accessibility Guidelines Working Group Teleconference
- 6 December: Web Content Accessibility Guidelines Working Group Teleconference
- 15 November: Web Content Accessibility Guidelines Working Group Teleconference
- 8 November: Web Content Accessibility Guidelines Working Group Teleconference
- 1 November: Web Content Accessibility Guidelines Working Group Teleconference
- 25 October: Web Content Accessibility Guidelines Working Group
Teleconference
- LC-2612 : H80 not accessibility support
- LC-2626 : For longer time-outs, would not a control that removes automatic refresh meet the SC?
- LC-2717 : WCAG 2.0 - 2.4.1 Bypass Blocks
- Approval of WCAG2ICT Success Criterion 2.4.2 (Page Titled)
- Approval of WCAG2ICT Success Criterion 4.1.1 (Parsing)
- Approval of WCAG2ICT definition of Non-embedded content
- Approval of WCAG2ICT note for "ambiguous to users in general"
- Approval of WCAG2ICT note for "contrast ratio"
- Approval of WCAG2ICT note for "keyboard interface"
- Approval of WCAG2ICT note for "label"
- Approval of WCAG2ICT note for "name"
- Approval of WCAG2ICT note for "relative luminance"
- Approval of WCAG2ICT note for "role"
- Approval of WCAG2ICT note for "supplemental content"
- Changes to SC 3.2.3 Sufficient Techniques
- 18 October: Web Content Accessibility Guidelines Working Group Teleconference
- 11 October: Web Content Accessibility Guidelines Working Group Teleconference
- 4 October: Web Content Accessibility Guidelines Working Group
Teleconference
- WCAG2ICT proposal: user controllable" (copied from the survey header)
- WCAG2ICT proposal: real-time event
- WCAG2ICT proposal: user controllable
- WCAG2ICT proposal: Understanding 3.3.1
- WCAG2ICT proposal Understanding 3.3.1
- LC-2611 floated lists (e.g. horizontal menus) not covered in test of H48
- SCR18: Providing client-side validation and alert
- PDF3: Example 3 uses invalid terms
- Provide Technique(s) using PDF/UA
- H91: Example incorrect
- 27 September: Web Content Accessibility Guidelines Working Group Teleconference
- 1. LC-2585 : Known failures should include setting main page container overflow to hidden preventing scrollbars
- LC-2624 : H69 is not a sufficient technique for SC 2.4.1
- LC-2627: quote should be removed from test in H49, semantics of elements depending on doctype
- LC-2629 : title attributes on images - SC 1.1
- LC-2633 : resize text versus zoom
- LC-2647: Test does not require check whether user-entered data is re-displayed
- LC-2648: Test does not require check whether user-entered data is re-displayed
- 20 September: Web Content Accessibility Guidelines Working Group Teleconference
- 13 September: Web Content Accessibility Guidelines Working Group Teleconference
- 6 September: Web Content Accessibility Guidelines Working Group Teleconference
- 30 August: Web Content Accessibility Guidelines Working Group Teleconference
- 16 August: Web Content Accessibility Guidelines Working Group Teleconference
- 9 August: Web Content Accessibility Guidelines Working Group Teleconference
- 2 August: Web Content Accessibility Guidelines Working Group Teleconference
- 19 July: Web Content Accessibility Guidelines Working Group
Teleconference
- Results of Questionnaire WCAG Issues for 19 July 2012 https://www.w3.org/2002/09/wbs/35422/July-19/results
- Reword of 1.4.4 to address the sentence that WCAG invited the WCAG2ICT Taskforce to rework.
- 1.3.2 Guidance - submitted for approval
- 2.4.2 Guidance - submitted for approval
- 2.4.3 Guidance - submitted for approval
- 3.3.1 edits to WCAG 2.0 INTENT for 3.3.1 Error Identification
- edit to WCAG 2.0 INTENT for 3.3.3 Error Suggestion
- Reword of 2.4.6 to address concerns of WCAG WG
- FRONT MATTER Text for the WCAG2ICT document
- INTRODUCTION to WCAG2ICT document - submitted for approval
- 1.4.3 Guidance - submitted for approval
- 12 July: Web Content Accessibility Guidelines Working Group
Teleconference
- Task force requests to WCAG for 12 July 2012 https://www.w3.org/2002/09/wbs/35422/WCAG2ICT-5/results
- Approval of 3.2.4 Consistent Identification
- SC 1.3.1Info and Relationships: Change to WCAG WG recommended edit to WCAG2ICT text
- 2.1.1 Keyboard: Change to WCAG WG recommended edit to WCAG2ICT text
- 2.2.2 Pause, Stop, Hide: Change to WCAG WG recommended edit to WCAG2ICT text
- 5 July: Web Content Accessibility Guidelines Working Group
Teleconference
- SC 3.1.2 in Understanding WCAG 2.0
- SC 1.3.1 in Understanding WCAG 2.0
- 1.1.1 Non-text Content
- 1.2.2 Captions (Prerecorded)
- 1.2.4 Captions (Live)
- 1.4.4 Resize text
- 2.1.1 Keyboard
- 2.1.2 No Keyboard Trap
- 2.2.1 Timing Adjustable
- 4.1.1 Parsing
- 4.1.2 Name, Role, Value
- General feedback for the WCAG2ICT Task Force
- 2.2.2 Pause, Stop, Hide
- 2.4.6 Headings and Labels
- 3.2.1 On focus
- 3.2.2 On Input
- 3.3.1 Error Identification
- 3.3.4 Error Prevention (Legal, Financial, Data)
- 28 June: Web Content Accessibility Guidelines Working Group Teleconference
- 21 June: Web Content Accessibility Guidelines Working Group Teleconference
- 14 June: Web Content Accessibility Guidelines Working Group Teleconference
- 7 June: Web Content Accessibility Guidelines Working Group
Teleconference
- Failure Technique : Failure of Success Criterion 1.3.1 for not correctly marking up table headers https://www.w3.org/2002/09/wbs/35422/20120607misc/results#xtablehea
- LC-2617 : Techniques do not apply (2.4.8) https://www.w3.org/2002/09/wbs/35422/20120607misc/results#x2617 and LC-2618 : Techniques do not apply (3.2.3) https://www.w3.org/2002/09/wbs/35422/20120607misc/results#x2618
- LC-2628 : Test not effective since it ignores invisible timings https://www.w3.org/2002/09/wbs/35422/20120607misc/results#x2628
- 31 May: Web Content Accessibility Guidelines Working Group
Teleconference
- LC-2586 : Failure to choose appropriate table row and column headings
- LC-2613 : Examples 5 and 6 should be deleted
- LC-2620 : Reference to the title attribute on a technique that deals with abbr https://www.w3.org/2002/09/wbs/35422/20120531misc/results#x2620
- LC-2621 : The permissible uses of heading levels and F43 https://www.w3.org/2002/09/wbs/35422/20120531misc/results#x2621
- 24 May: Web Content Accessibility Guidelines Working Group
Teleconference
- 1. Failure Technique : Failure of Success Criterion 1.3.1 for not correctly marking up table headers
- 2. Failure Technique : Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes
- 3. LC-2605 : H4 Example 3 seems to fail the test procedure in F44
- 4. LC-2619 : Improvement to text, PDF9
- 5. LC-2610 : Procedure #2 & Note in Expected Results
- 8. LC-2585 : Known failures should include setting main page container overflow to hidden preventing scrollbars
- 3 May: Web Content Accessibility Guidelines Working Group Teleconference
- 26 April: Web Content Accessibility Guidelines Working Group Teleconference
- 19 April: Web Content Accessibility Guidelines Working Group Teleconference
- 12 April: Web Content Accessibility Guidelines Working Group Teleconference
- 29 March: Web Content Accessibility Guidelines Working Group
Teleconference
- LC-2603 : Link text identical? https://www.w3.org/2002/09/wbs/35422/20120329misc/results#x2603
- Failure Technique : Failure of Success Criterion 1.3.1 for not correctly marking up table headers https://www.w3.org/2002/09/wbs/35422/20120329misc/results#xtabhead
- Failure Technique : Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes https://www.w3.org/2002/09/wbs/35422/20120329misc/results#xtabid
- 8 March: Web Content Accessibility Guidelines Working Group
Teleconference
- Website Accessibility Conformance Evaluation Methodology 1.0
- Application of WCAG in other domains
- Failure of Success Criterion 1.3.1 due to using elements within data tables that obscure structural relationships
- F69 : Failure of Success Criterion 1.4.4 when resizing visually rendered text up to 200 percent causes the text, image or control to be clipped, truncated or obscured
- 23 February: Web Content Accessibility Guidelines Working Group Teleconference
- Issue 2582: adjacent multiple image links
- Issue 2596 support notes are incorrect
- Issue 2597 the guidelines are way too tedius with way to much weasel room
- Issue 2601 G63 Description Difficult to Understand
- LC-2584 The description of what is sufficient to pass as a simple table is insufficient
- LC-2595 Older Versions - Informing Users
- LC-2585 Known failures should include setting main page container overflow to hidden preventing scrollbars
- LC-2586 Failure to choose appropriate table row and column headings
- 23 January: Web Content Accessibility Guidelines Working Group Teleconference
- 12 January: Web Content Accessibility Guidelines Working Group Teleconference
2011
- 8 December: Web Content Accessibility Guidelines Working Group Teleconference
- 1 December: wai-WCAG
- 17 November: Web Content Accessibility Guidelines Working Group Teleconference
- 10 November: Web Content Accessibility Guidelines Working Group Teleconference
- 27 October: Web Content Accessibility Guidelines Working Group Teleconference
- 20 October: Web Content Accessibility Guidelines Working Group Teleconference
- 13 October: Web Content Accessibility Guidelines Working Group
Teleconference
- Issue LC-2493: T3: Using standard text formatting conventions for headings
- Issue LC-2498: Understanding SC 2.4.6 needs improvement
- Issue LC-2499: Mixup in Understanding doc: SC 3.2.2 and SC 3.2.5
- Issue LC-2538: UA and AT out of date
- Issue LC-2569: Example 2
- Issue LC-2545: Situation B: Colors for stacked bar chart
- 6 October: Web Content Accessibility Guidelines Working Group Teleconference
- 29 September: Web Content Accessibility Guidelines Working Group
Teleconference
- Issue LC-2493: T3: Using standard text formatting conventions for headings
- Issue LC-2494: innerHTMLnow part of DOM spec (HTML5) and widely used - allow?
- Issue LC-2498: Understanding SC 2.4.6 needs improvement
- Issue LC-2499: Mixup in Understanding doc: SC 3.2.2 and SC 3.2.5
- Issue LC-2508: Linking to old version of Inspect Objects
- Issue LC-2533: Technique has poor and undocumented browser support
- Issue LC-2546: Embedded Flash content
- Issue LC-2562: Misinterpretation of list of assistive technologies and versions supporting PDF techniques
- Issue LC-2569: Example 2
- Issue LC-2570: Technique for a decorative image?
- New example for H48: Using ol, ul and dl for lists or groups of links
- 22 September: Web Content Accessibility Guidelines Working Group
Teleconference
- Issue LC-2550: H91, Example 7: Textarea
- Issue LC-2555: H91, Example 3: value attribute
- Issue LC-2565: Applicability of General WCAG 2.0 techniques
- Issue LC-2568: Inclusiveness of examples in PDF Techniques
- New Survey - Miscellaneous issues for 22 Sept 2011
- Issue LC-2509: Documentation for Inspect Objects (part of the Windows SDK)
- Issue LC-2567: Other PDF readers exist.
- Issue LC-2462: Understanding WCAG 2- SC 1.3.1
- Issue LC-2480: Make title of a document easier to identify
- Issue LC-2497:Make document titles more visible through italicising or other emphasis
- 15 September: Web Content Accessibility Guidelines Working Group
Teleconference
- Issue LC-2490: Excessive use of clicking to navigate a website
- Issue LC-2493: T3: Using standard text formatting conventions for headings
- Issue LC-2551: H91, Example 6: 'selected' attribute
- Issue LC-2555: H91, Example 3: value attribute
- Issue LC-2492: F60 may either apply also to SC 3.2.2 (On Input) or need further specification (context change announced/expected, window type)
- Issue LC-2496: "should" vs "must"
- Issue LC-2537: Reflow and Order panel can not guarantee the reading order
- Issue LC-2546: Embedded Flash content
- 8 September: Web Content Accessibility Guidelines Working Group Teleconference
- Issue LC-2533: Technique has poor and undocumented browser support
- LC-2545 for Web Content Accessibility Guidelines Working Group
- LC-2546: Embedded Flash content
- Issue LC-2549: G140, Example 2
- Issue LC-2552: Appendix A: Minor additional pointer
- Issue LC-2553: PDF6 Technique Title
- Issue LC-2554: Objectionable phrasing
- 1 September: Web Content Accessibility Guidelines Working Group Teleconference
- 18 August: Web Content Accessibility Guidelines Working Group Teleconference
- 4 August: Web Content Accessibility Guidelines Working Group
Teleconference
- Schedule for August
- ATAG response to WCAG WG comments http://www.w3.org/2002/09/wbs/35422/20110728misc/results#xq1
- Issue LC-2535: H1 elements should be used for titling the web site http://www.w3.org/2002/09/wbs/35422/20110728misc/results#x2535
- Documenting techniques
- Issue LC-2536: CSS Technique: Using an invisible header text in the sidebar navigation http://www.w3.org/2002/09/wbs/35422/20110728misc/results#x2535
- Issue LC-2532: Need (or not) for text equivalent of AV files http://www.w3.org/2002/09/wbs/35422/20110804misc/results#x2532
- HTML5 and 3.1.5 Reading Level http://www.w3.org/2002/09/wbs/35422/20110804misc/results#xq2
- 28 July: Web Content Accessibility Guidelines Working Group Teleconference
- 14 July: Web Content Accessibility Guidelines Working Group Teleconference
- 7 July: Web Content Accessibility Guidelines Working Group
Teleconference
- ADOD Framework http://www.w3.org/2002/09/wbs/35422/20110707misc/results#xq1
- Issue LC-2479: Translation of an easy-to-read text http://www.w3.org/2002/09/wbs/35422/20110707misc/results#x2479
- Response to Sufficient CSS Technique for SC 2.4.6: Using an invisible header text in the sidebar navigation http://www.w3.org/2002/09/wbs/35422/20110707misc/results#xnavhead
- Response to Sufficient HTML Technique for SC 2.4.2: H1 elements should be used for titling the web site and subpage information of a HTML/xhtml based web resource http://www.w3.org/2002/09/wbs/35422/20110707misc/results#xh1
- Sufficient General Technique for SC 1.2.3, 1.2.5: Using a static text alternative to describe a "talking head" video http://www.w3.org/2002/09/wbs/35422/20110707misc/results#xtxtaltvi
- 30 June: Web Content Accessibility Guidelines Working Group Teleconference
- 23 June: Web Content Accessibility Guidelines Working Group Teleconference
- 16 June: Web Content Accessibility Guidelines Working Group Teleconference
- 9 June: Web Content Accessibility Guidelines Working Group Teleconference
- 2 June: Web Content Accessibility Guidelines Working Group Teleconference
- 26 May: Web Content Accessibility Guidelines Working Group Teleconference
- 28 April: Web Content Accessibility Guidelines Working Group Teleconference
- 21 April: Web Content Accessibility Guidelines Working Group Teleconference
- 7 April: Web Content Accessibility Guidelines Working Group Teleconference
- 31 March: Web Content Accessibility Guidelines Working Group Teleconference
- 24 March: Web Content Accessibility Guidelines Working Group Teleconference
- 3 March: Web Content Accessibility Guidelines Working Group Teleconference
- 24 February: Web Content Accessibility Guidelines Working Group
Teleconference
- Issue LC-2448: use of fieldset should not be required for any group of logically related input elements
- Issue LC-2457: H93 and H94 are out of place
- Issue LC-2465: Test needs specification of window size and criteria for compliance
- Issue LC-2467: H82 missing?
- Issue LC-2471: H89: certainly cannot be a sufficient technique
- Issue LC-2472: Sufficient techniques- definition and guidance
- Issue LC-2474: Require both sufficient techniques
- Issue LC-2437: I think there is a failure missing
- 17 February: Web Content Accessibility Guidelines Working Group
Teleconference
- is WCAG a good home for HTML 5 techniques before the standard is settled... not for discussion today but to think about
- Issue LC-2438: Test in G68 does not seem to fit
- Issue LC-2427: F61: 24 hours?
- Issue LC-2466: Requirement for 200% text increase nearly impossible to meet in most cases
- Issue LC-2445: The test for the correct use of longdesc should be conditional on its application
- was before last topic... Issue LC-2443: The test should include a check whether the function to turn off blinking content is documented
- Issue LC-2448: use of fieldset should not be required for any group of logically related input elements
- Issue LC-2457: H93 and H94 are out of place
- Issue LC-2449: Test for percent is in itself not meaningful, should encompass %, em, font size names
- Issue LC-2450: Test contradicts other options to meet SC 1.4.4
- <scribe> topic: Issue LC-2451: Check for CSS seems less useful than test for use of deprecated elements (e.g., font, center, strike, i, b, u)
- Issue LC-2437: I think there is a failure missing
- Issue LC-2433: SM6, SM7: SC 1.2.5
- 10 February: Web Content Accessibility Guidelines Working Group
Teleconference
- Sufficient Silverlight Technique for SC 2.1.1: Providing Keyboard Shortcuts for a Silverlight Application as a Whole
- PDF Technology Notes
- Issue LC-2427: F61: 24 hours?
- Issue LC-2456: Reword G1 'Description' and 'Note'. (This will make "Skip to Main" as a permanent visible link)
- Issue LC-2438: Test in G68 does not seem to fit
- Issue LC-2439: either/or test seems incorrect: #2 must be true
- Issue LC-2441: Test does not cover appropriateness of audio description
- Issue LC-2442: Missing explicit requirement that styleswitcher be positioned at the top of the page
- Issue LC-2465: Test needs specification of window size and criteria for compliance
- 3 February: Web Content Accessibility Guidelines Working Group
Teleconference
- Issue LC-2454: WCAG 2 conformance claim: validating code
- Issue LC-2429: SC 3.2.1 Keyboard users only?
- Issue LC-2462: Understanding WCAG 2- SC 1.3.1
- Issue LC-2463: WCAG 2 techniques for SC 1.3.2 and 2.4.3
- Issue LC-2461: Understanding WCAG 2- SC 2.4.3
- Issue LC-2455: Note at end of sufficient techniques for 3.3.2 is ambiguous
- Issue LC-2453: techniques link to 20081211 version
- Issue LC-2431: G93: SC 1.2.4
- Issue LC-2430: G97: Only "immediately following the expanded form"?
- Issue LC-2428: G150: procedure and policy
- Issue LC-2432: SM7: Expected Results
- Issue LC-2444: Test does not check top position of link or mechanism
- Issue LC-2446: Equivalence of content of noembed element not explicitly checked
- Issue LC-2436: Formatting Convention
- Issue LC-2426: Table of Content needs summary of collections
- Issue LC-2440: last line of test redundant
- Issue LC-2458: Wording of G164
- Issue LC-2435: FLASH34 Using screen reader detection to turn off sounds that play automatically
- Issue LC-2434: FLASH17 wrong success criteria association
- Sufficient PDF Technique for SC 1.3.2, 2.1.1, 2.1.3, 2.4.3: Ensuring correct tab and reading order in PDF documents
- Sufficient PDF Technique for SC 1.3.1, 2.4.8, 3.2.3: Specifying consistent page numbering for PDF documents in Adobe Acrobat Pro or Reader
- Add link to Related Techniques for G91: Providing link text that describes the purpose of a link
- Add example to G130: Providing descriptive headings
- Sufficient Silverlight Technique for SC 2.4.7: Designing a Focused Visual State for Custom Silverlight Controls
- Sufficient Silverlight Technique for SC 1.1.1, 3.3.2: Displaying HelpText in Silverlight User Interfaces
- Sufficient Silverlight Technique for SC 2.1.1: Providing Keyboard Shortcuts for a Silverlight Application as a Whole
- Sufficient Silverlight Technique for SC 4.1.2: Using Silverlight Text Elements for Appropriate Accessibility Role
- 27 January: Web Content Accessibility Guidelines Working Group
Teleconference
- Sufficient PDF Technique for SC 1.3.1: Using List tags for lists in PDF documents
- Sufficient PDF Technique for SC 3.2.2: Providing submit buttons with the submit-form action in PDF forms
- Sufficient PDF Technique for SC 1.3.1: Tagging incorrectly merged or split table cells in PDF document
- Sufficient PDF Technique for SC 2.4.4, 2.4.9: Providing replacement text using the /Alt entry for links in PDF documents
- Add PDF example to G149: Using user interface components that are highlighted by the user agent when they receive focus
- Add SC 2.1.3 to PDF technique "Providing interactive form controls in PDF documents"
- Sufficient PDF Technique for SC 1.3.1, 4.1.2: Providing name, role, value information for form fields in PDF documents
- 20 January: Web Content Accessibility Guidelines Working Group
Teleconference
- Comments
- Sufficient PDF Technique for SC 1.3.1, 4.1.2: Providing name, role, state information for form fields in PDF documents
- Sufficient PDF Technique for SC 2.4.8, 3.2.3: Adding pagination artifacts that provide user location information in PDF documents
- Sufficient PDF Technique for SC 2.4.4, 2.4.9: Providing alternate link text with the /Alt entry for screen reader users of PDF documents
- Sufficient PDF Technique for SC 2.4.1, 2.4.5: Creating bookmarks in PDF documents
- Sufficient PDF Technique for SC 1.3.2, 2.4.3: Ensuring correct reading order in PDF documents
- Sufficient PDF Technique for SC 1.4.5, 1.4.9: Performing OCR on a scanned PDF document to provide actual text
- 13 January: Web Content Accessibility Guidelines Working Group
Teleconference
- Advisory Silverlight Technique for SC 1.1.1, 3.3.2: Providing User Instructions With AutomationProperties.HelpText in Silverlight
- Sufficient Silverlight Technique for SC 3.1.2: Declaring Discrete Silverlight Objects to Specify Language Parts in the HTML DOM
- Advisory Silverlight Technique for SC 3.1.2: Understanding Language/Culture Properties as Used by Silverlight Applications and Assistive Technologies
- Sufficient Silverlight Technique for SC 4.1.2: Understanding the Accessibility Roles of Silverlight Text Elements
- Sufficient Silverlight Technique for SC 1.4.5: Using Silverlight Font Properties to Control Text Presentation, and Avoid Images of Text
- Extend to SC 1.3.2 : Silverlight Technique "Using the Silverlight Default Tab Sequence and Altering Tab Sequences With Properties"
- Silverlight Technology Notes
- 6 January: Web Content Accessibility Guidelines Working Group
Teleconference
- Two minutes
- Sufficient PDF Technique for SC 2.1.1: Providing interactive form controls in PDF documents
- Sufficient PDF Technique for SC 1.3.1, 2.4.6, 3.3.2, 4.1.2: Providing labels for interactive form controls in PDF documents
- Sufficient PDF Technique for SC 1.3.1, 4.1.2: Providing name, role, and state information for form controls in PDF documents
- Sufficient PDF Technique for SC 1.3.2, 2.4.3: Ensuring correct reading order for form controls in PDF documents
- Sufficient PDF Technique for SC 3.3.1, 3.3.3, 3.3.4: Indicating required form controls in PDF forms
- Sufficient PDF Technique for SC 3.3.1, 3.3.3, 3.3.4: Indicating when user input falls outside the required format or values in PDF forms
- Sufficient PDF Technique for SC 3.2.3, 2.4.8: Providing consistent navigation mechanisms in PDF documents
- Sufficient PDF Technique for SC 2.4.1, 2.4.5: Providing multiple ways to access content in PDF documents
- Sufficient PDF Technique for SC 2.4.7, 2.4.9: Providing alternative link text for screen reader users of PDF documents
2010
- 9 December: Web Content Accessibility Guidelines Working Group
Teleconference
- Sufficient PDF Technique for SC 1.3.1, 2.4.6, 3.3.2, 4.1.2: Providing labels for interactive form controls in PDF documents
- Sufficient PDF Technique for SC 3.3.1, 3.3.3, 3.3.4: Indicating required form controls in PDF forms
- Sufficient PDF Technique for SC 3.3.1, 3.3.3, 3.3.4: Indicating when user input falls outside the required format or values in PDF forms
- Sufficient PDF Technique for SC 2.4.1, 2.4.5, 3.2.3: Providing consistent navigation mechanisms in PDF documents
- 2 December: Web Content Accessibility Guidelines Working Group
Teleconference
- capcha volunteers
- adaptabilityof html5 with wcag
- Christmas vacation
- Parsing Text-Format Text Captions for MediaElement Content
- Using Controls and Programmatic Focus to Bypass Blocks of Content in Silverlight
- Setting Language of Parts for Silverlight Content
- Providing Custom Control Key Handling for Keyboard Functionality in Silverlight
- Providing User Instructions With AutomationProperties.HelpText in Silverlight
- Using Silverlight Text Containers for Sequence and Relationships of Text Elements
- Making tables accessible in PDF documents by using table elements
- Providing interactive form controls in PDF documents
- 18 November: Web Content Accessibility Guidelines Working Group Teleconference
- PDF Techniques Roadmap
- Sufficient PDF Technique for SC 2.2.1, 2.2.3: Allowing time limits to be disabled or modified via scripting for interactions with PDF forms
- Sufficient PDF Technique for SC 1.3.1, 2.4.6, 3.3.2, 4.1.2: Adding interactive controls to forms in PDF documents
- Sufficient PDF Technique for SC 3.3.1, 3.3.3, 3.3.4: Providing form validation and error prevention in PDF forms
- <Loretta> http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html
- Sufficient PDF Technique for SC 2.4.4, 2.4.9, 3.2.4: Providing links and link text using the /Link structure element in PDF documents
- Sufficient PDF Technique for SC 1.3.1, 2.4.6, 3.3.2, 4.1.2: Adding labels to form controls in PDF documents
- Sufficient PDF Technique for SC 1.3.1, 2.4.3: Making tables accessible in PDF documents by using table elements
- Parsing Text-Format Text Captions for MediaElement Content
- 11 November: Web Content Accessibility Guidelines Working Group
Teleconference
- 1. Silverlight Techniques Roadmap
- 2. Silverlight Techniques for 11 November 2010
- 1. Sufficient Silverlight Technique for SC 1.1.1: Defining a Focusable Image Class for Silverlight
- Sufficient Silverlight Technique for SC 4.1.2: Defining a UI Automation Peer for a Custom Silverlight Control
- Sufficient Silverlight Technique for SC 3.3.1, 3.3.3, 3.3.4: Implementing Client Side Forms Validation in Silverlight
- Sufficient Silverlight Technique for SC 1.1.1, 3.3.2, 4.1.2: Using LabeledBy to Associate Labels and Targets in Silverlight
- Sufficient Silverlight Technique for SC 1.3.1: Using Silverlight Font Properties, Styles, and Templates
- 1. Sufficient PDF Technique for SC 1.3.1, 2.4.1: Providing headings by marking content with heading tags in PDF documents
- Sufficient PDF Technique for SC 1.3.1, 2.4.4, 2.4.9: Providing links and link text using the /Link structure element in PDF documents
- 4 November: Web Content Accessibility Guidelines Working Group
Teleconference
- Sufficient PDF Technique for SC 2.4.1, 2.4.10:Providing headings by marking content with heading tags in PDF documents
- Sufficient PDF Technique for SC 2.4.4, 2.4.9, 3.2.4: Providing understandable and consistent link text using the /Link structure element in PDF documents
- Sufficient PDF Technique for SC 2.2.1, 2.2.3: Allowing time limits to be disabled or modified via scripting for interactions with PDF documents
- Sufficient Silverlight Technique for SC 2.2.2: Pausing, Stopping, or Playing Media in Silverlight MediaElements
- Sufficient Silverlight Technique for SC 3.2.2:Implementing a Submit-Form Pattern in Silverlight
- Sufficient Silverlight Technique for SC 2.4.1: Using Silverlight Built-in Controls and Tab Navigation Behavior to Define Blocks that can be Bypassed
- Sufficient Silverlight Technique for SC 1.3.1: Relying on Silverlight AutomationPeer Behavior to Set AutomationProperties.Name
- Sufficient Silverlight Technique for SC 4.1.1: XAML and Parsing in Silverlight
- Sufficient Silverlight Technique for SC 1.3.1: Silverlight Object Tree Concepts, and Information and Relationships in Silverlight Applications
- 28 October: Web Content Accessibility Guidelines Working Group
Teleconference
- Silverlight survey
- Sufficient Silverlight Technique for SC 1.4.2: Controlling Silverlight MediaElement Audio Volume
- Silverlight Technique for SC 1.4.2, 2.2.2: Stopping Silverlight Media From Playing Using AutoPlay
- PDF Techniques
- Sufficient PDF Technique for SC 2.4.1, 2.4.10:Providing headings by marking content with heading tags in PDF documents
- 21 October: Web Content Accessibility Guidelines Working Group Teleconference
- 14 October: Web Content Accessibility Guidelines Working Group
Teleconference
- Sufficient Silverlight Technique for SC 1.4.3: Providing A Style Switcher To Switch To High Contrast
- Sufficient Silverlight Technique for SC 1.4.4: Using A Style Switcher to Increase Font Size of Silverlight Text Elements
- Sufficient Silverlight Technique for SC 1.4.2, 2.2.2: Defining a Silverlight MediaElement Control UI to Support Accessibility Techniques
- Sufficient Silverlight Technique for SC 2.1.1 Handling Key Events to Enable Keyboard Functionality in Silverlight
- PDF techniques...Sufficient PDF Technique for SC 2.4.1: Providing tagged headings using Headn elements at the beginning of each section of content in PDF documents
- 7 October: Web Content Accessibility Guidelines Working Group
Teleconference
- On track to publish by Oct 14th
- Sufficient Silverlight Technique for SC 2.4.7: Changing The Visual Focus Indicator in Silverlight
- Sufficient Silverlight Technique for SC 1.2.3: Accessing Alternate Audio Tracks in Silverlight Media
- Sufficient Silverlight Technique for SC 1.2.2: Providing Script-Embedded Text Captions for MediaElement Content
- Sufficient Silverlight Technique for SC 1.2.1, 1.2.3, 1.2.8: Providing Alternative Content for Silverlight Media Playing in a MediaElement
- Sufficient Silverlight Technique for SC 2.4.3: Using the Silverlight Default Tab Sequence and Altering Tab Sequences With Properties
- Sufficient Silverlight Technique for SC 1.4.4: Silverlight and Browser Zoom
- Sufficient PDF Technique for SC 1.1.1: Hiding decorative images with the Artifact tag in PDF documents
- Sufficient PDF Technique for SC 3.1.1: Specifying the default document language with the Lang entry in PDF documents
- Sufficient PDF Technique for SC 3.1.2: Specifying the human language for a passage or phrase with the Lang entry in PDF documents
- 30 September: Web Content Accessibility Guidelines Working Group Teleconference
- 23 September: Web Content Accessibility Guidelines Working Group
Teleconference
- Proposed updates of Understanding WCAG 2.0, Techniques for WCAG 2.0
- Sufficient PDF Technique for SC 1.1.1: Applying text alternatives to non-text objects with the Alt entry in PDF documents
- Sufficient Silverlight Technique for SC 2.2.2: Pausing A Decorative Silverlight Animation
- Sufficient Silverlight Technique for SC 2.2.1: Replacing A Silverlight Timed Animation With a Nonanimated Element
- 16 September: Web Content Accessibility Guidelines Working Group Teleconference
- 9 September: Web Content Accessibility Guidelines Working Group Teleconference
- 19 August: SV_MEETING_TITLE
- Misc. revisions to How to Meet WCAG 2.0
- Introduction
- New General Technique for 2.1.1: Ensuring keyboard control for all functionality
- Revisions to SC 2.4.4 and 2.4.9 Sufficient techniques
- Revisions to SC 3.1.1 Sufficient techniques
- Revisions to SC 3.1.2 Sufficient techniques
- Revisions to SC 3.1.6 Sufficient techniques
- Miscellaneous issues for 19 Aug 2010
- Issue 2830: Apparent contradiction with 2.4.4 and 2.4.9
- Issue 2842: F68: Example 2
- Issue 2843: F68: Tests Procedure #2
- WCAG Review of ATAG 2.0
- 1 April: Web Content Accessibility Guidelines Working Group
Teleconference
- Sufficient Flash Technique for SC 1.1.1, 1.3.1, 3.3.2, 4.1.2: Setting label property for form components
- Sufficient Flash Technique for SC 1.4.4: Using a flash based style switcher to provide text enlargement
- Sufficient Flash Technique for SC 1.4.2: Using screen reader detection to turn off sounds that play automatically
- Using the DataGrid component to associate column headers with cells
- 4 February: Web Content Accessibility Guidelines Working Group Teleconference
2009
- 13 August: Web Content Accessibility Guidelines Working Group
Teleconference
- Miscellaneous Issues for 13 Aug 2009 http://www.w3.org/2002/09/wbs/35422/20090813misc/results
- Errata - SC 1.4.4 Contrast (Minimum)
- Issue 2727: Text color, G148 1.4.3 & 1.4.6
- Issues 2724, 2742: 1.3.1. vs. 1.3.2 Meaningful Sequence vs. Info and Relationships
- Sufficient Technique for SC 2.2.1: Adjusting the time limit to ten times the time
- Issue 2702: H48 included in H50
- Issue 2704: H85 optgroup
- Issue 2746: ALT text for icon (H30, Example 4)
- Issue 2721: Resize Text (technique submission)
- Update on Rapid Response Process
- Face to Face at TPAC
- Planning for update of Understanding and Techniques
- 21 May: WCAG Weekly Telecon
- Sufficient Technique for SC 4.1.2: Using WAI-ARIA to provide semantic role information ...
- Review comments on Developing a Web Accessibility Business Case for Your Organization
- return to discussion about W3C note on AT Push items
- resume discusion about the amount of AT support necessary before we list a technique a sufficient
- 9 April: WCAG
2008
- 20 November: WCAG
- Announcements, Questions, and Updates
- Miscellaneous Proposals for 20 Nov 2008
- Addressing AC member Comment - RE Changing Short Names to Make it Easier to Understand when GL 1.2 Success Criteria Apply
- Combine C12 and C14
- Related Techniques changes
- Revisions to User Agent notes
- Issue 2677: Low-power devices?
- Issue 2678: Group common failures as well as (good) techniques
- Issue 2679: H32 only mentions one type of SUBMIT button
- Issue 2680: Technique H45 procedure description incomplete
- Issue 2681: HTML Headings technique: duplicated
- Issue 2682: H33 sufficient technique for 2.4.4?
- 29 October: WCAG 2.0 CR to PR Transition Review (Chairs)
- 3 October: WCAG Face to Face Day 3
- Accessibility Support of Special Characters
- Accessibility Support for Human Language of Content
- Decorative Images and null Alt Text
- Background Images
- New technique - Using a text alternative on one item within a group of images that describes all items in the group
- Programmatically associating a text transcript with audio- or video-only content
- 2 October: WCAG Face to Face Day 2
- 1 October: WCAG Face to Face Day 1
- 28 April: 28 Apr 2008
- 4 April: 04 Apr 2008
- 14 February: WCAG Weekly Telecon
- Announcements, Questions, and Updates
- Issue 2484: clarify keyboard shortcut
- Issue 2465: what if it's not the author's fault?
- Issue 2527-2530: add a guideline for understandable navigation (multiple 2.4.X criteria)
- Issue 2508: Contrast ratio (on text edges)
- Issue 2510: abbreviation refers to "organization"?
- Issue 2514: accessibility supported - users' assistive technologies
- Issue 2518: captions - awkward wording
- Issue 2519: conforming alternative version - awkward wording
- Issue 2550: flash
- Issue 2551: general flash and red threshold - confusing jargon?
- Issue 2558: set of Web pages - clarify
- Issue 2559: set of Web pages - unnecessarily convolute
- Issue 2561: synchronised media - awkward
- Issue 2564: web page example 4
- Issue 2571: changes of context definition
- Issue 2478: Optional components and the hint of metadata
- Issue 2506: Conformance logos
- Issue 2542: Can "conforming alternate versions" be objects on a page?
- Issue 2450: Provide a quick reference for web designer
- Issue 2485: Several Success Criteria include specific values
- Issue 2543: WCAG 2.0 should advance to Candidate Recommendation
- Issue 2567: Allow users to filter out HTML techniques
- Issue 2568: Consider title change (Quick Reference)
- Issue 2577: Change "accessibility supported" to "accessibility-supporting"
- 31 January: WAI WCAG Weekly Telecon
- Issue 2375: Problems with H34 and H56
- Issue 2400: SC 3.1.2 - "technical terms" definition and example
- Issue 2401: SC 3.1.2 - needs another exception
- Issue 2406: ... absence of support for scripting or programmatic objects
- Issue 2407: Absence of success criterion for deprecated and obsolete features
- Addition to Intent of Understanding SC 2.4.1, and removal of request
- Sufficient technique for 1.4.8: ... commonly-available user agents that can change the foreground ...
- Sufficient technique for 1.4.8: Specifying line spacing of 1.5 in CSS
- Sufficient technique for 1.4.8: Specifying alignment either to the left OR right in CSS
- Sufficient technique for 1.4.8: Not interfering with the user agent's reflow ...
- Sufficient technique for 1.4.8: Using ems to set the column width
- Sufficient technique for 1.3.1, 2.1.1, 2.1.3, 4.1.2: Modeling custom user interfaces in HTML semantics
- Sufficient technique for 1.3.1, 1.3.3, 1.4.4, 2.1.1, 2.1.3, 4.1.2: Creating Attractive Buttons ...
- 17 January: WCAG Weekly Telecon
- Sufficient technique for 3.1.3, 3.1.4: Using a dictionary cascade
- Sufficient technique for 3.1.5: Making the text easier to read
- Sufficient technique for 3.1.5: Providing sign language versions of information, ideas ...
- Sufficient technique for Conformance Requirement 1 (Alternate Versions): Using HTTP referer ...
- Modifications to H42: Using h1-h6 to identify headings
- New version of F82: Failure of SC 3.3.2 by visually formatting a set of phone number fields ...
- Sufficient technique for 1.3.1: Using OPTGROUP to group OPTION elements inside a SELECT
- Sufficient technique for 1.3.1: Grouping form controls with FIELDSET and LEGEND
- SC 1.4.5, 1.4.9 Sufficient Technique: "Using CSS to control visual presentation of text"
- Comparison of WCAG 1.0 Checkpoints to WCAG 2.0
- Issue 2274: use accessibility-supported technologies
- Issue 2289: distinction between blinking and flashing still isn't clear
- Issue 2293: Please clarify 3.1.4
- Issue 2373: doing a little more for people with cognitive limitations
2007
- 25 October: WAI WCAG
- Announcements, Questions, and Updates
- Link Purpose Proposals for 25 Oct 2007 <http://www.w3.org/2002/09/wbs/35422/20071025link/results>
- SC 2.4.4 and 2.4.8 Proposals
- Link Context: Preceding Heading
- Link Context: Nested Sublist
- Issue 2008, 2325: Ban hiding link text
- Issue 2009: Links give context
- Issue 2150: Change level to AA or AAA
- Issue 2252: Keep 2.4.4 as a Level-A Success Criterion
- Issue 2343: 2.4.4 and 2.4.8: 2.4.8 should move to Level 1 and replace 2.4.4
- Issue 2061, 2104 and 2127: Level of 2.4.8 should be higher
- Miscellaneous Proposals for 25 Oct 2007 <http://www.w3.org/2002/09/wbs/35422/20071025misc/results>
- Issue 2141, 2174, 2308: accessibility supported
- Images of Text (Success Criterion and Understanding Document)
- Issues 2118, 2228: Proposal for Focus-related Success Criteria
- Issue 2134, 2218: SC 4.1.1 and markup languages
- Issue 2238: H21 - test procedure
- Issue 2291: semantics conveyed through presentation?
- Issue 2160: Human testers should always be persons with disabilities
- Failure of SC 1.4.4 and SC 1.4.7 when resizing text does not resize text-based form controls
- Changing the background color or border of the element with focus
- 27 September: WCAG Weekly Telecon
- Announcements, Questions, and Updates
- Discussion of Metadata and proposals posted to list (GL)
- Misc. Questions for 20 September 2007 Survey: http://tinyurl.com/2xaw8a
- Issue 2003: Disabled elements should have a lower contrast ratio...
- Issue 2272
- Issue 2290: extend alternative to text to audio-only or video-only
- Issue 2162: readability formulas
- Issue 2175: Why "18 point or 14 point bold"?
- Announcements, Questions, and Updates
- Miscellaneous Proposals for 27 Sep 2007 Survey: http://tinyurl.com/3xjzaf
- Issue 2358: There is no SC governing the visibility of focus
- Issue 1980: no provision for link highlighting
- Issue 1994: SC 2.4.1: use of term "block of content"
- Issue 2007: Page title as context
- Issues 2016, 2126, 2031: SC 1.4.1 Color Differences
- 28 June: SV_MEETING_TITLE
2006
- 12 October: Web Content Accessibility Guidelines
- 6 July: Web Content Accessibility Guidelines
- Editors Survey 22 June, 2006 http://www.w3.org/2002/09/wbs/35422/20060622editorz/results
- LC-687 accepted by unanimous consent
- Editors Survey 22 June, 2006 http://www.w3.org/2002/09/wbs/35422/20060622editorz/results
- LC-660
- LC-685
- LC-738
- LC-785
- LC-793
- LC-800
- LC-659
- LC-700
- LC-728
- LC-741
- LC-774
- LC-743
- LC-790
- LC-1163
- LC-1277
- 8 June: WCAG Working Group
- 25 May: WCAG WG Meeting
- 3 May: SV_MEETING_TITLE
- 24 February: ERT / WCAG WG coordination on testing
2005
- 22 December: WCAG Weekly Telecon
- Planning and Next Steps
- Issues for Guideline 2.4 (http://tinyurl.com/cu49m)
- Issue 1646
- 1563
- 1647
- 1649
- 1654
- 1708
- 1741
- 1769
- Issue 1777
- issue 1130
- issue 1720
- Issues for Guideline 2.1 (http://tinyurl.com/7rbo8)
- Issue 1700
- issue 1378
- issues 1621 and 1740
- Issues for Guideline 3.2 (http://tinyurl.com/7kf3g)
- issue 1659
- issue 1747
- issue 1792
- issue 1661
- 15 December: WCAG Weekly Teleconference
- issue 1608
- Update and proposal for going forward <http://tinyurl.com/abaug>
- close all unanimous survey items
- Issues for Guideline 2.2 <http://www.w3.org/2002/09/wbs/35422/20051205time-limits/results>
- issue #1044
- issue #1550
- issue 1092
- issue 1382
- issue 1383
- issue 1459 and 1552
- Issues for Guideline 1.2 <http://www.w3.org/2002/09/wbs/35422/20051205media-equiv/results>
- issue 1152
- issue 1151
- 1625
- issue 1718
- Issues for Guideline 2.5 and definition of "multimedia" <http://www.w3.org/2002/09/wbs/35422/20051215_2-5/results>
- issue 1771
- Issues for Guideline 2.5 and definition of "multimedia" <http://www.w3.org/2002/09/wbs/35422/20051215_2-5/results>
- issue 1652
- proposed definition of multimedia
- Issues for Guideline 1.3 <http://www.w3.org/2002/09/wbs/35422/2005-12-15-1-3/results>
- 8 December: WCAG Weekly Telecon
- 1 December: WCAG Weekly Telecon
- 17 November: WCAG WG weekly telecon
- 11 November: WCAG 2.0 Weekly Meeting (marathon)
- GL 2.2 L1 SC1
- Consider Promotion of Guideline 2.2 Level 3 Success Criterion 3 to Level 2
- Guideline 4.1
- Guideline 1.2
- Luminosity 1.4 contrast foreground and background
- SC text and Guide Doc for GL 2.1 L1 SC1
- GL 2.3 L1 SC1
- definition of programmatically determined
- GL 2.4 L2 SC 1
- GL GL 2.4 L2 SC4
- 2.4 L1 SC1
- 1.3 L3
- GL 1.3 L1 SC2 - proposal to delete and to promote GL 1.3 L2 SC2 to Level 1
- 1.3 L3 SC1
- Guideline 3.1
- 3.1 L3 SC3
- Baseline
- 10 November: WCAG 2.0 Weekly Meeting (marathon)
- GL 2.2 L1 SC1
- Consider Promotion of Guideline 2.2 Level 3 Success Criterion 3 to Level 2
- Guideline 4.1
- Guideline 1.2
- Luminosity 1.4 contrast foreground and background
- SC text and Guide Doc for GL 2.1 L1 SC1
- GL 2.3 L1 SC1
- definition of programmatically determined
- GL 2.4 L2 SC 1
- GL GL 2.4 L2 SC4
- 2.4 L1 SC1
- 1.3 L3
- GL 1.3 L1 SC2 - proposal to delete and to promote GL 1.3 L2 SC2 to Level 1
- 1.3 L3 SC1
- Guideline 3.1
- 3.1 L3 SC3
- Baseline
- 3 November: WCAG Weekly Telecon
- 27 October: WCAG WG weekly telecon
- First block of guides - are they ready for publication?
- Status and updates
- Guideline 1.2 L3 SC3 - audio descriptions (live multimedia)
- Guideline 1.4 L1 SC1
- Guideline 3.1 L3 SC1
- Guideline 4.2 L2 SC1
- Guideline 3.2 L3 SC1
- Guideline 1.3 L3 SC2
- things for next week
- guides that need work and who's working on them
- 13 October: WCAG WG telecon
- General Comments from Gregg about goals for Face to Face
- Review results of Questionnaire for Guideline 1.3 Issues
- survey on issue 796
- Survey about issue 827 proposing a new SC
- Survey about issue 938 to modify examples
- Survey on issue 1036 - proposal to close
- issue to add new SC in GL 1.3: Instructions for understanding or operating a delivery unit do not depend on users' ability to perceive visual characteristics such as shape or visual location of components.
- Issue 1309 and 1339 - propose new wording for programmatically determined
- Issue 1441
- issue 1705 - want better assoc. of examples with the Guidelines
- Issue 1733 and 1734
- issue 1735
- GL 4.2 - issue 426
- issue 971 and 1713
- issue 1537
- new proposed wording for 2.2 L2 SC2
- GL 2.2 L1 SC1 warning about time expiration
- Does the text of all songs need to be provided for any song that can be downloaded?
- Move Guideline 2.4 Level 3 SC1 from Guideline 2.4 to Guideline 3.1?
- Delete GL 3.1 L3 SC4 - Section titles are descriptive. and split 2.4 L2 SC3 into two SC
- 6 October: WCAG WG
- 29 September: WCAG Weekly Telecon
- 22 September: WCAG WG weekly telecon
- 15 September: WCAG Weekly Telecon
- 1 September: WCAG WG weekly telecon
- Techniques Task Force (TTF) update
- 10.2 Mapping Proposal <http://tinyurl.com/c7mnq>
- Guideline 3.2 proposed SC <http://tinyurl.com/7fs8x>
- Plan to publish mapping/"heartbeat requirement" <http://tinyurl.com/7mgb2>
- Document formats and templates. Proposal: <http://tinyurl.com/9wv6c>
- Teams and assignments
- 31 August: WCAG Techniques Task Force Weekly Telecon
- 25 August: WCAG WG weekly telecon
- Techniques Task Force report
- Updated WCAG 1.0-WCAG 2.0 mapping http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/att-0499/WAI_GL_2005_06_30-mapping.html
- Guideline 3.2 proposals http://www.w3.org/2002/09/wbs/35422/consistent-behavior0822/results
- Guideline 1.4 survey http://www.w3.org/2002/09/wbs/35422/contrast20050608/results
- Toward our next draft: Teams and Templates http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/att-0658/WCAG_Guidelines_and_Support_DocumentsV2.doc
- 24 August: Techniques Task Force of WCAG WG telecon
- 18 August: WCAG WG telecon
- TTF update
- wcag 1.0 p2 mapping - http://www.w3.org/2002/09/wbs/35422/mapping2/results
- WCAG 1.0 Checkpoint 13.3
- WCAG 1.0 Checkpoint 10.1
- WCAG 1.0 Checkpoint 10.4
- WCAG 1.0 Checkpoint 10.3
- WCAG 1.0 Checkpoint 7.5
- WCAG 1.0 Checkpoint 11.1
- WCAG 1.0 Checkpoint 12.3
- WCAG 1.0 Checkpoint 13.2
- WCAG 1.0 Checkpoint 12.2
- WCAG 1.0 Checkpoint 10.2
- WCAG 1.0 Checkpoint 7.3
- WCAG 1.0 Checkpoint 8.1
- WCAG 1.0 Checkpoint 5.5
- WCAG 1.0 Checkpoint 5.6
- 17 August: WCAG Techniques 17 August 2005
- 11 August: WCAG WG telecon
- TTF update
- TTF Work Statement
- Disposition of frame title (http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/0250.html)
- Priority 3 Mapping Discussion.
- Mapping of WCAG 1.0 Checkpoint 4.2
- Mapping WCAG 1.0 CP 4.3 to GL 3.1 L1 SC1
- Mapping WCAG 1.0 CP 9.4
- Mapping WCAG 1.0 CP 9.5
- mapping of WCAG 1.0 CP 10.5
- Mapping of WCAG 1.0 Checkpoint 11.3
- Mapping of WCAG 1.0 Checkpoint 13.5
- Mapping of WCAG 1.0 Checkpoint 13.6
- Mapping of WCAG 1.0 Checkpoint 13.7
- Mapping of WCAG 1.0 Checkpoint 13.8
- Mapping of WCAG 1.0 Checkpoint 13.9
- Mapping of WCAG 1.0 Checkpoint 13.10
- WCAG 1.0 Checkpoint 14.2
- Mapping of WCAG 1.0 Checkpoint 14.3
- Mapping of WCAG 1.0 Checkpoint 1.5
- 10 August: WCAG Techniques Teleconference 10 August 2005
- Discuss Script techniques direction http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/0015.html
- Script techniques / baseline proposals http://lists.w3.org/Archives/Public/w3c-wai-gl/2005AprJun/0767.html
- Testing http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/0042.html
- Test case reviews http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/0326.html
- if time, check in on work statement edits
- 4 August: WCAG Weekly Telecon
- 3 August: WCAG Techniques 03 August 2005
- 28 July: WCAG WG weekly telecon
- Next face-to-face
- Techniques Task Force update
- checkpoint to SC mapping survey http://www.w3.org/2002/09/wbs/35422/mapping/results
- mapping of WCAG 1.0 Checkpoint 1.1
- mapping of WCAG 1.0 Checkpoint 2.1
- mapping of WCAG 1.0 Checkpoint 4.1
- mapping of WCAG 1.0 Checkpoint 6.1
- mapping of WCAG 1.0 Checkpoint 6.2
- mapping of WCAG 1.0 Checkpoint 7.1
- mapping of WCAG 1.0 Checkpoint 14.1
- mapping of WCAG 1.0 Checkpoint 1.2
- mapping of WCAG 1.0 Checkpoint 9.1
- mapping of WCAG 1.0 Checkpoint 5.1
- mapping of WCAG 1.0 Checkpoint 5.2
- mapping of WCAG 1.0 Checkpoint 12.1
- mapping of WCAG 1.0 Checkpoint 6.3
- mapping of WCAG 1.0 Checkpoint 1.3
- mapping of WCAG 1.0 Checkpoint 11.4
- mapping of WCAG 1.0 Checkpoint 1.4
- 27 July: WCAG Techniques Task Force Telecon 27 July 2005
- 21 July: WCAG WG weekly
- request for WCAG 1.0 interpretation regarding tables for layout. http://tinyurl.com/8drxs
- Mapping of 1.0 to 2.0 http://www.w3.org/WAI/GL/2005/06/30-mapping.html
- wording for principle 4 "Content is compatible with current user agents." or "Content is compatible with current and future user agents." or ???
- removing [I] and [V] notation http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JulSep/0104.html
- 14 July: WCAG WG weekly telecon
- 13 July: WCAG Techniques Telecon 13 July 2005
- 7 July: WCAG Weekly Telecon
- TTF Update
- WCAG Weekly Telecon
- Harvest techniques and/or tests beginning with Guideline 2.1
- 2.1 L1 SC1
- 2.1 L3 SC1
- 2.2 L1 SC1
- 2.2 L2 SC1
- 2.2 L2 SC2
- 2.2 L3 SC1
- 2.2 L3 SC2
- 2.2 L3 SC3
- 2.3 L1 SC1
- 2.3 L3 SC1
- 2.4 L1 SC1
- 2.4 L2 SC1
- 2.4 L2 SC2
- 2.4 L2 SC3
- 2.4 L3 SC1
- 2.4 L3 SC2
- 2.5 L1 SC1
- 2.5 L2 SC2
- GL 2.5 L2 SC3
- GL 2.5 L3 SC1
- GL 3.1 L1 SC1
- GL 3.1 L2 SC1
- GL 3.1 L3 SC1
- GL 3.1 L3 SC2
- GL 3.1 L3 SC3
- GL 3.1 L3 SC4
- GL 3.1 L3 SC 5
- 6 July: SV_MEETING_TITLE
- 30 June: WCAG WG
- Techniques Task Force update
- test development and techniques, priorities for next few months, requirements for Last Call and beyond
- Harvest techniques and/or tests
- GL 1.2 L1 SC2
- GL 1.2 L2 SC1
- GL 1.2 L3 SC1
- GL 1.2 L3 SC2
- GL 1.2 L3 SC 3
- GL 1.3 L1 SC1
- GL 1.3 L1 SC2
- GL 1.3 L2 SC1
- GL 1.3 L2 SC2
- GL 1.3 L3 SC1
- GL 1.4 L1 SC1
- GL 1.4 L2 SC1
- GL 1.4 L2 SC3
- GL 1.4 L3 SC1
- GL 1.4 L3 SC2
- 29 June: WCAG Techniques Weekly Telecon
- 23 June: WCAG WG weekly telecon
- Guide/General Techniques
- Agenda overview (5 minutes)
- Techniques Task Fore (5 minutes)
- Guideline 1.2 L1 SC1: captions - should they remain level 1 or move to level 2?
- Guideline 1.2 L1 SC2: audio descriptions - should they remain level 1 or move to level 2?
- Updated proposal for Guideline 2.3, its success criteria, and related definitions
- Keep the existing text of Guideline 2.4 Level 2 SC1: More than one way is available to locate content within a set of delivery units?
- Move Guideline 2.4 Level 3 SC1 from Level 3 to Level 1?
- Updated proposal for Guideline 4.2 Level 1 multiple criterion to replace current level 1 success criterion 2
- Delete current Guideline 4.2 Level 2 SC1 or move to Level 3?
- Two or three levels of conformance?
- Review of Editor's Draft (90 minutes) http://www.w3.org/WAI/GL/2005/06/f2f-proposed-resolutions-draft.html
- introduction - http://lists.w3.org/Archives/Public/w3c-wai-gl/2005AprJun/att-0924/intro_wcag20_2005-06-21.htm
- Checklist
- 22 June: Techniques Task Force of the WCAG WG weekly telecon
- 16 June: WCAG WG F2F 16 June (day #4)
- 15 June: WCAG WG F2F 15 June (day #3)
- 14 June: 14 June WCAG F2F, Brussels
- 13 June: WCAG WG Face to face 13 March (day 1)
- 9 June: WCAG WG weekly telecon
- 8 June: TTF weekly telecon
- 2 June: WCAG WG telecon
- 1 June: WCAG WG TTF telecon
- 26 May: WCAG WG weekly
- 25 May: Techniques Task Force Telecon
- 19 May: WCAG WG weekly
- 18 May: WCAG Techniques Task Force (TTF) Weekly Telecon
- 12 May: WCAG Weekly Teleconference
- 11 May: WCAG Techniques Task Force Weekly Telecon
- 5 May: WCAG WG Weekly Telecon
- 4 May: WCAG Techniques Weekly Telecon
- 28 April: WCAG WG weekly telecon
- 27 April: Techniques Task Force of the WCAG WG Telecon
- 21 April: WCAG WG weekly
- 20 April: WCAG Techniques Task Force Weekly Meeting
- 14 April: WCAG Weekly Telecon
- 13 April: WCAG WG Techniques Task Force weekly telecon
- 7 April: WCAG WG Meeting
- 6 April: WCAG Techniques
- 31 March: WCAG WG weekly telecon
- 30 March: Techniques Task Force weekly telecon
- 24 March: WCAG WG weekly telecon
- 9 March: SV_MEETING_TITLE
- 28 February: Techniques Task Force of the WCAG WG face-to-face (at the Technical Plenary)
- 24 February: WCAG WG weekly telecon
- 23 February: TTF of the WCAG WG weekly telecon
- test 195
- Checklist structure
- Test file structure
- Tests 70, 149, 150 (Tim's review) - http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JanMar/att-0422/wcagtestreview.htm
- tests 31, 32, 33, 34, 35, 36, 167, and 101 (jenae's review) - http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JanMar/0519.html
- wendy's review
- Agenda for Face to Face meeting and Meeting schedule for the next few weeks
- 17 February: WCAG WG weekly telecon
- 16 February: SV_MEETING_TITLE
- 10 February: WCAG WG weekly telecon
- 9 February: TTF of the WCAG WG weekly meeting
- checklists
- Requirements for checklists & techniques http://www.w3.org/WAI/GL/WCAG20/WD-wcag2-tech-req-20050208.html
- title http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JanMar/0379.html
- other reviewed test files http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JanMar/0387.html
- Agenda for Technical Plenary
- Action item reminder
- 3 February: WCAG WG weekly telecon
- Charter and Participation http://www.w3.org/wai/gl/participation.html
- Techniques Task Force Update
- Definition of structure (Issue 506) http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=506
- Issue 848: accept Loretta's proposal to reword? http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=848
- Issue 887: accept Ben's explanation and close this bug? http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=887
- Issue 499: covered in guideline 1.1? http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=499
- 2 February: Techniques Task Force of the WCAG WG weekly telecon
- Finish review of alt text test files http://www.w3.org/WAI/GL/WCAG20/tests/checkstatus.html#alttests
- Review Fasttrack tests http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JanMar/0341.html
- Review proposal to close issues 734 and 739 http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JanMar/0357.html
- Action item reminder
- 27 January: WCAG WG weekly telecon
- 26 January: WCAG WG TTF weekly telecon
- Requirements for General techniques http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JanMar/0301.html
- Requirements for checklists & techniques & test files http://www.w3.org/WAI/GL/WCAG20/WD-wcag2-tech-req-20050125.html
- Applicability Conditions http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JanMar/0062
- Assign reviewers to test files http://www.w3.org/WAI/GL/WCAG20/tests/
- 20 January: WCAG WG weekly telecon
- 19 January: WCAG WG TTF weekly telecon
- 13 January: WCAG WG telecon
- 6 January: WCAG WG Weekly Telecon