tr-pages
tr-pages copied to clipboard
w3c
Work on the w3.org/TR index page (not specs themselves)
[Editor's draft](https://www.w3.org/standards/types#ED) states: >An Editor's draft is a document produced by a W3C Group. To be clear, should "W3C Group" link to https://www.w3.org/2021/Process-20211102/#w3c-group or something else? If so, are Community...
See https://htmlpreview.github.io/?https://raw.githubusercontent.com/w3c/tr-pages/89a42c3115a49de10331f27e1d6b81a23afc9bb0/documents-respec.html for a preview Fixes https://github.com/w3c/tr-pages/issues/94
Following a discussion with @dontcallmedom, the term 'Browser API' will probably be less ambiguous than 'Web API'
"Tag Findings" are missing from: https://www.w3.org/standards/types
This is tracking issue for the project ClearSpec 2021. The description of the project is at https://pad.w3.org/p/clearspec2021 (note that this will move into a .md next week to make the...
suggested by @swickr The drop down for status should say "ALL, except Retired", which is currently the default. ANd also add an option to see "All".
There is also now an auto-focus into the "title" field of the search bar of the TR page. This means keyboard-based page scroll does not work, and is an accessibility...
The filter/disclosure widgets on the [mockup1](https://w3c.github.io/tr-pages/mockup1/) page are not keyboard or screen reader accessible because they're created with `````` and `````` elements. ``` versions ... ``` The widget needs to...
The search field on [mockup1](https://w3c.github.io/tr-pages/mockup1/) does not have an associated label (needed to indicate to screen reader users what the field is for). ``` ``` On the assumption that the...
The [mockup1](https://w3c.github.io/tr-pages/mockup1/) page has a hidden `````` element ("Site navigation"). A better (and more up to date) solution is to use the `````` element and an `aria-label` attribute to provide...