w3c
Repos
967

CSS Working Group Editor Drafts

3651
479

Web Content Accessibility Guidelines

739
144

Web Authentication: An API for accessing Public Key Credentials

839
117

team-strat, on GitHub, working in public. Current state: DRAFT

126
36

Checker used at W3C to validate the compliance of Technical Reports with publication rules

48
30

W3C Transitions

50
15

Events

issue comment
Charter next

👷 Deploy Preview for w3c-das-charter processing.

| Name | Link | |---------------------------------|------------------------| |🔨 Latest commit | 075976dc2232b14dfe01ef2ac3c2f1bc348e2acb | |🔍 Latest deploy log | https://app.netlify.com/sites/w3c-das-charter/deploys/633552c686be2a0008502739 |

Created at 5 minutes ago

Trigger Netlify

Created at 5 minutes ago

Update from Github

Created at 6 minutes ago

Update from Github

Created at 6 minutes ago

Update from Github

Created at 7 minutes ago

Update from Github

Created at 8 minutes ago

Update from Github

Created at 8 minutes ago

Update from Github

Created at 9 minutes ago

Update from Github

Created at 9 minutes ago

Update from Github

Created at 10 minutes ago

Update from Github

Created at 10 minutes ago

Update from Github

Created at 10 minutes ago

Update from Github

Created at 11 minutes ago

Update from Github

Created at 11 minutes ago

Update from Github

Created at 11 minutes ago
issue comment
does a control that exposes an incorrect/inappropriate role fail 4.1.2 or not

Yes, I meant recommendations. The APG is not normative, correct? All its guidance on keyboard operation and patterns constitute recommendations, not requirements, I believe.

sure. but we're here in the WCAG repo, so assumed you meant "as part of WCAG".

in your original response you mentioned "Leaving that point aside, your response suggests your own answer to the starting question for this issue is 'no, a control that exposes an incorrect/inappropriate role does not fail 4.1.2.'". just to clarify, no that's not my stance. my stance is specifically about the idea that a link, that acts as a link, but is styled as a call to action that some people may say is button-like, causes some failure (if not 4.1.2, then 1.3.1 Info and Relationships or similar). that is the dangerous path I'd like to avoid. if the outcome just of this aspect is "we can write something that says 'try not to make your links look too much like buttons' in some kind of handwavy way, sure...though i'd doubt how much people would actually care for that nugget of info

Created at 11 minutes ago

Update from Github

Created at 12 minutes ago

Update from Github

Created at 12 minutes ago

Update from Github

Created at 12 minutes ago

Update from Github

Created at 12 minutes ago
create branch
xfq create branch main
Created at 12 minutes ago

Update from Github

Created at 12 minutes ago

Update from Github

Created at 13 minutes ago
create repository
xfq create repository
Created at 14 minutes ago

Update from Github

Created at 14 minutes ago

Update from spreadsheets

Created at 15 minutes ago

Update from TR

Created at 15 minutes ago
issue comment
Charter next

And while we’re here, can we rename the repo to das-charter without breaking links?

I'll look into it.

Created at 17 minutes ago
issue comment
Charter next

@xfq thanks, does Netlify provide diff similar to pr-preview? Netlify docs did not mention.

No. We can use PR Preview to provide a diff. Although it can also provide previews, it has been unstable recently and only supports previews of a single document in a repo.

Created at 17 minutes ago
pull request opened
audio: add rtp sequence number on incoming frames

where it is easily available.

This is useful in cases where one decodes audio using other means and just wants to grab the encoded frame (similar to what @alvestrand describes here as "alternative consumers")

Created at 17 minutes ago