Prepare for Horizontal Review

[nigelmegitt]

This is a meta issue to track horizontal review steps for the specification.
See How to do wide review for details.

• Accessibility
  • Work through this questionnaire
  • request a review via GitHub from APA - raised as DAPT 2021-07-18 a11y-request#66
• Architecture
  • Ask the TAG for review; see how to work with the TAG
  • [-] If you are developing javascript APIs you may also want to ask public-script-coord@w3.org, a technical discussion list shared by W3C and ECMA's TC 39
• Internationalisation
  • Read the Request a review page
  • work through the Short Checklist
  • request a review via GitHub - raised as DAPT 2023-09-13 i18n-request#217
• Privacy
  • Write a "Privacy Considerations" section for your document, taking into account the Self-Review Questionnaire: Security and Privacy, Mitigating Browser Fingerprinting in Web Specifications, and RFC6973
  • request a review via GitHub from the Privacy Interest Group - raised as DAPT 2023-07-31 w3cping/privacy-request#122
• Security
  • Write a "Security Considerations" section for your document, taking into account the Self-Review Questionnaire: Security and Privacy
  • request a review via GitHub - raised as DAPT 2023-07-31 security-request#59

See also w3c/ttwg#259 for requesting wide review (related)

[nigelmegitt]

Slightly off topic (wide review not horizontal review), but it's useful to record that I presented DAPT to:

• EBU Timed Text group teleconference on 2023-05-02
• W3C MEIG teleconference on 2023-06-06 https://www.w3.org/2023/06/06-me-minutes.html

[nigelmegitt]

Looking at the Accessibility questionnaire:

The sections that apply are:

• If technology defines document semantics
• If technology provides time-based visual media (see also the Media Accessibility Checklist)
• If technology provides audio
• If technology allows text content
• (?) If technology provides content fallback mechanisms, whether text or other formats
• If technology provides internationalization support
• If technology defines accessible alternative features
• If technology provides content directly for end-users

There are a lot of questions in there, and no easily reusable template for completing the questionnaire as far as I can tell.

[nigelmegitt]

We'll create wiki pages in this repo for the HR questionnaires

@cconcolato to draft architecture and internationalisation
@nigelmegitt to draft accessibility, privacy and security

[nigelmegitt]

Privacy review done, pull request #168 raised to add privacy and security section.

[nigelmegitt]

All HR reviews initiated, closing.