Specification Review Task Force
Reviews of accessibility considerations in W3C specifications.
Note: this is a public wiki instance, but the PFWG must often do specification reviews in Member space. Be careful about what content is posted here.
HTML 5 is a W3C specification requiring sustained attention from the PFWG. Therefore, work on HTML 5 is performed by the HTML Task Force, not this specification review task force.
- Spec review matrix - groups, specs we care about, people with relevant expertise
- Monitor Community Groups for relevance to accessibility
- Come up with ways to identify specs that need review
- Organizer reviewers by knowledge area
- Track comments we send on specs and their disposition; in particular, be able to verify that our comments were addressed before the spec undergoes the next transition
- Ensure that reviews are conducted and comments sent in a timely manner
- Collect general accessibility principles we're discovering or using in our reviews
- Create review principles, e.g.,
- Focus on First Public Working Drafts and Last Call Working Drafts
- PFWG should only send accessibility comments
- Create use case personae to guide questions that should be asked
- Support accessibility of W3C specifications
- Create a feature wishlist for various technologies, e.g., HTML, CSS, etc. that we can submit for consideration as requirements when windows open
- Proxys - have good reasons to exist but have accessibility implications that need investigation, as a general topic rather than in the context of specific things that have come up. Some specs that have triggered this:
- AT support for Unicode
- Web Technology Accessibility Guidelines
- Use Cases for Extended Descriptions