tr-pages
tr-pages copied to clipboard
w3c
Work on the w3.org/TR index page (not specs themselves)
[mockup1](https://w3c.github.io/tr-pages/mockup1/) does not use sectioning elements to represent major areas of content. Elements like ``````, ``````, ``````, and ``````, provide useful semantic information for screen readers (many of which also...
The tabindex attribute is used on [mockup1](https://w3c.github.io/tr-pages/mockup1/) to impose a tab order through the content. This is [not advisable](https://www.paciellogroup.com/blog/2014/08/using-the-tabindex-attribute/) because it makes things awkward for sighted keyboard users, and also...
On [mockup1](https://w3c.github.io/tr-pages/mockup1/) the logo is marked up as an ``: ```html W3C ``` The logo should not be a heading because it does not preface a section of content. It...
The text of tags in the TR mockup often has bad contrast, making the text hardly readable
I've seen that users who detect issues don't know where to direct feedback. Imitate the “standard” footer that we have been using in other projects (w3c/wbs-design#40). If the footer is...
_Shared with permission:_ I am an autistic person who has several websites and is trying to make these websites accessible for people with disabilities. The format of WCAG and the...
I would expect many people may want to look for specifications and document published by a specific group. (I know I would use that.). Would that be possible to add...
Feedback from @ianbjacobs: >While I like the blue box with the status, I find it uncomfortable that it moves around >An alternative approach that would be consistent with our own...
At the moment, the Semantic Web specifications (RDF & Co) are lumped under the tag "Data". This is fine when doing search, but many people coming to the site will...