ARIA and Assistive Technologies Community Group - Calendar

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

This meeting seeks to advance the AT Driver protocol through discussion with folks who have experience with assistive technologies (e.g. screen readers), including end-users, authors, and implementers. We answer participants' questions, review open issues, report on new opportunities, and prioritize upcoming work.

We keep meeting minutes collaboratively and in real-time via IRC. (Participants volunteer to scribe at the beginning of each meeting; if you're interested in helping out, this guide may be useful.) Following each meeting, meeting minutes will be published online and posted to the public ARIA-AT mailing list.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

This meeting seeks to advance the AT Driver protocol through discussion with folks who have experience with assistive technologies (e.g. screen readers), including end-users, authors, and implementers. We answer participants' questions, review open issues, report on new opportunities, and prioritize upcoming work.

We keep meeting minutes collaboratively and in real-time via IRC. (Participants volunteer to scribe at the beginning of each meeting; if you're interested in helping out, this guide may be useful.) Following each meeting, meeting minutes will be published online and posted to the public ARIA-AT mailing list.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

This meeting seeks to advance the AT Driver protocol through discussion with folks who have experience with assistive technologies (e.g. screen readers), including end-users, authors, and implementers. We answer participants' questions, review open issues, report on new opportunities, and prioritize upcoming work.

We keep meeting minutes collaboratively and in real-time via IRC. (Participants volunteer to scribe at the beginning of each meeting; if you're interested in helping out, this guide may be useful.) Following each meeting, meeting minutes will be published online and posted to the public ARIA-AT mailing list.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

This meeting seeks to advance the AT Driver protocol through discussion with folks who have experience with assistive technologies (e.g. screen readers), including end-users, authors, and implementers. We answer participants' questions, review open issues, report on new opportunities, and prioritize upcoming work.

We keep meeting minutes collaboratively and in real-time via IRC. (Participants volunteer to scribe at the beginning of each meeting; if you're interested in helping out, this guide may be useful.) Following each meeting, meeting minutes will be published online and posted to the public ARIA-AT mailing list.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

This meeting seeks to advance the AT Driver protocol through discussion with folks who have experience with assistive technologies (e.g. screen readers), including end-users, authors, and implementers. We answer participants' questions, review open issues, report on new opportunities, and prioritize upcoming work.

We keep meeting minutes collaboratively and in real-time via IRC. (Participants volunteer to scribe at the beginning of each meeting; if you're interested in helping out, this guide may be useful.) Following each meeting, meeting minutes will be published online and posted to the public ARIA-AT mailing list.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

This meeting seeks to advance the AT Driver protocol through discussion with folks who have experience with assistive technologies (e.g. screen readers), including end-users, authors, and implementers. We answer participants' questions, review open issues, report on new opportunities, and prioritize upcoming work.

We keep meeting minutes collaboratively and in real-time via IRC. (Participants volunteer to scribe at the beginning of each meeting; if you're interested in helping out, this guide may be useful.) Following each meeting, meeting minutes will be published online and posted to the public ARIA-AT mailing list.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

This meeting seeks to advance the AT Driver protocol through discussion with folks who have experience with assistive technologies (e.g. screen readers), including end-users, authors, and implementers. We answer participants' questions, review open issues, report on new opportunities, and prioritize upcoming work.

We keep meeting minutes collaboratively and in real-time via IRC. (Participants volunteer to scribe at the beginning of each meeting; if you're interested in helping out, this guide may be useful.) Following each meeting, meeting minutes will be published online and posted to the public ARIA-AT mailing list.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

This meeting seeks to advance the AT Driver protocol through discussion with folks who have experience with assistive technologies (e.g. screen readers), including end-users, authors, and implementers. We answer participants' questions, review open issues, report on new opportunities, and prioritize upcoming work.

We keep meeting minutes collaboratively and in real-time via IRC. (Participants volunteer to scribe at the beginning of each meeting; if you're interested in helping out, this guide may be useful.) Following each meeting, meeting minutes will be published online and posted to the public ARIA-AT mailing list.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

This meeting seeks to advance the AT Driver protocol through discussion with folks who have experience with assistive technologies (e.g. screen readers), including end-users, authors, and implementers. We answer participants' questions, review open issues, report on new opportunities, and prioritize upcoming work.

We keep meeting minutes collaboratively and in real-time via IRC. (Participants volunteer to scribe at the beginning of each meeting; if you're interested in helping out, this guide may be useful.) Following each meeting, meeting minutes will be published online and posted to the public ARIA-AT mailing list.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

This meeting seeks to advance the AT Driver protocol through discussion with folks who have experience with assistive technologies (e.g. screen readers), including end-users, authors, and implementers. We answer participants' questions, review open issues, report on new opportunities, and prioritize upcoming work.

We keep meeting minutes collaboratively and in real-time via IRC. (Participants volunteer to scribe at the beginning of each meeting; if you're interested in helping out, this guide may be useful.) Following each meeting, meeting minutes will be published online and posted to the public ARIA-AT mailing list.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

This meeting seeks to advance the AT Driver protocol through discussion with folks who have experience with assistive technologies (e.g. screen readers), including end-users, authors, and implementers. We answer participants' questions, review open issues, report on new opportunities, and prioritize upcoming work.

We keep meeting minutes collaboratively and in real-time via IRC. (Participants volunteer to scribe at the beginning of each meeting; if you're interested in helping out, this guide may be useful.) Following each meeting, meeting minutes will be published online and posted to the public ARIA-AT mailing list.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.

Biweekly meeting focused primarily on generating ARIA-AT reports via manual testing.