Friday, 30 June 2017
- Re: Professional communication / Keeping emotions in check
- RE: Personalisation examples (Was: Re: should we say "critical controls" or just "controls")
- Re: Personalisation examples (Was: Re: should we say "critical controls" or just "controls")
- Re: Personalisation examples (Was: Re: should we say "critical controls" or just "controls")
- Personalisation examples (Was: Re: should we say "critical controls" or just "controls")
- Re: Personalisation: meta-data vs button(s) on page
- Personalisation: meta-data vs button(s) on page
- link to the simple demo for personlization
- Re: should we say "critical controls" or just "controls".
- Re: should we say "critical controls" or just "controls".
Thursday, 29 June 2017
- RE: should we say "critical controls" or just "controls".
- Re: Professional communication / Keeping emotions in check
- Re: Issues with Target Size SC
- RE: Issues with Target Size SC
- Professional communication / Keeping emotions in check
- Thursday call minutes
- Re: Extra AGWG meeting, Thursday June 29, 2017
- Issues with Target Size SC
- WCAG-ACTION-338: Put together a draft template of structure
- Re: Extra AGWG meeting, Thursday June 29, 2017
- Extra AGWG meeting, Thursday June 29, 2017
- RE: should we say "critical controls" or just "controls".
- Re: I think Issue #63 should be looked at fairly soon.
- Re: Adapting text CFC
- 6/29/17 AGWG call
- I think Issue #63 should be looked at fairly soon.
- Re: Adapting text CFC
Wednesday, 28 June 2017
Tuesday, 27 June 2017
- Re: should we say "critical controls" or just "controls".
- RE: should we say "critical controls" or just "controls".
- Re: should we say "critical controls" or just "controls".
- should we say "critical controls" or just "controls".
- Minutes for AGWG meeting June 27th, 2017
- Re: AGWG meeting June 27th, 2017
- RE: How long /hard is it to install the personlization.
- Re: How long /hard is it to install the personlization.
- Re: How long /hard is it to install the personlization.
- Re: How long /hard is it to install the personlization.
- Re: How long /hard is it to install the personlization.
- Re: How long /hard is it to install the personlization.
- Re: How long /hard is it to install the personlization.
Monday, 26 June 2017
- Re: How long /hard is it to install the personlization.
- Re: How long /hard is it to install the personlization.
- RE: AGWG meeting June 27th, 2017
- Re: AGWG meeting June 27th, 2017
- [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 26 June 2017
- Re: CFC Add Accessible Name (was Speech Input) to editors draft
- Re: AGWG meeting June 27th, 2017
- RE: CFC Add Accessible Name (was Speech Input) to editors draft
- Re: CFC Add Accessible Name (was Speech Input) to editors draft
- RE: CFC Add Accessible Name (was Speech Input) to editors draft
- Re: AGWG meeting June 27th, 2017
- Re: CFC Add Accessible Name (was Speech Input) to editors draft
- RE: AGWG meeting June 27th, 2017
- Re: How long /hard is it to install the personlization.
- How long /hard is it to install the personlization.
- Re: AGWG meeting June 27th, 2017
- RE: AGWG meeting June 27th, 2017
Sunday, 25 June 2017
Friday, 23 June 2017
- RE: CFC Add Device Sensors to Editors Draft
- RE: CFC Add Device Sensors to Editors Draft
- RE: CFC Add Device Sensors to Editors Draft
- RE: CFC Add Device Sensors to Editors Draft
- Re: AGWG meeting June 27th, 2017
- RE: AGWG meeting June 27th, 2017
- RE: CFC Add Device Sensors to Editors Draft
- Re: CFC Add Accessible authentication into Editors Draft
- Re: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: AGWG meeting June 27th, 2017
- Re: CFC Add Device Sensors to Editors Draft
- Re: CFC Add Device Sensors to Editors Draft
- Re: CFC Add Device Sensors to Editors Draft
- Re: CFC Add Accessible Name (was Speech Input) to editors draft
- AGWG meeting June 27th, 2017
- Re: CFC Add Device Sensors to Editors Draft
- Re: CFC Add Accessible Name (was Speech Input) to editors draft
- Re: Long list of sites that use personalization to meet wcag
- Re: Long list of sites that use personalization to meet wcag
- Re: CFC Add Device Sensors to Editors Draft
- Re: CFC Add Accessible Name (was Speech Input) to editors draft
- RE: CFC Add Device Sensors to Editors Draft
Thursday, 22 June 2017
- When is the next Public Working Draft going to be published?
- Re: Editorial note (was RE: CFC Add User Interface Component Contrast (Minimum) to Editors Draft)
- RE: CFC Add Accessible Name (was Speech Input) to editors draft
- RE: Long list of sites that use personalization to meet wcag
- Re: Long list of sites that use personalization to meet wcag
- Re: CFC Add Accessible Name (was Speech Input) to editors draft
- Re: Long list of sites that use personalization to meet wcag
- Re: CFC Add Accessible Name (was Speech Input) to editors draft
- MINUTES: Extra AGWG meeting Thurs June 22nd, 2017
- Re: Extra AGWG meeting Thurs June 22nd, 2017
- Re: Long list of sites that use personalization to meet wcag
- RE: CFC Add Accessible Name (was Speech Input) to editors draft
- Re: CFC Add Accessible Name (was Speech Input) to editors draft
- CFC Add Accessible Name (was Speech Input) to editors draft
- Updated WebEx information for Tuesday AG WG call
- RE: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- RE: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- Re: Extra AGWG meeting Thurs June 22nd, 2017
- Re: Long list of sites that use personalization to meet wcag
- Re: Long list of sites that use personalization to meet wcag
- Re: Long list of sites that use personalization to meet wcag
- Re: Long list of sites that use personalization to meet wcag
- RE: Extra AGWG meeting Thurs June 22nd, 2017
- RE: Long list of sites that use personalization to meet wcag
- RE: Extra AGWG meeting Thurs June 22nd, 2017
- Re: Extra AGWG meeting Thurs June 22nd, 2017
- Re: Extra AGWG meeting Thurs June 22nd, 2017
- Re: Extra AGWG meeting Thurs June 22nd, 2017
- Re: Long list of sites that use personalization to meet wcag
- Re: Extra AGWG meeting Thurs June 22nd, 2017
Wednesday, 21 June 2017
- Re: CFC Add Accessible authentication into Editors Draft
- Re: CFC Add Device Sensors to Editors Draft
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- RE: Long list of sites that use personalization to meet wcag
- RE: Long list of sites that use personalization to meet wcag
- Fwd: Long list of sites that use personalization to meet wcag
- Re: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- Re: Extra AGWG meeting Thurs June 22nd, 2017
- Re: Extra AGWG meeting Thurs June 22nd, 2017
- Re: Extra AGWG meeting Thurs June 22nd, 2017
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Extra AGWG meeting Thurs June 22nd, 2017
- RE: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- RE: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- RE: CFC Add Device Sensors to Editors Draft
- RE: CFC Add Device Sensors to Editors Draft
- RE: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- RE: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- RE: CFC Add Accessible authentication into Editors Draft
- RE: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- Re: CFC Add Device Sensors to Editors Draft
- RE: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- RE: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- RE: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: CFC Add Device Sensors to Editors Draft
- Re: CFC Add Device Sensors to Editors Draft
- Re: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: CFC Add Accessible authentication into Editors Draft
- Re: CFC Add Device Sensors to Editors Draft
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- RE: CFC Add Device Sensors to Editors Draft
- Re: AGWG meeting June 20th, 2017
Tuesday, 20 June 2017
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- Re: CFC Add Device Sensors to Editors Draft
- RE: CFC Add Device Sensors to Editors Draft
- RE: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- Editorial issues (was RE: CFC Add Accessible authentication into Editors Draft)
- Re: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Editorial note (was RE: CFC Add User Interface Component Contrast (Minimum) to Editors Draft)
- Re: AGWG meeting June 20th, 2017
- Re: AGWG meeting June 20th, 2017
- Re: CFC Add Zoom Content (formerly Resize content) to Editors Draft
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: CFC Add Accessible authentication into Editors Draft
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- Re: AGWG meeting June 20th, 2017
- CFC Add Device Sensors to Editors Draft
- CFC Add User Interface Component Contrast (Minimum) to Editors Draft
- CFC Add Accessible authentication into Editors Draft
- CFC Add Zoom Content (formerly Resize content) to Editors Draft
- Re: AGWG meeting June 20th, 2017
- RE: AGWG meeting June 20th, 2017
- Re: Next steps for accessible authentication
- Re: Some of the security people consulted - was RE: Next steps for accessible authentication
- Re: Next steps for accessible authentication
- Some of the security people consulted - was RE: Next steps for accessible authentication
- Re: Next steps for accessible authentication
- Re: Next steps for accessible authentication
- Re: AGWG meeting June 20th, 2017
- Temp WebEx today: AGWG meeting June 20th, 2017
- Re: AGWG meeting June 20th, 2017
- Re: AGWG meeting June 20th, 2017
- RE: Next steps for accessible authentication
- Re: AGWG meeting June 20th, 2017
- RE: Next steps for accessible authentication
- Re: AGWG meeting June 20th, 2017
- Re: AGWG meeting June 20th, 2017
- Re: AGWG meeting June 20th, 2017
- Re: Next steps for accessible authentication
- RE: AGWG meeting June 20th, 2017
- Re: AGWG meeting June 20th, 2017
- Re: Next steps for accessible authentication
- Re: AGWG meeting June 20th, 2017
- Re: AGWG meeting June 20th, 2017
- Re: AGWG meeting June 20th, 2017
- Re: Next steps for accessible authentication
- Re: Next steps for accessible authentication
- Re: Next steps for accessible authentication
- Re: Next steps for accessible authentication
- RE: AGWG meeting June 20th, 2017
- Re: Next steps for accessible authentication
- RE: Next steps for accessible authentication
Monday, 19 June 2017
- Re: AGWG meeting June 20th, 2017
- Re: AGWG meeting June 20th, 2017
- Re: AGWG meeting June 20th, 2017
- Re: Next steps for accessible authentication
- Re: Next steps for accessible authentication
- RE: Next steps for accessible authentication
- Re: Next steps for accessible authentication
- RE: Next steps for accessible authentication
- Re: Next steps for accessible authentication
- Re: Next steps for accessible authentication
- Re: AGWG meeting June 20th, 2017
- RE: Next steps for accessible authentication
- RE: Next steps for accessible authentication
- [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 19 June 2017
- RE: Next steps for accessible authentication
- RE: Next steps for accessible authentication
- Re: Next steps for accessible authentication
Friday, 16 June 2017
Thursday, 15 June 2017
- RE: Next steps for accessible authentication
- Re: Next steps for accessible authentication
- Minutes for Extra AGWG meeting Thurs June 15th, 2017
- Re: Extra AGWG meeting Thurs June 15th, 2017
- TPAC 2017 registration now open
- COGA survey - Accessible Authentication
- TPAC schedule and registration - book your flights!
- RE: Extra AGWG meeting Thurs June 15th, 2017
Wednesday, 14 June 2017
- RE: Extra AGWG meeting Thurs June 15th, 2017
- RE: Extra AGWG meeting Thurs June 15th, 2017
- Extra AGWG meeting Thurs June 15th, 2017
Tuesday, 13 June 2017
- RE: Discussion - Add Orientation SC to Editor's Draft
- RE: Can we put "help and support" into the wcag draft
- Re: Discussion - Add Orientation SC to Editor's Draft
- RE: Discussion - Add Orientation SC to Editor's Draft
- Re: Can we put "help and support" into the wcag draft
- Re: AGWG meeting June 13th, 2017
- Re: Discussion - Add Orientation SC to Editor's Draft
- [CANCELLED] Updated AGWG meeting June 13th, 2017
- Re: Discussion - Add Orientation SC to Editor's Draft
- Discussion - Add Orientation SC to Editor's Draft
- RE: CFC - Add Orientation SC to Editor's Draft
- Re: CFC - Add Orientation SC to Editor's Draft
- RE: Updated AGWG meeting June 13th, 2017
- RE: CFC - Add Orientation SC to Editor's Draft
- Re: CFC - Add Orientation SC to Editor's Draft
- Re: Updated AGWG meeting June 13th, 2017
- RE: Updated AGWG meeting June 13th, 2017
Monday, 12 June 2017
- Re: CFC: Add Orientation SC to Editor's Draft
- Re: CFC: Add Orientation SC to Editor's Draft
- [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 12 June 2017
- RE: Updated AGWG meeting June 13th, 2017
- RE: AGWG meeting June 13th, 2017
- RE: Updated AGWG meeting June 13th, 2017
- should we work on "help and support" another week?
- Re: Can we put "help and support" into the wcag draft
Saturday, 10 June 2017
- Re: Proposal: We need to identify whether a proposed SC applies broadly
- Re: Proposal: We need to identify whether a proposed SC applies broadly
Friday, 9 June 2017
- RE: Updated AGWG meeting June 13th, 2017
- Survey on WAI Accessible Media Tutorial
- Re: AGWG meeting June 13th, 2017
- Re: Stripping CFC from subject lines
- Re: AGWG meeting June 13th, 2017
- Re: AGWG meeting June 13th, 2017
- Stripping CFC from subject lines
- Re: CFC: Approval process for Understanding documents
- RE: AGWG meeting June 13th, 2017
- Re: CFC: Add Character Key Shortcuts to Editor's Draft
- Updated AGWG meeting June 13th, 2017
- RE: Orientation comments analysis
- RE: Orientation comments analysis
- RE: Orientation comments analysis
- RE: Orientation comments analysis
- RE: AGWG meeting June 13th, 2017
- AGWG meeting June 13th, 2017
- Re: Orientation comments analysis
- Re: Proposal: We need to identify whether a proposed SC applies broadly
Thursday, 8 June 2017
- RE: Orientation comments analysis
- RE: Orientation comments analysis
- Re: Orientation comments analysis
- RE: Can we put "help and support" into the wcag draft
- RE: Orientation comments analysis
- Re: CFC: Change of Content SC
- Orientation comments analysis
- Can we put "help and support" into the wcag draft
- Re: CFC: Add Orientation SC to Editor's Draft
- Re: CFC: Add Orientation SC to Editor's Draft
- Minutes AG Meeting, June 8th
- Re: CFC: Add Orientation SC to Editor's Draft
- Re: CFC: Add Orientation SC to Editor's Draft
- RE: CFC: Add Orientation SC to Editor's Draft
- RE: CFC: Add Orientation SC to Editor's Draft
- CFC: Add Orientation SC to Editor's Draft
- RE: Approval process for Understanding documents
- RE: Add Character Key Shortcuts to Editor's Draft
- Re: CFC: Add Character Key Shortcuts to Editor's Draft
- RE: CFC: Approval process for Understanding documents
- RE: Add Character Key Shortcuts to Editor's Draft
- Re: CFC: Approval process for Understanding documents
- Re: Further discussion on Change of Content SC
Wednesday, 7 June 2017
- Re: Zoom content updates Pt3
- Re: Further discussion on Change of Content SC
- Re: CFC: Approval process for Understanding documents
- Re: Further discussion on Change of Content SC
- Further discussion on Change of Content SC
- Re: CFC: Change of Content SC
- Re: Add Character Key Shortcuts to Editor's Draft
- Re: Bad link?
- Re: Bad link?
- RE: Bad link?
- Re: Question about email clients and "CFC" in the message subject
- Re: Sign up to Scribe! AGWG needs you!
- RE: Question about email clients and "CFC" in the message subject
- RE: Question about email clients and "CFC" in the message subject
- Re: Bad link?
- Question about email clients and "CFC" in the message subject
- RE: Bad link?
- Re: CFC: Change of Content SC
- Bad link?
- Re: CFC: Change of Content SC
- Re: Add Character Key Shortcuts to Editor's Draft
- RE: Add Character Key Shortcuts to Editor's Draft
- Re: Add Character Key Shortcuts to Editor's Draft
- RE: Add Character Key Shortcuts to Editor's Draft
- Re: Add Character Key Shortcuts to Editor's Draft
- Re: Add Character Key Shortcuts to Editor's Draft
- RE: Approval process for Understanding documents
- Re: CFC: Approval process for Understanding documents
- Re: CFC: Add Character Key Shortcuts to Editor's Draft
- Re: CFC: Approval process for Understanding documents
- Re: AGWG meeting June 8, 2017 at 11:30 ET
- The request to return font family bullet to the Adapting Text SC (was Re: Font Width Arabic Fonts on Google Fonts)
- RE: Add Character Key Shortcuts to Editor's Draft
- RE: Approval process for Understanding documents
- RE: Add Character Key Shortcuts to Editor's Draft
- RE: Add Character Key Shortcuts to Editor's Draft
- Re: Add Character Key Shortcuts to Editor's Draft
- Re: Sign up to Scribe! AGWG needs you!
- Re: Add Character Key Shortcuts to Editor's Draft
- Re: CFC: Add Character Key Shortcuts to Editor's Draft
- Re: Approval process for Understanding documents
- Re: Approval process for Understanding documents
- RE: Font Width Arabic Fonts on Google Fonts
- RE: Approval process for Understanding documents
- RE: CFC: Add Character Key Shortcuts to Editor's Draft
- RE: Add Character Key Shortcuts to Editor's Draft
- Font Width Arabic Fonts on Google Fonts
- RE: Approval process for Understanding documents
- AGWG meeting June 8, 2017 at 11:30 ET
- Re: CFC: Add Character Key Shortcuts to Editor's Draft
- Re: CFC: Approval process for Understanding documents
- CFC: Approval process for Understanding documents
- CFC: Add Character Key Shortcuts to Editor's Draft
- Re: CFC: Change of Content SC
Tuesday, 6 June 2017
- Orientation essential examples
- Character shortcuts & blind or low vision
- Sign up to Scribe! AGWG needs you!
- Meeting minutes
- MINUTES of AGWG meeting June 6, 2017
- TPAC dates
- Re: AGWG meeting June 6th, 2017
- Re: AGWG meeting June 6th, 2017
- [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 5 June 2017
- Re: AGWG meeting June 6th, 2017
- Re: AGWG meeting June 6th, 2017
- Re: AGWG meeting June 6th, 2017
- Re:grets AGWG meeting June 6th, 2017
- Re: Zoom content updates Pt3
- Re: Revised Wording for COGA Issue #32: Help
- Re: Zoom content updates Pt3
- Discussing modern css accessibility techniques
- Revised Wording for COGA Issue #32: Help
Monday, 5 June 2017
- RE: Zoom content updates Pt2
- Re: Zoom content updates Pt2
- Re: Zoom content updates Pt2
- Re: Zoom content updates Pt2
- Re: Zoom content updates Pt2
- Re: Zoom content updates Pt2
- RE: Zoom content updates Pt2
- Re: Zoom content updates Pt2
- RE: Zoom content updates Pt2
- Re: Zoom content updates Pt2
- Correct TinyURL for the summary spreadsheet
- Re: Zoom content updates Pt2
Saturday, 3 June 2017
- RE: AGWG meeting June 6th, 2017
- AGWG meeting June 6th, 2017
- Re: Spreadsheet updated
- Spreadsheet updated
Friday, 2 June 2017
- RE: help with voting
- RE: help with voting
- Re: CJK Letters some questions so I can compute font family sizes.
Thursday, 1 June 2017
- Re: CJK Letters some questions so I can compute font family sizes.
- Re: CJK Letters some questions so I can compute font family sizes.
- MINUTES of AGWG meeting June 1, 2017 at 11:30 ET
- Re: CFC: Change of Content SC
- RE: AGWG meeting June 1, 2017 at 11:30 ET
- Re: help with voting
- help with voting
- Re: AGWG meeting June 1, 2017 at 11:30 ET
- Re: RE: AGWG meeting June 1, 2017 at 11:30 ET
- Re: CFC: Change of Content SC
Wednesday, 31 May 2017
- CJK Letters some questions so I can compute font family sizes.
- RE: AGWG meeting June 1, 2017 at 11:30 ET
- Re: CFC: Change of Content SC
- Re: AGWG meeting June 1, 2017 at 11:30 ET
- Re: CFC: Change of Content SC
- Re: Mean character width for 16px Google Fonts (818 Families)
- RE: CFC: Change of Content SC
- Re: CFC: Change of Content SC
- Re: Mean character width for 16px Google Fonts (818 Families)
- Re: Mean character width for 16px Google Fonts (818 Families)
- Re: Mean character width for 16px Google Fonts (818 Families)
- Re: Mean character width for 16px Google Fonts (818 Families)
- Re: CFC: Change of Content SC
Tuesday, 30 May 2017
- Re: CFC: Change of Content SC
- Re: CFC: Change of Content SC
- Re: CFC: Change of Content SC
- Re: CFC: Change of Content SC
- Re: CFC: Change of Content SC
- RE: CFC: Change of Content SC
- Re: CFC: Change of Content SC
- RE: Change of Content SC
- Re: AGWG meeting June 1, 2017 at 11:30 ET
- AGWG meeting June 1, 2017 at 11:30 ET
- Re: CFC: Change of Content SC
- Re: CFC: Change of Content SC
- Re: Change of Content SC
- RE: Change of Content SC
- RE: Change of Content SC
- CFC: Change of Content SC
- MINUTES Re: AGWG call at 11:00am ET, May 30, 2017
- Re: Mean character width for 16px Google Fonts (818 Families)
- RE: Mean character width for 16px Google Fonts (818 Families)
- Re: AGWG meeting May 30, 2017
- Re: AGWG meeting May 30, 2017
- RE: AGWG meeting May 30, 2017
- Re: AGWG meeting May 30, 2017
- Mean character width for 16px Google Fonts (818 Families)
- Re: AGWG meeting May 30, 2017
- Updated: AGWG meeting May 30, 2017
Monday, 29 May 2017
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: AGWG meeting May 30, 2017
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: Proposal for moving COGA SC forward
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: Proposal for moving COGA SC forward
- [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 29 May 2017
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- AGWG meeting May 30, 2017
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
Sunday, 28 May 2017
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- RE: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- RE: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: Proposal for moving COGA SC forward
- RE: CFC: Target Size and Target Size (no exception) SC
- RE: CFC: Target Size and Target Size (no exception) SC
- Re: Proposal for moving COGA SC forward
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: Supplementary document for WCAG 2.1
Friday, 26 May 2017
- Re: Supplementary document for WCAG 2.1
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: Proposal for moving COGA SC forward
- Re: Target Size SCs issue feedback
- RE: Target Size SCs issue feedback
- RE: CFC: Target Size and Target Size (no exception) SC
- RE: Target Size and Target Size (no exception) SC
- RE: Proposal for moving COGA SC forward
- RE: Target Size SCs issue feedback
- RE: Target Size SCs issue feedback
- RE: Target Size SCs issue feedback
- Re: Target Size SCs issue feedback
- Re: Proposal for moving COGA SC forward
- RE: Supplementary document for WCAG 2.1
- RE: Target Size SCs issue feedback
- RE: Supplementary document for WCAG 2.1
- Re: Proposal for moving COGA SC forward
- Re: Supplementary document for WCAG 2.1
- RE: CFC: Target Size and Target Size (no exception) SC
- RE: Zoom content updates
- Target Size SCs issue feedback
- Re: Supplementary document for WCAG 2.1
- Re: Supplementary document for WCAG 2.1
- Re: Supplementary document for WCAG 2.1
- Re: CFC: Target Size and Target Size (no exception) SC
Thursday, 25 May 2017
- Zoom content updates
- Re: Proposal for moving COGA SC forward
- Re: CFC: Supplementary document for WCAG 2.1
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: Proposal for moving COGA SC forward
- Re: Proposal for moving COGA SC forward
- WCAG WG Meeting Minutes May 25, 2017
- Re: CFC: Supplementary document for WCAG 2.1
- Re: AGWG meeting May 25, 2017
- Actual call-in info for today's call
- RE: AGWG meeting May 25, 2017
- RE: AGWG meeting May 25, 2017
- Re: AGWG meeting May 25, 2017
- Re: Proposal for moving COGA SC forward
- Re: Proposal for moving COGA SC forward
- RE: Proposal for moving COGA SC forward
- Re: Supplementary document for WCAG 2.1
- Re: AGWG meeting May 25, 2017
- RE: Supplementary document for WCAG 2.1
- RE: Supplementary document for WCAG 2.1
- RE: Supplementary document for WCAG 2.1
- RE: Supplementary document for WCAG 2.1
- Re: Proposal for moving COGA SC forward
Wednesday, 24 May 2017
- Re: Proposal for moving COGA SC forward
- Re: Proposal for moving COGA SC forward
- Re: Proposal for moving COGA SC forward
- RE: Proposal for moving COGA SC forward
- Re: Proposal for moving COGA SC forward
- Re: Proposal for moving COGA SC forward
- Re: Proposal for moving COGA SC forward
- Re: AGWG meeting May 25, 2017
- Re: AGWG meeting May 25, 2017
- Re: AGWG meeting May 25, 2017
- AGWG meeting May 25, 2017
- Re: CFC: Supplementary document for WCAG 2.1
- Re: Target Size and Target Size (no exception) SC
- Re: Target Size and Target Size (no exception) SC
- RE: Proposal for moving COGA SC forward
- RE: Supplementary document for WCAG 2.1
- Re: Target Size and Target Size (no exception) SC
- Proposal for moving COGA SC forward
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Supplementary document for WCAG 2.1
- RE: CFC: Target Size and Target Size (no exception) SC
- Re: Alternative approach for Plain Language
- RE: CFC: Supplementary document for WCAG 2.1
- RE: CFC: Supplementary document for WCAG 2.1
- Re: Target Size and Target Size (no exception) SC
- RE: CFC: Target Size and Target Size (no exception) SC
- RE: Target Size and Target Size (no exception) SC
- RE: CFC: Target Size and Target Size (no exception) SC
- Re: Alternative approach for Plain Language
- Re: Supplementary document for WCAG 2.1
- Re: CFC: Supplementary document for WCAG 2.1
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: Target Size and Target Size (no exception) SC
- Re: Target size alternative
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: Do we like this better? - was way to move forward with plain language
- Re: Target size alternative
- Re: Alternative approach for Plain Language
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Supplementary document for WCAG 2.1
Tuesday, 23 May 2017
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Supplementary document for WCAG 2.1
- Re: CFC: Supplementary document for WCAG 2.1
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- RE: Target Size and Target Size (no exception) SC
- RE: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- RE: Supplementary document for WCAG 2.1
- RE: Target Size and Target Size (no exception) SC
- Re: CFC: Supplementary document for WCAG 2.1
- RE: Alternative approach for Plain Language
- Re: CFC: 1.3.3/1.4.1 Errata
- RE: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Supplementary document for WCAG 2.1
- Alternative approach for Plain Language
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Supplementary document for WCAG 2.1
- RE: Target Size and Target Size (no exception) SC
- Re: Target Size and Target Size (no exception) SC
- Re: CFC: Supplementary document for WCAG 2.1
- RE: CFC: Supplementary document for WCAG 2.1
- Re: CFC: Supplementary document for WCAG 2.1
- Re: CFC: Supplementary document for WCAG 2.1
- Re: Target Size and Target Size (no exception) SC
- Re: Target size alternative
- Re: CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Target Size and Target Size (no exception) SC
- [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 22 May 2017
- AG Meeting Minutes 23 May 2017
- Re: Target Size and Target Size (no exception) SC
- RE: CFC: Resolution to accept the candidate SC 'Target Size'
- RE: Supplementary document for WCAG 2.1
- Re: CFC: Resolution to accept the candidate SC 'Target Size'
- RE: Supplementary document for WCAG 2.1
- RE: Target size alternative
- Re: CFC: Resolution to accept the candidate SC 'Target Size'
- CFC: Supplementary document for WCAG 2.1
- RE: Target Size and Target Size (no exception) SC
- CFC: Resolution to accept the candidate SC 'Target Size'
- CFC: Target Size and Target Size (no exception) SC
- Re: CFC: Supplementary document for WCAG 2.1
- Re: Supplementary document for WCAG 2.1
- RE: Supplementary document for WCAG 2.1
- Re: CFC: Supplementary document for WCAG 2.1
- CFC: Supplementary document for WCAG 2.1
- Re: TPAC2017 - Book flights and hotel NOW if approved to go
- Re: TPAC2017 - Book flights and hotel NOW if approved to go
- Re: TPAC2017 - Book flights and hotel NOW if approved to go
- Re: CFC: 1.3.3/1.4.1 Errata
- Re: Combining the two.... Re: Do we like this better? - was way to move forward with plain language
- Re: Updated: AGWG meeting May 23 2017
- Re: Combining the two.... Re: Do we like this better? - was way to move forward with plain language
- Re: TPAC2017 - Book flights and hotel NOW if approved to go
- TPAC2017 - Book flights and hotel NOW if approved to go
- RE: Target size alternative
- RE: issue #60 target size: addressing unstyled native controls
- Re: issue #60 target size: addressing unstyled native controls
- Target size alternative
- RE: issue #60 target size: addressing unstyled native controls
- RE: issue #60 target size: addressing unstyled native controls
- issue #60 target size: addressing unstyled native controls
- Combining the two.... Re: Do we like this better? - was way to move forward with plain language
- Re: Do we like this better? - was way to move forward with plain language
- Re: Updated: AGWG meeting May 23 2017
- Agenda+ Target size discussion/legacy content and WCAG 2.1
Monday, 22 May 2017
- RE: AGWG meeting May 23 2017
- RE: 1.3.3/1.4.1 Errata
- RE: AGWG meeting May 23 2017
- RE: 1.3.3/1.4.1 Errata
- Re: CFC: 1.3.3/1.4.1 Errata
- RE: Do we like this better? - was way to move forward with plain language
- Re: Do we like this better? - was way to move forward with plain language
- RE: Do we like this better? - was way to move forward with plain language
- Re: Do we like this better? - was way to move forward with plain language
- Re: Do we like this better? - was way to move forward with plain language
- Re: Do we like this better? - was way to move forward with plain language
- Re: Do we like this better? - was way to move forward with plain language
- Re: Do we like this better? - was way to move forward with plain language
- Re: Do we like this better? - was way to move forward with plain language
- Do we like this better? - was way to move forward with plain language
- Re: language step by step: - was Re: might be last option for plain language
- Re: 1.3.3/1.4.1 Errata
Sunday, 21 May 2017
- Re: CFC: 1.3.3/1.4.1 Errata
- Re: CFC: 1.3.3/1.4.1 Errata
- language step by step: - was Re: might be last option for plain language
Saturday, 20 May 2017
Friday, 19 May 2017
- Re: CFC: 1.3.3/1.4.1 Errata
- Re: CFC: 1.3.3/1.4.1 Errata
- Re: CFC: 1.3.3/1.4.1 Errata
- Re: CFC: 1.3.3/1.4.1 Errata
- Re: CFC: 1.3.3/1.4.1 Errata
- CFC: 1.3.3/1.4.1 Errata
- Re: Re[2]: GitHub accessibility improvements
- Updated: AGWG meeting May 23 2017
- RE: Resize content - questions remaining
- Re[2]: GitHub accessibility improvements
- Re: GitHub accessibility improvements
- AGWG meeting May 23 2017
- RE: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Re: Resize content - questions remaining
Thursday, 18 May 2017
- Re: GitHub accessibility improvements
- Re: GitHub accessibility improvements
- Re: Legacy content - requirement for conformance to WCAG 2.1?
- Re: GitHub accessibility improvements
- GitHub accessibility improvements
- Re: Quick question, is WCAG 2.1 working draft being published monthly (or every other month)?
- Quick question, is WCAG 2.1 working draft being published monthly (or every other month)?
- Legacy content - requirement for conformance to WCAG 2.1?
- MInutes for AGWG Thursday call on May 18, 2017
- Re: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Re: Errata on WCAG 2.0 1.3.3 and 1.4.1
- RE: Resize content - questions remaining
- Re: Resize content - questions remaining
- Re: Resize content - questions remaining
- Re: Resize content - questions remaining
- RE: Resize content - questions remaining
- Re: might be last option for plain language
- Resize content - questions remaining
- Re: might be last option for plain language
- Re: might be last option for plain language
- Re: might be last option for plain language
Wednesday, 17 May 2017
- Re: changes to plain language based on the feedback
- Re: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Re: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Re: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Re: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Thursday call for AGWG at 11:30am ET May 18
- RE: Errata on WCAG 2.0 1.3.3 and 1.4.1
- RE: Errata on WCAG 2.0 1.3.3 and 1.4.1
- RE: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Re: might be last option for plain language
- Re: we need to quantify what the issues can not be meet for plain language
- Re: we need to quantify what the issues can not be meet for plain language
- RE: we need to quantify what the issues can not be meet for plain language
- Re: we need to quantify what the issues can not be meet for plain language
- RE: Re[2]: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Re: Re[2]: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Re[2]: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Re: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Re: we need to quantify what the issues can not be meet for plain language
- Re: Errata on WCAG 2.0 1.3.3 and 1.4.1
- Re: might be last option for plain language
- Re: Errata on WCAG 2.0 1.3.3 and 1.4.1
- we need to quantify what the issues can not be meet for plain language
- RE: might be last option for plain language
- Errata on WCAG 2.0 1.3.3 and 1.4.1
Tuesday, 16 May 2017
- RE: might be last option for plain language
- RE: might be last option for plain language
- Re: might be last option for plain language
- RE: might be last option for plain language
- Re: might be last option for plain language
- RE: might be last option for plain language
- Re: might be last option for plain language
- RE: might be last option for plain language
- might be last option for plain language
- Accessibility Guidelines Working Group Teleconference : 16 May 2017 , Minutes
- RE: changes to plain language based on the feedback
- Re: AGWG meeting May 16, 2017
- Re: Issue #69: Character key commands
- RE: AGWG meeting May 16, 2017
- Re: Issue #69: Character key commands
- Re: Issue #69: Character key commands
- Re: Issue #69: Character key commands
- Re: Issue #69: Character key commands
- Re: Issue #69: Character key commands
- Re: changes to plain language based on the feedback
- Re: AGWG meeting May 16, 2017
- RE: Issue #69: Character key commands
- Re: Issue #69: Character key commands
- Re: AGWG meeting May 16, 2017
- Re: Issue #69: Character key commands
- Re: Issue #69: Character key commands
- RE: Follow up from the meeting on Issue 14: timeouts
- Issue #69: Character key commands
Monday, 15 May 2017
- RE: changes to plain language based on the feedback
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: changes to plain language based on the feedback
- Re: changes to plain language based on the feedback
- changes to plain language based on the feedback
- Re: [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 15 May 2017
- Re: AGWG meeting May 16, 2017
- [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 15 May 2017
- Re: AGWG meeting May 16, 2017
- RE: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
Saturday, 13 May 2017
- Re: Request for Review and Comment: Confirm Important Information (Issue #33)
- RE: Request for Review and Comment: Confirm Important Information (Issue #33)
Friday, 12 May 2017
- Re: Request for Review and Comment: Confirm Important Information (Issue #33)
- RE: Request for Review and Comment: Confirm Important Information (Issue #33)
- Re: Request for Review and Comment: Confirm Important Information (Issue #33)
- RE: Request for Review and Comment: Confirm Important Information (Issue #33)
- Re: Request for Review and Comment: Confirm Important Information (Issue #33)
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Request for Review and Comment: Confirm Important Information (Issue #33)
- Request for Review and Comment: Confirm Important Information (Issue #33)
- RE: Follow up from the meeting on Issue 14: timeouts
- AGWG meeting May 16, 2017
- Re: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
Thursday, 11 May 2017
- Re: Follow up from the meeting on Issue 14: timeouts
- MINUTES Re: Thursday call for AGWG at 11:30am ET May 11
- RE: Follow up from the meeting on Issue 14: timeouts
- RE: Thursday call for AGWG at 11:30am ET May 11
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Thursday call for AGWG at 11:30am ET May 11
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Thursday call for AGWG at 11:30am ET May 11
- Re: Thursday call for AGWG at 11:30am ET May 11
- RE: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Thursday call for AGWG at 11:30am ET May 11
- RE: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Thursday call for AGWG at 11:30am ET May 11
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
Wednesday, 10 May 2017
- Re: Follow up from the meeting on Issue 14: timeouts
- Thursday call for AGWG at 11:30am ET May 11
- Re: OFF TOPIC (was Re: proposed change of language for common words)
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Feedback on changes to Minimize User Errors
- Feedback on changes to Minimize User Errors
- OFF TOPIC (was Re: proposed change of language for common words)
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
Tuesday, 9 May 2017
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- RE: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- Re: Follow up from the meeting on Issue 14: timeouts
- Follow up from the meeting on Issue 14: timeouts
- Accessibility Guidelines Working Group Teleconference : 09 May 2017 , Minutes
- Re: Can you confirm if you want the sensitive data exception for timeouts
- Re: AGWG meeting May 9th, 2017
- Re: AGWG meeting May 9th, 2017
- Re: Can you confirm if you want the sensitive data exception for timeouts
- RE: AGWG meeting May 9th, 2017
- Re: Issue 77 Resize Content SC
- Please remove from list serve
- Please remove from this list server
- Re: Issue 77 Resize Content SC
Monday, 8 May 2017
- Re: Understanding content now set up in WCAG 2.1 repository
- Re: Understanding content now set up in WCAG 2.1 repository
- Re: Issue 77 Resize Content SC
- Re: Issue 77 Resize Content SC
- Re: Understanding content now set up in WCAG 2.1 repository
- Re: Issue 77 Resize Content SC
- Re: Issue 77 Resize Content SC
- Re: Issue 77 Resize Content SC
- Re: Issue 77 Resize Content SC
- Re: Issue 77 Resize Content SC
- Re: Issue 77 Resize Content SC
- Re: Issue 77 Resize Content SC
- Re: Can you confirm if you want the sensitive data exception for timeouts
- Re: Can you confirm if you want the sensitive data exception for timeouts
- Fwd: Re: AGWG meeting May 9th, 2017
- Re: Can you confirm if you want the sensitive data exception for timeouts
- Re: Can you confirm if you want the sensitive data exception for timeouts
- Re: is this a way forward for familiar design?
- [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 8 May 2017
- Re: Issue 77 Resize Content SC
- Re: AGWG meeting May 9th, 2017
- Re: Issue 77 Resize Content SC
- Re: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- Re: Can you confirm if you want the sensitive data exception for timeouts
- Re: CFC: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
Sunday, 7 May 2017
- RE: Can you confirm if you want the sensitive data exception for timeouts
- RE: AGWG meeting May 9th, 2017
- is this a way forward for familiar design?
Friday, 5 May 2017
- Re: Issue 77 Resize Content SC
- Re: AGWG meeting May 9th, 2017
- Understanding content now set up in WCAG 2.1 repository
- Re: Can you confirm if you want the sensitive data exception for timeouts
- Re: Issue 77 Resize Content SC
- Re: Can you confirm if you want the sensitive data exception for timeouts
- Re: Issue 77 Resize Content SC
- Re: Issue 77 Resize Content SC
- Re: Can you confirm if you want the sensitive data exception for timeouts
- Re: Issue 77 Resize Content SC
- AGWG meeting May 9th, 2017
- Re: Issue 77 Resize Content SC
- Re: Can you confirm if you want the sensitive data exception for timeouts
- Can you confirm if you want the sensitive data exception for timeouts
- Re: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
Thursday, 4 May 2017
- Re: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- Re: CFC: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- Re: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- RE: CFC: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- RE: CFC: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- Re: CFC: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- RE: CFC: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- AG Meeting Minutes 4 May 2017
- Re: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- RE: Extra AGWG meeting on Thurs 4th May 2017
- Re: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- RE: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- Re: CFC: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- Re: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- Re: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- RE: Extra AGWG meeting on Thurs 4th May 2017
- RE: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- CFC: Issue 77 Resize Content SC - deadline - 6th May 18:00 EST.
- RE: please can you update your vote
- Re: Extra AGWG meeting on Thurs 4th May 2017
- RE: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
- Re: please can you update your vote
- Re: Re: Extra AGWG meeting on Thurs 3rd May 2017
- Re: please can you update your vote
- Re: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
- Re: please can you update your vote
- Re: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
Wednesday, 3 May 2017
- Re: please can you update your vote
- RE: Another way forward? (Just an idea for discussion)
- Re: Is Java Web Start covered by WCAG?
- RE: Another way forward? (Just an idea for discussion)
- RE: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
- Re: Another way forward? (Just an idea for discussion)
- Re: please can you update your vote
- Another way forward? (Just an idea for discussion)
- Re: please can you update your vote
- Github greasemonkey script
- Re: Is Java Web Start covered by WCAG?
- Re: please can you update your vote
- Re: please can you update your vote
- please can you update your vote
- Re: Extra AGWG meeting on Thurs 3rd May 2017
- Extra AGWG meeting on Thurs 3rd May 2017
Tuesday, 2 May 2017
- Minutes from May 2 teleconference
- Re: AGWG meeting May 2, 2017 (with updated agenda)
- Re: AGWG meeting May 2, 2017 (with updated agenda)
- Re: AGWG meeting May 2, 2017 (with updated agenda)
- Re: AGWG meeting May 2, 2017 (with updated agenda)
- Re:AGWG meeting May 2, 2017 (with updated agenda)
- Re: AGWG meeting May 2, 2017 (with updated agenda)
- RE: AGWG meeting May 2, 2017 (with updated agenda)
- Re: AGWG meeting May 2, 2017 (with updated agenda)
Monday, 1 May 2017
- Re: Is Java Web Start covered by WCAG?
- RE: AGWG meeting May 2, 2017
- AGWG meeting May 2, 2017 (with updated agenda)
- Re: AGWG meeting May 2, 2017
- AGWG meeting May 2, 2017
Saturday, 29 April 2017
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
Friday, 28 April 2017
- Re: Is Java Web Start covered by WCAG?
- RE: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- RE: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Meeting Minutes from 04/27/17
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- RE: Is Java Web Start covered by WCAG?
Thursday, 27 April 2017
- Re: Is Java Web Start covered by WCAG?
- RE: Extra AGWG meeting on Thurs 27th April
- Re: Correct info for Thursday call
- RE: Correct info for Thursday call
- Re: Extra AGWG meeting on Thurs 27th April
- Re: Extra AGWG meeting on Thurs 27th April
- Correct info for Thursday call
- Re: Extra AGWG meeting on Thurs 27th April
- use this link! was RE: Extra AGWG meeting on Thurs 27th April
- Re: Is Java Web Start covered by WCAG?
- RE: Extra AGWG meeting on Thurs 27th April
- Re: Extra AGWG meeting on Thurs 27th April
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- RE: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Resize content - initial responses
- [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 24 April 2017
- Re: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- Re: Is Java Web Start covered by WCAG?
- Re: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- Re: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- Re: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
Wednesday, 26 April 2017
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- RE: Is Java Web Start covered by WCAG?
- Re: Is Java Web Start covered by WCAG?
- Is Java Web Start covered by WCAG?
- Re: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- Re: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- Re: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- Re: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- Re: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- Re: Extra AGWG meeting on Thurs 27th April
- Re: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- Re: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- RE: Extra AGWG meeting on Thurs 27th April
Tuesday, 25 April 2017
- RE: Using Markdown for Github accessibility
- Re: Extra AGWG meeting on Thurs 27th April
- Re: Using Markdown for Github accessibility
- Using Markdown for Github accessibility
- Re: Extra AGWG meeting on Thurs 27th April
- Extra AGWG meeting on Thurs 27th April
- WebEx broke, abandoned AG call
- Call minutes April 25, 2017
- Re: AGWG meeting April 25th 2017
- Re: AGWG meeting April 25th 2017
- RE: Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Can anyone not live with this sentence as the Adapting Text SC's intro? (was Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?)
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- RE: AGWG meeting April 25th 2017
Monday, 24 April 2017
- RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Appling personalisation to a site
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Appling personalisation to a site
- Re: AGWG meeting April 25th 2017
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
Sunday, 23 April 2017
- RE: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Re: Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
- Must "technologies being used" be in a SC's text, if that SC has support in 2 technologies?
Saturday, 22 April 2017
- Re: Potential clarification of Web Content/User Agent
- Re: Potential clarification of Web Content/User Agent
Friday, 21 April 2017
- Re: Adding the word "meaning"?
- Re: Adding the word "meaning"?
- RE: Adding the word "meaning"?
- Re: Adding the word "meaning"?
- Re: Adding the word "meaning"?
- Re: Potential clarification of Web Content/User Agent
- Re: Potential clarification of Web Content/User Agent
- Re: Potential clarification of Web Content/User Agent
- Re: Potential clarification of Web Content/User Agent
- RE: AGWG meeting April 25th 2017
- Re: Potential clarification of Web Content/User Agent
- AGWG meeting April 25th 2017
Thursday, 20 April 2017
- Potential clarification of Web Content/User Agent
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Houston, do we have a problem?
- Re: Houston, do we have a problem?
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adding the word "meaning"?
- Houston, do we have a problem?
- Adding the word "meaning"?
- Minutes for Extra AGWG call on Thurs 20th April 2017
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- RE: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- RE: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- Re: SC #78 'Adapting text', and a question regarding consensus on icon fonts
- SC #78 'Adapting text', and a question regarding consensus on icon fonts
Wednesday, 19 April 2017
- A measure of element growth due to changing font family.
- Extra AGWG call on Thurs 20th April 2017
- Option H Testabilty (Adapting Text SC)
- Re: CFC: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- Re: CFC: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- Re: SC Managers and public comments
- Re: CFC: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- Re: SC Managers and public comments
- Re: SC Managers and public comments
- Re: SC Managers and public comments
- Re: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
Tuesday, 18 April 2017
- WCAG WG Meeting Minutes April 18, 2017
- Re: AGWG meeting April 18, 2017
- RE: AGWG meeting April 18, 2017
- RE: AGWG meeting April 18, 2017
- RE: AGWG meeting April 18, 2017
- RE: Key question on SC text and testability
- RE: Key question on SC text and testability
- Re: Key question on SC text and testability
- Key question on SC text and testability
- Re: AGWG meeting April 18, 2017
- RE: AGWG meeting April 18, 2017
Monday, 17 April 2017
Sunday, 16 April 2017
- Re: [public-low-vision-a11y-tf] <none>
- Re: Can someone explain the therapeutic value of switching to one font family
- AGWG meeting April 18, 2017
- Re: Can someone explain the therapeutic value of switching to one font family
Saturday, 15 April 2017
- [w3c-wai-gl] <none>
- Re: Can someone explain the therapeutic value of switching to one font family
- Survey questions for J&K and H&I
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Can someone explain the therapeutic value of switching to one font family
- Adapting Text: "narrow values" vs "wide values" how to reach consensus (was Can someone explain the therapeutic value of switching to one font family)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Can someone explain the therapeutic value of switching to one font family
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
Friday, 14 April 2017
- RE: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: SC Managers and public comments
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: SC Managers and public comments
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Adapting Text proposals for next week's survey. (was Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I)
- Re: SC Managers and public comments
- Re: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I
Thursday, 13 April 2017
- Re: CFC: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- Silver Task Force update
- Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I
- Re: Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I
- Re: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- RE: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- Re: 48-Hour Call for Consensus (CfC): Two COGA FPWDs
- Re: CFC: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- Re: CFC: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- RE: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- Re: CFC: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- Re: CFC: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- Call minutes
- Adding Greg L's Adapting Text proposals to the Wiki in anticipation of a vote between J&K and H&I
- RE: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- CFC: Request to publish COGA Issue papers, Gap Analysis & Road Map documents
- Re: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- Re: Extra AGWG call on Thurs 13th April 2017
- Please book for TPAC
- Re: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- Re: Extra AGWG call on Thurs 13th April 2017
Wednesday, 12 April 2017
- Re: target size
- RE: Resolution to accept the candidate SC 'Accidental Activation'
- Extra AGWG call on Thurs 13th April 2017
- RE: target size
- Re: target size
- target size
- Re: Resolution to accept the candidate SC 'Accidental Activation'
- Re: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- RE: Resolution to accept the candidate SC 'Accidental Activation'
- RE: Resolution to accept the candidate SC 'Accidental Activation'
- Re: Heading Navigation in GitHub Issues
Tuesday, 11 April 2017
- Re: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- RE: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- Heading Navigation in GitHub Issues
- Re: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- Re: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- RE: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- Re: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- Re: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- Re: CFC: Resolution to accept the candidate SC 'Accidental Activation'
- CFC: Resolution to accept the candidate SC 'Accidental Activation'
- Re: AGWG meeting April 11th - 2017
- Re: AGWG meeting April 11th - 2017
- WebRTC testing in WebEx
- Re: AGWG meeting April 11th - 2017
- RE: AGWG meeting April 11th - 2017
- RE: AGWG meeting April 11th - 2017
- RE: AGWG meeting April 11th - 2017
- Re: Adapting text question on this week's survey
- Re: AGWG meeting April 11th - 2017
- Re: Technolog Agnostic / Independent
- RE: AGWG meeting April 11th - 2017
- Re: AGWG meeting April 11th - 2017
- Re: Technolog Agnostic / Independent
- Re: Technolog Agnostic / Independent
Monday, 10 April 2017
- Re: Technolog Agnostic / Independent
- Re: Technolog Agnostic / Independent
- RE: Technolog Agnostic / Independent
- Re: Technolog Agnostic / Independent
- Re: Adapting text question on this week's survey
- Re: AGWG meeting April 11th - 2017
- RE: AGWG meeting April 11th - 2017
- Re: AGWG meeting April 11th - 2017
- RE: AGWG meeting April 11th - 2017
- Re: Technolog Agnostic / Independent
- RE: Separate WCAG doc for non-SC guidelines
- Re: Technolog Agnostic / Independent
- Re: Technolog Agnostic / Independent
- Adapting text question on this week's survey
- Re: Technolog Agnostic / Independent
- [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 10 April 2017
- Technolog Agnostic / Independent
- Re: SC Managers and public comments
- Re: SC Managers and public comments
- Re: SC Managers and public comments
- Re: SC Managers and public comments
- Re: SC Managers and public comments
- Re: SC Managers and public comments
- Re: SC Managers and public comments
- Re: SC Managers and public comments
- Re: SC Managers and public comments
- Re: SC Managers and public comments
- Re: SC Managers and public comments
Friday, 7 April 2017
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- RE: AGWG meeting April 11th - 2017
- AGWG meeting April 11th - 2017
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Separate WCAG doc for non-SC guidelines
- Re: Separate WCAG doc for non-SC guidelines
- RE: Separate WCAG doc for non-SC guidelines
- Re: Separate WCAG doc for non-SC guidelines
- Re: Separate WCAG doc for non-SC guidelines
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- RE: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
Thursday, 6 April 2017
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Fwd: Fwd: EME and Accessibility
- RE: EME impact on accessibility
- Fwd: EME and Accessibility
- RE: Adapting Text SC: Addressing the main issues
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Separating out SC 2.5.3 and 2.5.4 (issue #196) / draft definition of pointer gesture (issue #264)
- Minutes for Thursday, April 6, 2017 Supplemental AG Mtg
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Is there a call today
- Re: WebEx info for Thursday AG call, 11:30 am Boston time
- Re: Is there a call today
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- RE: Check List
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Is there a call today
- Is there a call today
- Re: Adapting Text SC: Addressing the main issues
- Re: Check List
- RE: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Check List
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Call for Exclusions: Accessibility Conformance Testing (ACT) Rules Format 1.0
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: Adapting Text SC: Addressing the main issues
Wednesday, 5 April 2017
- Re: Special fonts don't matter for font-family change.
- Low Vision and COGA should Drop Support for WCAG 2.1 if the AG WG is not willing make real change.
- Re: EME impact on accessibility
- Adapting Text SC: Addressing the main issues
- Re: Check List
- Check List
- Special fonts don't matter for font-family change.
- Re: EME impact on accessibility
- Re: EME impact on accessibility
- Re: EME impact on accessibility
- RE: EME impact on accessibility
- EME impact on accessibility
- Re: SC Managers and public comments
- TPAC 2017 Survey
- Re: Comments on the discussion about target size and accidental activation (was Re: Minutes: AGWG meeting April 4, 2017)
- SC Managers and public comments
Tuesday, 4 April 2017
- Re: Comments on the discussion about target size and accidental activation (was Re: Minutes: AGWG meeting April 4, 2017)
- RE: Comments on the discussion about target size and accidental activation (was Re: Minutes: AGWG meeting April 4, 2017)
- Re: Are these SC now testable?
- RE: Comments on the discussion about target size and accidental activation (was Re: Minutes: AGWG meeting April 4, 2017)
- Re: Comments on the discussion about target size and accidental activation (was Re: Minutes: AGWG meeting April 4, 2017)
- Re: Comments on the discussion about target size and accidental activation (was Re: Minutes: AGWG meeting April 4, 2017)
- Re: Comments on the discussion about target size and accidental activation (was Re: Minutes: AGWG meeting April 4, 2017)
- Re: Comments on the discussion about target size and accidental activation (was Re: Minutes: AGWG meeting April 4, 2017)
- Are these SC now testable?
- Comments on the discussion about target size and accidental activation (was Re: Minutes: AGWG meeting April 4, 2017)
- Minutes: AGWG meeting April 4, 2017
- ISSUE-48: How to tighten conformance model for adapting text sc
- ISSUE-47: Defining single-pointer activation
- Re: AGWG meeting April 5, 2017
- Re: AGWG meeting April 4, 2017
- FW: AGWG meeting April 5, 2017
- Re: AGWG meeting April 4, 2017
- Re: AGWG meeting April 4, 2017
- RE: AGWG meeting April 5, 2017
- Re: AGWG meeting April 4, 2017
- Re: AGWG meeting April 4, 2017
- Re: AGWG meeting April 4, 2017
- Re: AGWG meeting April 4, 2017
Monday, 3 April 2017
- Re: Color Test: A formal proposal
- Re: Color Test: A formal proposal
- [Minutes] WCAG Accessibility Conformance Testing (ACT) Task Force - Meeting on 3 April 2017
- Re: AGWG meeting April 4, 2017
- RE: AGWG meeting April 4, 2017
- RE: AGWG meeting April 4, 2017
- Re: Color Test: A formal proposal
- Re: Color Test: A formal proposal
- Re: Color Test: A formal proposal
- Re: CFC: Standing consent to publish working drafts on monthly schedule
Sunday, 2 April 2017
- Re: CFC: Publication of FPWD for Accessibility Conformance Testing Rules Format 1.0
- Re: CFC: Changes to Editor's draft require CFCs
- Re: Color Test: A formal proposal