Self-review for accessibility

[kalyanaj]

This is a self-review based on https://w3c.github.io/apa/fast/checklist.html for the W3C Baggage specification:

1. Does the technology allow visual rendering of content?
   No. The baggage standard does not provide this.

2. Does the technology provide author control over color?
   No. The baggage standard does not provide this.

3. Does the technology provide features to accept user input?
   No. The baggage standard does not provide this.

4. Does the technology provide user interaction features?
   No. The baggage standard does not provide this.

5. Does the technology define document semantics?
   No. The baggage standard does not provide this.

6. Does the technology provide time-based visual media?
   No. The baggage standard does not provide this.

7. Does the technology provide audio?
   No. The baggage standard does not provide this.

8. Does the technology provide time limits?
   No. The baggage standard does not provide this.

9. Does the technology provide text content?
   No. The baggage standard does not provide this.

10. Does the technology create objects that don't have an inherent text representation?
    No. The baggage standard does not do this.

11. Does the technology provide content fallback mechanisms, whether text or other formats?
    No. The baggage standard does not provide this.

12. Does the technology provide visual graphics?
    No. The baggage standard does not provide this.

13. Does the technology provide internationalization support?
    No. The baggage standard does not provide this.

14. Does the technology define accessible alternative features?
    No. The baggage standard does not define this.

15. Does the technology provide content directly for end-users?
    No. The baggage standard does not provide this.

16. Does the technology define an API?
    No. The baggage standard does not define an API.

17. Does the technology define a transmission protocol?
    No. The baggage standard does not define a transmission protocol - it defines a new HTTP header.

[kalyanaj]

Closing this per the discussion in w3c/a11y-request#22.